Bug 978443
| Summary: | virt-install without -w bridge=<name> using xen is unable to start | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Konrad Rzeszutek Wilk <ketuzsezr> |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | berrange, crobinso, extras-orphan, hbrock, jfehlig, jforbes, ketuzsezr, notting, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-31 14:38:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Konrad Rzeszutek Wilk
2013-06-26 15:59:33 UTC
Sorry about the extra parameters on the virt-install. The "Actual results" and "Expected Results" should have: "virt-install -l http://192.168.2.251/tftpboot/lab/tst031/f19-x86_64 --ram 1024 --disk /dev/vg_guests/guest2 --name F19-64" Aha! <dariof> darnok: 'cause I think I've seen something like that, having to do with the fact that it by defaults look for 'xenbr0' <dariof> darnok: "it" being the libxl driver (or so I think) .. <darnok> dariof, Right on the money: rror: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge online [1326] exited with error status 1 <darnok> libxl: error: libxl_device.c:979:device_hotplug_child_death_cb: script: Could not find bridge device xenbr0 And sure enough, if I setup 'xenbr0' bridge (instead of 'switch') it magically works! (In reply to Konrad Rzeszutek Wilk from comment #2) > <dariof> darnok: 'cause I think I've seen something like that, having to do > with the fact that it by defaults look for 'xenbr0' > <dariof> darnok: "it" being the libxl driver (or so I think) If the bridge name is not specified, libxl itself sets the default to xenbr0. From tools/libxl/libxl.c libxl__device_nic_setdefault(): if (!nic->bridge) { nic->bridge = strdup("xenbr0"); if (!nic->bridge) return ERROR_NOMEM; } Is there a default that libvirt uses? Meaning use the default one from libvirt instead of letting libxl set the default? (In reply to Konrad Rzeszutek Wilk from comment #4) > Is there a default that libvirt uses? No. And in fact I'm confused about how lack of a bridge name made it past libvirt. E.g. if I try to create or define a domain with a bridge type interface that does not contain a bridge name (<source bridge='br0'/> subelement), I get the following error error: internal error No <source> 'bridge' attribute specified with <interface type='bridge'/> What is the libvirt domXML created for F19-64? No response for 2 months, closing. |