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] Re : xen on Debian Etch : problem resolved !!!

To: gthiery@xxxxxxxxxxxx
Subject: Re: [Xen-users] Re : xen on Debian Etch : problem resolved !!!
From: Stefan Berner <Stefan.Berner@xxxxxxxxxxxxxxx>
Date: Thu, 10 Jan 2008 08:09:04 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Jan 2008 23:09:42 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20588769d86628bb0cecbb21d7937467@localhost>
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: <20588769d86628bb0cecbb21d7937467@localhost>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.12 (X11/20060911)
Dear Guillaume,

gthiery@xxxxxxxxxxxx wrote:
> Hi,
>
> I told you yesterday evening that I had succeeded to create a new domU
> using xen-tools but while launching this domU I had an error : the system
> tried to access to my dom0 filesystem, according to what I've seen on the
> console writings. The domU filesystem was hda1 and hda2 and the system
> tried to access to sda5 wich correspond to my dom0 filesystem.
> I have succeeded in launching a domU that I had configured in another
> method : I have copied the most important directories of the dom0
> filesystem to my domUdisk-image and launched it (I've seen that on the
> french wiki) but the configuration was not totally clear and for commercial
> purpose it isn't good to have this type of configuration. But I have
> compared the two config files and seen that in the config file which was
> working there was no initrd statement, although there was one in the config
> file made by xen-tools. I then removed the initrd statement in the
> xen-tools config-file and it works !!! 
> Now I think that the initrd file, which was made according to my dom0
> filesystem caused the problem and that's why I had seen som references to
> my dom0 filesystem...
>
> For your information : the first method I have used (copying the whole
> filesystem to the domU disk-image) worked but at each reboot of the domU
> the ethernet interface was increased by one, I tell you this because I've
> seen this some days ago on the mailing list, sorry I have'nt the mail under
> my eyes so I cannot tell you when. Hawaver the xen-tools domU doesn't have
> it's ethernet interface increasing at each reboot...
>
>   
Are you using a fixed MAC-address for your network interface?
Something like this:
vif=[ 'mac=AA:00:00:00:01:01,bridge=...]

Please use a fixed MAC for your interface and your ethxx wont increase
anymore.
if you need a certain ethxx you can create a udev rule something like:

SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:60:dd:47:80:dc", 
IMPORT="/lib/udev/rename_netiface %k eth0"


Stefan Berner
> Best regards,
>
> Guillaume Thiery
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>   

Attachment: stefan.berner.vcf
Description: Vcard

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>