thr3ads.net - Xen users - [Xen-users] Full Virtualised DomU Hang on Boot [Jan 2010]

If this information is useful, please help other people find it:
Share via:

<peter.chiu@stfc.ac.uk>

2010-Jan-28 19:27 UTC

[Xen-users] Full Virtualised DomU Hang on Boot

On an DELL R710 server, I mounted OpenSuse 11.2 (86-64) with the xen
kernel 2.6.31.8-0.1-xen.

 

I am trying to replicate an existing Red Hat Enterprise AS 3 (Taroon)
32-bit with kernel 2.4.21-57.ELsmp as a DomU.

 

Having done the dd of the entire system disk into an image, and use
yast2 to set up a full virtualisation guest configure file,

I then start up the guest.

 

On the console it only shows up:

apricot:/etc/xen/vm # xm create -c ignis

Using config file "./ignis".

Started domain ignis (id=23)

 

Then using vncviewer :5900, it returns a window that continues with the
start up.

  Booting ''Red Hat Enterprise Linux AS (2.4.21-57-Elsmp)''

 

root (hd0,1)

 Fileysystem type is ext2fs, partition type 0x83

kernel /boot/vmlinuz-2.4.21-57.ELsmp ro root=/dev/sda2

  [Linux-bzImage, setup=0x1400, size=0x14d31e]

initrd /boot/initrd-2.4.21-57.ELsmp.img

 

After this, the guest makes no further progress.

 

Below is the configuration file on the guest.

 

I can mount the guest image using the loop device, check the files, and
can chroot to it okay.

 

It looks as if it is waiting for the operating system disk to continue.

Does any have any idea how to investigate this?

 

Many thanks.

 

Peter Chiu

 

STFC Rutherford Appleton Laboratory

UK

 

/etc/xen/vm/ignis

name="ignis"

uuid="94259271-5e1f-2058-66c7-f91df8fb4f28"

memory=2048

maxmem=4096

vcpus=1

on_poweroff="destroy"

on_reboot="restart"

on_crash="destroy"

localtime=0

 

builder="hvm"

extid=0

device_model="/usr/lib/xen/bin/qemu-dm"

kernel="/usr/lib/xen/boot/hvmloader"

boot="c"

disk=[ ''tap:aio:/disks/apricot1/xen/ignis,hda,w'', ]

vif=[ ''bridge=br0,model=rtl8139'', ]

stdvga=0

vnc=1

vncunused=1

apic=1

acpi=1

pae=1

 

serial="pty"


-- 
Scanned by iCritical.


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

<peter.chiu@stfc.ac.uk>

2010-Jan-29 12:00 UTC

head link

[Xen-users] Full Virtualised DomU Hang on Boot

Hello All,

 

I am trying to make a currently running Red Hat Enterprise AS3 32-bit
system as a guest OS to an OpenSuse 11.2(86-64) Dom0.

 

When the guest os is started up,  from the vncviewer :5900 display, it
gets as far as

 

  Booting ''Red Hat Enterprise Linux AS (2.4.21-57-Elsmp)''

 

root (hd0,1)

 Fileysystem type is ext2fs, partition type 0x83

kernel /boot/vmlinuz-2.4.21-57.ELsmp ro root=/dev/sda2

  [Linux-bzImage, setup=0x1400, size=0x14d31e]

initrd /boot/initrd-2.4.21-57.ELsmp.img

 

and then it goes no further. 

 

It does not crash or reports errors,  just not going any further.

 

I have looked around in the xen-users archive, but don''t think there is
a similar problem reported.

 

I would appreciate for advice from anyone on this.

 

Below are the details.

 

Dom0: DELL 710 Server, OpenSuse 11.2 (86-64) with kernel
2.6.31.8-0.1-xen, xen 3.4.1_19718_04-2.1.x86_64.

              2 x E5540 Intel Xeon Quadcore, 48GB RAM.  - hostname
apricot

 

DomU: RH EL AS3 (32-bit) kernel 2.4.21-57.ELsmp

              2 x Intel Xeon 2.4GHz, 2GB RAM, OS disk 146GB, root on
/dev/sda2 10GB partition.

              hostname ignis

 

Guest Image prepared by dd if=/dev/sda | ssh apricot "dd
of=/disks/apricot1/xen/ignis"

# file /disks/apricot1/xen/ignis

