Xm-test fails to pass sanity checks in hvm mode

Xm-test fails to pass sanity checks in hvm mode

[Lynn Bendixsen]

I am attempting to run xm-test in hvm mode.  I built successfully and then started runtests.sh. After about 30 seconds an error message appeared "Timed out connecting to console" or similar.  I then used xmexample.hvm to manually try and start disk.img fully virtualized and the following was the last few lines on the VMs terminal:
 
VFS: Cannot open root device "0301" or unknown-block(3,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)

Has anyone else seen this issue?  Did I do something wrong?

I built on SLES 10 beta 9 using that kernel for --with-hvm-kernel.

Regards,
 Lynn





Lynn Bendixsen
Software Engineer
lbendixs@novell.com

Re: Xm-test fails to pass sanity checks in hvm mode

[Daniel Stekloff]

On Tue, 2006-04-11 at 11:06 -0600, Lynn Bendixsen wrote:
> I am attempting to run xm-test in hvm mode.  I built successfully and then started runtests.sh. After about 30 seconds an error message appeared "Timed out connecting to console" or similar.  I then used xmexample.hvm to manually try and start disk.img fully virtualized and the following was the last few lines on the VMs terminal:
>  
> VFS: Cannot open root device "0301" or unknown-block(3,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
> 
> Has anyone else seen this issue?  Did I do something wrong?
> 
> I built on SLES 10 beta 9 using that kernel for --with-hvm-kernel.


Hi, 

I just built the latest tip and was able to run the disk.img manually. I
was also able to run the _sanity tests from xm-test - all in hvm mode.

Questions:

1) Could you provide your config file - xmexample.hvm - that you're
using? 

2) Is the SLES10 beta 9 kernel a non-Xen kernel? 

3) Can you boot a non-xm-test disk image fully virtualized? 

Thanks,

Dan

Re: Xm-test fails to pass sanity checks in hvm mode

[Lynn Bendixsen]

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

>> I am attempting to run xm- test in hvm mode.  I built successfully and then 
> started runtests.sh. After about 30 seconds an error message appeared "Timed 
> out connecting to console" or similar.  I then used xmexample.hvm to manually 
> try and start disk.img fully virtualized and the following was the last few 
> lines on the VMs terminal:
>>  
>> VFS: Cannot open root device "0301" or unknown- block(3,1)
>> Please append a correct "root=" boot option
>> Kernel panic -  not syncing: VFS: Unable to mount root fs on unknown- block(3,1)
>> Has anyone else seen this issue?  Did I do something wrong?
>> I built on SLES 10 beta 9 using that kernel for -- with- hvm- kernel.
> 
> Hi, 
> 
> I just built the latest tip and was able to run the disk.img manually. I
> was also able to run the _sanity tests from xm- test -  all in hvm mode.
> 
> Questions:
> 1) Could you provide your config file -  xmexample.hvm -  that you're
> using? 
> 2) Is the SLES10 beta 9 kernel a non- Xen kernel? 
> 3) Can you boot a non- xm- test disk image fully virtualized? 
> 
> Thanks,
> Dan
>

Hi Dan,

Answers:
1) attached - All I changed from my original file was the "file=" line and possibly the memory.
2) yes
3) yes

TIA, :)
Lynn


