Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 452818

Summary: fully virtualized guests do not start when using routed xen configuration
Product: Red Hat Enterprise Linux 5 Reporter: Martin Jürgens <ma>
Component: xenAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 5.2   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-11 13:50:02 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 Martin Jürgens 2008-06-25 10:05:16 UTC 
Description of problem:
Because of internal infrastructure, I cannot use bridged XEN configuration but
have to use routed XEN configuration instead. I have modified the xen config
file to use it, and it works fine for paravirtualized guests.

The problem is the following: When I try to start fully virtualized guests
having ip=xx.xx.xx.xx and no bridge set, they do not start with the following
error message:

Watching /local/domain/4/logdirty/next-active
/etc/xen/qemu-ifup: could not launch network script
Could not initialize device 'tap'


How reproducible:
Always

Steps to Reproduce:
1. Switch to routed networking
2. Create fully virtualized guest
3. Start it
  
Actual results:
Does not start with error message above

Expected results:
Should start

Additional info:
-/-
Comment 1 Daniel Berrangé 2008-07-11 13:50:02 UTC 
The default network configuration script for HVM guests only supports bridged
networking configurations. 

If you want to use a non-bridged network, you will need to manually change the
/etc/xen/qemu-ifup script to handle your custom requirements.