/disks/apricot1/xen/ignis: x86 boot sector; GRand Unified Bootloader,
stage1 version 0x3, boot drive 0x80, 1st sector stage2 0x201425a, GRUB
version n.m; 

partition 1: ID=0x83, active, starthead 1, startsector 63, 24579387
sectors; partition 2: ID=0x83, starthead 254, startsector 24579450,
20482875 sectors; 

partition 3: ID=0x82, starthead 254, startsector 45062325, 4096575
sectors; partition 4: ID=0xf, starthead 254, startsector 49158900,
236958750 sectors, code offset 0x48

 

Configuration file: /etc/xen/vm/ignis

 

name="ignis"

uuid="94259271-5e1f-2058-66c7-f91df8fb4f28"

memory=2048

maxmem=4096

vcpus=1

on_poweroff="destroy"

on_reboot="restart"

on_crash="destroy"

localtime=0

 

builder="hvm"

extid=0

device_model="/usr/lib/xen/bin/qemu-dm"

kernel="/usr/lib/xen/boot/hvmloader"

boot="c"

disk=[ ''file:/disks/apricot1/xen/ignis,hda,w'', ]

vif=[ ''bridge=br0,model=rtl8139'', ]

stdvga=0

vnc=1

vncunused=1

apic=1

acpi=1

pae=1

 

serial="pty"

 

 

Many thanks in advance.

 

Peter Chiu

 

STFC Rutherford Appleton Laboratory

UK

 


-- 
Scanned by iCritical.


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

Fajar A. Nugraha

2010-Jan-29 14:19 UTC

head link

Re: [Xen-users] Full Virtualised DomU Hang on Boot

On Fri, Jan 29, 2010 at 7:00 PM,  <peter.chiu@stfc.ac.uk>
wrote:> root (hd0,1)
>
>  Fileysystem type is ext2fs, partition type 0x83
>
> kernel /boot/vmlinuz-2.4.21-57.ELsmp ro root=/dev/sda2
>
>   [Linux-bzImage, setup=0x1400, size=0x14d31e]
>
> initrd /boot/initrd-2.4.21-57.ELsmp.img
at least this means boot and initrd was loaded.
What does domU''s grub.conf look like? You might want to remove
"quiet"
and "rhgb" (so you get more verbose messages). Also HVM domUs sees
disk as hda, not sda, so you need to change that (grub.conf, fstab).
> Guest Image prepared by dd if=/dev/sda | ssh apricot “dd
> of=/disks/apricot1/xen/ignis”
I hope you use Live CD/USB for this? dd-ing the content of live disk
with mounted partitions (I assume sda is the disk you''re booting from)
is a bad idea.

-- 
Fajar

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

Karel Charousek

2010-Jan-29 14:33 UTC

head link

Re: [Xen-users] Full Virtualised DomU Hang on Boot

Hi,

we had same problem with domU HVM RHEL 3 U4 32bit, dom0 RHEL 5 U4 x86_64 
- out of box virtualization installation, Dell server Nehalem X5550.

I haven''t enouhg time to solve it completely,
but for me, it was sufficient, that NON SMP kernel booted without 
problem and is running without problems since September 2009.

Regards

Karel



