|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] RE: xl fails to work with some command
Hi all
I have do further investigation with xl last week. And here is the latest
status with xl.
I found there are some bugs with xl:
1. xl only can take one parameter with "disk=" in config file, or else it
will show "segment fault" when run "xl create".
2. libxl don't have the memory balloon support, so it will fail when guest
need to balloon memory from dom0. So our test case "XEN_4G_guest_64_g32e" will
fail sometimes.
3. xenu cannot work with xl. When boot xenu, guest will wait at XENBUS:
waiting for devices to initializes. And all the xenu cases fail
4. SAVE/RESTORE with xl cannot work. After restore, guest's network will
fail. And all the S/R and live migration cases fail.
5. All windows UP guest cannot start. It always will crash. And all the
windows UP cases fail.
6. vcpu-set is not supported by xl. So some RAS case which use xl vcpu-set to
set guest's cpu set will fails. case "vcpu_hot_add_64_g32e" fails.
All the data collection under changeset 21903 on the stoakley.
Following it the xvs report by xl:
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
ras_ept_vpid 3 2 1 0 0
control_panel_ept_vpid 17 8 9 0 0
gtest_ept_vpid 18 13 5 0 0
=====================================================================
ras_ept_vpid 3 2 1 0 0
:vcpu_hot_remove_64_g32e 1 1 0 0 0
:cpu_online_offline_64_g 1 1 0 0 0
:vcpu_hot_add_64_g32e 1 0 1 0 0
control_panel_ept_vpid 17 8 9 0 0
:XEN_1500M_guest_64_g32e 1 1 0 0 0
:XEN_4G_guest_64_g32e 1 1 1 0 0
:XEN_256M_xenu_64_gPAE 1 0 1 0 0
:XEN_four_vmx_xenu_seq_6 1 0 1 0 0
:XEN_vmx_vcpu_pin_64_g32 1 1 0 0 0
:XEN_linux_win_64_g32e 1 1 1 0 0
:XEN_SR_Continuity_64_g3 1 0 1 0 0
:XEN_vmx_2vcpu_64_g32e 1 1 0 0 0
:XEN_1500M_guest_64_gPAE 1 1 0 0 0
:XEN_four_dguest_co_64_g 1 1 1 0 0
:XEN_4G_guest_64_gPAE 1 1 1 0 0
:XEN_two_winxp_64_g32e 1 0 1 0 0
:XEN_four_sguest_seq_64_ 1 1 0 0 0
:XEN_256M_guest_64_gPAE 1 1 0 0 0
:XEN_256M_guest_64_g32e 1 1 0 0 0
:XEN_SR_SMP_64_g32e 1 0 1 0 0
:XEN_four_sguest_seq_64_ 1 1 0 0 0
gtest_ept_vpid 18 13 5 0 0
:reboot_xp_64_g32e 1 0 1 0 0
:boot_up_vista_64_g32e 1 0 1 0 0
:boot_up_acpi_xp_64_g32e 1 0 1 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
:boot_smp_acpi_xp_64_g32 1 1 0 0 0
:boot_up_acpi_64_g32e 1 1 0 0 0
:boot_base_kernel_64_g32 1 1 0 0 0
:boot_up_win2008_64_g32e 1 0 1 0 0
:kb_nightly_64_g32e 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 1 0 1 0 0
:boot_smp_vista_64_g32e 1 1 0 0 0
:ltp_nightly_64_g32e 1 1 0 0 0
:boot_fc9_64_g32e 1 1 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_smp_win7_ent_debug 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_rhel5u1_64_g32e 1 1 0 0 0
:reboot_fc6_64_g32e 1 1 0 0 0
=====================================================================
Total 38 23 15 0 0
best regards
yang
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Zhang, Yang Z
> Sent: Thursday, August 19, 2010 1:51 PM
> To: Ian Campbell; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] xl fails to work with some command
>
> Hi
> As we will use xl in xen 4.1. I had try use xl to do something. And I find
> some
> command is fails.
> For config file, when give "disk=" too args, it will show segment fault if we
> use
> xl create to start guest. Is there any change for xl's config file?
>
> Following command can not work:
> xl migrate: when I use xl migrate domain localhost to do migrate, it shows
> error:
> Saving to migration stream new xl format (info
> 0x0/0x0/15122)
> libxl: warning:
> libxl_dom.c:374:core_suspend
> Failed to get the suspend evtchn port
> Loading new save file incoming
> migration stream
> (new xl fmt info 0x0/0x0/15122)
> Savefile contains xl domain
> config
> xc: Saving memory: iter 0 (last
> sent 0 skipped 0):
> 98334/1048576 9%xc: error: Failed to allocate memory for batch.!:
> Internal error
> libxl: error:
> libxl_device.c:438:libxl_wait_for_device_model Device Model not ready
> xl: fatal error:
> xl_cmdimpl.c:1466, rc=-1:
> libxl_confirm_device_model_startup(&ctx, dm_starting)
> xc: error: Error when writing
> to state file (4c)
> (errno 32) (32 = Broken pipe): Internal error
> libxl: error:
> libxl_utils.c:328:libxl_write_exactly
> failed to write qemu signature from saved-state file: Broken pipe
> migration sender:
> libxl_domain_suspend failed
> (rc=32)
> libxl: info:
> libxl_exec.c:69:libxl_report_child_exitstatus migration target process [7098]
> exited with error status 1
> Migration failed, resuming at
> sender.
>
> xl pci-list-assign: It cannot show the hidden device. With xm, it can work.
> xl mem-set: use xl mem-set to set guest's memory have no effect
> xl trigger: xl have no s3resume option and some other option cannot work
> xl vnc: The arg of dom_id for xl vnc cannot work. If there have two guest,
> when use xl vnc guest2 try to connect guest2, it always connect to guest1.
> xl vcpu-set: Both xm vcpu-set and xl vcpu-set can not work.
>
> I used changeset 21951 for my test scenario.
>
> best regards
> yang
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |