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-devel] HVM networking in Xen 3.4-rc3

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] HVM networking in Xen 3.4-rc3
From: Gary Grebus <ggrebus@xxxxxxxxxxxxxxx>
Date: Tue, 28 Apr 2009 15:54:28 -0400
Delivery-date: Tue, 28 Apr 2009 12:54:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I'm trying to understand how networking is intended to work for HVM
domains in Xen 3.4-rc3.  My domain config file contains:

vif = [ 'type=ioemu, mac=00:16:3e:5b:f8:ed, bridge=eth2' ] 

and the bridge is correctly configured on eth2.  But the xm create
command gets hung waiting for something to happen with the vif, and
eventually fails with:

Error: Device 0 (vif) could not be connected. Hotplug scripts not

xend.log shows it's waiting for something to be written to xenstore:

[2009-04-28 15:33:37 5592] DEBUG (XendDomainInfo:1708) 
[2009-04-28 15:33:37 5592] DEBUG (DevController:139) Waiting for devices vif.
[2009-04-28 15:33:37 5592] DEBUG (DevController:144) Waiting for 0.
[2009-04-28 15:33:37 5592] DEBUG (DevController:629) hotplugStatusCallback 

which seems to be related to the udev hotplug rules.

But what happens with the vif is that qemu has
invoked /etc/xen/qemu-ifup, and that has added the tap device to the

# brctl show                                           
bridge name     bridge id               STP enabled     interfaces              
eth2            8000.000e0cb1a72d       no              peth2                   

Is qemu supposed to be involved in the hotplug mechanism, or is there
something else I'm missing?
If modify qemu-ifup to write a value for the xenstore key, then the
domain finishes booting and the network works.

Gary Grebus
Virtual Iron Software, Inc.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>