[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] problem about using xl create to start a domU



CC'ing new Julien's email address.

On Thu, 5 May 2016, Stefano Stabellini wrote:
> It looks like something is wrong with xenstore. Is xenstored running?
> Can you do xenstore-ls in dom0?
> 
> On Thu, 5 May 2016, Shannon Zhao wrote:
> > Hi,
> > 
> > I'm going to create a domU for XEN on ARM64. I'm following [1] to cross
> > compile the xen tools and [2] to create domU. One thing different is
> > that I'm using Build_AEMv8A-AEMv8A fastmodel.
> > 
> > After executing "/etc/init.d/xencommons start", xl list shows:
> > 
> > Name       ID   Mem VCPUs      State   Time(s)
> > Domain-0   0   256     2     r-----      27.3
> > 
> > Then I execute "losetup /dev/loop0 domU.img" and xl create domU.cfg, it
> > prints below logs:
> > Parsing config from domU.cfg
> > libxl: error: libxl_device.c:1033:device_backend_callback: unable to add
> > device with path /local/domain/0/backend/vbd/1/51712
> > libxl: error: libxl_create.c:1252:domcreate_launch_dm: unable to add
> > disk devices
> > libxl: error: libxl_device.c:1033:device_backend_callback: unable to
> > remove device with path /local/domain/0/backend/vbd/1/51712
> > libxl: error: libxl.c:1636:devices_destroy_cb: libxl__devices_destroy
> > failed for 1
> > libxl: error: libxl.c:1564:libxl__destroy_domid: non-existant domain 1
> > libxl: error: libxl.c:1523:domain_destroy_callback: unable to destroy
> > guest with domid 1
> > libxl: error: libxl.c:1452:domain_destroy_cb: destruction of domain 1 failed
> > 
> > Is there anything I missed?
> > 
> > [1]http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling
> > [2]https://wiki.linaro.org/LEG/Engineering/Virtualization/Xen_on_ARMv8_Foundation
> > 
> > Thanks,
> > -- 
> > Shannon
> > 
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.