virt December 2013

virt@lists.fedoraproject.org

12 participants
11 discussions

"You Are Here" on Snapshots
by Jorge Fábregas 01 Feb '14

01 Feb '14

Hello again, Another question with internal snapshots. I can see the snapshot tree with: virsh snapshot-list Win7vm --tree However, I would like to know from what previous snapshot I'm currently running off. Something like the "You are here" that VMware shows. Is there a way to find that out? Thanks, Jorge

3 7

Proper way to migrate (F19 to F20)
by Jorge Fábregas 06 Jan '14

06 Jan '14

Hello everyone, I have a F19 that I'm wiping out in order to perform a clean intall of F20. Is it ok to simply tar /etc/libvirt and /var/lib/libvirt/ and untar them on the new installation? Or is it better to grab the VM definition files & their disks and import them with vish on the new setup? The first option seems very straightforward but don't know if there are new config files or changes in syntax that I may be overriding by extracting the previous version. Thanks, Jorge

2 2

USB devices get reset a few seconds after attaching them to guest and then get binded to host
by Stewart Adam 03 Jan '14

03 Jan '14

Hi, I have been attempting to attach a USB keyboard & mouse from the host to a Windows 7 guest using QEMU's USB2 controller. The keyboard seems to attach correctly, however I have trouble with certain mice and devices. When starting the guest, the devices remain attached for a second or two, then they disconnect. the libvirt logs show that it no longer sees the USB device, and I see this in dmesg: [ 10.876071] usb 3-13: reset full-speed USB device number 2 using xhci_hcd [ 10.888206] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88041917f740 [ 10.888209] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88041917f800 [ 10.888210] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88041917f7c0 [ 11.041209] usb 3-14: reset full-speed USB device number 3 using xhci_hcd [ 11.054379] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c8d559c0 [ 11.054383] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c8d55440 <repeats for some time> [ 87.476806] usb 3-14: new full-speed USB device number 4 using xhci_hcd [ 87.491908] usb 3-14: New USB device found, idVendor=046d, idProduct=c066 [ 87.491911] usb 3-14: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 87.491912] usb 3-14: Product: G9x Laser Mouse [ 87.491914] usb 3-14: Manufacturer: Logitech [ 87.491914] usb 3-14: SerialNumber: 081BB92CA70018 [ 87.494697] input: Logitech G9x Laser Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14:1.0/input/input16 [ 87.494994] hid-generic 0003:046D:C066.0008: input,hidraw0: USB HID v1.11 Mouse [Logitech G9x Laser Mouse] on usb-0000:00:14.0-14/input0 [ 87.498834] input: Logitech G9x Laser Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14:1.1/input/input17 [ 87.499078] hid-generic 0003:046D:C066.0009: input,hiddev0,hidraw1: USB HID v1.11 Keyboard [Logitech G9x Laser Mouse] on usb-0000:00:14.0-14/input1 As you can see the device re-attaches to the host. The device is plugged into a USB2 port, but it appears to be controlled by Intel's XHCI controller: 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 04) I'm running 3.12.5-303.fc20.x86_64, which is Fedora 20's kernel-3.12.5-302.fc20.x86_64 with the i915 VGA arbitration patches applied. Should I report a bug against the kernel? Regards, Stewart

3 5

Issues with VGA passthrough using KVM and VFIO
by Stewart Adam 20 Dec '13

20 Dec '13

