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


Re: [Xen-devel] HVM networking in Xen 3.4-rc3

To: Gary Grebus <ggrebus@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] HVM networking in Xen 3.4-rc3
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Wed, 29 Apr 2009 17:04:18 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 29 Apr 2009 09:04:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1240948468.3115.34.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Newsgroups: chiark.mail.xen.devel
References: <1240948468.3115.34.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Gary Grebus writes ("[Xen-devel] HVM networking in Xen 3.4-rc3"):
> 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' ] 

This looks plausible.  Although I'm not 100% sure that the spaces are
permitted.  None of my config files have them ...

> 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:

What does your /var/log/xen/xen-hotplug.log say ?

> Is qemu supposed to be involved in the hotplug mechanism, or is there
> something else I'm missing?

It's all very complicated (much more so than it needs to be).  Most of
the messing about is done by xend and by the hotplug script run by

> If modify qemu-ifup to write a value for the xenstore key, then the
> domain finishes booting and the network works.

The xenstore key is supposed to be done by the xend script, not
qemu-ifup.  And anyway the xenstore key is not relevant to the
operation of qemu.  I think xend is hanging up on itself.


Xen-devel mailing list

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