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-users] HMV + linux no network interface

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] HMV + linux no network interface
From: "George Mavrogonatos" <jblackknee@xxxxxxxxx>
Date: Wed, 13 Dec 2006 14:55:13 +0100
Delivery-date: Wed, 13 Dec 2006 05:55:17 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WwVpono6AwJU3WAeRHXjyL3wYvL84Mc0xSMPmcSk5+iSvIPAVUcJ8g2Ojc6VjyNjlT11+aci6NgAgA7ZIk/Agr1UC6xqyuQ9eJHHzriSiobMH0UiB7RJpcnXN2UMwhWGRtolKqj2skMs5kZvWOP5Xasgdj7LuPSvVXgnCGCfOsk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <50ca6c890612130246i738daeb0wa743f5c6cd9f529@xxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <50ca6c890612110742y7cb4f766rec3278dae579226d@xxxxxxxxxxxxxx> <5bb00b3f0612120410i6346eeafi44137c07713eb75b@xxxxxxxxxxxxxx> <50ca6c890612130057p4c3db610u66e2234c2d75ab8e@xxxxxxxxxxxxxx> <50ca6c890612130246i738daeb0wa743f5c6cd9f529@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I managed to make it work....
In case routing is used, an interface tap0 should be created and configured.
Also the "brctl addif $2 $" line should be commented in the qemu-ifup script.


On 12/13/06, George Mavrogonatos <jblackknee@xxxxxxxxx> wrote:

The vif=['type=ioemu'] syntax is working (network interface is
detected) if I use
bridging. But I can't make it work if I use routing. The error that seems to
be is (from the qemu-dm.#.log)
domid: 11
qemu: the number of cpus is 1
/etc/xen/qemu-ifup: could not launch network script
Could not initialize device 'tap'

any ideas how can I have a network interface detected
when I use routing and boot an OS from HVM?

On 12/13/06, George Mavrogonatos <jblackknee@xxxxxxxxx> wrote:
> Hi,
> I tried both vif=['type=ioemu'] and
> vif=['type=ioemu,mac=FE:FF:FF:FF:FF:FF,ip='],
> but in both cases the domU was created and listed in the domains (xm
> list) but with no
> state (state= ------ ). Moreover no sdl window popped up on neither case.
> When I'm using the vif=[ '' ] syntax there is no error in the log
> files (i have attached only
> the xend.log, since the other were empty).
> On 12/12/06, Henning Sprang <henning_sprang@xxxxxx> wrote:
> > On 12/11/06, George Mavrogonatos <jblackknee@xxxxxxxxx> wrote:
> > > I have installed xen 3.0.3 on gentoo 2006.1
> > > The machine is  a laptop with amd turion x2 ML-60.
> > > I can boot into xen, xend stars normally.
> > > When I try to boot a linux livecd using HVM, there is
> > > no network interface (I used several different linux distributions).
> > > [...]
> > > vif = [ '' ]
> >
> > I'm not sure if HVM domains set a correct default when you define it
> > like this, which works for paravirtual domains.
> >
> > try at least vif=['type=ioemu']
> > (didn't test that, i have something like
> > vif=['type=ioemu, mac=xxxxxxxxxxxx, bridge=xenbr1]
> >
> > I'd be interested if this hint helps, and I'd be intersted to know if
> > when using the configuration that does *not* work, if there is maybe
> > some error message in the xend logs. (xend/debug/hotplug)?
> >
> > Henning
> >

Xen-users mailing list

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