To be sure, the base install of debian is a everything and the kitchen sink install. There are MANY package the average person is not going to need.
To be sure, the base install of debian is a everything and the kitchen sink install. There are MANY package the average person is not going to need.
Single GPU isn’t substantially harder than 2GPU pass through, that is what I have done, but it does require support by the UEFI bios and the GPU and not all support it.
@brian I have used it and with flyff at least the performance was far insuperior to kvm/qemu.
@brian Ok, just for kicks tell me where I can get this.
@brian To be honest, until and unless it becomes a problem for me, not really. KVM has the host CPU executing the VM instructions so timing on CPU instructions should product identical results. I have the VM setup as CPU and GPU pass through.
@Ptsf Haven’t played any of those. Anyway, there is a way to edit your xml to fake the machine id.
@PlasticPaperplane I’ve never been banned, but ok.
@daggermoon I just use a live boot usb,
mount /dev/sda1 (or whatever root is) /mnt
mount /dev/sda3 (or whatever EFI is) /mnt/boot/efi
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/pts
mount --rbind /sys /mnt/sys
mount --rbind /proc /mnt/proc
cp /etc/resolv.conf /mnt/resolv.conf
chroot /mnt
grub install /dev/sda (or whichever drive you want)
It seems like it would be pretty complex since I guess you need to disable the linux host from using the GPU, and do PCI passthrough in a VM that has Windows installed.@blobjim @shapis
This is all addressed by the Linux kernel and xml code specifying it for the VM.
And there’s still the problem of the graphics needing to move around the system in order to get to the display instead of the display being directly connected to the GPU.
Again handled by the kernel and qemu, just requires a bit of XML code in the vm description. Not a big deal.
@lord_ryvan Interesting, haven’t played that game so no experience with it. VirtualBox does do some things a bit differently, I was not able to get flyff to run it well, it runs but at about 3fps, where as it runs normally in kvm/qemu.
@thingsiplay I’m not ignoring, I am DISAGREEING, sorry if you’re having a difficult time making that distinction.
@halfapage Anti-cheats don’t generally care if they’re running in a vm as long as they can insert kernel drivers.
@thingsiplay Ok well I’ve been doing this for as long as Grub has been a thing (since retiring lilo) without an issue, so not sure why it is a problem for someone you know but I’m going to stick with probably operator error.
@thingsiplay Again, I’ve been doing this for many years without problems. If it’s interfering it’s most likely operator error.
@halfapage I’m saying from experience, nothing I could not get to run in a VM that ran in a physical machine.
@thingsiplay @metaStatic Normally I use grub on one drive to launch all of the OS’s from a boot menu.
@variants @shapis Not true, a root-kit will break it in wine because wine is just translating windows sys calls into Linux sys calls, but a vm is actually running a windows kernel, then the root kit anti-cheat works fine. With GPU pass through, I have found no games that work under Windows won’t also work within the VM.
@Magister @WhiteOakBayou There are a lot of things to like about MX, nice interface, I really like that you can boot up using either systemd or sys-V, since systemd tends to be a lot faster but also tends to break it makes it really nice to have a sys-v fallback when things do break. Support has been excellent, I’ve yet to have it take them more than three days to fix anything broken I’ve reported, contrast that with Ubuntu where if it happens within the next three major releases you’re doing good.