On June 02, 2016 8:09 PM, Jan Beulich <jbeul...@suse.com> wrote: > Attached both a hypervisor and a qemu patch. Their plus > debug key M and i output is what I'd like to start with.
Applied these two patches, the attach files are logs. -vf PT is working for SLES 12. The logs: qemu-dm-sles.log -- qemu log, vf PT for sles 12. xen-sles.log -- xen log, vf PT for sles 12. -vf PT is not working for win2008: the logs: qemu-dm-win2k8.log -- qemu log, vf PT for win2008. xen-win2k8.log -- xen log, vf PT for win2008. btw, when I updated the NIC driver for win2008, actually, it is working. Xudong, could you help me verify it again? (( xen commit: bbfd2d6ccb31a3aeea49c8f9c7884792ddc26e3b NIC: Intel Corporation I350 Gigabit Network Connection new win2k8 NIC driver ,https://downloadcenter.intel.com/download/18720/Network-Adapter-Driver-for-Windows-Server-2008-Final-Release?product=59679 )) qemu-dm-TestDom.log -- qemu log, pf PT for win2008. ... taken together, IMO, from qemu-dm-win2k8.log(also I have read xen/QEMU code), the win2k8 vf nic driver is not loading. (any idea, feel free to let me know. I will help you try as much as I can..). Thoughts? Quan
qemu-dm-sles.log
Description: qemu-dm-sles.log
qemu-dm-TestDom.log
Description: qemu-dm-TestDom.log
qemu-dm-win2k8.log
Description: qemu-dm-win2k8.log
xen-sles.log
Description: xen-sles.log
xen-win2k8.log
Description: xen-win2k8.log
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel