On Wed, 2006-03-01 at 00:56 +0000, Andrew Thompson wrote:
> On Tue, Feb 28, 2006 at 03:49:29PM -0500, Ted Kaczmarek wrote:
> > 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.
> > >
> > 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.
>
> Could you identify which files you cleaned up to bring your system back to
> running? I went through /var/run/ deleting xen related stuff(which hosed it
> up worse until i recreated some of them and rebooted), but was not able to
> resolve the main issue.
>From what I recall, /var/lib/xenstored/* and /var/lib/xend/* where all I
blew away. I may have redone an install from the dist dir as well. This
was a few months back, somewhere around changeset 7500 or so before 3.0
release. Worst case you can wipe all the xen stuff and just reinstall,
probably want to be running a non xen kernel when doing this though :-)
Do back up your domU configs though.
I would make sure you did not induce something first, I only got here
after a hard system crash and check the archives against the errors in
your log files.
If you rebuilt without hotplug support in your dom0 kernel the log entry
is crystal clear.
Regards,
Ted
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home