[Xen-users] Qemu and vif-route

[Florian Heigl <florian.heigl@xxxxxxxxx>]

Hi,

I have a dedicated server at Hetzner, where I'm alloted some extra
subnet for my VMs.

To support that I have set the following in my xend-config.sxp.
(network-script 'network-route netdev=eth0')
(vif-script vif-route)

All VMs in the addnl subnet will then have pointopoint routes to the
dom0 which forwards traffic out to the "real world".

Now I tried to add a HVM domU for the first time.

xm create will die as below:

waxh0002:/etc/xen# xm create xen08
Using config file "./xen08".
Error: Domain 'xen08' does not exist.

I checked a qemu logfile and found the following error:
waxh0002:/var/log/xen# cat qemu-dm-xen08.log
domid: 12
-c config qemu network with xen bridge for
tap12.0 xenbr0
bridge xenbr0 does not exist!
/etc/xen/scripts/qemu-ifup: could not launch network script
Could not initialize device 'tap'

This woud indicate the qemu VM ends up using vif-bridge. I just can't see WHY!
A (working) PVM domU
xen04:vif = [ 'mac=00:16:3E:02:00:04, ip=188.40.xxx.xxx' ]
A (not working) HVM domU
xen08:vif = [ 'type=ioemu, mac=00:16:3E:02:00:08, ip=188.40.xxx.xxx' ]

As soon as I disable the vif stanza the HVM domU can be created.

I had never run into this so far as I normally have a real router
somewhere and can just stick to bridges :)
Also I just rarely run HVM domUs. Unfortunately noone bothers to
provide current FreeBSD Xen images, even now that it's becoming stable
again, so I need to go via a HVM domU to build a rootfs at first.

Any ideas?

Flo

-- 
the purpose of libvirt is to provide an abstraction layer hiding all
xen features added since 2006 until they were finally understood and
copied by the kvm devs.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users