This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Qemu and vif-route

To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Qemu and vif-route
From: Florian Heigl <florian.heigl@xxxxxxxxx>
Date: Tue, 8 Feb 2011 01:00:06 +0100
Delivery-date: Mon, 07 Feb 2011 16:01:39 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=a1UlxfyuaVqqa/LkngN7tToJgOV5dulJy024yirJzis=; b=RzRP3nLgGbl+S5gIOEOvC8s+H1gaCpsRPVFl46m9OGP8YF9Mwp5VFF5/qW1fxPBIHk TbE9Ch0KnSnIvtcPxWoeKqvzT/sfN9h3gXVYMAy3pdwz9zpSvLbgHevhoK9yO8vK8x+D 10rrQZPPKQjrSrppQqMmqd4QPAK+dbvjW+6os=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ofM0pi3on0oZd/jbNu/j29L1fofcxpyK6UVcvcFI/IZldlr+4YXSXu1PL3iP2S0+qW z5nYV024/KidUValxyqthp+wGj5gaSbqwR2GrtaJSK3CZGvyy+QGasvFW65TjVLB4S8T MRMzhvyHNSiiE4ZbdIeA5BROf8Q4jMjtHhXFw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

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?


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Qemu and vif-route, Florian Heigl <=