Comment 17 for bug 1268955
Revision history for this message
| Andrew Kinney (andykinney) wrote Re: OVS agent updates the wrong port when using Xen + Neutron with HVM or PVHVM | #17 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
An HVM domU without any PV drivers keeps the tap *and* vif interfaces.
XenServer provides both tap and vif interfaces to an HVM domU. If the HVM domU employs PV drivers, activating the PV drivers tells XenServer to rip out the tap interfaces and keep the vif interfaces. If no PV drivers are employed in the HVM domU, the tap interfaces are used by the domU and XenServer continues to supply the vif interfaces "just in case" the domU installs PV drivers later.
Unfortunately, in this situation, my workaround does not correct the problem. Sometimes the vif gets the tag and sometimes the tap gets the tag. For an HVM domU without PV drivers, the network interface inside the domU can only pass traffic if the tap interface gets the tag. It is extremely "lucky" when multiple interfaces of such a domU get tags on all the tap interfaces all at the same time.