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


[Xen-users] domU startup freezes at "Starting plymouth"

To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] domU startup freezes at "Starting plymouth"
From: Mike Wright <mike.wright@xxxxxxxxxxxxxx>
Date: Sat, 02 Jul 2011 12:25:06 -0700
Delivery-date: Sat, 02 Jul 2011 12:26:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110621 Fedora/3.1.11-1.fc14 Thunderbird/3.1.11
Hi all,

I've got xen-4.1.1 running with linux-3.0.0-rc5 and am trying to start my first guest, f14-x86_64, which does boot on bare metal.

The configs below show kernel, ramdisk, and disk assignments for the virtual machine. They also show that the virtual machine uses the target disk devices. The last section shows part of the boot sequence starting with the disk assignments, which are successful. Everything stops at the last line until some time later when the messages "Boot has failed, sleeping forever" appears. (I think this is about where the initramfs hands off control to the kernel.)

dom0: /etc/xen/vm1

kernel = "/boot/vmlinuz-3.0.0-rc5"
ramdisk = "/boot/initramfs-3.0.0-rc5.img"

disk = [ 'phy:/dev/OneTB/f14_64,     sda1,w',
         'phy:/dev/OneTB/f14_64_swap,sda2,w' ]

vm1: /etc/fstab

/dev/sda1       /       ext4    defaults        1 1
/dev/sda2       /swap   swap    defaults        0 0

vm1: /etc/inittab


xl create vm1; xl console vm1;

[    0.171095] blkfront: xvde1: flush diskcache: enabled
[    0.172102] blkfront: xvde2: flush diskcache: enabled
[    0.172648] Setting capacity to 20512768
[    0.172658] xvde1: detected capacity change from 0 to 10502537216
[    0.172806] Setting capacity to 2097152
[    0.172812] xvde2: detected capacity change from 0 to 1073741824
[    0.270121]   Magic number: 1:252:3141
[    0.270167] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    0.270185] Initializing network drop monitor service
[    0.270547] Freeing unused kernel memory: 920k freed
[    0.270781] Write protecting the kernel read-only data: 10240k
[    0.274674] Freeing unused kernel memory: 1504k freed
[    0.275636] Freeing unused kernel memory: 1756k freed
[    0.297666] dracut: dracut-006-6.fc14
[    0.316248] udev[56]: starting version 161
[    0.415803] dracut: Starting plymouth daemon

cat qemu-dm-vm1.log

domid: 5
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M. /home/mike/Downloads/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap.c:628: Init blktap pipes
Could not open /var/run/tap/qemu-read-5
char device redirected to /dev/pts/2
xs_read(): target get error. /local/domain/5/target.
(qemu) (qemu)

This is the only thing I found but it doesn't make sense to me. I didn't setup a vif in the vm config because it said networking was not required.

If I can get just one vm running I'll be on my way... I've been stuck here since yesterday. Any help appreciated.

Mike Wright

ps. U.S.ers, happy 4th!

Xen-users mailing list

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