[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-users
Subject:    Re: [Xen-users] domU's can't find eth0
From:       Ted Kaczmarek <tedkaz () optonline ! net>
Date:       2006-02-28 20:49:29
Message-ID: 1141159769.20703.43.camel () ool-43507d88 ! dyn ! optonline ! net
[Download RAW message or body]

On Tue, 2006-02-28 at 19:05 +0000, Andrew Thompson wrote:
> Greetings,
> 
> Yesterday it was just one, but now I seem to have broken both the domUs on my home Xen box. I 
> have rebuilt Xen from source twice now, and rebooted the dom0 a few times but still no luck.
> 
> Basically, they no longer see eth0, and a vifx.x is not being generated for them.
> 
> Here are some misc errors that are near the end of xen-hotplug.log:
> 
> xenstore-read: couldn't read path backend/vif/14/0/ip
> xenstore-read: couldn't read path backend/vif/14/0/bridge
> mkdir: cannot create directory `/var/run/xen-hotplug/block': File exists
> xenstore-read: couldn't read path backend/vbd/14/769/physical-device
> xenstore-read: couldn't read path backend/vbd/14/770/physical-device
> mkdir: cannot create directory `/var/run/xen-hotplug/block': File exists
> xenstore-read: couldn't read path backend/vbd/14/770/physical-device
> xenstore-list: could not list path backend/vbd/vbd
> xenstore-list: could not list path backend/vbd/vbd
> 
> I'm also attaching the last boot attempt or so from xend.log.
> 
> I would appreciate any tips on what to dig into to get this box back to running.
> 
Did you kill the dom0 with properly bringing it down before this started
to happen? I saw something similar on a power loss and battery expired
before I did an init 0/shutdown. Manually cleaning up the files took
care of the problem for me.

Regards,
Ted


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
[prev in list] [next in list] [prev in thread] [next in thread]