What I ran in my Linksys WRT54G was DD-WRT, it provided all the normal functionality sans the occasional lockups the stock firmware did, and in addition you could attach to other networks, you could participate in a mesh network, you could increase the transmitter power from 7mw up to as much as 100mw (and this really helped in my environment).
@JoMiran @zShxck That is very nice. I love the way you can toggle between disk space usage and disk I/O usage. Here is a btop of the machine that friendica.eskimo.com is running on:
@Sheldan Yes I am referring to the game, back when I had tried on vmware it was still the main commercial one that I was playing, I have since moved to Insanity Flyff. One of those minor continuities in my life.
@ouch @WhiteOakBayou If you try to remove essential packages, it will not allow you without an extra flag, even as root.
@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.
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.
@sunzu2 @secret300 @Yingwu Unfortunately, some people, if not held accountable, abuse things and other people.
@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.
Yes it is possible and it works just fine.