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/
Home Products Support Community News


[XenARM] Using a block device on XenARM

To: xen-arm@xxxxxxxxxxxxxxxxxxx
Subject: [XenARM] Using a block device on XenARM
From: Comson <comson@xxxxxxxxx>
Date: Fri, 12 Mar 2010 16:01:52 -0500
Delivery-date: Fri, 12 Mar 2010 13:02:08 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type; bh=DBhr4GlOuGOEtfrwyfe36jlpA1z2ebTHUfo10hEZIJA=; b=JncXSsb/FiniyzTuK6QncA7PfhbMMsQPX8XyaguCWeoYiMcBHlkAIWn0Z7pQSbFhfm tUeFUjtGb5aU5k7UGAEVF4FVbpHuuKHOS542uAws7b6NWZYaCf3prXrqqm4Yksfb2qGf YB7T65LbCxJ3aV2V9zvD51KS8V7vOqctkZf1k=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=Wvb0WEbfN/wgAe7vP9JQnn1q0YRWDNqfNspyl9t6gDyOl/b/sHlfk5oBPcQ05d59Nv ai5zdQIlWoeyqLUqYJiBNgV54YCqb8br6bHaaXVi89mqGNeKz+MOiU0jVOyCGwflEL0L NoRcRsbgh34fFo0qFn4OLv1vH1+EQiC9/sdfA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-arm-request@lists.xensource.com?subject=help>
List-id: Xen ARM development <xen-arm.lists.xensource.com>
List-post: <mailto:xen-arm@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-arm>, <mailto:xen-arm-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-arm>, <mailto:xen-arm-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-arm-bounces@xxxxxxxxxxxxxxxxxxx

I am trying to use a file as a virtual disk for Dom1's root file system. However, Xen failed to initialize and froze Dom0 kernel. 

This is the Dom1 config file:
name = "dom1"
memory = "16"
kernel = "/images/vmlinux.out1"        #This file is stored in Dom0's /images directory
disk = [ 'file:/boot/dom1.fs,ioemu:xvda1,w' ]  #dom1.fs is the file system image for dom1

This is the output on Dom0's console before it died. 
root@Domain0:/usr/local/xen-tools# xm create /etc/xen/dom1

Using config file "/etc/xen/dom1".

* xen/xm/create.py --- main()--> parseCommandLine Completed TestPoint 1 ****

* xen/xm/create.py --- main()--> make_domain() function call started   TestPoint 2 ****

Entered make_domain() --------------------->

privcmd_ioctl, virual address : 40674000, mfn : c2c00 npages : 400
*** LOADING DOMAIN : 1 ***
[XEN] Physical Memory Arrangement: c2000000->c3000000
[XEN]  Loaded kernel: c0008000->c024bc00
[XEN]  Init. ramdisk: c024c000->c024c000
[XEN]  Phys-Mach map: c024c000->c0250000
[XEN]  Store mfn:     c0250000->c0251000
[XEN]  Console mfn:   c0251000->c0252000
[XEN]  Start info:    c0252000->c0253000
[XEN]  Page tables:   c0254000->c0263000
[XEN]  Boot stack:    c0263000->c0264000
[XEN]  TOTAL:         c0000000->c1000000
[XEN]  ENTRY ADDRESS: c0008000
[XEN] store_mfn physical addres c2250000
[XEN] console_mfn physical addres c2251000
[XEN]  [TODO] dma channel access permission, in construct_guest_dom()
privcmd_ioctl, virual address : 40018000, mfn : c2250 npages : 1
fbsetback_probe called
fbsetback_probe: be->fbsetif = 0xc116ae60
privcmd_ioctl, virual address : 40017000, mfn : c2251 npages : 1

** xen/xm/create.py -- make_domain()--> xend.domain.create() completed [TP #1]  *****

   dominfo returned completed

** xen/xm/create.py -- make_domain()--> xend.domain.waitForDevices() START [TP #2] *****

    xmlrpclib.Fault exception occured @ [TP #2] dom1 is being destroyed!

    calling server.xend.domain.destroy()

Device 768 (vbd) could not be connected. Hotplug scripts not working.
[XEN] returnVal = -22, domain = -16553344, current->domain = -16554624
[XEN] sync_vcpu_execstate : Not Yet
[XEN] domain_relinquish_resources : Not Yet
[XEN] Domain 1 killed

I inserted some custom print statements in the Python scripts for debugging. As you can see,  waitForDevices() returned Timeout which caused the system to shutdown Dom1. Strangely, this also caused the entire Dom0 kernel to freeze. I searched online for the above error message, "Device 768 (vbd) could not be connected. Hotplug scripts not working.", but couldn't find any useful information. 

I wonder if someone from the XenARM community has more insight knowledge about this and hopefully can give me some directions. 

Thank you,


Xen-arm mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [XenARM] Using a block device on XenARM, Comson <=