[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] system reboots half way through virt-install
- To: Jeff Lane <dreadpiratejeff@xxxxxxxxx>
- From: Kevin McKeon <kevin.w.mckeon@xxxxxxxxx>
- Date: Thu, 21 May 2009 16:03:59 -0400
- Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Thu, 21 May 2009 13:04:57 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=FLdrAQLFXQaecd+6JdQ6EKlXEh+gm7GstBpnIsL11pL9lTdHX0gpnI4rzFPaUSTLn+ bd6S0WbC1M3I4wmjpZRlev4r6qfeJw97R2uH6GQ4TTbD7Nb5WyXunrHb7kSH2j3HK3Xv Urdt7tuAjG9QMG8ApbvzAXXCXDaDonapFb+6s=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
I found the problem. After a lot of googling, it appears there's a bug when creating a DomU within a CentOS5.3 Dom0. The solution? If you must use CentOS for your Dom0, just use 5.2. This issue seems to be isolated to the DomU creation process (using virt-install or virt-manager) when running CentOS5.3. You can however build 5.3 DomUs, as long as your Dom0 is NOT CentOS 5.3.
regards,
kevin
On Wed, May 20, 2009 at 12:51 PM, Jeff Lane <dreadpiratejeff@xxxxxxxxx> wrote:
First, what version of Xen and what host OS are you running? That may
be important...
And not that this helps a lot, but I've always found that
instantaneous shutdowns like that tend to be either memory or a bad
processor...
There usually has to be something very very wrong with the OS to
actually force a full reboot, unless you have some sort of watchdog
looking for a weird error which forces a reboot... but again, most of
the ones I have seen like that would throw a weird NMI error and
reboot the machine, and usually it was something memory related...
BUT it could be something with the host OS or Xen or something xen is
doing with memory mapping, perhaps...
Just an idea, and I know it's probably not terribly useful, but I
couldnt really say for sure...
But check the Xen logs to see what's going on, and if you have
something like kdump on the system, configure and run that, and you'll
at least, hopefully, get a core dump from the kernel that could give
you an idea of what's going on...
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