peter.chiu@stfc.ac.uk napsal(a):>
> Hello All,
>
> I am trying to make a currently running Red Hat Enterprise AS3 32-bit 
> system as a guest OS to an OpenSuse 11.2(86-64) Dom0.
>
> When the guest os is started up, from the vncviewer :5900 display, it 
> gets as far as
>
> Booting ‘Red Hat Enterprise Linux AS (2.4.21-57-Elsmp)’
>
> root (hd0,1)
>
> Fileysystem type is ext2fs, partition type 0x83
>
> kernel /boot/vmlinuz-2.4.21-57.ELsmp ro root=/dev/sda2
>
> [Linux-bzImage, setup=0x1400, size=0x14d31e]
>
> initrd /boot/initrd-2.4.21-57.ELsmp.img
>
> and then it goes no further.
>
> It does not crash or reports errors, just not going any further.
>
> I have looked around in the xen-users archive, but don’t think there 
> is a similar problem reported.
>
> I would appreciate for advice from anyone on this.
>
> Below are the details.
>
> Dom0: DELL 710 Server, OpenSuse 11.2 (86-64) with kernel 
> 2.6.31.8-0.1-xen, xen 3.4.1_19718_04-2.1.x86_64.
>
> 2 x E5540 Intel Xeon Quadcore, 48GB RAM. – hostname apricot
>
> DomU: RH EL AS3 (32-bit) kernel 2.4.21-57.ELsmp
>
> 2 x Intel Xeon 2.4GHz, 2GB RAM, OS disk 146GB, root on /dev/sda2 10GB 
> partition.
>
> hostname ignis
>
> Guest Image prepared by dd if=/dev/sda | ssh apricot “dd 
> of=/disks/apricot1/xen/ignis”
>
> # file /disks/apricot1/xen/ignis
>
> /disks/apricot1/xen/ignis: x86 boot sector; GRand Unified Bootloader, 
> stage1 version 0x3, boot drive 0x80, 1st sector stage2 0x201425a, GRUB 
> version n.m;
>
> partition 1: ID=0x83, active, starthead 1, startsector 63, 24579387 
> sectors; partition 2: ID=0x83, starthead 254, startsector 24579450, 
> 20482875 sectors;
>
> partition 3: ID=0x82, starthead 254, startsector 45062325, 4096575 
> sectors; partition 4: ID=0xf, starthead 254, startsector 49158900, 
> 236958750 sectors, code offset 0x48
>
> Configuration file: /etc/xen/vm/ignis
>
> name="ignis"
>
> uuid="94259271-5e1f-2058-66c7-f91df8fb4f28"
>
> memory=2048
>
> maxmem=4096
>
> vcpus=1
>
> on_poweroff="destroy"
>
> on_reboot="restart"
>
> on_crash="destroy"
>
> localtime=0
>
> builder="hvm"
>
> extid=0
>
> device_model="/usr/lib/xen/bin/qemu-dm"
>
> kernel="/usr/lib/xen/boot/hvmloader"
>
> boot="c"
>
> disk=[ ''file:/disks/apricot1/xen/ignis,hda,w'', ]
>
> vif=[ ''bridge=br0,model=rtl8139'', ]
>
> stdvga=0
>
> vnc=1
>
> vncunused=1
>
> apic=1
>
> acpi=1
>
> pae=1
>
> serial="pty"
>
> Many thanks in advance.
>
> Peter Chiu
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

<peter.chiu@stfc.ac.uk>

2010-Jan-29 14:49 UTC

head link

RE: [Xen-users] Full Virtualised DomU Hang on Boot

Thanks Fajar for your response.

DomU has this grub.conf

# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,1)
#          kernel /boot/vmlinuz-version ro root=/dev/sda2
#          initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
title Red Hat Enterprise Linux AS (2.4.21-57.ELsmp)
        root (hd0,1)
        kernel /boot/vmlinuz-2.4.21-57.ELsmp ro root=/dev/sda2 1
        initrd /boot/initrd-2.4.21-57.ELsmp.img
title Red Hat Enterprise Linux AS (2.4.21-57.EL)
        root (hd0,1)
        kernel /boot/vmlinuz-2.4.21-57.EL ro root=LABEL=/1
        initrd /boot/initrd-2.4.21-57.EL.img
title Red Hat Enterprise Linux AS (2.4.21-53.ELsmp)
        root (hd0,1)
        kernel /boot/vmlinuz-2.4.21-53.ELsmp ro root=LABEL=/1
        initrd /boot/initrd-2.4.21-53.ELsmp.img
title Red Hat Enterprise Linux AS (2.4.21-53.EL)
... shortened.

On the guest OS, the actually devices are sda, and not hda.
[root@ignis log]# df -hl
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2             9.7G  8.4G  817M  92% /
none                 1004M     0 1004M   0% /dev/shm
/dev/sda1              12G   10G  1.1G  91% /mnt/rh9
/dev/sda5             112G   66G   40G  63% /disks/ignis1

Are you saying that the full virtualised loader (HVM?) cannot support sda?


Regarding the other command on the use of live CD/USB?
I don''t quite follow the use on that.

The main objective I am trying to achieve is to flexibly transfer a running
service to run on a xen server,
in the hope that we do not need to redo a fresh installation and its layered
applications.
This will be useful so we can save time, but also some applications may not
easily be redone due to departure of staff who set them up.

If we use live CD/USB, can you tell how to transfer a running service to run as
a guest OS?

