After investigating a little more I have the impression, that a) Alex's patch #4 is required and b) 'val' does not need to be initialised
Thus remains replacing each of the two instances of 0x10000000U with 0x80000000U, where it remains open whether the 'xor' operation (now on bit 31 rather than bit 27) in vfio_rtl8168_window_quirk_read() really creates the required result. I'd rather envision an 'or bit31' or an 'and ~bit31'. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1384892 Title: RTL8168 NIC VFIO not working anymore since QEMU 2.1 Status in QEMU: New Bug description: After upgrading QEMU from 2.0 to 2.1 (and libiscsi from 1.7.0 to 1.12 as a dependency) my two RTL8168 NICs stopped working. The NICs do not respond to any command and even the LEDs on the network connection turn off, a few seconds after the VM started. To get them back running I had to downgrade to 2.0 and restart the system. Unfortunately, I have no clue what to do or how to debug this problem since there are no specific errors logged. I tried two different VMs: Debian Wheezy and IPFire (see attachment for further details). The QEMU 2.1 changelog states "Support for RTL8168 NICs." so there were some major changes done, I guess. On the IPFire guest the kernel log shows many of these lines: r8169 0000:00:07.0 green1: rtl_eriar_cond == 1 (loop: 100, delay: 100) r8169 0000:00:07.0 green1: rtl_phy_reset_cond == 1 (loop: 100, delay: 1) On the Debian guest there is only: r8169 0000:00:07.0: firmware: agent loaded rtl_nic/rtl8168e-3.fw into memory r8169 0000:00:07.0: lan0: link down ADDRCONF(NETDEV_UP): lan0: link is not ready The commandline for IPFire can be seen in the attachment. It is the same for Debian. There are also the complete kernel logs for the working (2.0) and non-working (2.1) cases. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1384892/+subscriptions
