Re: [Xen-devel] problem in booting hvm guest on x86_64 dual-core VT machine

[Steve Dobbelstein <steved@xxxxxxxxxx>]

"sanjay kushwaha" <sanjay.kushwaha@xxxxxxxxx> wrote on 09/11/2006 03:22:57
PM:

> Hi Folks,
> I am working with the Xen changeset 11437. I am trying to boot a RHEL
> 2.6.9-22.EL (non-smp) kernel into a guest VM on this dual-core 64 bit
> machine (dom0 is running smp 2.6.16.13 kernel) . But the guest VM
> doesn't boot. apparently it gets stuck during the kernel boot process.
> I get the grub menu and when I select the specified kernel I get the
> following message
>
>   Booting 'RHEL'
>
> root (hd0,0)
>  Filesystem type is ext2fs, partition type 0x83
> kernel /boot/vmlinuz-2.6.9-22.EL ro root=/dev/hda1 console=ttyS0,
> 115200 console
> =tty0 acpi=off noapic nolapic
>    [Linux-bzImage, setup=0x1400, size=0x1af739]
>
>
> I don;t get any output after the above message. The boot process gets
> stuck here.
> I also observe that the "xm list" command shows that the guest VM is
> hogging most of the CPU cycles.
>
> [root@vt2 ksanjay]# xm lis
> Name                              ID Mem(MiB) VCPUs State  Time(s)
> Domain-0                           0      250     2 r-----    47.8
> vm                                        1      256     1 r-----
2981.9
> [root@vt2 ksanjay]#
>
> Is anybody else experiencing this problem? Does anyone know how to fix
it?
> The same kernel boots fine with an older version of Xen (changeset 9379).
>
> Thanks,
> Sanjay
>
> PS: below is the "xm info" and guest config file
>
> [root@vt2 ksanjay]# xm info
> host                   : vt2
> release                : 2.6.16.13-xen
> version                : #1 SMP Sun Sep 10 15:07:03 EDT 2006
> machine                : x86_64
> nr_cpus                : 2
> nr_nodes               : 1
> sockets_per_node       : 1
> cores_per_socket       : 2
> threads_per_core       : 1
> cpu_mhz                : 2999
> hw_caps                :
> bfebfbff:20100800:00000000:00000180:0000e4f5:00000000:00000001
> total_memory           : 1011
> free_memory            : 457
> xen_major              : 3
> xen_minor              : 0
> xen_extra              : -unstable
> xen_caps               : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p
> hvm-3.0-x86_64
> xen_pagesize           : 4096
> platform_params        : virt_start=0xffff800000000000
> xen_changeset          : Fri Sep  8 18:46:54 2006 -0700
11437:7acaba46e15e
> cc_compiler            : gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)
> cc_compile_by          : root
> cc_compile_domain      :
> cc_compile_date        : Mon Sep 11 15:08:19 EDT 2006
> xend_config_format     : 2
> [root@vt2 ksanjay]#
>
> [root@vt2 ksanjay]# cat xmexample.hvm
> #  -*- mode: python; -*-
>
#============================================================================

> # Python configuration setup for 'xm create'.
> # This script sets the parameters used when a domain is created using
> 'xm create'.
> # You use a separate script for each domain you want to create, or
> # you can set the parameters for the domain on the xm command line.
>
#============================================================================

>
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>     arch_libdir = 'lib64'
> else:
>     arch_libdir = 'lib'
>
>
#----------------------------------------------------------------------------

> # Kernel image file.
> kernel = "/usr/lib/xen/boot/hvmloader"
>
> # The domain build function. HVM domain uses 'hvm'.
> builder='hvm'
>
> # Initial memory allocation (in megabytes) for the new domain.
> #
> # WARNING: Creating a domain with insufficient memory may cause out of
> #          memory errors. The domain needs enough memory to boot kernel
> #          and modules. Allocating less than 32MBs is not recommended.
> memory = 256
>
> # Shadow pagetable memory for the domain, in MB.
> # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
> shadow_memory = 8
>
> # A name for your domain. All domains must have different names.
> name = "vm"
>
> # 128-bit UUID for the domain.  The default behavior is to generate a new
UUID
> # on each call to 'xm create'.
> #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"
>
>
#-----------------------------------------------------------------------------

> # the number of cpus guest platform has, default=1
> vcpus=1
>
> # enable/disable HVM guest PAE, default=0 (disabled)
> #pae=0
>
> # enable/disable HVM guest ACPI, default=0 (disabled)
> acpi=0
>
> # enable/disable HVM guest APIC, default=0 (disabled)
> apic=0
>
> vif = [ 'type=ioemu, bridge=xenbr0' ]
>
> disk = [ 'file:/home/ksanjay/test-2030_16_63.img,ioemu:hda,w' ]
> device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
>
> sdl=0
>
> vnc=0
>
> nographic=0
>
> stdvga=0
>
> serial='pty'
>
> [root@vt2 ksanjay]#

Set "pae=1" in your HVM configuration file (xmexample.hvm).  Not sure why
that is, but that's what I do to get my 64-bit guests to boot.

Steve D.


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