thr3ads.net - Xen devel - [Xen-devel] xm-test with vmx failes sanity checks [Jan 2006]

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

Adam Wendt

2006-Jan-29 12:55 UTC

[Xen-devel] xm-test with vmx failes sanity checks

When I try running runtest.sh after succesfully building xm-test with
--enable-vmx-support it fails with:

Running sanity checks...
REASON: Timed out waiting for console
Sanity checks failed.

This is on dual core presler cpu, 64bit host linux

And if I manually try ''xm console 1'' it definitly does hang.

Below I''ve provided output from xend.log and qemu-dm.log, are there
other logs I
could provide? Other tests I can run? Debug options to enable?

Here is the messages in xend.log:

[2006-01-29 12:34:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:177)
XendDomainInfo.create([''vm'', [''name'',
''01_domu_proc-1138566851''], [''m
emory'', ''64''], [''vcpus'',
''1''], [''image'', [''vmx'',
[''kernel'',
''/usr/lib/xen/boot/vmxloader''],
[''device_model'',
''/usr/lib64/xen/bin/qemu-dm'']
, [''vcpus'', ''1''], [''boot'',
''c''], [''serial'', ''pty''],
[''nographic'', ''1'']]],
[''device'', [''vbd'',
[''uname'', ''file:/data/xen/xmtest01-bk/tools/x
m-test/ramdisk/disk.img''], [''dev'',
''ioemu:hda''], [''mode'',
''w'']]]])
[2006-01-29 12:34:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:282)
parseConfig:
config is [''vm'', [''name'',
''01_domu_proc-1138566851''], [''
memory'', ''64''], [''vcpus'',
''1''], [''image'', [''vmx'',
[''kernel'',
''/usr/lib/xen/boot/vmxloader''],
[''device_model'',
''/usr/lib64/xen/bin/qemu-dm''
], [''vcpus'', ''1''],
[''boot'', ''c''], [''serial'',
''pty''], [''nographic'',
''1'']]],
[''device'', [''vbd'',
[''uname'', ''file:/data/xen/xmtest01-bk/tools/
xm-test/ramdisk/disk.img''], [''dev'',
''ioemu:hda''], [''mode'',
''w'']]]]
[2006-01-29 12:34:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:376)
parseConfig:
result is {''ssidref'': None, ''uuid'': None,
''on_crash'': No
ne, ''on_reboot'': None, ''image'':
[''vmx'', [''kernel'',
''/usr/lib/xen/boot/vmxloader''],
[''device_model'',
''/usr/lib64/xen/bin/qemu-dm''],
[''vcpus
'', ''1''], [''boot'',
''c''], [''serial'', ''pty''],
[''nographic'', ''1'']],
''on_poweroff'':
None, ''cpus'': None, ''name'':
''01_domu_proc-1138566851'', ''bac
kend'': [], ''vcpus'': 1,
''cpu_weight'': None, ''vcpu_avail'': None,
''memory'': 64,
''device'': [(''vbd'', [''vbd'',
[''uname'', ''file:/data/xen/xmtest01
-bk/tools/xm-test/ramdisk/disk.img''], [''dev'',
''ioemu:hda''], [''mode'',
''w'']])],
''bootloader'': None, ''cpu'': None,
''maxmem'': None}
[2006-01-29 12:34:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:1130)
XendDomainInfo.construct: None 0
[2006-01-29 12:34:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:1162)
XendDomainInfo.initDomain: 1 1.0
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: cdrom, val: None
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: boot, val: c
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: fda, val: None
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: fdb, val: None
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: nic-ne2000, val: None
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: enable-audio, val: None
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: localtime, val: None
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: serial, val: pty
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: std-vga, val: None
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: isa, val: None
[2006-01-29 12:34:11 xend] DEBUG (image:266) args: vcpus, val: 1
[2006-01-29 12:34:11 xend] DEBUG (balloon:84) Balloon: free 2630; need 66; done.
[2006-01-29 12:34:11 xend] INFO (image:133) buildDomain os=vmx dom=1 vcpus=1
[2006-01-29 12:34:11 xend] INFO (image:220) VMX device model port: 3
[2006-01-29 12:34:11 xend] DEBUG (image:224) dom            = 1
[2006-01-29 12:34:11 xend] DEBUG (image:225) image         
/usr/lib/xen/boot/vmxloader
[2006-01-29 12:34:11 xend] DEBUG (image:226) control_evtchn = 3
[2006-01-29 12:34:11 xend] DEBUG (image:227) store_evtchn   = 1
[2006-01-29 12:34:11 xend] DEBUG (image:228) memsize        = 64
[2006-01-29 12:34:11 xend] DEBUG (image:229) vcpus          = 1
[2006-01-29 12:34:11 xend] DEBUG (image:230) acpi           = 0
[2006-01-29 12:34:11 xend] DEBUG (image:231) apic           = 0
[2006-01-29 12:34:11 xend] DEBUG (image:409) vmx shutdown watch registered
[2006-01-29 12:34:11 xend] DEBUG (DevController:103) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'': ''/local/domain/0/
backend/vbd/1/768''} to /local/domain/1/device/vbd/768.
[2006-01-29 12:34:11 xend] DEBUG (DevController:105) DevController: writing
{''domain'': ''01_domu_proc-1138566851'',
''frontend'': ''/local/doma
in/1/device/vbd/768'', ''dev'':
''ioemu:hda'', ''state'': ''1'',
''params'':
''/data/xen/xmtest01-bk/tools/xm-test/ramdisk/disk.img'',
''mode'': ''w'', ''fr
ontend-id'': ''1'', ''type'':
''file''} to /local/domain/0/backend/vbd/1/768.
[2006-01-29 12:34:11 xend] INFO (image:352) spawning device models:
/usr/lib64/xen/bin/qemu-dm [''/usr/lib64/xen/bin/qemu-dm'',
''-d'', ''1'', ''
-p'', ''3'', ''-m'',
''64'', ''-boot'', ''c'',
''-serial'', ''pty'',
''-vcpus'', ''1'',
''-domain-name'', ''01_domu_proc-1138566851'',
''-hda'', ''/data/xen/xmtest0
1-bk/tools/xm-test/ramdisk/disk.img'', ''-nics'',
''0'', ''-nographic'']
[2006-01-29 12:34:11 xend] INFO (image:354) device model pid: 7486
[2006-01-29 12:34:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:663) Storing VM
details: {''ssidref'': ''0'',
''uuid'': ''4e8c07da-6c26-e889-84f5
-73f929132a2d'', ''on_reboot'':
''restart'', ''start_time'':
''1138566851.35'',
''on_poweroff'': ''destroy'',
''name'': ''01_domu_proc-1138566851'',
''vcpus
'': ''1'', ''vcpu_avail'':
''1'', ''memory'': ''64'',
''on_crash'': ''restart'',
''image'': ''(vmx
(kernel /usr/lib/xen/boot/vmxloader) (device_model /usr/l
ib64/xen/bin/qemu-dm) (vcpus 1) (boot c) (serial pty) (nographic 1))'',
''maxmem'':
''64''}
[2006-01-29 12:34:11 xend.XendDomainInfo] DEBUG (XendDomainInfo:688) Storing
domain details: {''console/port'': ''2'',
''name'': ''01_domu_proc-1
138566851'', ''console/limit'':
''1048576'', ''vm'':
''/vm/4e8c07da-6c26-e889-84f5-73f929132a2d'',
''domid'': ''1'',
''cpu/0/availability'':
''online'', ''m
emory/target'': ''65536'',
''store/ring-ref'': ''679105'',
''store/port'': ''1''}
[2006-01-29 12:34:11 xend] DEBUG (image:432) vmx_shutdown fired, shutdown
reason=None
[2006-01-29 12:34:11 xend] DEBUG (DevController:132) Waiting for devices vif.
[2006-01-29 12:34:11 xend] DEBUG (DevController:132) Waiting for devices usb.
[2006-01-29 12:34:11 xend] DEBUG (DevController:132) Waiting for devices vbd.
[2006-01-29 12:34:11 xend] DEBUG (DevController:138) Waiting for 768.
[2006-01-29 12:34:11 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vbd/1/768/hotplug-status.
[2006-01-29 12:34:11 xend] DEBUG (DevController:403) hotplugStatusCallback
/local/domain/0/backend/vbd/1/768/hotplug-status.
[2006-01-29 12:34:11 xend] DEBUG (DevController:417) hotplugStatusCallback 1.
[2006-01-29 12:34:11 xend] DEBUG (DevController:132) Waiting for devices pci.
[2006-01-29 12:34:11 xend] DEBUG (DevController:132) Waiting for devices
ioports.
[2006-01-29 12:34:11 xend] DEBUG (DevController:132) Waiting for devices vtpm.
[2006-01-29 12:34:11 xend] INFO (XendDomain:360) Domain 01_domu_proc-1138566851
(1) unpaused.

And qemu-dm.log:
domid: 1
eport: 3
qemu: the number of cpus is 1
shared page at pfn:4428, mfn: a5894
char device redirected to /dev/pts/0
False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, count:
0, size: 0
VMXAssist Loader
Loading ROMBIOS ...
Loading Cirrus VGABIOS ...
Loading VMXAssist ...
Go ...
VMXAssist (Jan 29 2006)
Memory size 64 MB
E820 map:
0000000000000000 - 000000000009F800 (RAM)
000000000009F800 - 00000000000A0000 (Reserved)
00000000000A0000 - 00000000000C0000 (Type 16)
00000000000F0000 - 0000000000100000 (Reserved)
0000000000100000 - 0000000003FFE000 (RAM)
0000000003FFF000 - 0000000004000000 (Type 17)
0000000003FFE000 - 0000000003FFF000 (Type 18)
0000000004000000 - 0000000004003000 (ACPI NVS)
0000000004003000 - 000000000400D000 (ACPI Data)
00000000FEC00000 - 0000000100000000 (Type 16)

Start BIOS ...
Starting emulated 16-bit real-mode: ip=F000:FFF0
 rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
VMX_PIT:guest init pit channel 0!
VMX_PIT:pass info 0xc00e90b to HV!
VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $
VMXAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $

ata0-0: PCHS=64/8/32 translation=none LCHS=64/8/32
ata0 master: QEMU HARDDISK ATA-2 Hard-Disk (8 MBytes)
ata0  slave: Unknown device
ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
ata1  slave: Unknown device

Booting from Hard Disk...
int13_harddisk: function 15, unmapped device for ELDL=81
*** int 15h function AX=EC00, BX=0002 not yet supported!
KBD: unsupported int 16h function 03
int13_harddisk: function 15, unmapped device for ELDL=81
int13_harddisk: function 02, unmapped device for ELDL=81
int13_harddisk: function 41, unmapped device for ELDL=81
VMX_PIT:guest init pit channel 0!
VMX_PIT:pass info 0xc0012a5 to HV!
VMX_PIT:guest init pit channel 0!
VMX_PIT:pass info 0xc0012a5 to HV!





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

Adam Wendt

2006-Jan-29 14:49 UTC

head link

Re: [Xen-devel] xm-test with vmx failes sanity checks

Is it possible to build 32bit disk.img from a 64bit host? I''d rather
not have to
reinstall a 32bit host, or I guess I could just run a 32bit guest on a 64bit
kernel and compile disk.img from there?

Thanks,

Adam Wendt
IPCoast, Inc.

On Sun, 29 Jan 2006 14:40 , Daniel Stekloff <dsteklof@us.ibm.com> sent:
>On Sunday 29 January 2006 04:55, Adam Wendt wrote:
>> When I try running runtest.sh after succesfully building xm-test with
>> --enable-vmx-support it fails with:
>>
>> Running sanity checks...
>> REASON: Timed out waiting for console
>> Sanity checks failed.
>>
>> This is on dual core presler cpu, 64bit host linux
>
>
>Did you build the xm-list disk.img on your 64bit host with a 64bit kernel? I
>didn''t think 64bit guests worked for hvm yet? Could you try
building a 32bit
>disk.img and see if that works? 
>
>You can manually load the disk.img with xmexample.vmx and see if it works 
>before running tests. 
>
>Thanks,
>
>Dan
>




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

Daniel Stekloff

2006-Jan-29 22:40 UTC

head link

Re: [Xen-devel] xm-test with vmx failes sanity checks

On Sunday 29 January 2006 04:55, Adam Wendt wrote:> When I try running runtest.sh after succesfully building xm-test with
> --enable-vmx-support it fails with:
>
> Running sanity checks...
> REASON: Timed out waiting for console
> Sanity checks failed.
>
> This is on dual core presler cpu, 64bit host linux

Did you build the xm-list disk.img on your 64bit host with a 64bit kernel? I 
didn''t think 64bit guests worked for hvm yet? Could you try building a
32bit
disk.img and see if that works? 

You can manually load the disk.img with xmexample.vmx and see if it works 
before running tests. 

Thanks,

Dan

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

Daniel Stekloff

2006-Jan-30 00:58 UTC

head link

Re: [Xen-devel] xm-test with vmx failes sanity checks

On Sunday 29 January 2006 06:49, Adam Wendt wrote:> Is it possible to build 32bit disk.img from a 64bit host? I''d
rather not
> have to reinstall a 32bit host, or I guess I could just run a 32bit guest
> on a 64bit kernel and compile disk.img from there?

You should be able to build one on a 32bit guest. I imagine you can make one 
on your host too.

It would be cool if Xensource could host an initrd and disk.img on their 
server somewhere, then xm-test could look for it and wget if available before 
starting down the whole rebuild the world case.

Thanks,

Dan


> Thanks,
>
> Adam Wendt
> IPCoast, Inc.
>
> On Sun, 29 Jan 2006 14:40 , Daniel Stekloff <dsteklof@us.ibm.com>
sent:
> >On Sunday 29 January 2006 04:55, Adam Wendt wrote:
> >> When I try running runtest.sh after succesfully building xm-test
with
> >> --enable-vmx-support it fails with:
> >>
> >> Running sanity checks...
> >> REASON: Timed out waiting for console
> >> Sanity checks failed.
> >>
> >> This is on dual core presler cpu, 64bit host linux
> >
> >Did you build the xm-list disk.img on your 64bit host with a 64bit
kernel?
> > I didn''t think 64bit guests worked for hvm yet? Could you try
building a
> > 32bit disk.img and see if that works?
> >
> >You can manually load the disk.img with xmexample.vmx and see if it
works
> >before running tests.
> >
> >Thanks,
> >
> >Dan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Ewan Mellor

2006-Jan-31 06:09 UTC

head link

Re: [Xen-devel] xm-test with vmx failes sanity checks

On Sun, Jan 29, 2006 at 04:58:31PM -0800, Daniel Stekloff wrote:
> It would be cool if Xensource could host an initrd and disk.img on their 
> server somewhere, then xm-test could look for it and wget if available
before
> starting down the whole rebuild the world case.
I believe that XenSource have agreed to do that.  If someone could
provide known good versions of the images, make sure that xm-test knows
how to look for the ramdisk version that matches the xm-test version,
and preferably make sure that wget is told to continue downloads rather than
starting again from scratch, so that our server doesn''t melt, then
I''m sure
we could host images there.

Ewan.

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

Xen devel - Jan 2006 - xm-test with vmx failes sanity checks

[Xen-devel] xm-test with vmx failes sanity checks

Re: [Xen-devel] xm-test with vmx failes sanity checks

Re: [Xen-devel] xm-test with vmx failes sanity checks

Re: [Xen-devel] xm-test with vmx failes sanity checks

Re: [Xen-devel] xm-test with vmx failes sanity checks