Bug 452818 - fully virtualized guests do not start when using routed xen configuration
fully virtualized guests do not start when using routed xen configuration
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Xen Maintainance List
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2008-06-25 06:05 EDT by Martin Jürgens
Modified: 2009-12-14 16:26 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-11 09:50:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Jürgens 2008-06-25 06:05:16 EDT
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:

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 Berrange 2008-07-11 09:50:02 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.