[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] I upgraded, now vms won't start


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • Date: Sun, 13 Nov 2011 10:19:46 +0700
  • Delivery-date: Sat, 12 Nov 2011 19:23:29 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Sun, Nov 13, 2011 at 9:38 AM, Chris <cjdl01@xxxxxxxxxxxxxxxxxx> wrote:
>>> dom0box:/etc/xen/configs# xm console domubox

>>> [    0.000000] Command line: root=/dev/xvda2 ro

So your root is /dev/xvda2?

>>> [    0.047112] XENBUS: Device with no driver: device/vbd/51713
>>> [    0.047119] XENBUS: Device with no driver: device/vbd/51714

those are the disks. If you see those lines, it means at that time the
frontend drivers (xen-blkfront) is not loaded. Load it.

>>> Begin: Assembling all MD arrays ... mdadm: No devices listed in  conf
>>> file were found.
>>> Failure: failed to assemble all arrays.

this one should be irrelevant. You're using /dev/xvda2 as root, not
/dev/md*, remember?

>>> Begin: Waiting for root file system ... done.
>>> Gave up waiting for root device.  Common problems:
>>> - Boot args (cat /proc/cmdline)
>>>  - Check rootdelay= (did the system wait long enough?)
>>>  - Check root= (did the system wait for the right device?)
>>> - Missing modules (cat /proc/modules; ls /dev)
>>> ALERT!  /dev/xvda2 does not exist.  Dropping to a shell!

well, do what it tells you to.
- cat /proc/cmdline
- cat /proc/modules
- ls /dev/?da*

> I have read some on pygrub, I understand what it is supposed to accomplish,
> but I am very confused on how it is supposed to work.  I am running Squeeze,
> which uses grub 2, which does NOT use a menu.lst.

pygrub (at least newer versions of it) can read grub2's grub.cfg just fine.

Or you can just create a dummy menu.lst.

> but I really think that we are barking up the
> wrong tree...

No, you don't.

Using pygrub of pvgrub means you're using domU's kernel, which might
contain the necessary drivers (e.g. xen-blkfront) while dom0's kernel
doesn't. It also means you can treat domU just like any other machine,
upgrading packages (including kernel) on the domU, and you can have
different versions of kernel between dom0 and domU.

> even if I get it running under pygrub, I don't know what that
> would prove.  I need it running normally through xen.

pygrub IS part of xen.

Thinking that you HAVE to use a kernel on dom0 to boot domU is simply wrong.

>
> Why the heck is it trying to rebuild the array anyway?

possibly because you use dom0's kernel and initrd. Are you using md in dom0?

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.