Red Hat Bugzilla – Bug 452818
fully virtualized guests do not start when using routed xen configuration
Last modified: 2009-12-14 16:26:19 EST
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: -/-
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.