Bug 217509
Summary: | virt-install requires xenbr0 and does not use xenbr1 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Paolo Campegiani <campegiani> |
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-11-28 14:36:35 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Paolo Campegiani
2006-11-28 10:23:22 UTC
Bug 217495 is not related - that is merely describing a misleading error message thrown by libvirt which is now fixed. The root problem here is that the virt-install / virt-manager programs both assume a 'default' network configuration. In XenD terms 'default' means xenbr0, even if the network-bridge script deciding to create xenbr1 instead. The latest version of python-virtinst 0.97.0-1 has a workaround for this problem, which checks the default network route to decide whether to use xenbr0 or any other xenbrX device: $ rpm -q --changelog python-virtinst * Mon Nov 20 2006 Jeremy Katz <katzj> - 0.97.0-1 - handle multiple nics with virt-install (#215726) Can you confirm what version of python-virtinst is installed ? I am using python-virtinst-0.96.0-2.el5 Opps, I didn't mean 0.97.0 - the neccessary fix is actually in version 0.96.0-3.el5 * Thu Nov 16 2006 Daniel P. Berrange <berrange> - 0.96.0-3 - Autodetect primary bridge device when creating guests (bz 207210, 201626) Since you only have version 0.96.0-2.el5 I'm going to close this bug since it looks like the same core issue. The updated RPMs will be available in GA (and possibly even before). *** This bug has been marked as a duplicate of 201626 *** |