[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] ethX device ubuntu 7.10
- To: Casper <kl@xxxxx>
- From: "Todd Deshane" <deshantm@xxxxxxxxx>
- Date: Wed, 6 Feb 2008 02:10:10 +0000
- Cc: xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Tue, 05 Feb 2008 18:10:42 -0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=lhIBqu6XQmu39GFSHd45OV0SQLAqr/2lu+MKLwMRYBFwP39NhZq3B+80tByKQeOg+w6S8rF1WC1TsCQ4q97ildXJXV565ecnbV654smNLrrgxn8sAxRW+FAZTmn4ld3qLWHly5dO5nHpldIJ3CpkzGV8fjT0aR1Y1oJWpsnjoCM=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
On Feb 4, 2008 5:04 PM, Casper < kl@xxxxx> wrote:
Hello,
I experienced that on few Xen servers after maybe not clean reboot
ubuntu 7.10 server DomU changes device number to next eth"X" number and
network script uses previous on boot so there is no network on DomU... I
experienced in 3.1.x and new 3.2.0 Xen versions... How I understand
maybe udev not correctly discover Xen network device and every time
assigns next number for eth device... Anybody experienced this? What is
best way to repair it? I`m thinking maybe if I put my generated HW
address for DomU configuration udev will not change numbers...
thanx,
Casper
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