[-- Attachment #2: xmexample.hvm --]
[-- Type: application/octet-stream, Size: 5606 bytes --]

#  -*- 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.
memory = 128

# A name for your domain. All domains must have different names.
name = "ExampleHVMDomain"

#-----------------------------------------------------------------------------
# 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

# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = ""         # leave to Xen to pick
#cpus = "0"        # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5

# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0' ]
# type=ioemu specify the NIC is an ioemu device not netfront
vif = [ 'type=ioemu, bridge=xenbr0' ]

#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.

#disk = [ 'phy:hda1,hda1,r' ]
disk = [ 'file:/tests/xm-test/ramdisk/disk.img,ioemu:hda,w' ]

#----------------------------------------------------------------------------
# Configure the behaviour when a domain exits.  There are three 'reasons'
# for a domain to stop: poweroff, reboot, and crash.  For each of these you
# may specify:
#
#   "destroy",        meaning that the domain is cleaned up as normal;
#   "restart",        meaning that a new domain is started in place of the old
#                     one;
#   "preserve",       meaning that no clean-up is done until the domain is
#                     manually destroyed (using xm destroy, for example); or
#   "rename-restart", meaning that the old domain is not cleaned up, but is
#                     renamed and a new domain started in its place.
#
# The default is
#
#   on_poweroff = 'destroy'
#   on_reboot   = 'restart'
#   on_crash    = 'restart'
#
# For backwards compatibility we also support the deprecated option restart
#
# restart = 'onreboot' means on_poweroff = 'destroy'
#                            on_reboot   = 'restart'
#                            on_crash    = 'destroy'
#
# restart = 'always'   means on_poweroff = 'restart'
#                            on_reboot   = 'restart'
#                            on_crash    = 'restart'
#
# restart = 'never'    means on_poweroff = 'destroy'
#                            on_reboot   = 'destroy'
#                            on_crash    = 'destroy'

#on_poweroff = 'destroy'
#on_reboot   = 'restart'
#on_crash    = 'restart'

#============================================================================

# New stuff
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'

#-----------------------------------------------------------------------------
# Disk image for 
#cdrom=

#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d) 
#boot=[a|c|d]
#-----------------------------------------------------------------------------
#  write to temporary files instead of disk image files
#snapshot=1

#----------------------------------------------------------------------------
# enable SDL library for graphics, default = 0
sdl=0

#----------------------------------------------------------------------------
# enable VNC library for graphics, default = 1
vnc=0

#----------------------------------------------------------------------------
# enable spawning vncviewer(only valid when vnc=1), default = 1
vncviewer=1

#----------------------------------------------------------------------------
# no graphics, use serial port
#nographic=0

#----------------------------------------------------------------------------
# enable stdvga, default = 0 (use cirrus logic device model)
stdvga=0

#-----------------------------------------------------------------------------
#   serial port re-direct to pty deivce, /dev/pts/n 
#   then xm console or minicom can connect
serial='pty'

#----------------------------------------------------------------------------
# enable ne2000, default = 0(use pcnet)
ne2000=0


#-----------------------------------------------------------------------------
#   enable audio support
#audio=1


#-----------------------------------------------------------------------------
#    set the real time clock to local time [default=0 i.e. set to utc]
#localtime=1


#-----------------------------------------------------------------------------
#    start in full screen
#full-screen=1   

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Xm-test fails to pass sanity checks in hvm mode

[Daniel Stekloff]

On Tue, 2006-04-11 at 14:21 -0600, Lynn Bendixsen wrote:
> >> I am attempting to run xm- test in hvm mode.  I built successfully and then 
> > started runtests.sh. After about 30 seconds an error message appeared "Timed 
> > out connecting to console" or similar.  I then used xmexample.hvm to manually 
> > try and start disk.img fully virtualized and the following was the last few 
> > lines on the VMs terminal:
> >>  
> >> VFS: Cannot open root device "0301" or unknown- block(3,1)
> >> Please append a correct "root=" boot option
> >> Kernel panic -  not syncing: VFS: Unable to mount root fs on unknown- block(3,1)
> >> Has anyone else seen this issue?  Did I do something wrong?
> >> I built on SLES 10 beta 9 using that kernel for -- with- hvm- kernel.
> > 
> > Hi, 
> > 
> > I just built the latest tip and was able to run the disk.img manually. I
> > was also able to run the _sanity tests from xm- test -  all in hvm mode.
> > 
> > Questions:
> > 1) Could you provide your config file -  xmexample.hvm -  that you're
> > using? 
> > 2) Is the SLES10 beta 9 kernel a non- Xen kernel? 
> > 3) Can you boot a non- xm- test disk image fully virtualized? 
> > 
> > Thanks,
> > Dan
> >
> 
> Hi Dan,
> 
> Answers:
> 1) attached - All I changed from my original file was the "file=" line and possibly the memory.
> 2) yes
> 3) yes


