From: 王若曾 <ruozeng.w@gmail.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Dom0 network problem
Date: Fri, 9 Jul 2010 02:44:57 +0800 [thread overview]
Message-ID: <201007090244530861866@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 533 bytes --]
Host OS: CentOS 5.5
Xen version: 3.4.2
Compiling succeeded, everything seems to be normal.
But, when the dom0 start up, it says "Device eth0 has different MAC address than expacted, ignoring."
I've searched for the solution, someone suggests to remove the line "HWADDR=xx:xx:xx:xx:xx:xx" from /etc/sysconfig/networkscript/ifcfg-eth0, but after I did that, eth0 still cannot start up, "Bringing up interface eth0: e1000e device eth0 does not semm to be present, delaying initialization."
Could anyone help?
Thanks!
[-- Attachment #1.2: Type: text/html, Size: 1351 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-07-08 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 18:44 王若曾 [this message]
2010-07-08 19:40 ` Dom0 network problem Felix Kuperjans
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=201007090244530861866@gmail.com \
--to=ruozeng.w@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).