[Qemu-devel] [Bug 1433081] Re: qcow2 causing kvm hardware error 0xffffffff with vfio-pci VGA passthrough
** Tags removed: gpu hardware kvm passthrough vfio-pci ** Attachment removed: "qcow2_dmesg_report.txt" https://bugs.launchpad.net/qemu/+bug/1433081/+attachment/4347843/+files/qcow2_dmesg_report.txt -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1433081 Title: kvm hardware error 0x with vfio-pci VGA passthrough Status in QEMU: New Bug description: Please delete this bug report - it's conclusions are incorrect. While the iso boots with raw but not qcow2, attempting to install using the iso causes the same hardware error. Changing smp and cores to 1 allows both qcow2 and raw to move forward with installs. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1433081/+subscriptions
[Qemu-devel] [Bug 1433081] Re: qcow2 causing kvm hardware error 0xffffffff with vfio-pci VGA passthrough
** Description changed:
- Hi,
-
- Using qcow2 format for an ide-hd device is causing "KVM: entry failed,
- hardware error 0x". When this error occurs, qemu-monitor shows
- the guest has stopped. The error did not occur immediately, but at the
- point that the boot, running from an attached Ubuntu 14.04.1 iso,
- switched to graphical mode after text-mode startup.
-
- The root-cause was verified by switching only the ide-hd disk to raw
- format (no OS installed), which allowed the guest to boot normally from
- the iso. The error and fix are reliably repeatable.
-
- The interesting part is that the ide-hd (with no OS installed) with
- qcow2 format was not actually being used for boot - the boot was from a
- Ubuntu iso, with the intention of installing an ubuntu guest on the
- attached ide-hd device. The guest was using a vfio-pci passthrough GPU
- connected to an external UHD monitor.
-
- The commands used to create the disk images:
- qemu-img create -f qcow2
/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img 20G
- qemu-img create -f raw
/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img 20G
-
- The script vm1 was used to launch the guests with "sudo ./vm1", with the
- only difference between launches being the ide-hd format (raw vs qcow2).
- With qcow2 this resulted in the terminal below. The corresponding dmesg
- snippets are attached. There were two dmesg entries each time the error
- occurred.
-
- The same problem occurred when using the latest packages from the
- ppa:jacob/virtualisation. However, when using jacob's packages, it was
- not verified that raw format resolves the error (I am running this on my
- primary system and purged jacob's ppa when this problem first occured).
-
- A fix would be helpful as the qcow2 format allows snapshots, while raw
- does not.
-
- --System
info---
- Linux v2min 3.18.9-031809-generic #201503080036 SMP Sun Mar 8 00:37:46 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
-
- /var/log/libvirt/libvirt.d is 0 bytes
-
- Libvirt versions are these:
-
- v2min@v2min:~/QCOW2-Error$ dpkg -l | grep libvirt
- ii libvirt-bin 1.2.2-0ubuntu13.1.9amd64
programs for the libvirt library
- rc libvirt-glib-1.0-0 0.1.6-1ubuntu2 amd64
libvirt glib mainloop integration
- ii libvirt01.2.2-0ubuntu13.1.9amd64
library for interfacing with different virtualization systems
- ii python-libvirt 1.2.2-0ubuntu2 amd64
libvirt Python bindings
-
-
- v2min@v2min:~/QCOW2-Error$ dpkg -l | grep qemu
- ii ipxe-qemu 1.0.0+git-2013.c3d1e78-2ubuntu1.1
all PXE boot firmware - ROM images for qemu
- ii qemu-keymaps2.0.0+dfsg-2ubuntu1.10
all QEMU keyboard maps
- ii qemu-kvm2.0.0+dfsg-2ubuntu1.10
amd64QEMU Full virtualization on x86 hardware
(transitional package)
- ii qemu-system-common 2.0.0+dfsg-2ubuntu1.10
amd64QEMU full system emulation binaries (common files)
- ii qemu-system-x86 2.0.0+dfsg-2ubuntu1.10
amd64QEMU full system emulation binaries (x86)
- ii qemu-utils 2.0.0+dfsg-2ubuntu1.10
amd64QEMU utilities
-
- Passthrough GPU: Zotac GT 730 2GB.
- Processor: AMD A10-5800K APU
- Primary GPU: Radeon R9-290X
-
-
- --vm1
script-
- #!/bin/bash
-
- configfile=/etc/vfio-pci1.cfg
-
- vfiobind() {
- dev="$1"
- vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
- device=$(cat /sys/bus/pci/devices/$dev/device)
- if [ -e /sys/bus/pci/devices/$dev/driver ]; then
- echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
- fi
- echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
-
- }
-
- modprobe vfio-pci
-
- cat $configfile | while read line;do
- echo $line | grep ^# >/dev/null 2>&1 && continue
- vfiobind $line
- done
-
- sudo qemu-system-x86_64 -enable-kvm -M q35 -m 4096 -cpu host \
- -smp 2,sockets=1,cores=2,threads=1 \
- -bios /usr/share/qemu/bios.bin -vga none \
- -usb -device usb-host,hostbus=5,hostaddr=8 \
- -device
ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \
- -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on \
- -device vfio-pci,host=04:00.1,bus=root.1,addr=00.1 \
- -drive
file=/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img,id=disk,format=qcow2
-device ide-hd,bus=ide.0
[Qemu-devel] [Bug 1433081] Re: kvm hardware error 0xffffffff with vfio-pci VGA passthrough
** Description changed:
- Please delete this bug report - it's conclusions are incorrect. While
- the iso boots with raw but not qcow2, attempting to install using the
- iso causes the same hardware error. Changing smp and cores to 1 allows
- both qcow2 and raw to move forward with installs.
+ Hi,
+
+ Using smp 2 and cores=2 causes "KVM: entry failed, hardware error
+ 0x". When this error occurs, qemu-monitor shows the guest has
+ stopped. The error did not occur immediately, but at the point that the
+ boot, running from an attached Ubuntu 14.04.1 iso, switched to graphical
+ mode after text-mode startup, or after starting the Ubuntu guest
+ install.
+
+ The root-cause was verified by changing smp to 1 and cores=1 which
+ results in the guest working ok. Tested upto installing Ubuntu 14.04.1
+ and updating without any proprietary drivers.
+
+ The boot was from an Ubuntu iso, with the intention of installing an
+ ubuntu guest on the attached ide-hd device. The guest was using a vfio-
+ pci passthrough GPU connected to an external UHD monitor.
+
+ The commands used to create the disk images:
+ qemu-img create -f qcow2
/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img 20G
+ qemu-img create -f raw
/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img 20G
+
+ The script vm1 was used to launch the guests with "sudo ./vm1", with the
+ only difference between launches being the smp and cores settings. With
+ smp 2 and cores=2 this resulted in the terminal below. The corresponding
+ dmesg snippets are attached. There were two dmesg entries each time the
+ error occurred.
+
+ The same problem occurred when using the latest packages from the
+ ppa:jacob/virtualisation. However, when using jacob's packages, it was
+ not verified that changing smp to 1 and cores=1 resolves the error (I am
+ running this on my primary system and purged jacob's ppa when this
+ problem first occured).
+
+
+ --System
info---
+ Linux v2min 3.18.9-031809-generic #201503080036 SMP Sun Mar 8 00:37:46 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
+
+ /var/log/libvirt/libvirt.d is 0 bytes
+
+ Libvirt versions are these:
+
+ v2min@v2min:~/QCOW2-Error$ dpkg -l | grep libvirt
+ ii libvirt-bin 1.2.2-0ubuntu13.1.9 amd64 programs for the libvirt library
+ rc libvirt-glib-1.0-0 0.1.6-1ubuntu2 amd64 libvirt glib mainloop integration
+ ii libvirt0 1.2.2-0ubuntu13.1.9 amd64 library for interfacing with different
virtualization systems
+ ii python-libvirt 1.2.2-0ubuntu2 amd64 libvirt Python bindings
+
+ v2min@v2min:~/QCOW2-Error$ dpkg -l | grep qemu
+ ii ipxe-qemu 1.0.0+git-2013.c3d1e78-2ubuntu1.1 all PXE boot firmware -
ROM images for qemu
+ ii qemu-keymaps 2.0.0+dfsg-2ubuntu1.10 all QEMU keyboard maps
+ ii qemu-kvm 2.0.0+dfsg-2ubuntu1.10 amd64 QEMU Full virtualization on x86
hardware (transitional package)
+ ii qemu-system-common 2.0.0+dfsg-2ubuntu1.10 amd64 QEMU full system emulation
binaries (common files)
+ ii qemu-system-x86 2.0.0+dfsg-2ubuntu1.10 amd64 QEMU full system emulation
binaries (x86)
+ ii qemu-utils 2.0.0+dfsg-2ubuntu1.10 amd64 QEMU utilities
+
+ Passthrough GPU: Zotac GT 730 2GB.
+ Processor: AMD A10-5800K APU
+ Primary GPU: Radeon R9-290X
+
+ --vm1
script-
+ #!/bin/bash
+
+ configfile=/etc/vfio-pci1.cfg
+
+ vfiobind() {
+ dev="$1"
+ vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
+ device=$(cat /sys/bus/pci/devices/$dev/device)
+ if [ -e /sys/bus/pci/devices/$dev/driver ]; then
+ echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
+ fi
+ echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
+
+ }
+
+ modprobe vfio-pci
+
+ cat $configfile | while read line;do
+ echo $line | grep ^# >/dev/null 2>&1 && continue
+ vfiobind $line
+ done
+
+ sudo qemu-system-x86_64 -enable-kvm -M q35 -m 4096 -cpu host \
+ -smp 2,sockets=1,cores=2,threads=1 \
+ -bios /usr/share/qemu/bios.bin -vga none \
+ -usb -device usb-host,hostbus=5,hostaddr=8 \
+ -device
ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \
+ -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on \
+ -device vfio-pci,host=04:00.1,bus=root.1,addr=00.1 \
+ -drive
file=/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img,id=disk,format=qcow2
-device ide-hd,bus=ide.0,drive=disk \
+ -drive
file=/media/v2min/Data/Shr/Software/OSes/ubuntu-14.04.1-desktop-amd64.iso,id=isocd
-device ide-cd,bus=ide.1,drive=isocd \
+ -boot menu=on \
+ -boot d
+
+ exit 0
+
+
----gnome-terminal-----
+ v2min@v2min:~$ sudo ./vm1
+ [sudo] password for v2min:
+ KVM: entry failed, hardware error 0x
[Qemu-devel] [Bug 1433081] Re: kvm hardware error 0xffffffff with vfio-pci VGA passthrough
Thank you for reviewing this. Removed VirtualBox and tried again, unfortunately same error. Terminal results and dmesg snippets below. ---terminal- v2min@v2min:~$ sudo ./vm1 KVM: entry failed, hardware error 0x RAX=0005 RBX= RCX= RDX=81eaf3e8 RSI= RDI= RBP=880179559930 RSP=880179559910 R8 =81eaf3e0 R9 = R10=0206 R11=000f R12=8801795feb1c R13=0028 R14= R15=8801795fe800 RIP=8104ed58 RFL=0046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 0080 CS =0010 00a09b00 DPL=0 CS64 [-RA] SS =0018 00c09300 DPL=0 DS [-WA] DS = 0080 FS = 7ff2108ed880 0080 GS = 88017fd0 0080 LDT= TR =0040 88017fd11900 2087 8b00 DPL=0 TSS64-busy GDT= 88017fd0a000 007f IDT= ff576000 0fff CR0=8005003b CR2=7ff2108f CR3=000174114000 CR4=000406e0 DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER=0d01 Code=00 01 48 c7 c0 6a b0 00 00 31 db 0f b7 0c 01 b8 05 00 00 00 <0f> 01 c1 0f 1f 44 00 00 5b 41 5c 41 5d 41 5e 5d c3 89 f0 31 c9 f0 0f b0 0d 9b 06 e6 00 40 -dmesg snippet [ 143.638160] vfio-pci :04:00.0: enabling device ( -> 0003) [ 143.641607] vfio-pci :04:00.1: enabling device ( -> 0002) [ 146.481082] usb 5-4.2: reset full-speed USB device number 8 using ehci-pci [ 146.749241] usb 5-4.2: reset full-speed USB device number 8 using ehci-pci [ 146.961035] usb 5-4.2: reset full-speed USB device number 8 using ehci-pci [ 147.161244] usb 5-4.2: reset full-speed USB device number 8 using ehci-pci [ 150.135296] kvm: zapping shadow pages for mmio generation wraparound [ 163.101237] kvm [4414]: vcpu0 unhandled rdmsr: 0xc0011005 [ 163.101246] kvm [4414]: vcpu0 unhandled rdmsr: 0xc0011021 [ 163.101252] kvm [4414]: vcpu0 unhandled rdmsr: 0xc0010112 [ 163.101266] kvm [4414]: vcpu0 unhandled rdmsr: 0xc408 [ 163.243382] kvm [4414]: vcpu0 unimplemented perfctr wrmsr: 0xc0010004 data 0x [ 163.261011] kvm [4414]: vcpu1 unhandled rdmsr: 0xc0011005 [ 163.261024] kvm [4414]: vcpu1 unhandled rdmsr: 0xc0011021 [ 163.261056] kvm [4414]: vcpu1 unhandled rdmsr: 0xc408 [ 163.979495] usb 5-4.2: reset full-speed USB device number 8 using ehci-pci [ 166.943830] usb 5-4.2: reset full-speed USB device number 8 using ehci-pci [ 167.687954] usb 5-4.2: reset full-speed USB device number 8 using ehci-pci [ 167.798019] [ cut here ] [ 167.798078] WARNING: CPU: 2 PID: 4417 at /home/kernel/COD/linux/arch/x86/kvm/emulate.c:4994 x86_emulate_insn+0xa74/0xc30 [kvm]() [ 167.798082] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter ip_tables x_tables bridge stp llc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nouveau aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd mxm_wmi wmi ttm drm_kms_helper drm serio_raw i2c_algo_bit k10temp joydev i2c_piix4 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm dm_multipath scsi_dh snd_seq_midi snd_seq_midi_event snd_rawmidi fglrx(POE) snd_seq snd_seq_device snd_timer snd amd_iommu_v2 soundcore shpchp 8250_fintek video mac_hid tpm_infineon parport_pc ppdev kvm_amd kvm vfio_pci rfcomm vfio_iommu_type1 vfio bnep it87 hwmon_vid bluetooth lp parport nls_iso8859_1 ses enclosure hid_generic btrfs hid_logitech ff_memless raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor uas usb_storage hid_logitech_dj usbhid hid raid6_pq raid1 raid0 psmouse multipath r8169 ahci linear libahci mii pci_stub [ 167.798211] CPU: 2 PID: 4417 Comm: qemu-system-x86 Tainted: P OE 3.18.9-031809-generic #201503080036 [ 167.798215] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A88X-D3H, BIOS F5 05/28/2014 [ 167.798219] 1382 880641e03b68 8179ba3d 0007 [ 167.798226] 880641e03ba8 81074bac 0004 [ 167.798232] 8805f23e9550 0006 c075f640 8805f23e9550 [ 167.798238] Call Trace: [ 167.798250] [] dump_stack+0x46/0x58 [ 167.798258] [] warn_slowpath_common+0x8c/0xc0 [ 167.798269] [] warn_slowpath_nu
[Qemu-devel] [Bug 1433081] Re: kvm hardware error 0xffffffff with vfio-pci VGA passthrough
** Attachment added: "KVM-HardwareError-dmesg_report.txt"
https://bugs.launchpad.net/qemu/+bug/1433081/+attachment/4349775/+files/KVM-HardwareError-dmesg_report.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1433081
Title:
kvm hardware error 0x with vfio-pci VGA passthrough
Status in QEMU:
New
Bug description:
Hi,
Using smp 2 and cores=2 causes "KVM: entry failed, hardware error
0x". When this error occurs, qemu-monitor shows the guest has
stopped. The error did not occur immediately, but at the point that
the boot, running from an attached Ubuntu 14.04.1 iso, switched to
graphical mode after text-mode startup, or after starting the Ubuntu
guest install.
The root-cause was verified by changing smp to 1 and cores=1 which
results in the guest working ok. Tested upto installing Ubuntu 14.04.1
and updating without any proprietary drivers.
The boot was from an Ubuntu iso, with the intention of installing an
ubuntu guest on the attached ide-hd device. The guest was using a
vfio-pci passthrough GPU connected to an external UHD monitor.
The commands used to create the disk images:
qemu-img create -f qcow2
/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img 20G
qemu-img create -f raw
/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img 20G
The script vm1 was used to launch the guests with "sudo ./vm1", with
the only difference between launches being the smp and cores settings.
With smp 2 and cores=2 this resulted in the terminal below. The
corresponding dmesg snippets are attached. There were two dmesg
entries each time the error occurred.
The same problem occurred when using the latest packages from the
ppa:jacob/virtualisation. However, when using jacob's packages, it was
not verified that changing smp to 1 and cores=1 resolves the error (I
am running this on my primary system and purged jacob's ppa when this
problem first occured).
--System
info---
Linux v2min 3.18.9-031809-generic #201503080036 SMP Sun Mar 8 00:37:46 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
/var/log/libvirt/libvirt.d is 0 bytes
Libvirt versions are these:
v2min@v2min:~/QCOW2-Error$ dpkg -l | grep libvirt
ii libvirt-bin 1.2.2-0ubuntu13.1.9 amd64 programs for the libvirt library
rc libvirt-glib-1.0-0 0.1.6-1ubuntu2 amd64 libvirt glib mainloop integration
ii libvirt0 1.2.2-0ubuntu13.1.9 amd64 library for interfacing with different
virtualization systems
ii python-libvirt 1.2.2-0ubuntu2 amd64 libvirt Python bindings
v2min@v2min:~/QCOW2-Error$ dpkg -l | grep qemu
ii ipxe-qemu 1.0.0+git-2013.c3d1e78-2ubuntu1.1 all PXE boot firmware -
ROM images for qemu
ii qemu-keymaps 2.0.0+dfsg-2ubuntu1.10 all QEMU keyboard maps
ii qemu-kvm 2.0.0+dfsg-2ubuntu1.10 amd64 QEMU Full virtualization on x86
hardware (transitional package)
ii qemu-system-common 2.0.0+dfsg-2ubuntu1.10 amd64 QEMU full system emulation
binaries (common files)
ii qemu-system-x86 2.0.0+dfsg-2ubuntu1.10 amd64 QEMU full system emulation
binaries (x86)
ii qemu-utils 2.0.0+dfsg-2ubuntu1.10 amd64 QEMU utilities
Passthrough GPU: Zotac GT 730 2GB.
Processor: AMD A10-5800K APU
Primary GPU: Radeon R9-290X
--vm1
script-
#!/bin/bash
configfile=/etc/vfio-pci1.cfg
vfiobind() {
dev="$1"
vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
device=$(cat /sys/bus/pci/devices/$dev/device)
if [ -e /sys/bus/pci/devices/$dev/driver ]; then
echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
fi
echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
}
modprobe vfio-pci
cat $configfile | while read line;do
echo $line | grep ^# >/dev/null 2>&1 && continue
vfiobind $line
done
sudo qemu-system-x86_64 -enable-kvm -M q35 -m 4096 -cpu host \
-smp 2,sockets=1,cores=2,threads=1 \
-bios /usr/share/qemu/bios.bin -vga none \
-usb -device usb-host,hostbus=5,hostaddr=8 \
-device
ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \
-device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on \
-device vfio-pci,host=04:00.1,bus=root.1,addr=00.1 \
-drive
file=/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img,id=disk,format=qcow2
-device ide-hd,bus=ide.0,drive=disk \
-drive
file=/media/v2min/Data/Shr/Software/OSes/ubuntu-14.04.1-desktop-amd64.iso,id=isocd
-device ide-cd,bus=ide.1,drive=isocd \
-boot menu=on \
-boot d
exit 0
----gnome-terminal-----
v2min@v2mi
[Qemu-devel] [Bug 1433081] [NEW] qcow2 causing kvm hardware error 0xffffffff with vfio-pci VGA passthrough
Public bug reported:
Hi,
Using qcow2 format for an ide-hd device is causing "KVM: entry failed,
hardware error 0x". When this error occurs, qemu-monitor shows
the guest has stopped. The error did not occur immediately, but at the
point that the boot, running from an attached Ubuntu 14.04.1 iso,
switched to graphical mode after text-mode startup.
The root-cause was verified by switching only the ide-hd disk to raw
format (no OS installed), which allowed the guest to boot normally from
the iso. The error and fix are reliably repeatable.
The interesting part is that the ide-hd (with no OS installed) with
qcow2 format was not actually being used for boot - the boot was from a
Ubuntu iso, with the intention of installing an ubuntu guest on the
attached ide-hd device. The guest was using a vfio-pci passthrough GPU
connected to an external UHD monitor.
The commands used to create the disk images:
qemu-img create -f qcow2
/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img 20G
qemu-img create -f raw
/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img 20G
The script vm1 was used to launch the guests with "sudo ./vm1", with the
only difference between launches being the ide-hd format (raw vs qcow2).
With qcow2 this resulted in the terminal below. The corresponding dmesg
snippets are attached. There were two dmesg entries each time the error
occurred.
The same problem occurred when using the latest packages from the
ppa:jacob/virtualisation. However, when using jacob's packages, it was
not verified that raw format resolves the error (I am running this on my
primary system and purged jacob's ppa when this problem first occured).
A fix would be helpful as the qcow2 format allows snapshots, while raw
does not.
--System
info---
Linux v2min 3.18.9-031809-generic #201503080036 SMP Sun Mar 8 00:37:46 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
/var/log/libvirt/libvirt.d is 0 bytes
Libvirt versions are these:
v2min@v2min:~/QCOW2-Error$ dpkg -l | grep libvirt
ii libvirt-bin 1.2.2-0ubuntu13.1.9amd64
programs for the libvirt library
rc libvirt-glib-1.0-0 0.1.6-1ubuntu2 amd64
libvirt glib mainloop integration
ii libvirt01.2.2-0ubuntu13.1.9amd64
library for interfacing with different virtualization systems
ii python-libvirt 1.2.2-0ubuntu2 amd64
libvirt Python bindings
v2min@v2min:~/QCOW2-Error$ dpkg -l | grep qemu
ii ipxe-qemu 1.0.0+git-2013.c3d1e78-2ubuntu1.1
all PXE boot firmware - ROM images for qemu
ii qemu-keymaps2.0.0+dfsg-2ubuntu1.10
all QEMU keyboard maps
ii qemu-kvm2.0.0+dfsg-2ubuntu1.10
amd64QEMU Full virtualization on x86 hardware (transitional
package)
ii qemu-system-common 2.0.0+dfsg-2ubuntu1.10
amd64QEMU full system emulation binaries (common files)
ii qemu-system-x86 2.0.0+dfsg-2ubuntu1.10
amd64QEMU full system emulation binaries (x86)
ii qemu-utils 2.0.0+dfsg-2ubuntu1.10
amd64QEMU utilities
Passthrough GPU: Zotac GT 730 2GB.
Processor: AMD A10-5800K APU
Primary GPU: Radeon R9-290X
--vm1
script-
#!/bin/bash
configfile=/etc/vfio-pci1.cfg
vfiobind() {
dev="$1"
vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
device=$(cat /sys/bus/pci/devices/$dev/device)
if [ -e /sys/bus/pci/devices/$dev/driver ]; then
echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
fi
echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
}
modprobe vfio-pci
cat $configfile | while read line;do
echo $line | grep ^# >/dev/null 2>&1 && continue
vfiobind $line
done
sudo qemu-system-x86_64 -enable-kvm -M q35 -m 4096 -cpu host \
-smp 2,sockets=1,cores=2,threads=1 \
-bios /usr/share/qemu/bios.bin -vga none \
-usb -device usb-host,hostbus=5,hostaddr=8 \
-device
ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \
-device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on \
-device vfio-pci,host=04:00.1,bus=root.1,addr=00.1 \
-drive
file=/media/v2min/Data/VMachines-KVM/KVM-NVidia/kvm-nvidia.img,id=disk,format=qcow2
-device ide-hd,bus=ide.0,drive=disk \
-drive
file=/media/v2min/Data/Shr/Software/OSes/ubuntu-14.04.1-desktop-amd64.iso,id=isocd
-device ide-cd,bus=ide.1,drive=isocd \
-boot menu=on \
-boot d
exit 0
--
