Xen users - Jul 2011 - domU startup freezes at "Starting plymouth"

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

id:3:initdefault:

______________________________
xl create vm1; xl console vm1;

<snip/>
[    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.

Thanks,
Mike Wright

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

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

On Sun, Jul 3, 2011 at 2:25 AM, Mike Wright <mike.wright@mailinator.com>
wrote:
> 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.
... and here''s the first mistake. I assume you''re converting
an
existing linux installation to Xen?
I highly suggest NOT to do so on your first domU/guest.
>
> 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"
This is the first mistake.

While domU can use kernel located in dom0, if you choose to do so then
you also need to specify the additional kernel arguments needed (e.g.
"root=/dev/xvda1"). It should be on an "extra" line.

Also, you need to have a matching set of modules in domU''s
/lib/modules (although this does not directly related to the error
you''re having now).
>
> disk = [ ''phy:/dev/OneTB/f14_64,     sda1,w'',
>         ''phy:/dev/OneTB/f14_64_swap,sda2,w'' ]
this one should be xvda instead of sda
> [    0.171095] blkfront: xvde1: flush diskcache: enabled
> [    0.172102] blkfront: xvde2: flush diskcache: enabled
... and you need to match "root=..." kernel arg to whatever''s
detected
here. Since you use sda on the config file, F14''s kernel will actually
detect the disk as xvde, which can be confusing. Better stick with
xvda.
> If I can get just one vm running I''ll be on my way...
 I''ve been stuck here
> since yesterday.  Any help appreciated.
The best way for beginners is start with the easy things first.
Install virt-manager, install a new domU, look at the generated config
file and disk image, then start changing things from there.

-- 
Fajar

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

On 07/02/2011 03:12 PM, Fajar A. Nugraha wrote:
> On Sun, Jul 3, 2011 at 2:25 AM, Mike
Wright<mike.wright@mailinator.com>  wrote:
>> 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.
>
> ... and here''s the first mistake. I assume you''re
converting an
> existing linux installation to Xen?
> I highly suggest NOT to do so on your first domU/guest.
>
>>
>> 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"
>
> This is the first mistake.
>
> While domU can use kernel located in dom0, if you choose to do so then
> you also need to specify the additional kernel arguments needed (e.g.
> "root=/dev/xvda1"). It should be on an "extra" line.
>
> Also, you need to have a matching set of modules in domU''s
> /lib/modules (although this does not directly related to the error
> you''re having now).
>
>>
>> disk = [ ''phy:/dev/OneTB/f14_64,     sda1,w'',
>>          ''phy:/dev/OneTB/f14_64_swap,sda2,w'' ]
>
> this one should be xvda instead of sda
>
>> [    0.171095] blkfront: xvde1: flush diskcache: enabled
>> [    0.172102] blkfront: xvde2: flush diskcache: enabled
>
> ... and you need to match "root=..." kernel arg to
whatever''s detected
> here. Since you use sda on the config file, F14''s kernel will
actually
> detect the disk as xvde, which can be confusing. Better stick with
> xvda.
>
>> If I can get just one vm running I''ll be on my way... 
I''ve been stuck here
>> since yesterday.  Any help appreciated.
>
> The best way for beginners is start with the easy things first.
> Install virt-manager, install a new domU, look at the generated config
> file and disk image, then start changing things from there.
>
Thanks for your help Fajar.

I think you may be being a bit alarmist ;)  All I was missing was the 
root = (or extra =) option (my fault for not reading all the way to the 
bottom) and that sda1 and sda2 have been superceded by xvda1 and xvda2.

Here are the basics from my vm1 config file:
(boots the virtual machine w/o networking)

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

# vif = ['''']

disk = [ ''phy:/dev/OneTB/f14_64,      xvda1, w'',
          ''phy:/dev/OneTB/f14_64_swap, xvda2, w'' ]

root = ''root=/dev/xvda1 ro''

Here are the required changes to the virtual to boot:

Mount the virtual''s root partition and make these changes:

/mnt/etc/fstab
   /dev/xvda1 /     ext4 defaults 1 1
   /dev/xvda2 /swap swap defaults 0 0
   #comment out /boot

make sure /lib/modules has matching modules (in my case "3.0.0-rc5").

Now to figure out networking...

Thanx,
Mike Wright

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