Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| gpu_accelerated_vm_with_kvm [21.11.2018 22:46] – [retry DCV] Pascal Suter | gpu_accelerated_vm_with_kvm [08.12.2018 08:21] – [GPU Forwarding for KVM] Pascal Suter | ||
|---|---|---|---|
| Line 162: | Line 162: | ||
| in order to get the middle mous button (wheel) to click, i had to modify the config of my citrix receiver on my client machine. I had to edit the file '' | in order to get the middle mous button (wheel) to click, i had to modify the config of my citrix receiver on my client machine. I had to edit the file '' | ||
| ===== GPU Forwarding for KVM ===== | ===== GPU Forwarding for KVM ===== | ||
| + | First of all you need to enable VT-d and VT-x or they might be also called something like Intel Virtualization tech, in the BIOS. without these guys you won't be able to load the vfio module later on. | ||
| + | |||
| Helpful links: | Helpful links: | ||
| * [[https:// | * [[https:// | ||
| Line 294: | Line 296: | ||
| RGS runs smooth and windows feels reasonably fast too with the SSD as storage behind it. however, When the vm is left running over night usually the next morning it hangs or is so slow that one often can't even shut it down properly. I don't know why that is, i've deactivated all power saving features of windows, screen blanking etc. but I still have this issue. The machine hangs the same when I connect vie windows RDP. Also in those cases where i can still see something, I usually get alot of horizontal lines as artefacts on the screen both with RGS and RDP. The only solution is then to shut down the VM and start it again, a Reboot (instead of a power cycle) will make the VM fast again but the Artefacts remain. so there is definately something wrong with my VM here. This needs further investigation! | RGS runs smooth and windows feels reasonably fast too with the SSD as storage behind it. however, When the vm is left running over night usually the next morning it hangs or is so slow that one often can't even shut it down properly. I don't know why that is, i've deactivated all power saving features of windows, screen blanking etc. but I still have this issue. The machine hangs the same when I connect vie windows RDP. Also in those cases where i can still see something, I usually get alot of horizontal lines as artefacts on the screen both with RGS and RDP. The only solution is then to shut down the VM and start it again, a Reboot (instead of a power cycle) will make the VM fast again but the Artefacts remain. so there is definately something wrong with my VM here. This needs further investigation! | ||
| + | |||
| + | ==== LVM stuff ==== | ||
| + | just as a quick side note: here is how you create and revert to a snapshot in lvm. using dd you can also copy a snapshot into a new lvm volume if the new volume is at least the size of the snapshotted one. | ||
| + | |||
| + | create a snapshot: | ||
| + | lvcreate -s -L 50G -n win10base / | ||
| + | revert to a snapshot: | ||
| + | lvconvert --merge / | ||
| + | |||
| + | ==== using a vm with just the forwarded GPU ==== | ||
| + | this is the ultimate goal. so far i could not get this to work, whenver i booted a vm without a emulated graphics card i could no longer connect to it. and it was hard to debug as i had no " | ||
| + | |||
| + | to start a vm without a emulated graphics card, use '' | ||
| + | |||