aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKeir Fraser <keir.fraser@citrix.com>2008-01-08 09:40:33 +0000
committerKeir Fraser <keir.fraser@citrix.com>2008-01-08 09:40:33 +0000
commit24895b5f9b8288d7320f13025711980eff492111 (patch)
tree6780c397b471427bb5678d4d9aaafdfc39bbf080
parent340aaaf4790fc7d36ee21914818ef05d3f127d4d (diff)
downloadxen-24895b5f9b8288d7320f13025711980eff492111.tar.gz
xen-24895b5f9b8288d7320f13025711980eff492111.tar.bz2
xen-24895b5f9b8288d7320f13025711980eff492111.zip
HVM vif without bridge.
When using xen without a bridge but NAT or routing, HVM domains can't boot, and qemu-dm-n.log contains: config qemu network with xen bridge for tap0 xenbr0 bridge xenbr0 does not exist! That's because the qemu-ifup script always tries to add the vif to a default-named xenbr0 bridge. On the contrary, PV domains just work fine with the same configuration file except HVM parameters. Signed-off-by: Samuel Thibault <samuel.thibault@citrix.com>
-rw-r--r--tools/ioemu/target-i386-dm/qemu-ifup2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/ioemu/target-i386-dm/qemu-ifup b/tools/ioemu/target-i386-dm/qemu-ifup
index bdc5aecc0e..bcbee92d65 100644
--- a/tools/ioemu/target-i386-dm/qemu-ifup
+++ b/tools/ioemu/target-i386-dm/qemu-ifup
@@ -34,4 +34,4 @@ then
fi
ifconfig $1 0.0.0.0 up
-brctl addif $bridge $1
+brctl addif $bridge $1 || true