Hi, I am trying to get VGA passthrough working using KVM and VFIO like described on this [1] thread and ran into some issues I was hoping someone could shed some light on. I have tried various configurations, but can't seem to get it working correctly. Either I get "Code 10" device error in Windows, or I get a BSOD 0x00000116 (VIDEO_TDR_ ERROR: attempt to reset the display driver and recover from a timeout failed) when booting the machine after installing the Catalyst 3D drivers. Other users on the Arch Linux forum have also reported similar issues. I have included my hardware, software, and QEMU command-line flags at the end of this message for reference. I tried using virt-manager to create the VM and modified the libvirt configuration per the Fedora test case [2] as well as various Q35 machine configurations by launching QEMU directly and all resulted in a "Code 10" on the GPU device except for when disabling emulated graphics entirely and passing x-vga=on. This results in a monitor signal on the card and it seems to work very well enough - with kernel 3.12.5 I could even restart the VM several times and it all works well *until* I install the Catalyst drivers. Then I get the BSOD 0x116 right after the Windows splash-screen. Safe mode and system repair still work correctly. There are no errors on the console or in dmesg, and I can provide that output in a pastebin if required. Is this indicative of a hardware problem, or a bug in the Catalyst drivers? Is there anything I can do to help debug this? I'm happy to provide any information necessary. Here's some background information about my software configuration: * Host: Fedora 20 with virt-preview repo o kernel-3.12.5-301.fc20.x86_64 (from updates-testing) o kernel-3.12.5-302.fc20.x86_64 (built with fedpkg from git, f20 branch w/ patches from comment #23 in [3] to fix pci_find_upstream_pcie_bridge bug) o qemu-kvm-1.7.0-1.fc20.x86_64 + also tried latest qemu-vfio from git o libvirt-daemon-1.2.0-1.fc20.x86_64 * Guest: Windows 7 SP1 x64 And now the hardware: * Xeon E3-1225 v3 (has VT-d, VT-x) * SuperMicro MBD-X10SAE-O * Sapphire Radeon R9 270X This is the QEMU command-line to boot the machine: /usr/bin/qemu-system-x86_64 -machine accel=kvm -name win7 -S -M q35 -m 2048 -cpu host \ -rtc base=localtime -realtime mlock=off \ -smp 4,sockets=1,cores=4,threads=1 \ -bios /usr/share/qemu/bios.bin -vga none \ -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \ -device vfio-pci,host=01:00.0,bus=root.1,addr=0x00,multifunction=on,x-vga=on,romfile=/home/sysadmin/vm/R9270X.rom \ -device vfio-pci,host=00:19.0,bus=pcie.0 \ -device ahci,bus=pcie.0,id=ahci \ -drive file=/home/VMs/win7-q35-ahci.img,id=disk0,format=qcow2 -device ide-hd,bus=ahci.0,drive=disk0 \ -boot menu=on I have omitted passing through the HDMI audio device, although including it and/or moving it to pcie.0 as suggested by some users in the Arch Linux thread didn't make any difference. Tried with and without romfile, also no difference. I did clean Windows installs with each attempt. PCIe 00:19:00 is a network controller. Thanks, Stewart [1] https://bbs.archlinux.org/viewtopic.php?pid=1361071 [2] https://fedoraproject.org/wiki/QA:Testcase_Virtualization_KVM_PCI_Device_As… [3] https://bugzilla.kernel.org/show_bug.cgi?id=44881

2 5

How to simulate unplug network cable from virt-manager
by Dario Lesca 10 Dec '13

10 Dec '13

>From command line, this trick is do from the command: $ sudo virsh domif-setlink f20 vnet0 down It's possible perform this function from a click on GUI virt-manager? Thanks -- Dario Lesca - sip:dario@solinos.it (Inviato dal mio Linux Fedora19+Gnome3.8)

2 1

Fedora reboots when using libvirt
by Marco André Dinis 09 Dec '13

09 Dec '13

Hi This is my system: Fedora 19 libvirtd (libvirt) 1.0.5.7 ( I downgraded to this kernel version trying to solve the problem, but no luck.) ------------- This is the error message: > [ 536.083922] Disabling lock debugging due to kernel taint > > [ 536.089320] mce: [Hardware Error]: CPU 3: Machine Check Exception: 4 >> Bank 5: be00000000800400 > > [ 536.097942] mce: [Hardware Error]: TSC 1343d498e08 ADDR 3fbbf66e4a78 >> MISC 1 > > [ 536.105139] mce: [Hardware Error]: PROCESSOR 0:20652 TIME 1386007650 >> SOCKET 0 APIC 5 microcode 9 > > [ 536.114021] mce: [Hardware Error]: Run the above through 'mcelog >> --ascii' > > [ 536.120889] mce: [Hardware Error]: CPU 1: Machine Check Exception: 4 >> Bank 5: be00000000800400 > > [ 536.129505] mce: [Hardware Error]: TSC 1343d4b4948 ADDR 3fbbf66e4a78 >> MISC 1 > > [ 536.136700] mce: [Hardware Error]: PROCESSOR 0:20652 TIME 1386007650 >> SOCKET 0 APIC 4 microcode 9 > > [ 536.145582] mce: [Hardware Error]: Run the above through 'mcelog >> --ascii' > > [ 536.152444] mce: [Hardware Error]: Machine check: Processor context >> corrupt > > [ 536.159483] Kernel panic - not syncing: Fatal Machine check > > [ 536.165127] drm_kms_helper: panic occurred, switching back to text >> console > > [ 536.174297] Rebooting in 30 seconds.. > > [ 566.288306] ACPI MEMORY or I/O RESET_REG. > > I was running a virtual machine using qemu-kvm. What i already tried: - memtest -> no error. - formatted and installed only the base system (no DE). - downgraded kernel: 3.9.5-301.fc19.x86 - swapped the disk with another server (no error with kernel 3.9.5 but i could only test during some hours, i dont have an extra machine anymore) Any suggestions? Thanks, and sorry my not-good english

