From: "Jonathan M. McCune" <jonmccune@cmu.edu>
To: "Jonathan M. McCune" <jonmccune@cmu.edu>
Cc: xen-devel@lists.xensource.com, "Puthiyaparambil,
Aravindh" <aravindh.puthiyaparambil@unisys.com>
Subject: Re: pcnet32 device eth0 does not seem to be present, delaying initialization
Date: Tue, 07 Feb 2006 18:18:23 -0500 [thread overview]
Message-ID: <43E92ABF.7090102@cmu.edu> (raw)
In-Reply-To: <43E7E371.10805@cmu.edu>
I'm afraid I spoke too soon.
vif = ['type=ioemu, bridge=xenbr0']
gives me an eth0 in the guest, but there is no corresponding vifX.0 in
dom0. Looking in /etc/xen/xmexample.hvm, I see the comment:
# type=ioemu specify the NIC is an ioemu device not netfront
I think vifX.0 is the backend, thus there is no reason for it to exist
if the guest has no frontend. However, what do I do instead? I have
been looking through documentation without luck.
Thanks!
-Jon
Jonathan M. McCune wrote:
> That did the trick. Many thanks.
>
> -Jon
>
>
> Puthiyaparambil, Aravindh wrote:
>
>> Please try replacing vif = [''] with
>>
>> vif = [ 'type=ioemu, bridge=xenbr0' ]
>>
>> Cheers,
>> Aravindh
>>
>>
>>
>>> -----Original Message-----
>>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
>>> bounces@lists.xensource.com] On Behalf Of Jonathan M. McCune
>>> Sent: Monday, February 06, 2006 5:42 PM
>>> To: xen-devel@lists.xensource.com
>>> Subject: [Xen-devel] pcnet32 device eth0 does not seem to be
>>> present,delaying initialization
>>>
>>> Hi,
>>>
>>> I'm trying to bring up an HVM guest with networking support, but I
>>> cannot get the guest to recognize an ethernet interface. The guest is
>>> rhel5, and I'm running Debian linux dom0 on top of xen-unstable-hvm
>>> changeset 8724.
>>>
>>> Running `/etc/init.d/networking restart` gives:
>>>
>>> Shutting down loopback interface: [ OK ]
>>> Setting network parameters: [ OK ]
>>> Bringing up loopback interface: [ OK ]
>>> Bringing up interface eth0: pcnet32 device eth0 does not seem to be
>>> present, delaying initialization.
>>> [FAILED]
>>>
>>> I have tried several stock 2.4 redhat kernels, and I have built a
>>>
>>
>> 2.6.12
>>
>>
>>> kernel and taken care to include the pcnet32 driver. The config file
>>> for the guest domain contains the line:
>>>
>>> vif = ['']
>>>
>>> `lspci` inside the guest does not show any ethernet interface.
>>>
>>> I'm not sure what to do to enable networking.
>>>
>>> Thanks,
>>> -Jon
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>
>
next prev parent reply other threads:[~2006-02-07 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 22:50 pcnet32 device eth0 does not seem to be present, delaying initialization Puthiyaparambil, Aravindh
2006-02-07 0:01 ` Jonathan M. McCune
2006-02-07 23:18 ` Jonathan M. McCune [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-06 22:42 Jonathan M. McCune
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E92ABF.7090102@cmu.edu \
--to=jonmccune@cmu.edu \
--cc=aravindh.puthiyaparambil@unisys.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.