[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen-4.4-rc6 problems launching a PV guest
On 07.03.2014 14:39, Andrew Cooper wrote: > On 07/03/14 13:34, Stefan Bader wrote: >> Playing around with the release candidate of Xen-4.4 I seems to have problems >> launching a PV guest with a config that used to work with Xen-4.3. The normal >> logging would hint problems with the NIC setup (witch the slightly confusing >> origin of vtpm). >> >> Comparing the output to one produced by xen-4.3 I found a weird deregister >> of a >> watch never registered (see below) instead of a call to the hotplug script. >> Am I doing something wrong? >> >> -Stefan > > CC'ing IanJ - this looks related to the recent libxl events/forking work. Oh... maybe pebkac... Looks like several binaries can move to ../sbin instead of ../bin with the same packaging. But as packaging does not name things individually I missed them missing. Let me fix this and see whether that solves all issues... -Stefan > >> >> --- cfg --- >> name = "arg-saucy6401-pv" >> kernel = "/root/boot/pv-grub-hd0--x86_64.gz" >> memory = 4096 >> vcpus = 4 >> disk = [ >> >> 'file:/home/ec2/amis/saucy-server-uec/arg-saucy6401-pv.img,xvda1,w' >> ] >> vif = ['mac=02:e1:9c:43:ef:af,bridge=br0'] >> on_crash = "coredump-destroy" >> #device_model_version = "qemu-xen-traditional" >> >> --- log --- >> libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x9cba30: create: >> how=(nil) callback=(nil) poller=0x9c0fa0 >> libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk >> vdev=xvda1 >> spec.backend=unknown >> libxl: debug: libxl_device.c:197:disk_try_backend: Disk vdev=xvda1, backend >> phy >> unsuitable as phys path not a block device >> libxl: debug: libxl_device.c:286:libxl__device_disk_set_backend: Disk >> vdev=xvda1, using backend qdisk >> libxl: debug: libxl_create.c:797: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:618:libxl__ev_xswatch_deregister: watch >> w=0x9c13d8: >> deregister unregistered >> libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA >> placement candidate found: nr_nodes=1, nr_cpus=4, nr_vcpus=12, >> free_memkb=15612 >> libxl: debug: libxl_numa.c:475:libxl__get_numa_candidate: New best NUMA >> placement candidate found: nr_nodes=1, nr_cpus=4, nr_vcpus=12, >> free_memkb=15769 >> libxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement candidate >> with >> 1 nodes, 4 cpus and 15769 KB free selected >> domainbuilder: detail: xc_dom_allocate: cmdline="", features="(null)" >> libxl: debug: libxl_dom.c:357:libxl__build_pv: pv kernel mapped 0 path >> /root/boot/pv-grub-hd0--x86_64.gz >> domainbuilder: detail: xc_dom_kernel_file: >> filename="/root/boot/pv-grub-hd0--x86_64.gz" >> domainbuilder: detail: xc_dom_malloc_filemap : 769 kB >> domainbuilder: detail: xc_dom_malloc : 4384 kB >> domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0xc050e -> 0x448085 >> domainbuilder: detail: xc_dom_boot_xen_init: ver 4.4, caps xen-3.0-x86_64 >> xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 >> 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 bzImage loader ... >> domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage >> domainbuilder: detail: loader probe failed >> domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... >> domainbuilder: detail: loader probe OK >> xc: detail: elf_parse_binary: phdr: paddr=0x0 memsz=0x98fe68 >> xc: detail: elf_parse_binary: memory: 0x0 -> 0x98fe68 >> xc: detail: elf_xen_parse: __xen_guest: >> "GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,LOADER=generic" >> xc: detail: elf_xen_parse_guest_info: GUEST_OS="Mini-OS" >> xc: detail: elf_xen_parse_guest_info: XEN_VER="xen-3.0" >> xc: detail: elf_xen_parse_guest_info: VIRT_BASE="0x0" >> xc: detail: elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0" >> xc: detail: elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2" >> xc: detail: elf_xen_parse_guest_info: LOADER="generic" >> xc: detail: elf_xen_addr_calc_check: addresses: >> xc: detail: virt_base = 0x0 >> xc: detail: elf_paddr_offset = 0x0 >> xc: detail: virt_offset = 0x0 >> xc: detail: virt_kstart = 0x0 >> xc: detail: virt_kend = 0x98fe68 >> xc: detail: virt_entry = 0x0 >> xc: detail: p2m_base = 0xffffffffffffffff >> domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> >> 0x98fe68 >> domainbuilder: detail: xc_dom_mem_init: mem 4096 MB, pages 0x100000 pages, >> 4k each >> domainbuilder: detail: xc_dom_mem_init: 0x100000 pages >> domainbuilder: detail: xc_dom_boot_mem_init: called >> domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 >> domainbuilder: detail: xc_dom_malloc : 8192 kB >> domainbuilder: detail: xc_dom_build_image: called >> domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x0 -> 0x990000 >> (pfn 0x0 + 0x990 pages) >> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn >> 0x0+0x990 >> at 0x7f2f34eca000 >> xc: detail: elf_load_binary: phdr 0 at 0x7f2f34eca000 -> 0x7f2f34f4ab00 >> domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0x990000 -> >> 0x1190000 (pfn 0x990 + 0x800 pages) >> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn >> 0x990+0x800 >> at 0x7f2f346ca000 >> domainbuilder: detail: xc_dom_alloc_page : start info : 0x1190000 (pfn >> 0x1190) >> domainbuilder: detail: xc_dom_alloc_page : xenstore : 0x1191000 (pfn >> 0x1191) >> domainbuilder: detail: xc_dom_alloc_page : console : 0x1192000 (pfn >> 0x1192) >> domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: >> 0x0000000000000000 >> -> 0x0000ffffffffffff, 1 table(s) >> domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: >> 0x0000000000000000 >> -> 0x0000007fffffffff, 1 table(s) >> domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: >> 0x0000000000000000 >> -> 0x000000003fffffff, 1 table(s) >> domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: >> 0x0000000000000000 >> -> 0x00000000013fffff, 10 table(s) >> domainbuilder: detail: xc_dom_alloc_segment: page tables : 0x1193000 -> >> 0x11a0000 (pfn 0x1193 + 0xd pages) >> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn >> 0x1193+0xd >> at 0x7f2f382ea000 >> domainbuilder: detail: xc_dom_alloc_page : boot stack : 0x11a0000 (pfn >> 0x11a0) >> domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x11a1000 >> domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x1400000 >> 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-x86_64 >> <= matches >> domainbuilder: detail: xc_dom_compat_check: supported guest type: >> xen-3.0-x86_32p >> domainbuilder: detail: xc_dom_compat_check: supported guest type: >> hvm-3.0-x86_32 >> domainbuilder: detail: xc_dom_compat_check: supported guest type: >> hvm-3.0-x86_32p >> domainbuilder: detail: xc_dom_compat_check: supported guest type: >> hvm-3.0-x86_64 >> domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x100000 >> domainbuilder: detail: clear_page: pfn 0x1192, mfn 0x81e765 >> domainbuilder: detail: clear_page: pfn 0x1191, mfn 0x81e766 >> domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn >> 0x1190+0x1 >> at 0x7f2f382e9000 >> domainbuilder: detail: start_info_x86_64: called >> domainbuilder: detail: setup_hypercall_page: vaddr=0x2000 pfn=0x2 >> domainbuilder: detail: domain builder memory footprint >> domainbuilder: detail: allocated >> domainbuilder: detail: malloc : 12684 kB >> domainbuilder: detail: anon mmap : 0 bytes >> domainbuilder: detail: mapped >> domainbuilder: detail: file mmap : 769 kB >> domainbuilder: detail: domU mmap : 18040 kB >> domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xdfaf5 >> domainbuilder: detail: shared_info_x86_64: called >> domainbuilder: detail: vcpu_x86_64: called >> domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x1193 mfn 0x81e764 >> domainbuilder: detail: launch_vm: called, ctxt=0x7f2f383c0004 >> domainbuilder: detail: xc_dom_release: called >> libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk >> vdev=xvda1 >> spec.backend=qdisk >> libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch >> w=0x9c27a0: >> deregister unregistered >> libxl: debug: libxl_dm.c:1303:libxl__spawn_local_dm: Spawning device-model >> /usr/bin/qemu-system-i386 with arguments: >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: >> /usr/bin/qemu-system-i386 >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -xen-domid >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: 7 >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -chardev >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: >> socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-7,server,nowait >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -mon >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: >> chardev=libxl-cmd,mode=control >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -nodefaults >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -xen-attach >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -name >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: arg-saucy6401-pv >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -nographic >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -machine >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: xenpv >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: -m >> libxl: debug: libxl_dm.c:1305:libxl__spawn_local_dm: 4097 >> libxl: debug: libxl_event.c:570:libxl__ev_xswatch_register: watch w=0x9c1610 >> wpath=/local/domain/0/device-model/7/state token=3/0: register slotnum=3 >> libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x9cba30: inprogress: >> poller=0x9c0fa0, flags=i >> libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x9c1610 >> wpath=/local/domain/0/device-model/7/state token=3/0: event >> epath=/local/domain/0/device-model/7/state >> libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x9c1610 >> wpath=/local/domain/0/device-model/7/state token=3/0: event >> epath=/local/domain/0/device-model/7/state >> libxl: debug: libxl_event.c:606:libxl__ev_xswatch_deregister: watch >> w=0x9c1610 >> wpath=/local/domain/0/device-model/7/state token=3/0: deregister slotnum=3 >> libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch >> w=0x9c1610: >> deregister unregistered >> libxl: debug: libxl_qmp.c:696:libxl__qmp_initialize: connected to >> /var/run/xen/qmp-libxl-7 >> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: qmp >> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{ >> "execute": "qmp_capabilities", >> "id": 1 >> } >> ' >> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return >> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{ >> "execute": "query-chardev", >> "id": 2 >> } >> ' >> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return >> libxl: debug: libxl_qmp.c:546:qmp_send_prepare: next qmp command: '{ >> "execute": "query-vnc", >> "id": 3 >> } >> ' >> libxl: debug: libxl_qmp.c:296:qmp_handle_response: message type: return >> libxl: debug: libxl_event.c:570:libxl__ev_xswatch_register: watch w=0x9c4bd8 >> wpath=/local/domain/0/backend/vif/7/0/state token=3/1: register slotnum=3 >> libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x9c4bd8 >> wpath=/local/domain/0/backend/vif/7/0/state token=3/1: event >> epath=/local/domain/0/backend/vif/7/0/state >> libxl: debug: libxl_event.c:657:devstate_watch_callback: backend >> /local/domain/0/backend/vif/7/0/state wanted state 2 still waiting state 1 >> libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x9c4bd8 >> wpath=/local/domain/0/backend/vif/7/0/state token=3/1: event >> epath=/local/domain/0/backend/vif/7/0/state >> libxl: debug: libxl_event.c:653:devstate_watch_callback: backend >> /local/domain/0/backend/vif/7/0/state wanted state 2 ok >> libxl: debug: libxl_event.c:606:libxl__ev_xswatch_deregister: watch >> w=0x9c4bd8 >> wpath=/local/domain/0/backend/vif/7/0/state token=3/1: deregister slotnum=3 >> >> libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch >> w=0x9c4bd8: >> deregister unregistered >> libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch >> w=0x9c4c60: >> deregister unregistered >> --- >> >> This second watch getting unregistered, I do not get in xen-4.3. Also there >> never seems to be a register with that handle. In 4.3 at this point the >> hotplug >> script gets called. >> >> --- >> libxl: error: libxl_create.c:1226:domcreate_attach_vtpms: unable to add nic >> devices >> libxl: debug: libxl_dm.c:1478:kill_device_model: Device Model signaled >> libxl: error: libxl_device.c:780:libxl__initiate_device_remove: unable to >> get my >> domid >> libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch >> w=0x9c5700: >> deregister unregistered >> libxl: error: libxl_device.c:780:libxl__initiate_device_remove: unable to >> get my >> domid >> libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch >> w=0x9c5a10: >> deregister unregistered >> libxl: error: libxl.c:1457:devices_destroy_cb: libxl__devices_destroy failed >> for 7 >> libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x9cba30: complete, >> rc=-3 >> libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x9cba30: destroy >> xc: debug: hypercall buffer: total allocations:782 total releases:782 >> xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 >> xc: debug: hypercall buffer: cache current size:4 >> xc: debug: hypercall buffer: cache hits:771 misses:4 toobig:7 >> Parsing config from arg-saucy6401-pv.cfg >> >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@xxxxxxxxxxxxx >> http://lists.xen.org/xen-devel > > Attachment:
signature.asc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |