WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] qcow image fail to work with xl

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: [Xen-devel] qcow image fail to work with xl
From: "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx>
Date: Thu, 9 Dec 2010 10:52:08 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, "Dugger, Donald D" <donald.d.dugger@xxxxxxxxx>
Delivery-date: Thu, 09 Dec 2010 01:29:21 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcuXTBITXUMKzgU7T3C1NaMnSNrhGQ==
Thread-topic: qcow image fail to work with xl
Hi stafano
I am working on moving our test scenario to xl now. But there are some bugs 
block it.
1. qcow and qcow2 image fail to work.
it will stall at booting guest when using cow image and it will show 
"had:dma_timer_expiry: dma status ==0x21" in guest console and guest hangs(See 
attachment).
Then I use xl destroy to shutdown it. But it fail too, xl list shows the guest 
was destroyed successfully, but the guest's console still exist and use ps -ax, 
I can see
"8432 pts/1    Zl     3:13 [qemu-dm] <defunct>"
After seen this, I cannot use xl create to create guest again. It will show:
[root@vt-nhm7 var]# xl create config.vmxCPL_MEM_29
Parsing config file config.vmxCPL_MEM_29
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->0000000000179710
  TOTAL:         0000000000000000->000000001f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000000fb
  1GB PAGES: 0x0000000000000000
libxl: error: libxl_device.c:471:libxl__wait_for_device_model Device Model not 
ready
xl: fatal error: xl_cmdimpl.c:1699, rc=-1: 
libxl_confirm_device_model_startup(&ctx, dm_starting)

Here is the log from /var/log/xen/:
Waiting for domain vCPL_MEM_29_1291859410 (domid 1) to die [pid 8470]
Domain 1 is dead
Unknown shutdown reason code 255. Destroying domain.
Action for shutdown reason code 255 is destroy
Domain 1 needs to be cleaned up: destroying the domain
libxl: error: libxl.c:909:libxl_destroy_device_model Couldn't find device 
model's pid: No such file or directory
libxl: error: libxl.c:973:libxl_domain_destroy libxl_destroy_device_model 
failed for 1
libxl: error: libxl_device.c:324:libxl__devices_destroy /local/domain/1/device 
is empty
Done. Exiting now

2. xl vnc cannot work but xm vnc works well
3.If use the default config(/xen/etc/xmexample.hvm), it assign ',hdc:cdrom,r' 
to disk and xl create will raise segment fault when to parse it.

Another question is that do we need to start xend when using xl. If no, how to 
create the bridge.

best regards
yang

Attachment: guest fail to boot with qcow image.bmp
Description: guest fail to boot with qcow image.bmp

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>