Re: [Xen-devel] Unable to create VM with nic device on Arndale

[Eugene Fedotov <e.fedotov@xxxxxxxxxxx>]

> Stefano Stabellini writes ("Re: [Xen-devel] Unable to create VM with nic device on 
> Arndale"):
> > On Wed, 18 Dec 2013, Eugene Fedotov wrote:
> ...
> > > "xl create domU.conf" causes following output:
> > > Parsing config from domU.conf
> > > libxl: error: libxl_create.c:1180:domcreate_attach_vtpms: unable to add nic
> > > devices
> ...
> > > Libxl code assumes that domcreate_attach_vtpms handler called, that calls
> > > domcreate_attach_pci.
> > > Why vif is logically depend on PCI and vtpm on ARM platform? (it is
> > > confusing).
> This is just the asynchronous callback structure.  There's a function
> which starts the addition of NICs and arranges when it's done for the
> next function to be called, which is the one for adding vtpms.
>
> > Is it possible that the error message is actually wrong?
> > I guess the error is just related to the creation of the vif somehow but
> > it is printed by domcreate_attach_vtpms because it is the first callback
> > being called.
> Exactly.
>
> It's very unhelpful that this is the only message being printed.
> There really ought to be a message about which NIC failed.
>
> Can you try it again with "xl -vvvv" ?
arndale# xl -vvvv create domU.conf
Parsing config from domU.conf
libxl: debug: libxl_create.c:1296:do_domain_create: ao 0x1b3af28: 
create: how=(nil) callback=(nil) poller=0x1b34e88
libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: 
qemu-xen is unavailable, use qemu-xen-traditional instead: No such file 
or directory
libxl: debug: libxl_create.c:740:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:327:libxl__bootloader_run: no 
bootloader configured, using user supplied kernel
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch 
w=0x1b35188: deregister unregistered
libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA 
placement candidate found: nr_nodes=1, nr_cpus=1, nr_vcpus=2, 
free_memkb=1500
libxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement 
candidate with 1 nodes, 1 cpus and 1500 KB free selected
domainbuilder: detail: xc_dom_allocate: cmdline="console=hvc0 debug 
rdinit=/bin/sh", features="(null)"
libxl: debug: libxl_dom.c:353:libxl__build_pv: pv kernel mapped 0 path 
/boot/zImageU
domainbuilder: detail: xc_dom_kernel_file: filename="/boot/zImageU"
domainbuilder: detail: xc_dom_malloc_filemap    : 2816 kB
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.4, caps xen-3.0-armv7l
domainbuilder: detail: xc_dom_rambase_init: RAM starts at 80000
domainbuilder: detail: xc_dom_parse_image: called
domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary 
loader ...
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux zImage (ARM64) 
loader ...
domainbuilder: detail: xc_dom_probe_zimage64_kernel: kernel is not an 
arm64 Image
domainbuilder: detail: loader probe failed
domainbuilder: detail: xc_dom_find_loader: trying Linux zImage (ARM32) 
loader ...
domainbuilder: detail: loader probe OK
domainbuilder: detail: xc_dom_parse_zimage32_kernel: called
domainbuilder: detail: xc_dom_parse_zimage32_kernel: xen-3.0-armv7l: 
0x80008000 -> 0x802c8158
libxl: debug: libxl_arm.c:433:libxl__arch_domain_configure: constructing 
DTB for Xen version 4.4 guest
libxl: debug: libxl_arm.c:497:libxl__arch_domain_configure: fdt total 
size 1174
domainbuilder: detail: xc_dom_devicetree_mem: called
domainbuilder: detail: xc_dom_mem_init: mem 128 MB, pages 0x8000 pages, 
4k each
domainbuilder: detail: xc_dom_mem_init: 0x8000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: set_mode: guest xen-3.0-armv7l, address size 32
domainbuilder: detail: xc_dom_malloc            : 256 kB
domainbuilder: detail: arch_setup_meminit: devicetree: 0x87fff000 -> 
0x87fff496
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_alloc_segment:   kernel       : 0x80008000 
-> 0x802c9000  (pfn 0x80008 + 0x2c1 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
0x80008+0x2c1 at 0xb6771000
domainbuilder: detail: xc_dom_load_zimage_kernel: called
domainbuilder: detail: xc_dom_load_zimage_kernel: kernel seg 
0x80008000-0x802c9000
domainbuilder: detail: xc_dom_load_zimage_kernel: copy 2883928 bytes 
from blob 0xb6a73000 to dst 0xb6771000
domainbuilder: detail: xc_dom_alloc_segment:   devicetree   : 0x87fff000 
-> 0x88000000  (pfn 0x87fff + 0x1 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 
0x87fff+0x1 at 0xb6770000
domainbuilder: detail: alloc_magic_pages: called
domainbuilder: detail: count_pgtables_arm: called
domainbuilder: detail: xc_dom_build_image  : virt_alloc_end : 0x88000000
domainbuilder: detail: xc_dom_build_image  : virt_pgtab_end : 0x0
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: arch_setup_bootearly: doing nothing
domainbuilder: detail: xc_dom_compat_check: supported guest type: 
xen-3.0-armv7l <= matches
domainbuilder: detail: setup_pgtables_arm: called
domainbuilder: detail: clear_page: pfn 0x88000, mfn 0x88000
domainbuilder: detail: clear_page: pfn 0x88001, mfn 0x88001
domainbuilder: detail: start_info_arm: called
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail:    allocated
domainbuilder: detail:       malloc             : 274 kB
domainbuilder: detail:       anon mmap          : 0 bytes
domainbuilder: detail:    mapped
domainbuilder: detail:       file mmap          : 2816 kB
domainbuilder: detail:       domU mmap          : 2824 kB
domainbuilder: detail: vcpu_arm32: called
domainbuilder: detail: Initial state CPSR 0x1d3 PC 0x80008000
domainbuilder: detail: launch_vm: called, ctxt=0xb6ff6004
domainbuilder: detail: xc_dom_release: called
libxl: debug: libxl_event.c:559:libxl__ev_xswatch_register: watch 
w=0x1b37078 wpath=/local/domain/0/backend/vif/12/0/state token=3/0: 
register slotnum=3
libxl: debug: libxl_create.c:1310:do_domain_create: ao 0x1b3af28: 
inprogress: poller=0x1b34e88, flags=i
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1b37078 
wpath=/local/domain/0/backend/vif/12/0/state token=3/0: event 
epath=/local/domain/0/backend/vif/12/0/state
libxl: debug: libxl_event.c:646:devstate_watch_callback: backend 
/local/domain/0/backend/vif/12/0/state wanted state 2 still waiting state 1
libxl: debug: libxl_event.c:503:watchfd_callback: watch w=0x1b37078 
wpath=/local/domain/0/backend/vif/12/0/state token=3/0: event 
epath=/local/domain/0/backend/vif/12/0/state
libxl: debug: libxl_event.c:642:devstate_watch_callback: backend 
/local/domain/0/backend/vif/12/0/state wanted state 2 ok
libxl: debug: libxl_event.c:595:libxl__ev_xswatch_deregister: watch 
w=0x1b37078 wpath=/local/domain/0/backend/vif/12/0/state token=3/0: 
deregister slotnum=3
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch 
w=0x1b37078: deregister unregistered
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch 
w=0x1b370c0: deregister unregistered
libxl: error: libxl_create.c:1180:domcreate_attach_vtpms: unable to add 
nic devices
libxl: error: libxl_device.c:780:libxl__initiate_device_remove: unable 
to get my domid
libxl: debug: libxl_event.c:607:libxl__ev_xswatch_deregister: watch 
w=0x1b37e88: deregister unregistered
libxl: error: libxl.c:1452:devices_destroy_cb: libxl__devices_destroy 
failed for 12
libxl: debug: libxl_event.c:1560:libxl__ao_complete: ao 0x1b3af28: 
complete, rc=-3
libxl: debug: libxl_event.c:1532:libxl__ao__destroy: ao 0x1b3af28: destroy
xc: debug: hypercall buffer: total allocations:216 total releases:216
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:208 misses:4 toobig:4

Best regards,
Evgeny


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