Many thanks again.

Kind regards,

Peter 


-----Original Message-----
From: Fajar A. Nugraha [mailto:fajar@fajar.net] 
Sent: 29 January 2010 14:19
To: Chiu, Peter (STFC,RAL,SSTD)
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Full Virtualised DomU Hang on Boot

On Fri, Jan 29, 2010 at 7:00 PM,  <peter.chiu@stfc.ac.uk>
wrote:> root (hd0,1)
>
>  Fileysystem type is ext2fs, partition type 0x83
>
> kernel /boot/vmlinuz-2.4.21-57.ELsmp ro root=/dev/sda2
>
>   [Linux-bzImage, setup=0x1400, size=0x14d31e]
>
> initrd /boot/initrd-2.4.21-57.ELsmp.img
at least this means boot and initrd was loaded.
What does domU''s grub.conf look like? You might want to remove
"quiet"
and "rhgb" (so you get more verbose messages). Also HVM domUs sees
disk as hda, not sda, so you need to change that (grub.conf, fstab).
> Guest Image prepared by dd if=/dev/sda | ssh apricot "dd
> of=/disks/apricot1/xen/ignis"
I hope you use Live CD/USB for this? dd-ing the content of live disk
with mounted partitions (I assume sda is the disk you''re booting from)
is a bad idea.

-- 
Fajar
-- 
Scanned by iCritical.

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

<peter.chiu@stfc.ac.uk>

2010-Jan-29 16:24 UTC

head link

RE: [Xen-users] Full Virtualised DomU Hang on Boot

Thanks very much, Karel,

That is a good thought.  I have just tried that, unfortunately the
problem persists.

I have tried a few other combinations too; 
  - selected kernel
    title Red Hat Enterprise Linux AS (2.4.21-57.EL)
        root (hd0,1)
        kernel /boot/vmlinuz-2.4.21-57.EL ro root=LABEL=/1
        initrd /boot/initrd-2.4.21-57.EL.img
  - using root device name from LABEL=/1 to /dev/sda2
  - selected another kernel on partition 1
    title Red Hat 9 Linux-up (2.4.20-8)
        root (hd0,0)
        kernel /boot/vmlinuz-2.4.20-8 ro root=/dev/sda1
        initrd /boot/initrd-2.4.20-8.img

   still no joy.  Stuck as before - see screen dump attached.

Any more idea?

Many thanks anyway.

Kind regards,
Peter


-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Karel
Charousek
Sent: 29 January 2010 14:34
To: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Full Virtualised DomU Hang on Boot


Hi,

we had same problem with domU HVM RHEL 3 U4 32bit, dom0 RHEL 5 U4 x86_64

- out of box virtualization installation, Dell server Nehalem X5550.

I haven''t enouhg time to solve it completely,
but for me, it was sufficient, that NON SMP kernel booted without 
problem and is running without problems since September 2009.

Regards

Karel



