[vfio-users] gpu passthrough problems after upgrade qemu 2.5 -> 2.6
Jiri 'Ghormoon' Novak
ghormoon at gmail.com
Sat Jun 4 22:28:17 UTC 2016
Hi,
I'm still on pc-i440fx-2.1 for some reason (i.e. laziness to change
scripts), so that likely won't help.
my full qemu line in case it might help someone spotting the problem
(sorry for it being over-verbose, it was originally a libvirt host that
I copied out and modified when making the vga passthrough work):
LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 \
-name 10-debian \
-machine pc-i440fx-2.1,accel=kvm,usb=off \
-cpu
SandyBridge,+invtsc,+osxsave,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff
\
-m 4096 \
-realtime mlock=off \
-smp 2,sockets=1,cores=2,threads=1 \
-uuid 2c6bdea9-af93-401a-42b8-57515e851553 \
-nographic -no-user-config -nodefaults \
-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=discard \
-no-hpet -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 \
-boot menu=off,strict=on \
-device pci-bridge,chassis_nr=1,id=pci.1,bus=pci.0,addr=0x2 \
-device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.0,addr=0x3 \
-device pci-bridge,chassis_nr=3,id=pci.3,bus=pci.0,addr=0x4 \
-device pci-bridge,chassis_nr=4,id=pci.4,bus=pci.0,addr=0x5 \
-device pci-bridge,chassis_nr=5,id=pci.5,bus=pci.0,addr=0x6 \
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \
-drive
file=/dev/A-ssd/qemu/10-debian,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native
\
-device
virtio-blk-pci,scsi=off,bus=pci.2,addr=0x1,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
\
-netdev tap,id=netdev0,ifname=br0vmtap10,script=no,downscript=no \
-device
virtio-net-pci,netdev=netdev0,id=net0,mac=42:42:42:00:00:0a,bus=pci.2,addr=0x2
\
-netdev tap,id=netdev1,ifname=br1vmtap10,script=no,downscript=no \
-device
virtio-net-pci,netdev=netdev1,id=net1,mac=42:42:42:00:01:0a,bus=pci.2,addr=0x3
\
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-device vfio-pci,host=05:00.0,id=hostdev2,bus=pci.4,addr=0x1 \
-device vfio-pci,host=00:1a.0,id=hostdev3,bus=pci.2,addr=0x4 \
-device vfio-pci,host=00:1b.0,id=hostdev4,bus=pci.2,addr=0x5 \
-device vfio-pci,host=00:1d.0,id=hostdev5,bus=pci.2,addr=0x6 \
-device
vfio-pci,host=01:00.0,id=hostdev6,bus=pci.5,multifunction=on,addr=0x1,x-vga=on
\
-device vfio-pci,host=01:00.1,id=hostdev7,bus=pci.5,addr=0x1.0x1 \
-device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x7 \
-vga none \
-chardev stdio,id=seabios \
-device isa-debugcon,iobase=0x402,chardev=seabios \
-msg timestamp=on \
-device
virtio-input-host-pci,evdev=/dev/input/by-path/platform-i8042-serio-1-event-mouse
\
-object
input-linux,id=input0,evdev=/dev/input/by-path/platform-i8042-serio-0-event-kbd
\
2>/dev/null >/dev/null &
Gh.
Nick Sarnie wrote:
> Hi Jiri,
>
> I just wanted to add that a similar issue is effecting me. With qemu
> 2.6, I get a black screen after the seabios screen. Downgrading to
> 2.5.1 fixes it for me. I tried 2.6 with the pc-i440fx-2.5 machine
> type, but that didn't work either.
>
> If anyone has any ideas, let us know.
>
> Thanks
>
> On Fri, Jun 3, 2016 at 3:26 AM, Jiri 'Ghormoon' Novak
> <ghormoon at gmail.com <mailto:ghormoon at gmail.com>> wrote:
>
> Hello,
>
> yesterday I've upgraded to qemu 2.6 (I've just rebuilt debian sid
> package for jessie, previously I did the same with 2.5 and just added
> input-linux patches).
>
> I'm using vga passthrough on HP Elitebook 8560p laptop with Radeon HD
> 6470M, passing it in with x-vga=on (no ovmf, it doesn't have ovmf
> firmware)
>
> After the upgrade, when booting linux, it shows bios screen, then
> alternates black and garbage screen for few minutes, then reboots (?),
> bios screen again, black screen, linux (only after driver kicks in, no
> grub/boot screen, previously it worked). Rebooting from guest makes it
> go through this all again including the few minutes of garbage sreens.
> There's nothing in guest logs for that time, likely it doesn't
> even pass
> grub.
>
> For windows it actually boots on first attempt, but also no output
> until
> driver kicks in (previosly it shown boot screen or worked without ati
> drivers installed)
>
> in the dmesg, there's quite a lot of rdmsr errors (on 2.5 there few a
> few too, but they appeared once, not in multiple batches like now).
>
> I assume some graphic modes are now handled differently. Is it only a
> change in defaults that I can override or is it a bug?
>
> dmesg:
> [ 136.888758] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
> [ 136.992866] e1000e 0000:00:19.0: irq 46 for MSI/MSI-X
> [ 136.993181] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 140.329803] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
> Control: None
> [ 140.329858] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [ 148.661906] VFIO - User Level meta-driver version: 0.3
> [ 148.667113] ehci-pci 0000:00:1a.0: remove, state 1
> [ 148.667123] usb usb3: USB disconnect, device number 1
> [ 148.667126] usb 3-1: USB disconnect, device number 2
> [ 148.667128] usb 3-1.1: USB disconnect, device number 3
> [ 148.667327] usb 3-1.2: USB disconnect, device number 4
> [ 148.667931] cdc_ncm 3-1.2:1.6 usb0: unregister 'cdc_ncm'
> usb-0000:00:1a.0-1.2, CDC NCM
> [ 148.701340] ehci-pci 0000:00:1a.0: USB bus 3 deregistered
> [ 148.876484] ehci-pci 0000:00:1d.0: remove, state 1
> [ 148.876505] usb usb4: USB disconnect, device number 1
> [ 148.876512] usb 4-1: USB disconnect, device number 2
> [ 148.876517] usb 4-1.1: USB disconnect, device number 3
> [ 148.986636] usb 4-1.4: USB disconnect, device number 4
> [ 149.045785] usb 4-1.6: USB disconnect, device number 5
> [ 149.055202] ehci-pci 0000:00:1d.0: USB bus 4 deregistered
> [ 149.099334] xhci_hcd 0000:05:00.0: remove, state 4
> [ 149.099348] usb usb2: USB disconnect, device number 1
> [ 149.116629] xhci_hcd 0000:05:00.0: USB bus 2 deregistered
> [ 149.116699] xhci_hcd 0000:05:00.0: remove, state 4
> [ 149.116710] usb usb1: USB disconnect, device number 1
> [ 149.118085] xhci_hcd 0000:05:00.0: USB bus 1 deregistered
> [ 149.408028] IPv6: ADDRCONF(NETDEV_CHANGE): br0vmtap10: link
> becomes ready
> [ 149.408081] br0: port 1(br0vmtap10) entered forwarding state
> [ 149.408092] br0: port 1(br0vmtap10) entered forwarding state
> [ 149.408305] IPv6: ADDRCONF(NETDEV_CHANGE): br1vmtap10: link
> becomes ready
> [ 149.408333] br1: port 1(br1vmtap10) entered forwarding state
> [ 149.408343] br1: port 1(br1vmtap10) entered forwarding state
> [ 151.128482] vfio_cap_init: 0000:00:1a.0 hiding cap 0xa
> [ 151.232527] vfio_ecap_init: 0000:00:1b.0 hiding ecap 0x5 at 0x130
> [ 151.340394] vfio_cap_init: 0000:00:1d.0 hiding cap 0xa
> [ 156.620596] dmar: DRHD: handling fault status reg 3
> [ 156.620662] dmar: DMAR:[DMA Read] Request device [00:1d.0]
> fault addr
> ef000
> DMAR:[fault reason 06] PTE Read access is not set
> [ 157.585018] kvm: zapping shadow pages for mmio generation
> wraparound
> [ 164.431957] br0: port 1(br0vmtap10) entered forwarding state
> [ 164.431966] br1: port 1(br1vmtap10) entered forwarding state
> [ 243.766285] kvm [4369]: vcpu0 unhandled rdmsr: 0x606
> [ 243.766358] kvm [4369]: vcpu0 unhandled rdmsr: 0x34
> [ 244.095770] vfio-pci 0000:05:00.0: irq 47 for MSI/MSI-X
> [ 244.149600] vfio-pci 0000:05:00.0: irq 47 for MSI/MSI-X
> [ 244.149606] vfio-pci 0000:05:00.0: irq 48 for MSI/MSI-X
> [ 244.149828] vfio-pci 0000:05:00.0: irq 47 for MSI/MSI-X
> [ 244.149832] vfio-pci 0000:05:00.0: irq 48 for MSI/MSI-X
> [ 244.149835] vfio-pci 0000:05:00.0: irq 49 for MSI/MSI-X
> [ 245.276448] kvm [4369]: vcpu0 unhandled rdmsr: 0x611
> [ 245.276518] kvm [4369]: vcpu0 unhandled rdmsr: 0x639
> [ 245.276582] kvm [4369]: vcpu0 unhandled rdmsr: 0x641
> [ 245.276644] kvm [4369]: vcpu0 unhandled rdmsr: 0x619
> [ 245.438562] vfio-pci 0000:00:1b.0: irq 50 for MSI/MSI-X
> [ 245.499553] vfio-pci 0000:01:00.1: irq 51 for MSI/MSI-X
> [ 245.608806] vfio-pci 0000:01:00.0: irq 54 for MSI/MSI-X
> [ 577.967787] kvm [4369]: vcpu0 unhandled rdmsr: 0x606
> [ 577.967861] kvm [4369]: vcpu0 unhandled rdmsr: 0x34
> [ 578.306848] vfio-pci 0000:05:00.0: irq 47 for MSI/MSI-X
> [ 578.357705] vfio-pci 0000:05:00.0: irq 47 for MSI/MSI-X
> [ 578.357712] vfio-pci 0000:05:00.0: irq 48 for MSI/MSI-X
> [ 578.357855] vfio-pci 0000:05:00.0: irq 47 for MSI/MSI-X
> [ 578.357859] vfio-pci 0000:05:00.0: irq 48 for MSI/MSI-X
> [ 578.357863] vfio-pci 0000:05:00.0: irq 49 for MSI/MSI-X
> [ 579.069686] kvm [4369]: vcpu0 unhandled rdmsr: 0x611
> [ 579.069757] kvm [4369]: vcpu0 unhandled rdmsr: 0x639
> [ 579.069822] kvm [4369]: vcpu0 unhandled rdmsr: 0x641
> [ 579.069885] kvm [4369]: vcpu0 unhandled rdmsr: 0x619
> [ 579.197944] vfio-pci 0000:00:1b.0: irq 50 for MSI/MSI-X
> [ 579.251914] vfio-pci 0000:01:00.0: irq 51 for MSI/MSI-X
> [ 581.257044] vfio-pci 0000:01:00.1: irq 54 for MSI/MSI-X
>
> Thanks,
> Gh.
>
> _______________________________________________
> vfio-users mailing list
> vfio-users at redhat.com <mailto:vfio-users at redhat.com>
> https://www.redhat.com/mailman/listinfo/vfio-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20160605/d6789297/attachment.htm>
More information about the vfio-users
mailing list