It won't boot an SMP kernel. I bet the default kernel you're building
with is SMP, right? HVM doesn't support SMP yet, I believe, although
Intel people are working on that. I haven't debugged any further but
I've confirmed that an SMP kernel on the disk.img won't boot.

Thanks,

Dan

RE: Xm-test fails to pass sanity checks in hvm mode

[Li, Xin B]

>
>It won't boot an SMP kernel. I bet the default kernel you're building
>with is SMP, right? HVM doesn't support SMP yet, I believe, although
>Intel people are working on that. I haven't debugged any further but
>I've confirmed that an SMP kernel on the disk.img won't boot.

I'm not in the context, but still have some comments here :-).
Basically we *can* boot a SMP kernel in a UP VMX domain. To boot up a
SMP kernel, we need vcpus > 1, acpi = 1 and apic = 1 in the config file,
or you are just running a UP VMX domain.
Some old version Linux SMP kernel can *not* boot in a SMP VMX domain,
but the root cause is PAE support code, which is mixed with SMP code in
Linux kernel :-(, newer version Linux, like 2.6.12+, should work.
Actually we have a fix to this PAE issue, but more tests needed.

-Xin


>
>Thanks,
>
>Dan
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>

RE: Xm-test fails to pass sanity checks in hvm mode

[Daniel Stekloff]

On Wed, 2006-04-12 at 05:59 +0800, Li, Xin B wrote:
> >
> >It won't boot an SMP kernel. I bet the default kernel you're building
> >with is SMP, right? HVM doesn't support SMP yet, I believe, although
> >Intel people are working on that. I haven't debugged any further but
> >I've confirmed that an SMP kernel on the disk.img won't boot.
> 
> I'm not in the context, but still have some comments here :-).
> Basically we *can* boot a SMP kernel in a UP VMX domain. To boot up a
> SMP kernel, we need vcpus > 1, acpi = 1 and apic = 1 in the config file,
> or you are just running a UP VMX domain.
> Some old version Linux SMP kernel can *not* boot in a SMP VMX domain,
> but the root cause is PAE support code, which is mixed with SMP code in
> Linux kernel :-(, newer version Linux, like 2.6.12+, should work.
> Actually we have a fix to this PAE issue, but more tests needed.


Are you using the qemu-dm that's in the xen-unstable tree? 

I can't get the SMP kernel to boot. I got a 2.6.16 SMP kernel, made sure
the options were set in the config, and I get the following error
repeatedly:

"Unknown interrupt or fault at EIP 00000060 c0100295 0000294"

Either way, if you'd like to do more testing using xm-test - then it
will need to be patched to have the correct config options.

Thanks,

Dan

RE: Xm-test fails to pass sanity checks in hvm mode

[Li, Xin B]

>> I'm not in the context, but still have some comments here :-).
>> Basically we *can* boot a SMP kernel in a UP VMX domain. To boot up a
>> SMP kernel, we need vcpus > 1, acpi = 1 and apic = 1 in the 
>config file,
>> or you are just running a UP VMX domain.
>> Some old version Linux SMP kernel can *not* boot in a SMP VMX domain,
>> but the root cause is PAE support code, which is mixed with 
>SMP code in
>> Linux kernel :-(, newer version Linux, like 2.6.12+, should work.
>> Actually we have a fix to this PAE issue, but more tests needed.
>
>
>Are you using the qemu-dm that's in the xen-unstable tree? 
>
>I can't get the SMP kernel to boot. I got a 2.6.16 SMP kernel, 
>made sure
>the options were set in the config, and I get the following error
>repeatedly:
>
>"Unknown interrupt or fault at EIP 00000060 c0100295 0000294"
>

Your SMP kernel is PAE enabled, so add pae = 1 to your config file.
Or, compile a none PAE SMP kernel.
-Xin



>Either way, if you'd like to do more testing using xm-test - then it
>will need to be patched to have the correct config options.
>
>Thanks,
>
>Dan
>
>
>
>

RE: Xm-test fails to pass sanity checks in hvm mode

[Daniel Stekloff]

On Wed, 2006-04-12 at 06:32 +0800, Li, Xin B wrote:
> >> I'm not in the context, but still have some comments here :-).
> >> Basically we *can* boot a SMP kernel in a UP VMX domain. To boot up a
> >> SMP kernel, we need vcpus > 1, acpi = 1 and apic = 1 in the 
> >config file,
> >> or you are just running a UP VMX domain.
> >> Some old version Linux SMP kernel can *not* boot in a SMP VMX domain,
> >> but the root cause is PAE support code, which is mixed with 
> >SMP code in
> >> Linux kernel :-(, newer version Linux, like 2.6.12+, should work.
> >> Actually we have a fix to this PAE issue, but more tests needed.
> >
> >
> >Are you using the qemu-dm that's in the xen-unstable tree? 
> >
> >I can't get the SMP kernel to boot. I got a 2.6.16 SMP kernel, 
> >made sure
> >the options were set in the config, and I get the following error
> >repeatedly:
> >
> >"Unknown interrupt or fault at EIP 00000060 c0100295 0000294"
> >
> 
> Your SMP kernel is PAE enabled, so add pae = 1 to your config file.
> Or, compile a none PAE SMP kernel.


I do have pae=1.

RE: Xm-test fails to pass sanity checks in hvm mode

[Li, Xin B]

>
>I do have pae=1.

Are you using 32 bit xen? We can not run a PAE SMP kernel on it.

-Xin


>
>
>

RE: Xm-test fails to pass sanity checks in hvm mode

[Daniel Stekloff]

On Wed, 2006-04-12 at 06:38 +0800, Li, Xin B wrote:
> >
> >I do have pae=1.
> 
> Are you using 32 bit xen? We can not run a PAE SMP kernel on it.


D'oh!... my bad. <grin> 

I still can't get it to work - 32bit system with a 32bit 2.6.15 SMP
kernel. This is with the xm-test disk.img.

I'll need to make a new disk image (not xm-test disk.img) tomorrow with
an SMP kernel and try again. 

Thanks for your help.

Dan

RE: Xm-test fails to pass sanity checks in hvm mode

[Li, Xin B]

>
>On Wed, 2006-04-12 at 06:38 +0800, Li, Xin B wrote:
>> >
>> >I do have pae=1.
>> 
>> Are you using 32 bit xen? We can not run a PAE SMP kernel on it.
>
>
>D'oh!... my bad. <grin> 
>
>I still can't get it to work - 32bit system with a 32bit 2.6.15 SMP
>kernel. This is with the xm-test disk.img.
>
>I'll need to make a new disk image (not xm-test disk.img) tomorrow with
>an SMP kernel and try again. 

You'll get blocked by a SMP bug on 32bit xen, use this patch should get
you pass.

diff -r edefe24d78bd xen/arch/x86/hvm/vmx/vmx.c
--- a/xen/arch/x86/hvm/vmx/vmx.c        Tue Apr 11 12:51:48 2006 +0100
+++ b/xen/arch/x86/hvm/vmx/vmx.c        Wed Apr 12 06:35:11 2006 +0800
@@ -1472,7 +1472,7 @@ static int vmx_set_cr0(unsigned long val
             }
         }

-        clear_all_shadow_status(v->domain);
+        //clear_all_shadow_status(v->domain);
         if ( vmx_assist(v, VMX_ASSIST_INVOKE) ) {
             set_bit(VMX_CPU_STATE_ASSIST_ENABLED,
&v->arch.hvm_vmx.cpu_state);
             __vmread(GUEST_RIP, &eip);

Hope a better fix will be sent out soon.

-Xin