I’ve been using Virtual Box for some time and wanted to something different. It took me a few tries to figure out the creation steps but I have a working Win10 Home VM running! Yay! Virtual Machine Manager with QEMU/KVM on 15.2 Leap installed easily. But I have to run “systemctl start libvirtd” after every reboot/waking from suspend. Did libvirtd end up in the wrong location maybe? Host pc is an Asus X570, AMD 3700X, SVM and IOMMU both enabled in MB bios.
* libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Sun 2021-07-18 15:53:47 EDT; 1h 47min ago
Docs: man:libvirtd(8)
https://libvirt.org
Process: 23622 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=0/SUCCESS) Main PID: 23622 (code=exited, status=0/SUCCESS)
Tasks: 2 (limit: 32768)
CGroup: /system.slice/libvirtd.service
|-3794 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper
`-3795 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper
Jul 18 15:30:23 localhost.localdomain libvirtd[23622]: Unable to remove disk metadata on vm win10 from /vmdrive/win10kvm/win10.qcow2 (disk target sda)
Jul 18 15:30:23 localhost.localdomain libvirtd[23622]: this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata
Jul 18 15:30:23 localhost.localdomain libvirtd[23622]: Unable to remove disk metadata on vm win10 from /home/brian/Downloads/Win10_21H1_English_x64.iso (disk target sdb)
Jul 18 15:34:44 localhost.localdomain dnsmasq-dhcp[3794]: DHCPREQUEST(virbr0) 192.168.122.191 52:54:00:9c:d1:a7
Jul 18 15:34:44 localhost.localdomain dnsmasq-dhcp[3794]: DHCPACK(virbr0) 192.168.122.191 52:54:00:9c:d1:a7 DESKTOP-MA3KQNL Jul 18 15:48:55 localhost.localdomain libvirtd[23622]: internal error: End of file from qemu monitor Jul 18 15:48:56 localhost.localdomain libvirtd[23622]: this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata
Jul 18 15:48:56 localhost.localdomain libvirtd[23622]: Unable to remove disk metadata on vm win10 from /vmdrive/win10kvm/win10.qcow2 (disk target sda)
Jul 18 15:48:56 localhost.localdomain libvirtd[23622]: this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata
Jul 18 15:48:56 localhost.localdomain libvirtd[23622]: Unable to remove disk metadata on vm win10 from (disk target sdb)
* libvirtd.socket - Libvirt local socket
Loaded: loaded (/usr/lib/systemd/system/libvirtd.socket; disabled; vendor preset: disabled)
Active: active (listening) since Sun 2021-07-18 15:06:08 EDT; 2h 34min ago Listen: /run/libvirt/libvirt-sock (Stream)
Jul 18 15:06:08 localhost.localdomain systemd[1]: Listening on Libvirt local socket.
I also want to work out the GPU pass through steps eventually. Any advice?
Thanks for looking.
b
Hi
As root user enable the service to start at boot…
systemctl enable libvirtd
For qemu and hardware passthrough it’s a process… what is the motherboard in use? I had it all working fine with Nvidia GT710 and SATA on an Intel motherboard with additional hardware for the SATA.
My Linux-Fu is weak. LoL “systemctl enable libvirtd” did the trick. Thanks. Currently running a Tuff Gaming Asus x570-Plus MB with a Ryzen7 3700x with an MSI Nvidia 1660 Super GPU. I have two options to try GPU pass through, Nvidia GT640 and a GTX 1050 Ti. I’m hoping the 1050 can be configured for this project as it should be the better card. Should be no issues with power, PSU is a gold rated 750 watt Thremaltake. 16GB ram (2x8).
Opensuse 15.2 on a sata SSD but VM drive is a 1TB spinner. I’ll probably move the VM stuff to another identical SSD. Further hardware upgrades won’t be possible until after Setp. Like a Ryzen 9 5900x, M.2 SSD, more ram.
Can i configure an existing VM for pass through or is it better to start with a clean slate?
Hi
Should work fine, does the motherboard have dual ethernet devices? Did you follow some of the steps to configure up the groups etc? Do you have an extra monitor keyboard and mouse? Keyboard/Mouse is needed at times. On my system I use barrier for shared keyboard/mouse to the qemu system, however still have mouse/keyboard attached.
I found that heiko-sieger page several days ago while googling on my own. Very helpful. Motherboard has one wired Ethernet port but also has onboard WiFi and shares the antenna for Bluetooth. Both are available. I just use the wired port mainly.
My rig has dual 24 inch 1080p monitors already - adding another monitor for the guest VM is a wrinkle I hadn’t anticipated. Both monitors have 3 different input types available so I may have some flexibility there.
I haven’t configured the groups yet but followed along with the guides and did “sudo lspci” as well “sudo find /sys/kernel/iommu_groups/ -type l” to understand what I was reading. Looked at the output again now and see both the Ethernet and wireless controllers in the list and the four entries for the current GPU. I haven’t installed the second GPU yet. Curious why I might need another keyboard/mouse? Is this due to the VM being displayed on a different monitor rather than in the virt manager window on the host? I see Barrier is in the repos and looks easy to use.
The ultimate goal besides the learning experience is kind of a lame one - I want to play 3d accelerated windows games that do not work on Linux. But I appreciate your help.
Hi
Yes, the keyboard mouse is needed, especially to configure the BIOS to get booting right when installing the OS, after that it’s only really needed if boot issues, but still needs to be present, I have a small keyboard with trackpad on it (USB wired), but also have a logictech one that have also tried.
Yes you could use the an existing monitor and switch inputs, I have done that but so use to three screens, it’s weird with only two So have a spare monitor I connected up.
Just work through each part, to get the hardware all ready and running on vfio-pci then it’s a matter of crafting the qemu script. I would suggest either a USB->ethernet device or an onboard PCIx1 card to use.