* Error while running the xm test suite: Cannot handle page request order 0!
@ 2008-09-16 16:33 Stefan Berger
2008-09-16 16:58 ` Keir Fraser
0 siblings, 1 reply; 13+ messages in thread
From: Stefan Berger @ 2008-09-16 16:33 UTC (permalink / raw)
To: xen-devel; +Cc: Keir Fraser
[-- Attachment #1.1: Type: text/plain, Size: 4016 bytes --]
Hello!
It seems there is an error occurring in the hypervisor while running the
xm-test suite on an i386 machine:
[...]
(XEN) Init. ramdisk: c06cb000->c0c3e000
(XEN) Phys-Mach map: c0c3e000->c0d3e000
(XEN) Start info: c0d3e000->c0d3e474
(XEN) Page tables: c0d3f000->c0d4c000
(XEN) Boot stack: c0d4c000->c0d4d000
(XEN) TOTAL: c0000000->c1000000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM: .............................done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input
to Xen)
(XEN) Freed 100kB init memory.
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
(XEN) Cannot handle page request order 0!
The results from the test suite look like this on that machine:
FAIL: 02_block_attach_file_device_pos.test
FAIL: 11_create_concurrent_pos.test
FAIL: 12_create_concurrent_stress_pos.test
FAIL: 13_create_multinic_pos.test
FAIL: 14_create_blockroot_pos.test
FAIL: 15_create_smallmem_pos.test
FAIL: 16_create_smallmem_neg.test
FAIL: 01_destroy_basic_pos.test
FAIL: 05_destroy_byid_pos.test
FAIL: 07_destroy_stale_pos.test
FAIL: 01_enforce_dom0_cpus_basic_pos.test
FAIL: 05_help_nonroot_pos.test
FAIL: 04_list_goodparm_pos.test
FAIL: 06_list_nonroot.test
FAIL: 01_memset_basic_pos.test
FAIL: 03_memset_random_pos.test
FAIL: 04_memset_smallmem_pos.test
FAIL: 01_migrate_localhost_pos.test
XFAIL: 02_network_local_ping_pos.test
FAIL: 03_network_local_tcp_pos.test
FAIL: 04_network_local_udp_pos.test
XFAIL: 05_network_dom0_ping_pos.test
FAIL: 06_network_dom0_tcp_pos.test
FAIL: 07_network_dom0_udp_pos.test
XFAIL: 11_network_domU_ping_pos.test
FAIL: 12_network_domU_tcp_pos.test
FAIL: 13_network_domU_udp_pos.test
FAIL: 01_network_attach_pos.test
FAIL: 02_network_attach_detach_pos.test
FAIL: 03_network_attach_detach_multiple_pos.test
FAIL: 01_pause_basic_pos.test
FAIL: 02_pause_badopt_neg.test
FAIL: 01_reboot_basic_pos.test
FAIL: 02_reboot_badopt_neg.test
FAIL: 01_restore_basic_pos.test
FAIL: 04_restore_withdevices_pos.test
FAIL: 01_save_basic_pos.test
FAIL: 03_save_bogusfile_neg.test
FAIL: 01_sched_credit_weight_cap_pos.test
FAIL: 08_security-acm_xapi.test
FAIL: 01_shutdown_basic_pos.test
FAIL: 02_shutdown_badparm_neg.test
FAIL: 02_sysrq_sync_pos.test
FAIL: 03_sysrq_withreboot_pos.test
FAIL: 01_unpause_basic_pos.test
FAIL: 01_vcpu-disable_basic_pos.test
FAIL: 01_vcpu-pin_basic_pos.test
SKIP: 01_security-acm_basic.test
SKIP: 02_security-acm_dom_start.test
SKIP: 03_security-acm_dom_conflict.test
SKIP: 04_security-acm_dom_res.test
SKIP: 05_security-acm_dom_res_conf.test
SKIP: 06_security-acm_dom_block_attach.test
SKIP: 07_security-acm_pol_update.test
SKIP: 09_security-acm_pol_update.test
SKIP: 10_security-acm_pol_update.test
SKIP: 01_vtpm-list_pos.test
SKIP: 02_vtpm-cat_pcrs.test
SKIP: 03_vtpm-susp_res.test
SKIP: 04_vtpm-loc_migr.test
SKIP: 05_vtpm-loc_migr.test
SKIP: 06_vtpm-susp_res_pcrs.test
SKIP: 07_vtpm-mig_pcrs.test
SKIP: 08_vtpm-mig_pcrs.test
SKIP: 09_vtpm-xapi.test
Stefan
[-- Attachment #1.2: Type: text/html, Size: 4821 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-16 16:33 Error while running the xm test suite: Cannot handle page request order 0! Stefan Berger
@ 2008-09-16 16:58 ` Keir Fraser
2008-09-16 17:09 ` Stefan Berger
0 siblings, 1 reply; 13+ messages in thread
From: Keir Fraser @ 2008-09-16 16:58 UTC (permalink / raw)
To: Stefan Berger, xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 4350 bytes --]
Not enough memory?
-- Keir
On 16/9/08 17:33, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>
> Hello!
>
> It seems there is an error occurring in the hypervisor while running the
> xm-test suite on an i386 machine:
>
> [...]
> (XEN) Init. ramdisk: c06cb000->c0c3e000
> (XEN) Phys-Mach map: c0c3e000->c0d3e000
> (XEN) Start info: c0d3e000->c0d3e474
> (XEN) Page tables: c0d3f000->c0d4c000
> (XEN) Boot stack: c0d4c000->c0d4d000
> (XEN) TOTAL: c0000000->c1000000
> (XEN) ENTRY ADDRESS: c0100000
> (XEN) Dom0 has maximum 4 VCPUs
> (XEN) Scrubbing Free RAM: .............................done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to
> Xen)
> (XEN) Freed 100kB init memory.
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
>
>
> The results from the test suite look like this on that machine:
>
> FAIL: 02_block_attach_file_device_pos.test
> FAIL: 11_create_concurrent_pos.test
> FAIL: 12_create_concurrent_stress_pos.test
> FAIL: 13_create_multinic_pos.test
> FAIL: 14_create_blockroot_pos.test
> FAIL: 15_create_smallmem_pos.test
> FAIL: 16_create_smallmem_neg.test
> FAIL: 01_destroy_basic_pos.test
> FAIL: 05_destroy_byid_pos.test
> FAIL: 07_destroy_stale_pos.test
> FAIL: 01_enforce_dom0_cpus_basic_pos.test
> FAIL: 05_help_nonroot_pos.test
> FAIL: 04_list_goodparm_pos.test
> FAIL: 06_list_nonroot.test
> FAIL: 01_memset_basic_pos.test
> FAIL: 03_memset_random_pos.test
> FAIL: 04_memset_smallmem_pos.test
> FAIL: 01_migrate_localhost_pos.test
> XFAIL: 02_network_local_ping_pos.test
> FAIL: 03_network_local_tcp_pos.test
> FAIL: 04_network_local_udp_pos.test
> XFAIL: 05_network_dom0_ping_pos.test
> FAIL: 06_network_dom0_tcp_pos.test
> FAIL: 07_network_dom0_udp_pos.test
> XFAIL: 11_network_domU_ping_pos.test
> FAIL: 12_network_domU_tcp_pos.test
> FAIL: 13_network_domU_udp_pos.test
> FAIL: 01_network_attach_pos.test
> FAIL: 02_network_attach_detach_pos.test
> FAIL: 03_network_attach_detach_multiple_pos.test
> FAIL: 01_pause_basic_pos.test
> FAIL: 02_pause_badopt_neg.test
> FAIL: 01_reboot_basic_pos.test
> FAIL: 02_reboot_badopt_neg.test
> FAIL: 01_restore_basic_pos.test
> FAIL: 04_restore_withdevices_pos.test
> FAIL: 01_save_basic_pos.test
> FAIL: 03_save_bogusfile_neg.test
> FAIL: 01_sched_credit_weight_cap_pos.test
> FAIL: 08_security-acm_xapi.test
> FAIL: 01_shutdown_basic_pos.test
> FAIL: 02_shutdown_badparm_neg.test
> FAIL: 02_sysrq_sync_pos.test
> FAIL: 03_sysrq_withreboot_pos.test
> FAIL: 01_unpause_basic_pos.test
> FAIL: 01_vcpu-disable_basic_pos.test
> FAIL: 01_vcpu-pin_basic_pos.test
> SKIP: 01_security-acm_basic.test
> SKIP: 02_security-acm_dom_start.test
> SKIP: 03_security-acm_dom_conflict.test
> SKIP: 04_security-acm_dom_res.test
> SKIP: 05_security-acm_dom_res_conf.test
> SKIP: 06_security-acm_dom_block_attach.test
> SKIP: 07_security-acm_pol_update.test
> SKIP: 09_security-acm_pol_update.test
> SKIP: 10_security-acm_pol_update.test
> SKIP: 01_vtpm-list_pos.test
> SKIP: 02_vtpm-cat_pcrs.test
> SKIP: 03_vtpm-susp_res.test
> SKIP: 04_vtpm-loc_migr.test
> SKIP: 05_vtpm-loc_migr.test
> SKIP: 06_vtpm-susp_res_pcrs.test
> SKIP: 07_vtpm-mig_pcrs.test
> SKIP: 08_vtpm-mig_pcrs.test
> SKIP: 09_vtpm-xapi.test
>
>
> Stefan
>
[-- Attachment #1.2: Type: text/html, Size: 5712 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-16 16:58 ` Keir Fraser
@ 2008-09-16 17:09 ` Stefan Berger
2008-09-16 19:03 ` Keir Fraser
0 siblings, 1 reply; 13+ messages in thread
From: Stefan Berger @ 2008-09-16 17:09 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel, xen-devel-bounces
[-- Attachment #1.1: Type: text/plain, Size: 6885 bytes --]
Keir,
memory should not be the problem unless the memory requirements of those
test domains have been increased considerably recently. Here's the upper
part of 'xm dmesg':
\ \/ /___ _ __ |___ /| || | _ _ _ __ ___| |_ __ _| |__ | | ___
\ // _ \ '_ \ |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
/ \ __/ | | | ___) |__ _|__| |_| | | | \__ \ || (_| | |_) | | __/
/_/\_\___|_| |_| |____(_) |_| \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
(XEN) Xen version 3.4-unstable (root@watson.ibm.com) (gcc version 4.3.0
20080428 (Red Hat 4.3.0-8) (GCC) ) Tue Sep 16 07:20:38 EDT 2008
(XEN) Latest ChangeSet: Mon Sep 15 17:10:43 2008 +0100 18482:087008dfb005
(XEN) Command line: dom0_mem=1G
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds
(XEN) EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009e000 (usable)
(XEN) 000000000009e000 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000f7fed380 (usable)
(XEN) 00000000f7fed380 - 00000000f7ff0000 (ACPI data)
(XEN) 00000000f7ff0000 - 00000000f8000000 (reserved)
(XEN) 00000000fec00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000108000000 (usable)
(XEN) System RAM: 4095MB (4193836kB)
(XEN) ACPI: RSDP 000FDFC0, 0014 (r0 IBM )
(XEN) ACPI: RSDT F7FEFF80, 002C (r1 IBM SERBLADE 1000 IBM 45444F43)
(XEN) ACPI: FACP F7FEFF00, 0074 (r1 IBM SERBLADE 1000 IBM 45444F43)
(XEN) ACPI: DSDT F7FED380, 2A22 (r1 IBM SERBLADE 1000 INTL 2002025)
(XEN) ACPI: FACS F7FEFE00, 0040
(XEN) ACPI: APIC F7FEFE40, 0092 (r1 IBM SERBLADE 1000 IBM 45444F43)
(XEN) Xen heap: 9MB (9676kB)
(XEN) Domain heap initialised
The system has 4GB and domain0 gets 1GB.
Stefan
xen-devel-bounces@lists.xensource.com wrote on 09/16/2008 12:58:20 PM:
> Keir Fraser <keir.fraser@eu.citrix.com>
> Sent by: xen-devel-bounces@lists.xensource.com
>
> 09/16/2008 12:58 PM
>
> To
>
> Stefan Berger/Watson/IBM@IBMUS, <xen-devel@lists.xensource.com>
>
> cc
>
> Subject
>
> [Xen-devel] Re: Error while running the xm test suite: Cannot handle
> page request order 0!
>
> Not enough memory?
>
> -- Keir
>
> On 16/9/08 17:33, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>
> Hello!
>
> It seems there is an error occurring in the hypervisor while
> running the xm-test suite on an i386 machine:
>
> [...]
> (XEN) Init. ramdisk: c06cb000->c0c3e000
> (XEN) Phys-Mach map: c0c3e000->c0d3e000
> (XEN) Start info: c0d3e000->c0d3e474
> (XEN) Page tables: c0d3f000->c0d4c000
> (XEN) Boot stack: c0d4c000->c0d4d000
> (XEN) TOTAL: c0000000->c1000000
> (XEN) ENTRY ADDRESS: c0100000
> (XEN) Dom0 has maximum 4 VCPUs
> (XEN) Scrubbing Free RAM: .............................done.
> (XEN) Xen trace buffers: disabled
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen)
> (XEN) Freed 100kB init memory.
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
> (XEN) Cannot handle page request order 0!
>
>
> The results from the test suite look like this on that machine:
>
> FAIL: 02_block_attach_file_device_pos.test
> FAIL: 11_create_concurrent_pos.test
> FAIL: 12_create_concurrent_stress_pos.test
> FAIL: 13_create_multinic_pos.test
> FAIL: 14_create_blockroot_pos.test
> FAIL: 15_create_smallmem_pos.test
> FAIL: 16_create_smallmem_neg.test
> FAIL: 01_destroy_basic_pos.test
> FAIL: 05_destroy_byid_pos.test
> FAIL: 07_destroy_stale_pos.test
> FAIL: 01_enforce_dom0_cpus_basic_pos.test
> FAIL: 05_help_nonroot_pos.test
> FAIL: 04_list_goodparm_pos.test
> FAIL: 06_list_nonroot.test
> FAIL: 01_memset_basic_pos.test
> FAIL: 03_memset_random_pos.test
> FAIL: 04_memset_smallmem_pos.test
> FAIL: 01_migrate_localhost_pos.test
> XFAIL: 02_network_local_ping_pos.test
> FAIL: 03_network_local_tcp_pos.test
> FAIL: 04_network_local_udp_pos.test
> XFAIL: 05_network_dom0_ping_pos.test
> FAIL: 06_network_dom0_tcp_pos.test
> FAIL: 07_network_dom0_udp_pos.test
> XFAIL: 11_network_domU_ping_pos.test
> FAIL: 12_network_domU_tcp_pos.test
> FAIL: 13_network_domU_udp_pos.test
> FAIL: 01_network_attach_pos.test
> FAIL: 02_network_attach_detach_pos.test
> FAIL: 03_network_attach_detach_multiple_pos.test
> FAIL: 01_pause_basic_pos.test
> FAIL: 02_pause_badopt_neg.test
> FAIL: 01_reboot_basic_pos.test
> FAIL: 02_reboot_badopt_neg.test
> FAIL: 01_restore_basic_pos.test
> FAIL: 04_restore_withdevices_pos.test
> FAIL: 01_save_basic_pos.test
> FAIL: 03_save_bogusfile_neg.test
> FAIL: 01_sched_credit_weight_cap_pos.test
> FAIL: 08_security-acm_xapi.test
> FAIL: 01_shutdown_basic_pos.test
> FAIL: 02_shutdown_badparm_neg.test
> FAIL: 02_sysrq_sync_pos.test
> FAIL: 03_sysrq_withreboot_pos.test
> FAIL: 01_unpause_basic_pos.test
> FAIL: 01_vcpu-disable_basic_pos.test
> FAIL: 01_vcpu-pin_basic_pos.test
> SKIP: 01_security-acm_basic.test
> SKIP: 02_security-acm_dom_start.test
> SKIP: 03_security-acm_dom_conflict.test
> SKIP: 04_security-acm_dom_res.test
> SKIP: 05_security-acm_dom_res_conf.test
> SKIP: 06_security-acm_dom_block_attach.test
> SKIP: 07_security-acm_pol_update.test
> SKIP: 09_security-acm_pol_update.test
> SKIP: 10_security-acm_pol_update.test
> SKIP: 01_vtpm-list_pos.test
> SKIP: 02_vtpm-cat_pcrs.test
> SKIP: 03_vtpm-susp_res.test
> SKIP: 04_vtpm-loc_migr.test
> SKIP: 05_vtpm-loc_migr.test
> SKIP: 06_vtpm-susp_res_pcrs.test
> SKIP: 07_vtpm-mig_pcrs.test
> SKIP: 08_vtpm-mig_pcrs.test
> SKIP: 09_vtpm-xapi.test
>
>
> Stefan
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 9356 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-16 17:09 ` Stefan Berger
@ 2008-09-16 19:03 ` Keir Fraser
2008-09-16 19:09 ` Keir Fraser
2008-09-16 20:50 ` Stefan Berger
0 siblings, 2 replies; 13+ messages in thread
From: Keir Fraser @ 2008-09-16 19:03 UTC (permalink / raw)
To: Stefan Berger; +Cc: xen-devel, xen-devel-bounces
[-- Attachment #1.1: Type: text/plain, Size: 7901 bytes --]
Unfortunately I don¹t think xm-test has been running in our automated tests
for a while, so I¹m not sure when this issue would have been introduced.
-- Keir
On 16/9/08 18:09, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>
> Keir,
>
> memory should not be the problem unless the memory requirements of those test
> domains have been increased considerably recently. Here's the upper part of
> 'xm dmesg':
>
> \ \/ /___ _ __ |___ /| || | _ _ _ __ ___| |_ __ _| |__ | | ___
> \ // _ \ '_ \ |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
> / \ __/ | | | ___) |__ _|__| |_| | | | \__ \ || (_| | |_) | | __/
> /_/\_\___|_| |_| |____(_) |_| \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
>
> (XEN) Xen version 3.4-unstable (root@watson.ibm.com) (gcc version 4.3.0
> 20080428 (Red Hat 4.3.0-8) (GCC) ) Tue Sep 16 07:20:38 EDT 2008
> (XEN) Latest ChangeSet: Mon Sep 15 17:10:43 2008 +0100 18482:087008dfb005
> (XEN) Command line: dom0_mem=1G
> (XEN) Video information:
> (XEN) VGA is text mode 80x25, font 8x16
> (XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds
> (XEN) EDID info not retrieved because no DDC retrieval method detected
> (XEN) Disc information:
> (XEN) Found 1 MBR signatures
> (XEN) Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN) 0000000000000000 - 000000000009e000 (usable)
> (XEN) 000000000009e000 - 00000000000a0000 (reserved)
> (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 00000000f7fed380 (usable)
> (XEN) 00000000f7fed380 - 00000000f7ff0000 (ACPI data)
> (XEN) 00000000f7ff0000 - 00000000f8000000 (reserved)
> (XEN) 00000000fec00000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 0000000108000000 (usable)
> (XEN) System RAM: 4095MB (4193836kB)
> (XEN) ACPI: RSDP 000FDFC0, 0014 (r0 IBM )
> (XEN) ACPI: RSDT F7FEFF80, 002C (r1 IBM SERBLADE 1000 IBM 45444F43)
> (XEN) ACPI: FACP F7FEFF00, 0074 (r1 IBM SERBLADE 1000 IBM 45444F43)
> (XEN) ACPI: DSDT F7FED380, 2A22 (r1 IBM SERBLADE 1000 INTL 2002025)
> (XEN) ACPI: FACS F7FEFE00, 0040
> (XEN) ACPI: APIC F7FEFE40, 0092 (r1 IBM SERBLADE 1000 IBM 45444F43)
> (XEN) Xen heap: 9MB (9676kB)
> (XEN) Domain heap initialised
>
>
> The system has 4GB and domain0 gets 1GB.
>
> Stefan
>
>
>
> xen-devel-bounces@lists.xensource.com wrote on 09/16/2008 12:58:20 PM:
>
>> > Keir Fraser <keir.fraser@eu.citrix.com>
>> > Sent by: xen-devel-bounces@lists.xensource.com
>> >
>> > 09/16/2008 12:58 PM
>> >
>> > To
>> >
>> > Stefan Berger/Watson/IBM@IBMUS, <xen-devel@lists.xensource.com>
>> >
>> > cc
>> >
>> > Subject
>> >
>> > [Xen-devel] Re: Error while running the xm test suite: Cannot handle
>> > page request order 0!
>> >
>> > Not enough memory?
>> >
>> > -- Keir
>> >
>> > On 16/9/08 17:33, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>
>> >
>> > Hello!
>> >
>> > It seems there is an error occurring in the hypervisor while
>> > running the xm-test suite on an i386 machine:
>> >
>> > [...]
>> > (XEN) Init. ramdisk: c06cb000->c0c3e000
>> > (XEN) Phys-Mach map: c0c3e000->c0d3e000
>> > (XEN) Start info: c0d3e000->c0d3e474
>> > (XEN) Page tables: c0d3f000->c0d4c000
>> > (XEN) Boot stack: c0d4c000->c0d4d000
>> > (XEN) TOTAL: c0000000->c1000000
>> > (XEN) ENTRY ADDRESS: c0100000
>> > (XEN) Dom0 has maximum 4 VCPUs
>> > (XEN) Scrubbing Free RAM: .............................done.
>> > (XEN) Xen trace buffers: disabled
>> > (XEN) Std. Loglevel: Errors and warnings
>> > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
>> > (XEN) Xen is relinquishing VGA console.
>> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
>> > input to Xen)
>> > (XEN) Freed 100kB init memory.
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> > (XEN) Cannot handle page request order 0!
>> >
>> >
>> > The results from the test suite look like this on that machine:
>> >
>> > FAIL: 02_block_attach_file_device_pos.test
>> > FAIL: 11_create_concurrent_pos.test
>> > FAIL: 12_create_concurrent_stress_pos.test
>> > FAIL: 13_create_multinic_pos.test
>> > FAIL: 14_create_blockroot_pos.test
>> > FAIL: 15_create_smallmem_pos.test
>> > FAIL: 16_create_smallmem_neg.test
>> > FAIL: 01_destroy_basic_pos.test
>> > FAIL: 05_destroy_byid_pos.test
>> > FAIL: 07_destroy_stale_pos.test
>> > FAIL: 01_enforce_dom0_cpus_basic_pos.test
>> > FAIL: 05_help_nonroot_pos.test
>> > FAIL: 04_list_goodparm_pos.test
>> > FAIL: 06_list_nonroot.test
>> > FAIL: 01_memset_basic_pos.test
>> > FAIL: 03_memset_random_pos.test
>> > FAIL: 04_memset_smallmem_pos.test
>> > FAIL: 01_migrate_localhost_pos.test
>> > XFAIL: 02_network_local_ping_pos.test
>> > FAIL: 03_network_local_tcp_pos.test
>> > FAIL: 04_network_local_udp_pos.test
>> > XFAIL: 05_network_dom0_ping_pos.test
>> > FAIL: 06_network_dom0_tcp_pos.test
>> > FAIL: 07_network_dom0_udp_pos.test
>> > XFAIL: 11_network_domU_ping_pos.test
>> > FAIL: 12_network_domU_tcp_pos.test
>> > FAIL: 13_network_domU_udp_pos.test
>> > FAIL: 01_network_attach_pos.test
>> > FAIL: 02_network_attach_detach_pos.test
>> > FAIL: 03_network_attach_detach_multiple_pos.test
>> > FAIL: 01_pause_basic_pos.test
>> > FAIL: 02_pause_badopt_neg.test
>> > FAIL: 01_reboot_basic_pos.test
>> > FAIL: 02_reboot_badopt_neg.test
>> > FAIL: 01_restore_basic_pos.test
>> > FAIL: 04_restore_withdevices_pos.test
>> > FAIL: 01_save_basic_pos.test
>> > FAIL: 03_save_bogusfile_neg.test
>> > FAIL: 01_sched_credit_weight_cap_pos.test
>> > FAIL: 08_security-acm_xapi.test
>> > FAIL: 01_shutdown_basic_pos.test
>> > FAIL: 02_shutdown_badparm_neg.test
>> > FAIL: 02_sysrq_sync_pos.test
>> > FAIL: 03_sysrq_withreboot_pos.test
>> > FAIL: 01_unpause_basic_pos.test
>> > FAIL: 01_vcpu-disable_basic_pos.test
>> > FAIL: 01_vcpu-pin_basic_pos.test
>> > SKIP: 01_security-acm_basic.test
>> > SKIP: 02_security-acm_dom_start.test
>> > SKIP: 03_security-acm_dom_conflict.test
>> > SKIP: 04_security-acm_dom_res.test
>> > SKIP: 05_security-acm_dom_res_conf.test
>> > SKIP: 06_security-acm_dom_block_attach.test
>> > SKIP: 07_security-acm_pol_update.test
>> > SKIP: 09_security-acm_pol_update.test
>> > SKIP: 10_security-acm_pol_update.test
>> > SKIP: 01_vtpm-list_pos.test
>> > SKIP: 02_vtpm-cat_pcrs.test
>> > SKIP: 03_vtpm-susp_res.test
>> > SKIP: 04_vtpm-loc_migr.test
>> > SKIP: 05_vtpm-loc_migr.test
>> > SKIP: 06_vtpm-susp_res_pcrs.test
>> > SKIP: 07_vtpm-mig_pcrs.test
>> > SKIP: 08_vtpm-mig_pcrs.test
>> > SKIP: 09_vtpm-xapi.test
>> >
>> >
>> > Stefan
>
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xensource.com
>> > http://lists.xensource.com/xen-devel <http://lists.xensource.com/xen-devel>
>
[-- Attachment #1.2: Type: text/html, Size: 11034 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-16 19:03 ` Keir Fraser
@ 2008-09-16 19:09 ` Keir Fraser
2008-09-16 20:50 ` Stefan Berger
1 sibling, 0 replies; 13+ messages in thread
From: Keir Fraser @ 2008-09-16 19:09 UTC (permalink / raw)
To: Keir Fraser, Stefan Berger; +Cc: xen-devel, xen-devel-bounces
[-- Attachment #1.1: Type: text/plain, Size: 8573 bytes --]
It¹s the Xen heap which is running out of memory (a fixed size ~10MB heap
which Xen¹s internal book-keeping structures are allocated from). Either
demands have increased on that heap, or something is leaking.
-- Keir
On 16/9/08 20:03, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
> Unfortunately I don¹t think xm-test has been running in our automated tests
> for a while, so I¹m not sure when this issue would have been introduced.
>
> -- Keir
>
> On 16/9/08 18:09, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>
>>
>> Keir,
>>
>> memory should not be the problem unless the memory requirements of those test
>> domains have been increased considerably recently. Here's the upper part of
>> 'xm dmesg':
>>
>> \ \/ /___ _ __ |___ /| || | _ _ _ __ ___| |_ __ _| |__ | | ___
>> \ // _ \ '_ \ |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
>> / \ __/ | | | ___) |__ _|__| |_| | | | \__ \ || (_| | |_) | | __/
>> /_/\_\___|_| |_| |____(_) |_| \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
>>
>> (XEN) Xen version 3.4-unstable (root@watson.ibm.com) (gcc version 4.3.0
>> 20080428 (Red Hat 4.3.0-8) (GCC) ) Tue Sep 16 07:20:38 EDT 2008
>> (XEN) Latest ChangeSet: Mon Sep 15 17:10:43 2008 +0100 18482:087008dfb005
>> (XEN) Command line: dom0_mem=1G
>> (XEN) Video information:
>> (XEN) VGA is text mode 80x25, font 8x16
>> (XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds
>> (XEN) EDID info not retrieved because no DDC retrieval method detected
>> (XEN) Disc information:
>> (XEN) Found 1 MBR signatures
>> (XEN) Found 1 EDD information structures
>> (XEN) Xen-e820 RAM map:
>> (XEN) 0000000000000000 - 000000000009e000 (usable)
>> (XEN) 000000000009e000 - 00000000000a0000 (reserved)
>> (XEN) 00000000000e0000 - 0000000000100000 (reserved)
>> (XEN) 0000000000100000 - 00000000f7fed380 (usable)
>> (XEN) 00000000f7fed380 - 00000000f7ff0000 (ACPI data)
>> (XEN) 00000000f7ff0000 - 00000000f8000000 (reserved)
>> (XEN) 00000000fec00000 - 0000000100000000 (reserved)
>> (XEN) 0000000100000000 - 0000000108000000 (usable)
>> (XEN) System RAM: 4095MB (4193836kB)
>> (XEN) ACPI: RSDP 000FDFC0, 0014 (r0 IBM )
>> (XEN) ACPI: RSDT F7FEFF80, 002C (r1 IBM SERBLADE 1000 IBM 45444F43)
>> (XEN) ACPI: FACP F7FEFF00, 0074 (r1 IBM SERBLADE 1000 IBM 45444F43)
>> (XEN) ACPI: DSDT F7FED380, 2A22 (r1 IBM SERBLADE 1000 INTL 2002025)
>> (XEN) ACPI: FACS F7FEFE00, 0040
>> (XEN) ACPI: APIC F7FEFE40, 0092 (r1 IBM SERBLADE 1000 IBM 45444F43)
>> (XEN) Xen heap: 9MB (9676kB)
>> (XEN) Domain heap initialised
>>
>>
>> The system has 4GB and domain0 gets 1GB.
>>
>> Stefan
>>
>>
>>
>> xen-devel-bounces@lists.xensource.com wrote on 09/16/2008 12:58:20 PM:
>>
>>> > Keir Fraser <keir.fraser@eu.citrix.com>
>>> > Sent by: xen-devel-bounces@lists.xensource.com
>>> >
>>> > 09/16/2008 12:58 PM
>>> >
>>> > To
>>> >
>>> > Stefan Berger/Watson/IBM@IBMUS, <xen-devel@lists.xensource.com>
>>> >
>>> > cc
>>> >
>>> > Subject
>>> >
>>> > [Xen-devel] Re: Error while running the xm test suite: Cannot handle
>>> > page request order 0!
>>> >
>>> > Not enough memory?
>>> >
>>> > -- Keir
>>> >
>>> > On 16/9/08 17:33, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>>
>>> >
>>> > Hello!
>>> >
>>> > It seems there is an error occurring in the hypervisor while
>>> > running the xm-test suite on an i386 machine:
>>> >
>>> > [...]
>>> > (XEN) Init. ramdisk: c06cb000->c0c3e000
>>> > (XEN) Phys-Mach map: c0c3e000->c0d3e000
>>> > (XEN) Start info: c0d3e000->c0d3e474
>>> > (XEN) Page tables: c0d3f000->c0d4c000
>>> > (XEN) Boot stack: c0d4c000->c0d4d000
>>> > (XEN) TOTAL: c0000000->c1000000
>>> > (XEN) ENTRY ADDRESS: c0100000
>>> > (XEN) Dom0 has maximum 4 VCPUs
>>> > (XEN) Scrubbing Free RAM: .............................done.
>>> > (XEN) Xen trace buffers: disabled
>>> > (XEN) Std. Loglevel: Errors and warnings
>>> > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
>>> > (XEN) Xen is relinquishing VGA console.
>>> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
>>> > input to Xen)
>>> > (XEN) Freed 100kB init memory.
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> > (XEN) Cannot handle page request order 0!
>>> >
>>> >
>>> > The results from the test suite look like this on that machine:
>>> >
>>> > FAIL: 02_block_attach_file_device_pos.test
>>> > FAIL: 11_create_concurrent_pos.test
>>> > FAIL: 12_create_concurrent_stress_pos.test
>>> > FAIL: 13_create_multinic_pos.test
>>> > FAIL: 14_create_blockroot_pos.test
>>> > FAIL: 15_create_smallmem_pos.test
>>> > FAIL: 16_create_smallmem_neg.test
>>> > FAIL: 01_destroy_basic_pos.test
>>> > FAIL: 05_destroy_byid_pos.test
>>> > FAIL: 07_destroy_stale_pos.test
>>> > FAIL: 01_enforce_dom0_cpus_basic_pos.test
>>> > FAIL: 05_help_nonroot_pos.test
>>> > FAIL: 04_list_goodparm_pos.test
>>> > FAIL: 06_list_nonroot.test
>>> > FAIL: 01_memset_basic_pos.test
>>> > FAIL: 03_memset_random_pos.test
>>> > FAIL: 04_memset_smallmem_pos.test
>>> > FAIL: 01_migrate_localhost_pos.test
>>> > XFAIL: 02_network_local_ping_pos.test
>>> > FAIL: 03_network_local_tcp_pos.test
>>> > FAIL: 04_network_local_udp_pos.test
>>> > XFAIL: 05_network_dom0_ping_pos.test
>>> > FAIL: 06_network_dom0_tcp_pos.test
>>> > FAIL: 07_network_dom0_udp_pos.test
>>> > XFAIL: 11_network_domU_ping_pos.test
>>> > FAIL: 12_network_domU_tcp_pos.test
>>> > FAIL: 13_network_domU_udp_pos.test
>>> > FAIL: 01_network_attach_pos.test
>>> > FAIL: 02_network_attach_detach_pos.test
>>> > FAIL: 03_network_attach_detach_multiple_pos.test
>>> > FAIL: 01_pause_basic_pos.test
>>> > FAIL: 02_pause_badopt_neg.test
>>> > FAIL: 01_reboot_basic_pos.test
>>> > FAIL: 02_reboot_badopt_neg.test
>>> > FAIL: 01_restore_basic_pos.test
>>> > FAIL: 04_restore_withdevices_pos.test
>>> > FAIL: 01_save_basic_pos.test
>>> > FAIL: 03_save_bogusfile_neg.test
>>> > FAIL: 01_sched_credit_weight_cap_pos.test
>>> > FAIL: 08_security-acm_xapi.test
>>> > FAIL: 01_shutdown_basic_pos.test
>>> > FAIL: 02_shutdown_badparm_neg.test
>>> > FAIL: 02_sysrq_sync_pos.test
>>> > FAIL: 03_sysrq_withreboot_pos.test
>>> > FAIL: 01_unpause_basic_pos.test
>>> > FAIL: 01_vcpu-disable_basic_pos.test
>>> > FAIL: 01_vcpu-pin_basic_pos.test
>>> > SKIP: 01_security-acm_basic.test
>>> > SKIP: 02_security-acm_dom_start.test
>>> > SKIP: 03_security-acm_dom_conflict.test
>>> > SKIP: 04_security-acm_dom_res.test
>>> > SKIP: 05_security-acm_dom_res_conf.test
>>> > SKIP: 06_security-acm_dom_block_attach.test
>>> > SKIP: 07_security-acm_pol_update.test
>>> > SKIP: 09_security-acm_pol_update.test
>>> > SKIP: 10_security-acm_pol_update.test
>>> > SKIP: 01_vtpm-list_pos.test
>>> > SKIP: 02_vtpm-cat_pcrs.test
>>> > SKIP: 03_vtpm-susp_res.test
>>> > SKIP: 04_vtpm-loc_migr.test
>>> > SKIP: 05_vtpm-loc_migr.test
>>> > SKIP: 06_vtpm-susp_res_pcrs.test
>>> > SKIP: 07_vtpm-mig_pcrs.test
>>> > SKIP: 08_vtpm-mig_pcrs.test
>>> > SKIP: 09_vtpm-xapi.test
>>> >
>>> >
>>> > Stefan
>>
>>> > _______________________________________________
>>> > Xen-devel mailing list
>>> > Xen-devel@lists.xensource.com
>>> > http://lists.xensource.com/xen-devel
>>> <http://lists.xensource.com/xen-devel>
>>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 11953 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-16 19:03 ` Keir Fraser
2008-09-16 19:09 ` Keir Fraser
@ 2008-09-16 20:50 ` Stefan Berger
2008-09-16 21:10 ` Keir Fraser
1 sibling, 1 reply; 13+ messages in thread
From: Stefan Berger @ 2008-09-16 20:50 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 8500 bytes --]
xen-devel-bounces@lists.xensource.com wrote on 09/16/2008 03:03:24 PM:
> Keir Fraser <keir.fraser@eu.citrix.com>
> Sent by: xen-devel-bounces@lists.xensource.com
>
> 09/16/2008 03:03 PM
>
> To
>
> Stefan Berger/Watson/IBM@IBMUS
>
> cc
>
> xen-devel@lists.xensource.com, xen-devel-bounces@lists.xensource.com
>
> Subject
>
> Re: [Xen-devel] Re: Error while running the xm test suite: Cannot
> handle page request order 0!
>
> Unfortunately I don’t think xm-test has been running in our
> automated tests for a while, so I’m not sure when this issue would
> have been introduced.
The problem may have been introduced as far back as (around) the beginning
of the month.
Stefan
>
> -- Keir
>
> On 16/9/08 18:09, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>
> Keir,
>
> memory should not be the problem unless the memory requirements of
> those test domains have been increased considerably recently. Here's
> the upper part of 'xm dmesg':
>
> \ \/ /___ _ __ |___ /| || | _ _ _ __ ___| |_ __ _| |__ | | ___
> \ // _ \ '_ \ |_ \| || |_ __| | | | '_ \/ __| __/ _` | '_ \| |/ _
\
> / \ __/ | | | ___) |__ _|__| |_| | | | \__ \ || (_| | |_) | | __/
> /_/\_\___|_| |_| |____(_) |_| \__,_|_|
|_|___/\__\__,_|_.__/|_|\___|
>
> (XEN) Xen version 3.4-unstable (root@watson.ibm.com) (gcc version 4.
> 3.0 20080428 (Red Hat 4.3.0-8) (GCC) ) Tue Sep 16 07:20:38 EDT 2008
> (XEN) Latest ChangeSet: Mon Sep 15 17:10:43 2008 +0100
18482:087008dfb005
> (XEN) Command line: dom0_mem=1G
> (XEN) Video information:
> (XEN) VGA is text mode 80x25, font 8x16
> (XEN) VBE/DDC methods: none; EDID transfer time: 2 seconds
> (XEN) EDID info not retrieved because no DDC retrieval method detected
> (XEN) Disc information:
> (XEN) Found 1 MBR signatures
> (XEN) Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN) 0000000000000000 - 000000000009e000 (usable)
> (XEN) 000000000009e000 - 00000000000a0000 (reserved)
> (XEN) 00000000000e0000 - 0000000000100000 (reserved)
> (XEN) 0000000000100000 - 00000000f7fed380 (usable)
> (XEN) 00000000f7fed380 - 00000000f7ff0000 (ACPI data)
> (XEN) 00000000f7ff0000 - 00000000f8000000 (reserved)
> (XEN) 00000000fec00000 - 0000000100000000 (reserved)
> (XEN) 0000000100000000 - 0000000108000000 (usable)
> (XEN) System RAM: 4095MB (4193836kB)
> (XEN) ACPI: RSDP 000FDFC0, 0014 (r0 IBM )
> (XEN) ACPI: RSDT F7FEFF80, 002C (r1 IBM SERBLADE 1000 IBM
45444F43)
> (XEN) ACPI: FACP F7FEFF00, 0074 (r1 IBM SERBLADE 1000 IBM
45444F43)
> (XEN) ACPI: DSDT F7FED380, 2A22 (r1 IBM SERBLADE 1000 INTL
2002025)
> (XEN) ACPI: FACS F7FEFE00, 0040
> (XEN) ACPI: APIC F7FEFE40, 0092 (r1 IBM SERBLADE 1000 IBM
45444F43)
> (XEN) Xen heap: 9MB (9676kB)
> (XEN) Domain heap initialised
>
>
> The system has 4GB and domain0 gets 1GB.
>
> Stefan
>
>
>
> xen-devel-bounces@lists.xensource.com wrote on 09/16/2008 12:58:20 PM:
>
> > Keir Fraser <keir.fraser@eu.citrix.com>
> > Sent by: xen-devel-bounces@lists.xensource.com
> >
> > 09/16/2008 12:58 PM
> >
> > To
> >
> > Stefan Berger/Watson/IBM@IBMUS, <xen-devel@lists.xensource.com>
> >
> > cc
> >
> > Subject
> >
> > [Xen-devel] Re: Error while running the xm test suite: Cannot handle
> > page request order 0!
> >
> > Not enough memory?
> >
> > -- Keir
> >
> > On 16/9/08 17:33, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>
> >
> > Hello!
> >
> > It seems there is an error occurring in the hypervisor while
> > running the xm-test suite on an i386 machine:
> >
> > [...]
> > (XEN) Init. ramdisk: c06cb000->c0c3e000
> > (XEN) Phys-Mach map: c0c3e000->c0d3e000
> > (XEN) Start info: c0d3e000->c0d3e474
> > (XEN) Page tables: c0d3f000->c0d4c000
> > (XEN) Boot stack: c0d4c000->c0d4d000
> > (XEN) TOTAL: c0000000->c1000000
> > (XEN) ENTRY ADDRESS: c0100000
> > (XEN) Dom0 has maximum 4 VCPUs
> > (XEN) Scrubbing Free RAM: .............................done.
> > (XEN) Xen trace buffers: disabled
> > (XEN) Std. Loglevel: Errors and warnings
> > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> > (XEN) Xen is relinquishing VGA console.
> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> > input to Xen)
> > (XEN) Freed 100kB init memory.
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> > (XEN) Cannot handle page request order 0!
> >
> >
> > The results from the test suite look like this on that machine:
> >
> > FAIL: 02_block_attach_file_device_pos.test
> > FAIL: 11_create_concurrent_pos.test
> > FAIL: 12_create_concurrent_stress_pos.test
> > FAIL: 13_create_multinic_pos.test
> > FAIL: 14_create_blockroot_pos.test
> > FAIL: 15_create_smallmem_pos.test
> > FAIL: 16_create_smallmem_neg.test
> > FAIL: 01_destroy_basic_pos.test
> > FAIL: 05_destroy_byid_pos.test
> > FAIL: 07_destroy_stale_pos.test
> > FAIL: 01_enforce_dom0_cpus_basic_pos.test
> > FAIL: 05_help_nonroot_pos.test
> > FAIL: 04_list_goodparm_pos.test
> > FAIL: 06_list_nonroot.test
> > FAIL: 01_memset_basic_pos.test
> > FAIL: 03_memset_random_pos.test
> > FAIL: 04_memset_smallmem_pos.test
> > FAIL: 01_migrate_localhost_pos.test
> > XFAIL: 02_network_local_ping_pos.test
> > FAIL: 03_network_local_tcp_pos.test
> > FAIL: 04_network_local_udp_pos.test
> > XFAIL: 05_network_dom0_ping_pos.test
> > FAIL: 06_network_dom0_tcp_pos.test
> > FAIL: 07_network_dom0_udp_pos.test
> > XFAIL: 11_network_domU_ping_pos.test
> > FAIL: 12_network_domU_tcp_pos.test
> > FAIL: 13_network_domU_udp_pos.test
> > FAIL: 01_network_attach_pos.test
> > FAIL: 02_network_attach_detach_pos.test
> > FAIL: 03_network_attach_detach_multiple_pos.test
> > FAIL: 01_pause_basic_pos.test
> > FAIL: 02_pause_badopt_neg.test
> > FAIL: 01_reboot_basic_pos.test
> > FAIL: 02_reboot_badopt_neg.test
> > FAIL: 01_restore_basic_pos.test
> > FAIL: 04_restore_withdevices_pos.test
> > FAIL: 01_save_basic_pos.test
> > FAIL: 03_save_bogusfile_neg.test
> > FAIL: 01_sched_credit_weight_cap_pos.test
> > FAIL: 08_security-acm_xapi.test
> > FAIL: 01_shutdown_basic_pos.test
> > FAIL: 02_shutdown_badparm_neg.test
> > FAIL: 02_sysrq_sync_pos.test
> > FAIL: 03_sysrq_withreboot_pos.test
> > FAIL: 01_unpause_basic_pos.test
> > FAIL: 01_vcpu-disable_basic_pos.test
> > FAIL: 01_vcpu-pin_basic_pos.test
> > SKIP: 01_security-acm_basic.test
> > SKIP: 02_security-acm_dom_start.test
> > SKIP: 03_security-acm_dom_conflict.test
> > SKIP: 04_security-acm_dom_res.test
> > SKIP: 05_security-acm_dom_res_conf.test
> > SKIP: 06_security-acm_dom_block_attach.test
> > SKIP: 07_security-acm_pol_update.test
> > SKIP: 09_security-acm_pol_update.test
> > SKIP: 10_security-acm_pol_update.test
> > SKIP: 01_vtpm-list_pos.test
> > SKIP: 02_vtpm-cat_pcrs.test
> > SKIP: 03_vtpm-susp_res.test
> > SKIP: 04_vtpm-loc_migr.test
> > SKIP: 05_vtpm-loc_migr.test
> > SKIP: 06_vtpm-susp_res_pcrs.test
> > SKIP: 07_vtpm-mig_pcrs.test
> > SKIP: 08_vtpm-mig_pcrs.test
> > SKIP: 09_vtpm-xapi.test
> >
> >
> > Stefan
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel <
http://lists.xensource.com/xen-devel>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 12021 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-16 20:50 ` Stefan Berger
@ 2008-09-16 21:10 ` Keir Fraser
2008-09-16 21:17 ` Stefan Berger
2008-09-17 21:23 ` Stefan Berger
0 siblings, 2 replies; 13+ messages in thread
From: Keir Fraser @ 2008-09-16 21:10 UTC (permalink / raw)
To: Stefan Berger; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 529 bytes --]
On 16/9/08 21:50, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>> > Unfortunately I don¹t think xm-test has been running in our
>> > automated tests for a while, so I¹m not sure when this issue would
>> > have been introduced.
>
>
> The problem may have been introduced as far back as (around) the beginning of
> the month.
>
> Stefan
I suspect a memory leak in your particular configuration. It¹d be good to
try to narrow down which changeset or range of changesets introduced the
problem.
-- Keir
[-- Attachment #1.2: Type: text/html, Size: 1275 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-16 21:10 ` Keir Fraser
@ 2008-09-16 21:17 ` Stefan Berger
2008-09-16 21:21 ` Keir Fraser
2008-09-17 21:23 ` Stefan Berger
1 sibling, 1 reply; 13+ messages in thread
From: Stefan Berger @ 2008-09-16 21:17 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 998 bytes --]
Keir Fraser <keir.fraser@eu.citrix.com> wrote on 09/16/2008 05:10:40 PM:
> Keir Fraser <keir.fraser@eu.citrix.com>
> 09/16/2008 05:10 PM
>
> To
>
> Stefan Berger/Watson/IBM@IBMUS
>
> cc
>
> <xen-devel@lists.xensource.com>
>
> Subject
>
> Re: [Xen-devel] Re: Error while running the xm test suite: Cannot
> handle page request order 0!
>
> On 16/9/08 21:50, "Stefan Berger" <stefanb@us.ibm.com> wrote:
> > Unfortunately I don’t think xm-test has been running in our
> > automated tests for a while, so I’m not sure when this issue would
> > have been introduced.
>
>
> The problem may have been introduced as far back as (around) the
> beginning of the month.
>
> Stefan
>
> I suspect a memory leak in your particular configuration. It’d be
> good to try to narrow down which changeset or range of changesets
> introduced the problem.
>
I'll narrow it down, but it will take a while. I'll let you know.
Stefan
> -- Keir
[-- Attachment #1.2: Type: text/html, Size: 1733 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-16 21:17 ` Stefan Berger
@ 2008-09-16 21:21 ` Keir Fraser
0 siblings, 0 replies; 13+ messages in thread
From: Keir Fraser @ 2008-09-16 21:21 UTC (permalink / raw)
To: Stefan Berger; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 898 bytes --]
On 16/9/08 22:17, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>> > I suspect a memory leak in your particular configuration. It¹d be
>> > good to try to narrow down which changeset or range of changesets
>> > introduced the problem.
>> >
>
> I'll narrow it down, but it will take a while. I'll let you know.
As a starting point, if you are also using up-to-date linux-2.6.18-xen.hg
then try reverting it back a month and see if the problem goes away. If not,
bring back to tip and try same on xen-unstable.hg. This will establish which
repo contains the bug. It¹ll probably turn out to be xen-unstable.hg, at
which point I would do Œhg v history xen | less¹ to look for scary looking
patches inside the hypervisor itself, and use that to guide which changesets
I test for working vs non-working. You should be able to do much better than
a binary chop this way.
-- Keir
[-- Attachment #1.2: Type: text/html, Size: 1556 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-16 21:10 ` Keir Fraser
2008-09-16 21:17 ` Stefan Berger
@ 2008-09-17 21:23 ` Stefan Berger
2008-09-17 21:39 ` Keir Fraser
1 sibling, 1 reply; 13+ messages in thread
From: Stefan Berger @ 2008-09-17 21:23 UTC (permalink / raw)
To: Keir Fraser; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1272 bytes --]
xen-devel-bounces@lists.xensource.com wrote on 09/16/2008 05:10:40 PM:
> Keir Fraser <keir.fraser@eu.citrix.com>
> Sent by: xen-devel-bounces@lists.xensource.com
>
> 09/16/2008 05:10 PM
>
> To
>
> Stefan Berger/Watson/IBM@IBMUS
>
> cc
>
> xen-devel@lists.xensource.com
>
> Subject
>
> Re: [Xen-devel] Re: Error while running the xm test suite: Cannot
> handle page request order 0!
>
> On 16/9/08 21:50, "Stefan Berger" <stefanb@us.ibm.com> wrote:
> > Unfortunately I don’t think xm-test has been running in our
> > automated tests for a while, so I’m not sure when this issue would
> > have been introduced.
>
>
> The problem may have been introduced as far back as (around) the
> beginning of the month.
>
> Stefan
>
> I suspect a memory leak in your particular configuration. It’d be
> good to try to narrow down which changeset or range of changesets
> introduced the problem.
I narrowed it down as far as : 18411 fails and 18407 works, which is very
strange since I don't see any critical changes in between...
Stefan
>
> -- Keir_______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 2220 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-17 21:23 ` Stefan Berger
@ 2008-09-17 21:39 ` Keir Fraser
2008-09-17 21:45 ` Daniel Magenheimer
0 siblings, 1 reply; 13+ messages in thread
From: Keir Fraser @ 2008-09-17 21:39 UTC (permalink / raw)
To: Stefan Berger; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 596 bytes --]
On 17/9/08 22:23, "Stefan Berger" <stefanb@us.ibm.com> wrote:
>> > I suspect a memory leak in your particular configuration. It¹d be
>> > good to try to narrow down which changeset or range of changesets
>> > introduced the problem.
>
> I narrowed it down as far as : 18411 fails and 18407 works, which is very
> strange since I don't see any critical changes in between...
Yes. 18411 affects only ia64. 18410 affects only internal ioemu (not used by
default build). 18409 reverts 18408, and simply adds a wrapper around
Œinstall¹ inside the tools/ directory. Weird!
-- Keir
[-- Attachment #1.2: Type: text/html, Size: 1241 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* RE: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-17 21:39 ` Keir Fraser
@ 2008-09-17 21:45 ` Daniel Magenheimer
2008-09-18 1:54 ` Stefan Berger
0 siblings, 1 reply; 13+ messages in thread
From: Daniel Magenheimer @ 2008-09-17 21:45 UTC (permalink / raw)
To: Keir Fraser, Stefan Berger; +Cc: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]
Re: [Xen-devel] Re: Error while running the xm test suite: Cannot handle page request order 0!Perhaps the cset numbers refer to 3.3-testing, not xen-unstable?
-----Original Message-----
From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
Sent: Wednesday, September 17, 2008 3:40 PM
To: Stefan Berger
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Re: Error while running the xm test suite: Cannot handle page request order 0!
On 17/9/08 22:23, "Stefan Berger" <stefanb@us.ibm.com> wrote:
> I suspect a memory leak in your particular configuration. It’d be
> good to try to narrow down which changeset or range of changesets
> introduced the problem.
I narrowed it down as far as : 18411 fails and 18407 works, which is very strange since I don't see any critical changes in between...
Yes. 18411 affects only ia64. 18410 affects only internal ioemu (not used by default build). 18409 reverts 18408, and simply adds a wrapper around ‘install’ inside the tools/ directory. Weird!
-- Keir
[-- Attachment #1.2: Type: text/html, Size: 2113 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* RE: Re: Error while running the xm test suite: Cannot handle page request order 0!
2008-09-17 21:45 ` Daniel Magenheimer
@ 2008-09-18 1:54 ` Stefan Berger
0 siblings, 0 replies; 13+ messages in thread
From: Stefan Berger @ 2008-09-18 1:54 UTC (permalink / raw)
To: Daniel Magenheimer; +Cc: xen-devel, Keir Fraser
[-- Attachment #1.1: Type: text/plain, Size: 1718 bytes --]
xen-devel-bounces@lists.xensource.com wrote on 09/17/2008 05:45:14 PM:
> Daniel Magenheimer <dan.magenheimer@oracle.com>
> Sent by: xen-devel-bounces@lists.xensource.com
>
> 09/17/2008 05:45 PM
>
> To
>
> Keir Fraser <keir.fraser@eu.citrix.com>, Stefan Berger/Watson/IBM@IBMUS
>
> cc
>
> xen-devel@lists.xensource.com
>
> Subject
>
> RE: [Xen-devel] Re: Error while running the xm test suite: Cannot
> handle page request order 0!
>
> Perhaps the cset numbers refer to 3.3-testing, not xen-unstable?
No, they refer to the staging tree. If no one else is encountering these
errors, please disregard for now. I'll find out what's going on.
Stefan
> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> Sent: Wednesday, September 17, 2008 3:40 PM
> To: Stefan Berger
> Cc: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] Re: Error while running the xm test suite:
> Cannot handle page request order 0!
> On 17/9/08 22:23, "Stefan Berger" <stefanb@us.ibm.com> wrote:
> > I suspect a memory leak in your particular configuration. It?x2019;d
be
> > good to try to narrow down which changeset or range of changesets
> > introduced the problem.
>
> I narrowed it down as far as : 18411 fails and 18407 works, which is
> very strange since I don't see any critical changes in between...
>
> Yes. 18411 affects only ia64. 18410 affects only internal ioemu (not
> used by default build). 18409 reverts 18408, and simply adds a
> wrapper around ?x2018;install?x2019; inside the tools/ directory. Weird!
>
> -- Keir_______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 2783 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2008-09-18 1:54 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-09-16 16:33 Error while running the xm test suite: Cannot handle page request order 0! Stefan Berger
2008-09-16 16:58 ` Keir Fraser
2008-09-16 17:09 ` Stefan Berger
2008-09-16 19:03 ` Keir Fraser
2008-09-16 19:09 ` Keir Fraser
2008-09-16 20:50 ` Stefan Berger
2008-09-16 21:10 ` Keir Fraser
2008-09-16 21:17 ` Stefan Berger
2008-09-16 21:21 ` Keir Fraser
2008-09-17 21:23 ` Stefan Berger
2008-09-17 21:39 ` Keir Fraser
2008-09-17 21:45 ` Daniel Magenheimer
2008-09-18 1:54 ` Stefan Berger
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.