3 4

still issues with virtio / macvtap and bridge (host lock-up)
by Reartes Guillermo 05 Dec '13

05 Dec '13

Hi, I recently tried with a guest (network: virtio: macvtap: bridge) and this caused the host to lock-up or panic as soon as the guest was powered on. I opened bug 1038343. Cheers.

3 2

F20 still missing something after 'yum groupinstall virtualization'
by Reartes Guillermo 04 Dec '13

04 Dec '13

When i try to launch Virt-Manager, a pop-up dialog says it want to install some packages... But i already installed the Virtualization group... The package it want to install are: qemu-system-x86 libvirt-daemon-kvm libvirt-daemon-kvm-config-network # yum groupinstall virtualization Loaded plugins: langpacks, refresh-packagekit No packages in any requested group available to install or update # yum install qemu-system-x86 libvirt-daemon-kvm libvirt-daemon-kvm-config-network Loaded plugins: langpacks, refresh-packagekit Package 2:qemu-system-x86-1.6.1-2.fc20.x86_64 already installed and latest version Package libvirt-daemon-kvm-1.1.3.1-2.fc20.x86_64 already installed and latest version No package libvirt-daemon-kvm-config-network available. If i follow the popup, it also fails to install: Error talking to PackageKit: GDBus.Error:org.freedesktop.PackageKit.Failed: The packages qemu-system-x86,libvirt-daemon-kvm,libvirt-daemon-config-network are already installed Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/packageutils.py", line 54, in check_packagekit packagekit_install(parent, packages) File "/usr/share/virt-manager/virtManager/packageutils.py", line 88, in packagekit_install timeout=timeout) File "/usr/lib64/python2.7/site-packages/gi/overrides/Gio.py", line 171, in __call__ None) GError: GDBus.Error:org.freedesktop.PackageKit.Failed: The packages qemu-system-x86,libvirt-daemon-kvm,libvirt-daemon-config-network are already installed I am launching Virt-Manager via a ssh -Y session for the first time after install. I know for past experience that Virt-Manager always request something. So it seems harmless as Virt-Manager does run after the dialog. If i close Virt-Manager and launch it again, the pop-up luckily does not appear. I am using the latest iso TC4 and it is fully updated. Cheers.

2 2

broken link on "Getting Started with Virtualization" page
by Robert P. J. Day 04 Dec '13

04 Dec '13

here: https://fedoraproject.org/wiki/Getting_started_with_virtualization the early link to "Installing a Fedora Virtual Machine" no longer works as that blog doesn't even seem to exist anymore. i'd fix it but i have no idea where it should now link. rday

2 1

Questions Fedora 20 Beta
by David Highley 04 Dec '13

04 Dec '13

First off I'm not very experienced setting up and running virtual guest systems. I install Fedora 20 Beta using virt-manager. It is hosted on a Fedora 19 system. 1) Reocurring issue with the pointer not being visible in the guest window. Some times cleared by stopping and restarting the guest system. Most of the time need to force stop. 2) During initial install I did not seem to beable to create a network bridge. I was able to add a network bridge after the install. 3) I shutdown the guest and when I went to bring it up it failed trying to create the network bridge again. I then looked at configuration and found two network bridge devices. I deleted one but it still failed. So I deleted the other one and then added a new network bridge which worked. Configuration specifics: - Network bridge is macvtap off the host network device. Device model rtl8139. Source mode is VEPA. Basically took defaults. - Display is spice with no setting changes.

2 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt December 2013