http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1742
Summary: Passthrough VF does not work after DomU reboot
Product: Xen
Version: unstable
Platform: x86-64
OS/Version: Linux-2.6
Status: NEW
Severity: normal
Priority: P2
Component: HVM
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: jason.kwon@ericsson.com
Running 4.1.0-rc4-pre on top of CentOS 5.5 base system, with PCI passthrough of
82599 VFs to Ubuntu 10.10 DomU. On the first boot of the DomU, when I select
the 2.6.35-22-server kernel (which is the kernel installed with the distro), VF
passthrough works, and I am able to configure the interfaces within the guest
and ping through the interfaces. I see a WARN message from msi.c in 'xm dmesg'
but VF functionality seems to be unaffected.
If I then shutdown the guest and boot it again, this time selecting another
kernel (e.g. 2.6.35-23-server), the VFs appear in the guest and can be
configured, but I cannot ping through them. 'xm dmesg' shows multiple
IOMMU-related page faults.
If I select the original DomU distro kernel (2.6.35-22-server) on any guest
boot, VF passthrough works and I can ping through the VFs--it is only when I
select a different kernel from 2.6.35-22-server that VF traffic fails.
If I boot 2.6.35-23-server in the DomU first, without first booting the
original distro kernel (2.6.35-22-server), I cannot ping through the VF, but
there are no IOMMU page fault message in 'xm dmesg.'
To recap: VF passthrough and network functionality always works with the
original guest distro kernel (2.6.35-22-server). Booting the guest with any
other kernel causes VF network functionality to fail, but we may or may not see
IOMMU errors in 'xm dmesg' as a result.
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
Summary: Passthrough VF does not work after DomU reboot
Product: Xen
Version: unstable
Platform: x86-64
OS/Version: Linux-2.6
Status: NEW
Severity: normal
Priority: P2
Component: HVM
AssignedTo: xen-bugs@lists.xensource.com
ReportedBy: jason.kwon@ericsson.com
Running 4.1.0-rc4-pre on top of CentOS 5.5 base system, with PCI passthrough of
82599 VFs to Ubuntu 10.10 DomU. On the first boot of the DomU, when I select
the 2.6.35-22-server kernel (which is the kernel installed with the distro), VF
passthrough works, and I am able to configure the interfaces within the guest
and ping through the interfaces. I see a WARN message from msi.c in 'xm dmesg'
but VF functionality seems to be unaffected.
If I then shutdown the guest and boot it again, this time selecting another
kernel (e.g. 2.6.35-23-server), the VFs appear in the guest and can be
configured, but I cannot ping through them. 'xm dmesg' shows multiple
IOMMU-related page faults.
If I select the original DomU distro kernel (2.6.35-22-server) on any guest
boot, VF passthrough works and I can ping through the VFs--it is only when I
select a different kernel from 2.6.35-22-server that VF traffic fails.
If I boot 2.6.35-23-server in the DomU first, without first booting the
original distro kernel (2.6.35-22-server), I cannot ping through the VF, but
there are no IOMMU page fault message in 'xm dmesg.'
To recap: VF passthrough and network functionality always works with the
original guest distro kernel (2.6.35-22-server). Booting the guest with any
other kernel causes VF network functionality to fail, but we may or may not see
IOMMU errors in 'xm dmesg' as a result.
--
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs