Hello,
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.
I can see several solutions:
- The attached "patch" just ignores brctl failure. Far from elegant,
but
works fine
- The attached "patch2" drops the default xenbr0 bridge, and then
people
have to set bridge=xenbr0 in their configuration file.
- move qemu-ifup into three bridge, nat and route scripts, and add
another xend-config parameter, along network-script and vif-script,
which should point to either of those according to the values of
network-script and vif-script.
It looks to me like the first solution could be used as a workaround for
now and the last one would be preferable for the long run.
Samuel
Signed-off-by: Samuel Thibault <samuel.thibault@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
