WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Networking problems

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Networking problems
From: Didier Trosset <didier_trosset@xxxxxxxxxxx>
Date: Tue, 22 May 2007 15:45:51 +0200
Cc: Michel Drescher <Michel.Drescher@xxxxxxxxxxxxxx>
Delivery-date: Tue, 22 May 2007 06:44:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4652EB7E.1080604@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: <4652EB7E.1080604@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Icedove 1.5.0.10 (X11/20070329)
Michel Drescher wrote:
Dear Xen wranglers,

I have the following problem:

> ---- 8< ----

However, and this is the downside, the VM brings up only the loopback
device. The VM exports the virtual eth0 as RTL8139, but trying to bring up
eth0 manually results in the following error:

---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP ----------
mdrescher@baseline-vm:~$ sudo ifup eth0
Password:
eth0: ERROR while getting interface flags: No such device
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
eth0: ERROR while getting interface flags: No such device
Failed to bring up eth0.
---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP ----------

Unfortunately, as I don't have network and my vncViewer does'nt capture
screens, I have to describe the dmesg output of domU:

According to the dmesg output, the RTL8139too Fast Ethernet driver v0.9.28
is loaded, which detects an "enhanced" 8139C+ chip (?) so it will use the
8139cp driver for improved performance (well, well...)
Later, the driver says "unknown chip version, assuming RTL-8139"

Can you help me out getting the following issues resolved?
a) Getting networking up (obviously) using the real Tigon3 driver or
something emulating
b) When booting domU from the mini.iso, networking went just fine, but why?

You have to specify the mac address in the vif=... line of the domU config file. As you don't, the mac address is asigned a new random mac on each boot. This is the reason why the network works correctly during the install, but fails after the reboot: the system doesn't know about this *new* network device.

You should be able to know the mac you have been assigned during the install by looking in the file /etc/udev/rules.d/z25_persistent-net.rules

I've already been hit by this feature ;)

HTH
Didier

b) When trying to export the disk image as "ioemu:sda" the domU Ubuntu 7.04
mini.iso wasn't able to find the disk, probably because lacking an
appropriate kernel module?

Thanks, and any help is much appreciated!

Attached TEXT files:
- dom0-eth0-txt: Excerpt from dom0 dmesg output related to eth0
- test.hvm: My HVM VM config file I'm using.


Cheers,
Michel

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

--
Didier Trosset-Moreau
Agilent Technologies
Geneva, Switzerland

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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