This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Cannot start PV guests

To: Andreas Sommer <AndiDog@xxxxxx>
Subject: Re: [Xen-users] Cannot start PV guests
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Thu, 3 Sep 2009 18:43:01 +0700
Cc: XenUsers <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 03 Sep 2009 04:47:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A9F7E7F.9090806@xxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4A9E4D85.5040401@xxxxxx> <7207d96f0909021011h78d908fei7cba175fbdd23c29@xxxxxxxxxxxxxx> <4A9F7E7F.9090806@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Sep 3, 2009 at 3:29 PM, Andreas Sommer<AndiDog@xxxxxx> wrote:
> Fajar A. Nugraha wrote:

> extra = "video=xenfb xencons=tty1"
> vfb = ['type=vnc,vncdisplay=10']
> Try this :
> - remove (or mark) those two lines
> - setup domU's /etc/inittab to spawn login prompt on hvc0

> I tried the following kernels (and removed the framebuffer configuration),
> with no luck:
> Output for and (both are from the xenbits.xensource.com
> GIT repo; output is the same):

> [  300.031631] Xen virtual console successfully installed as tty1

There's no mention of hvc0 or xvc0. Do you still have xencons=tty1
line? Try removing it first. I find it easier to debug that way.

> [  599.991814] XENBUS: Timeout connecting to device: device/vbd/2049 (local
> state 3, remote state 1)
> [  599.991820] XENBUS: Device not ready: device/vbd/2049

That one shows something wrong with domU's disk. Perhaps you don't
have the block device frontend compiled on domU kernel? Or maybe your
dom0 kernel does not have block device backend compiled?

> [  599.992864]   ** WARNING: Currently emulating unsupported memory
> accesses  **
> [  599.992867]   **          in /lib/tls glibc libraries. The emulation

That warning can sometimes be ignored. You can investigate later after
domU boots correctly.

> 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/sda1 does not exist. Dropping to a shell!

That one is bad :D
Make sure :
- your domU disk backend is accessible
- you have block device frontend driver on domU kernel
- you have block device backend driver on dom0 kernel
- you use correct name

AFAIK later kernels will silently change all reference to hda/sda for
domU disk to xvda, so you might want to try changing that.

> Output for 2.6.31-rc8 (mainline):
> Using config file "./config.cfg".
> Started domain c08d06e6-cb72-48ab-88a9-24360beff248 (id=5)
> Then the CPU goes up to 100% and dom0 hardly reacts to my user input...

vanilla kernel is somewhat tricky. In my config I had to compile SCTP
support built in to get it to work, otherwise domU can't start at all.
You might want to start with a known good config.

> Output for 2.6.30-rc6-tip (from jeremy repository, but without dom0
> support):
> ...
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
> [   10.691178] device-mapper: uevent: version 1.0.3
> [   10.692853] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised:
> dm-devel@xxxxxxxxxx
> done.
> Begin: Waiting for root file system ...
> Then it waits forever for the root file system. Note that it's in my
> configuration (root = "/dev/sda1 ro").

Try changing it to /dev/xvda1

> So I'm pretty much stuck, no matter which kernel version :(...

You mentioned earlier you already had a working domU on another
machine. What happens when you copy it (disk image, kernel, and
config) to this machine? It should work.


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>