peter.chiu@stfc.ac.uk napsal(a):>
> Hello All,
>
> I am trying to make a currently running Red Hat Enterprise AS3 32-bit 
> system as a guest OS to an OpenSuse 11.2(86-64) Dom0.
>
> When the guest os is started up, from the vncviewer :5900 display, it 
> gets as far as
>
> Booting ''Red Hat Enterprise Linux AS (2.4.21-57-Elsmp)''
>
> root (hd0,1)
>
> Fileysystem type is ext2fs, partition type 0x83
>
> kernel /boot/vmlinuz-2.4.21-57.ELsmp ro root=/dev/sda2
>
> [Linux-bzImage, setup=0x1400, size=0x14d31e]
>
> initrd /boot/initrd-2.4.21-57.ELsmp.img
>
> and then it goes no further.
>
> It does not crash or reports errors, just not going any further.
>
> I have looked around in the xen-users archive, but don''t think
there
> is a similar problem reported.
>
> I would appreciate for advice from anyone on this.
>
> Below are the details.
>
> Dom0: DELL 710 Server, OpenSuse 11.2 (86-64) with kernel 
> 2.6.31.8-0.1-xen, xen 3.4.1_19718_04-2.1.x86_64.
>
> 2 x E5540 Intel Xeon Quadcore, 48GB RAM. - hostname apricot
>
> DomU: RH EL AS3 (32-bit) kernel 2.4.21-57.ELsmp
>
> 2 x Intel Xeon 2.4GHz, 2GB RAM, OS disk 146GB, root on /dev/sda2 10GB 
> partition.
>
> hostname ignis
>
> Guest Image prepared by dd if=/dev/sda | ssh apricot "dd 
> of=/disks/apricot1/xen/ignis"
>
> # file /disks/apricot1/xen/ignis
>
> /disks/apricot1/xen/ignis: x86 boot sector; GRand Unified Bootloader, 
> stage1 version 0x3, boot drive 0x80, 1st sector stage2 0x201425a, GRUB
> version n.m;
>
> partition 1: ID=0x83, active, starthead 1, startsector 63, 24579387 
> sectors; partition 2: ID=0x83, starthead 254, startsector 24579450, 
> 20482875 sectors;
>
> partition 3: ID=0x82, starthead 254, startsector 45062325, 4096575 
> sectors; partition 4: ID=0xf, starthead 254, startsector 49158900, 
> 236958750 sectors, code offset 0x48
>
> Configuration file: /etc/xen/vm/ignis
>
> name="ignis"
>
> uuid="94259271-5e1f-2058-66c7-f91df8fb4f28"
>
> memory=2048
>
> maxmem=4096
>
> vcpus=1
>
> on_poweroff="destroy"
>
> on_reboot="restart"
>
> on_crash="destroy"
>
> localtime=0
>
> builder="hvm"
>
> extid=0
>
> device_model="/usr/lib/xen/bin/qemu-dm"
>
> kernel="/usr/lib/xen/boot/hvmloader"
>
> boot="c"
>
> disk=[ ''file:/disks/apricot1/xen/ignis,hda,w'', ]
>
> vif=[ ''bridge=br0,model=rtl8139'', ]
>
> stdvga=0
>
> vnc=1
>
> vncunused=1
>
> apic=1
>
> acpi=1
>
> pae=1
>
> serial="pty"
>
> Many thanks in advance.
>
> Peter Chiu
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

-- 
Scanned by iCritical.


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

Fajar A. Nugraha

2010-Jan-29 22:16 UTC

head link

Re: [Xen-users] Full Virtualised DomU Hang on Boot

On Fri, Jan 29, 2010 at 9:49 PM,  <peter.chiu@stfc.ac.uk>
wrote:> On the guest OS, the actually devices are sda, and not hda.
> [root@ignis log]# df -hl
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/sda2             9.7G  8.4G  817M  92% /
> none                 1004M     0 1004M   0% /dev/shm
> /dev/sda1              12G   10G  1.1G  91% /mnt/rh9
> /dev/sda5             112G   66G   40G  63% /disks/ignis1
>
> Are you saying that the full virtualised loader (HVM?) cannot support sda?
I''m saying that the OS running on HVM domU will see a different
hardware than the original one. It will see the virtual disk as hda
(an IDE disk), and not sda. At least that''s the case with older
kernels..
>
>
> Regarding the other command on the use of live CD/USB?
> I don''t quite follow the use on that.
>
> The main objective I am trying to achieve is to flexibly transfer a running
service to run on a xen server,
> in the hope that we do not need to redo a fresh installation and its
layered applications.
> This will be useful so we can save time, but also some applications may not
easily be redone due to departure of staff who set them up.
Are you familiar with backup system? The recommended way to perform
backup is to make sure that the data remains the same (unchanged) when
backup process occurs. That''s why good backup software make use of LVM
snapshot, Windows Volume Shadow Copy, or application-specific backup
strategy.
>
> If we use live CD/USB, can you tell how to transfer a running service to
run as a guest OS?
Same way. The idea is that when dd-ing from a disk, the "original"
disk must NOT have any filesystem mounted to prevent corruption. Note
that this is a different problem from being unable to boot.

-- 
Fajar

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

Xen users - Jan 2010 - Full Virtualised DomU Hang on Boot

[Xen-users] Full Virtualised DomU Hang on Boot

[Xen-users] Full Virtualised DomU Hang on Boot

Re: [Xen-users] Full Virtualised DomU Hang on Boot

Re: [Xen-users] Full Virtualised DomU Hang on Boot

RE: [Xen-users] Full Virtualised DomU Hang on Boot

RE: [Xen-users] Full Virtualised DomU Hang on Boot

Re: [Xen-users] Full Virtualised DomU Hang on Boot