* unable to start VM after xen upgrade to 4.8.2
@ 2017-12-01 2:00 Alex Braunegg
2017-12-01 9:40 ` Paul Durrant
0 siblings, 1 reply; 3+ messages in thread
From: Alex Braunegg @ 2017-12-01 2:00 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 2909 bytes --]
Hi all,
I recently updated from xen-4.6.6 to xen-4.8.2 and I am unable to start any
guest that previously worked without issue under 4.6.6. The create process
fails with the following:
libxl: debug: libxl_event.c:636:libxl__ev_xswatch_register: watch
w=0x9cea28 wpath=/local/domain/0/device-model/1/state token=3/1: register
slotnum=3
libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x9cea28
wpath=/local/domain/0/device-model/1/state token=3/1: event
epath=/local/domain/0/device-model/1/state
libxl: debug: libxl_exec.c:398:spawn_watch_event: domain 1 device
model: spawn watch p=(null)
libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch
w=0x9cea28 wpath=/local/domain/0/device-model/1/state token=3/1: deregister
slotnum=3
libxl: error: libxl_dm.c:2189:device_model_spawn_outcome: domain 1
device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1504:domcreate_devmodel_started: device
model did not start: -3
Reading on similar issues in the past, I have validated that the versions of
xen libraries are all 4.8.2:
xen-runtime-4.8.2-3.el6.x86_64
xen-ocaml-4.8.2-3.el6.x86_64
xen-libs-4.8.2-3.el6.x86_64
xen-doc-4.8.2-3.el6.x86_64
xen-4.8.2-3.el6.x86_64
xen-licenses-4.8.2-3.el6.x86_64
xen-hypervisor-4.8.2-3.el6.x86_64
xl info:
host : intel-s5000xvn.<redacted>
release : 4.4.102-1.el6.x86_64
version : #1 SMP Fri Dec 1 08:17:06 EST 2017
machine : x86_64
nr_cpus : 8
max_cpu_id : 7
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 1861
hw_caps :
b7ebfbff:0004e3bd:20100800:00000001:00000000:00000000:00000000:00000000
virt_caps : hvm
total_memory : 8165
free_memory : 6022
sharing_freed_memory : 0
sharing_used_memory : 0
outstanding_claims : 0
free_cpus : 0
xen_major : 4
xen_minor : 8
xen_extra : .2
xen_version : 4.8.2
xen_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
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset :
xen_commandline : dom0_mem=2048M,max:2048M cpufreq=xen
dom0_max_vcpus=1 dom0_vcpus_pin
cc_compiler : gcc (GCC) 4.6.2 20111027 (Red Hat 4.6.2-1)
cc_compile_by : mockbuild
cc_compile_domain : <redacted>
cc_compile_date : Fri Dec 1 12:00:55 EST 2017
build_id : 419c922ca399ca987e0d19bef7e8823f5711ee54
xend_config_format : 4
If I roll back to my 4.6.6 version of xen using the same kernel (4.4.102),
the guest starts without issue.
Attached is the full output from "xl -vvvv create" when using xen 4.8.2. Any
suggestions is greatly appreciated.
Best regards,
Alex
[-- Attachment #2: xl_create_error_output.txt --]
[-- Type: text/plain, Size: 15599 bytes --]
[root@intel-s5000xvn ~]# xl -vvvv create /etc/xen/config/test.cfg
Parsing config from /etc/xen/config/test.cfg
libxl: debug: libxl_create.c:1614:do_domain_create: ao 0x9ccc50: create: how=(nil) callback=(nil) poller=0x9cdc20
libxl: debug: libxl_device.c:361:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=unknown
libxl: debug: libxl_device.c:396:libxl__device_disk_set_backend: Disk vdev=hda, using backend phy
libxl: debug: libxl_device.c:361:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=qdisk
libxl: debug: libxl_create.c:970:initiate_domain_create: running bootloader
libxl: debug: libxl_bootloader.c:324:libxl__bootloader_run: not a PV domain, skipping bootloader
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9ce730: deregister unregistered
domainbuilder: detail: xc_dom_allocate: cmdline="(null)", features="(null)"
domainbuilder: detail: xc_dom_kernel_file: filename="/usr/lib/xen/boot/hvmloader"
domainbuilder: detail: xc_dom_malloc_filemap : 174 kB
libxl: debug: libxl_dom.c:884:libxl__load_hvm_firmware_module: Loading BIOS: /usr/lib/xen/boot/seabios.bin
domainbuilder: detail: xc_dom_boot_xen_init: ver 4.8, 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 HVM-generic loader ...
domainbuilder: detail: loader probe OK
xc: detail: ELF: phdr: paddr=0x100000 memsz=0x33c24
xc: detail: ELF: memory: 0x100000 -> 0x133c24
domainbuilder: detail: xc_dom_mem_init: mem 1008 MB, pages 0x3f000 pages, 4k each
domainbuilder: detail: xc_dom_mem_init: 0x3f000 pages
domainbuilder: detail: xc_dom_boot_mem_init: called
domainbuilder: detail: xc_dom_malloc : 2016 kB
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail: 4KB PAGES: 0x0000000000000200
xc: detail: 2MB PAGES: 0x00000000000001f7
xc: detail: 1GB PAGES: 0x0000000000000000
domainbuilder: detail: xc_dom_build_image: called
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x100+0x34 at 0x7fdccbc37000
domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x100000 -> 0x134000 (pfn 0x100 + 0x34 pages)
xc: detail: ELF: phdr 0 at 0x7fdccbc03000 -> 0x7fdccbc2d1a0
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x134+0x40 at 0x7fdccbbf7000
domainbuilder: detail: xc_dom_alloc_segment: System Firmware module : 0x134000 -> 0x174000 (pfn 0x134 + 0x40 pages)
domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x174+0x1 at 0x7fdccbce9000
domainbuilder: detail: xc_dom_alloc_segment: HVM start info : 0x174000 -> 0x175000 (pfn 0x174 + 0x1 pages)
domainbuilder: detail: alloc_pgtables_hvm: doing nothing
domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x175000
domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x0
domainbuilder: detail: xc_dom_boot_image: called
domainbuilder: detail: bootearly: doing nothing
domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64
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 <= matches
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: clear_page: pfn 0xfefff, mfn 0xfefff
domainbuilder: detail: clear_page: pfn 0xfeffc, mfn 0xfeffc
domainbuilder: detail: domain builder memory footprint
domainbuilder: detail: allocated
domainbuilder: detail: malloc : 2021 kB
domainbuilder: detail: anon mmap : 0 bytes
domainbuilder: detail: mapped
domainbuilder: detail: file mmap : 174 kB
domainbuilder: detail: domU mmap : 468 kB
domainbuilder: detail: vcpu_hvm: called
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000
domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff001
domainbuilder: detail: xc_dom_release: called
libxl: debug: libxl_device.c:361:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=phy
libxl: debug: libxl_event.c:636:libxl__ev_xswatch_register: watch w=0x9d0900 wpath=/local/domain/0/backend/vbd/1/768/state token=3/0: register slotnum=3
libxl: debug: libxl_device.c:361:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=qdisk
libxl: debug: libxl_linux.c:221:libxl__get_hotplug_script_info: backend_kind 3, no need to execute scripts
libxl: debug: libxl_device.c:1143:device_hotplug: No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9d2040: deregister unregistered
libxl: debug: libxl_create.c:1640:do_domain_create: ao 0x9ccc50: inprogress: poller=0x9cdc20, flags=i
libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x9d0900 wpath=/local/domain/0/backend/vbd/1/768/state token=3/0: event epath=/local/domain/0/backend/vbd/1/768/state
libxl: debug: libxl_event.c:874:devstate_callback: backend /local/domain/0/backend/vbd/1/768/state wanted state 2 ok
libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch w=0x9d0900 wpath=/local/domain/0/backend/vbd/1/768/state token=3/0: deregister slotnum=3
libxl: debug: libxl_device.c:1059:device_backend_callback: calling device_backend_cleanup
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9d0900: deregister unregistered
libxl: debug: libxl_linux.c:183:libxl__hotplug_disk: Args and environment ready
libxl: debug: libxl_device.c:1157:device_hotplug: calling hotplug script: /etc/xen/scripts/block add
libxl: debug: libxl_device.c:1158:device_hotplug: extra args:
libxl: debug: libxl_device.c:1166:device_hotplug: env:
libxl: debug: libxl_device.c:1173:device_hotplug: script: /etc/xen/scripts/block
libxl: debug: libxl_device.c:1173:device_hotplug: XENBUS_TYPE: vbd
libxl: debug: libxl_device.c:1173:device_hotplug: XENBUS_PATH: backend/vbd/1/768
libxl: debug: libxl_device.c:1173:device_hotplug: XENBUS_BASE_PATH: backend
libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block add
libxl: debug: libxl_event.c:542:watchfd_callback: watch epath=/local/domain/0/backend/vbd/1/768/state token=3/0: empty slot
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9d0a00: deregister unregistered
libxl: debug: libxl_linux.c:200:libxl__get_hotplug_script_info: num_exec 1, not running hotplug scripts
libxl: debug: libxl_device.c:1143:device_hotplug: No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9d0a00: deregister unregistered
libxl: debug: libxl.c:2889:libxl__device_disk_find_local_path: Directly accessing local RAW disk /dev/zvol/storage0/xen/test/disk_sda
libxl: debug: libxl.c:2889:libxl__device_disk_find_local_path: Directly accessing local RAW disk /storage0/data-shares/iso/en_windows_7_ultimate_x64_dvd_x15-65922.iso
libxl: debug: libxl_dm.c:1500:libxl__build_device_model_args_new: Could not find user xen-qemuuser-shared, starting QEMU as root
libxl: debug: libxl_dm.c:2094:libxl__spawn_local_dm: Spawning device-model /usr/lib/xen/bin/qemu-system-i386 with arguments:
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: /usr/lib/xen/bin/qemu-system-i386
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -xen-domid
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: 1
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -chardev
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-1,server,nowait
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -no-shutdown
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -mon
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: chardev=libxl-cmd,mode=control
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -chardev
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-1,server,nowait
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -mon
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: chardev=libxenstat-cmd,mode=control
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -nodefaults
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -no-user-config
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -name
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: test
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -vnc
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: 0.0.0.0:0,websocket,x509=/etc/pki/xen,password,to=99
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -display
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: none
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -serial
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: pty
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -device
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: VGA,vgamem_mb=16
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -boot
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: order=dc
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -usb
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -usbdevice
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: tablet
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -soundhw
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: ac97
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -device
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: rtl8139,id=nic0,netdev=net0,mac=00:16:3e:df:98:fd
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -netdev
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: type=tap,id=net0,ifname=vif1.0-emu,script=no,downscript=no
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -machine
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: xenfv
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -m
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: 1008
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -drive
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: file=/dev/zvol/storage0/xen/test/disk_sda,if=ide,index=0,media=disk,format=raw,cache=writeback
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: -drive
libxl: debug: libxl_dm.c:2096:libxl__spawn_local_dm: if=ide,index=2,readonly=on,media=cdrom,id=ide-5632,file=/storage0/data-shares/iso/en_windows_7_ultimate_x64_dvd_x15-65922.iso,format=raw
libxl: debug: libxl_dm.c:2098:libxl__spawn_local_dm: Spawning device-model /usr/lib/xen/bin/qemu-system-i386 with additional environment:
libxl: debug: libxl_dm.c:2100:libxl__spawn_local_dm: XEN_QEMU_CONSOLE_LIMIT=1048576
libxl: debug: libxl_event.c:636:libxl__ev_xswatch_register: watch w=0x9cea28 wpath=/local/domain/0/device-model/1/state token=3/1: register slotnum=3
libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x9cea28 wpath=/local/domain/0/device-model/1/state token=3/1: event epath=/local/domain/0/device-model/1/state
libxl: debug: libxl_exec.c:398:spawn_watch_event: domain 1 device model: spawn watch p=(null)
libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch w=0x9cea28 wpath=/local/domain/0/device-model/1/state token=3/1: deregister slotnum=3
libxl: error: libxl_dm.c:2189:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1504:domcreate_devmodel_started: device model did not start: -3
libxl: error: libxl_dm.c:2303:kill_device_model: Device Model already exited
libxl: debug: libxl_event.c:636:libxl__ev_xswatch_register: watch w=0x9d7480 wpath=/local/domain/0/backend/vbd/1/768/state token=3/2: register slotnum=3
libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x9d7480 wpath=/local/domain/0/backend/vbd/1/768/state token=3/2: event epath=/local/domain/0/backend/vbd/1/768/state
libxl: debug: libxl_event.c:874:devstate_callback: backend /local/domain/0/backend/vbd/1/768/state wanted state 6 ok
libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch w=0x9d7480 wpath=/local/domain/0/backend/vbd/1/768/state token=3/2: deregister slotnum=3
libxl: debug: libxl_device.c:1059:device_backend_callback: calling device_backend_cleanup
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9d7480: deregister unregistered
libxl: debug: libxl_linux.c:183:libxl__hotplug_disk: Args and environment ready
libxl: debug: libxl_device.c:1157:device_hotplug: calling hotplug script: /etc/xen/scripts/block remove
libxl: debug: libxl_device.c:1158:device_hotplug: extra args:
libxl: debug: libxl_device.c:1166:device_hotplug: env:
libxl: debug: libxl_device.c:1173:device_hotplug: script: /etc/xen/scripts/block
libxl: debug: libxl_device.c:1173:device_hotplug: XENBUS_TYPE: vbd
libxl: debug: libxl_device.c:1173:device_hotplug: XENBUS_PATH: backend/vbd/1/768
libxl: debug: libxl_device.c:1173:device_hotplug: XENBUS_BASE_PATH: backend
libxl: debug: libxl_aoutils.c:593:libxl__async_exec_start: forking to execute: /etc/xen/scripts/block remove
libxl: debug: libxl_event.c:542:watchfd_callback: watch epath=/local/domain/0/backend/vbd/1/768/state token=3/2: empty slot
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9d7580: deregister unregistered
libxl: debug: libxl_linux.c:200:libxl__get_hotplug_script_info: num_exec 1, not running hotplug scripts
libxl: debug: libxl_device.c:1143:device_hotplug: No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9d7580: deregister unregistered
libxl: debug: libxl_linux.c:221:libxl__get_hotplug_script_info: backend_kind 3, no need to execute scripts
libxl: debug: libxl_device.c:1143:device_hotplug: No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9d7870: deregister unregistered
libxl: debug: libxl_linux.c:221:libxl__get_hotplug_script_info: backend_kind 6, no need to execute scripts
libxl: debug: libxl_device.c:1143:device_hotplug: No hotplug script to execute
libxl: debug: libxl_event.c:686:libxl__ev_xswatch_deregister: watch w=0x9d2c40: deregister unregistered
libxl: debug: libxl.c:1712:devices_destroy_cb: forked pid 32155 for destroy of domain 1
libxl: debug: libxl_event.c:1869:libxl__ao_complete: ao 0x9ccc50: complete, rc=-3
libxl: debug: libxl_event.c:1838:libxl__ao__destroy: ao 0x9ccc50: destroy
libxl: debug: libxl.c:1445:libxl_domain_destroy: ao 0x9cfba0: create: how=(nil) callback=(nil) poller=0x9cdc20
libxl: error: libxl.c:1575:libxl__destroy_domid: non-existant domain 1
libxl: error: libxl.c:1534:domain_destroy_callback: unable to destroy guest with domid 1
libxl: error: libxl.c:1463:domain_destroy_cb: destruction of domain 1 failed
libxl: debug: libxl_event.c:1869:libxl__ao_complete: ao 0x9cfba0: complete, rc=-21
libxl: debug: libxl.c:1454:libxl_domain_destroy: ao 0x9cfba0: inprogress: poller=0x9cdc20, flags=ic
libxl: debug: libxl_event.c:1838:libxl__ao__destroy: ao 0x9cfba0: destroy
xencall:buffer: debug: total allocations:424 total releases:424
xencall:buffer: debug: current allocations:0 maximum allocations:3
xencall:buffer: debug: cache current size:3
xencall:buffer: debug: cache hits:406 misses:3 toobig:15
[-- Attachment #3: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: unable to start VM after xen upgrade to 4.8.2
2017-12-01 2:00 unable to start VM after xen upgrade to 4.8.2 Alex Braunegg
@ 2017-12-01 9:40 ` Paul Durrant
2017-12-01 21:03 ` Alex Braunegg
0 siblings, 1 reply; 3+ messages in thread
From: Paul Durrant @ 2017-12-01 9:40 UTC (permalink / raw)
To: 'Alex Braunegg', xen-devel@lists.xenproject.org
> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xenproject.org] On Behalf
> Of Alex Braunegg
> Sent: 01 December 2017 02:01
> To: xen-devel@lists.xenproject.org
> Subject: [Xen-devel] unable to start VM after xen upgrade to 4.8.2
>
> Hi all,
>
> I recently updated from xen-4.6.6 to xen-4.8.2 and I am unable to start any
> guest that previously worked without issue under 4.6.6. The create process
> fails with the following:
>
> libxl: debug: libxl_event.c:636:libxl__ev_xswatch_register: watch
> w=0x9cea28 wpath=/local/domain/0/device-model/1/state token=3/1:
> register
> slotnum=3
> libxl: debug: libxl_event.c:573:watchfd_callback: watch w=0x9cea28
> wpath=/local/domain/0/device-model/1/state token=3/1: event
> epath=/local/domain/0/device-model/1/state
> libxl: debug: libxl_exec.c:398:spawn_watch_event: domain 1 device
> model: spawn watch p=(null)
> libxl: debug: libxl_event.c:673:libxl__ev_xswatch_deregister: watch
> w=0x9cea28 wpath=/local/domain/0/device-model/1/state token=3/1:
> deregister
> slotnum=3
> libxl: error: libxl_dm.c:2189:device_model_spawn_outcome: domain
> 1
> device model: spawn failed (rc=-3)
> libxl: error: libxl_create.c:1504:domcreate_devmodel_started: device
> model did not start: -3
>
That's QEMU failing to start which is, most likely, an incompatibility between libxl and the QEMU command line. With any luck you should have a log file called /var/log/xen/qemu-dm-<guest name>.log which in which QEMU should say what it is unhappy about.
Paul
> Reading on similar issues in the past, I have validated that the versions of
> xen libraries are all 4.8.2:
>
> xen-runtime-4.8.2-3.el6.x86_64
> xen-ocaml-4.8.2-3.el6.x86_64
> xen-libs-4.8.2-3.el6.x86_64
> xen-doc-4.8.2-3.el6.x86_64
> xen-4.8.2-3.el6.x86_64
> xen-licenses-4.8.2-3.el6.x86_64
> xen-hypervisor-4.8.2-3.el6.x86_64
>
> xl info:
>
> host : intel-s5000xvn.<redacted>
> release : 4.4.102-1.el6.x86_64
> version : #1 SMP Fri Dec 1 08:17:06 EST 2017
> machine : x86_64
> nr_cpus : 8
> max_cpu_id : 7
> nr_nodes : 1
> cores_per_socket : 4
> threads_per_core : 1
> cpu_mhz : 1861
> hw_caps :
> b7ebfbff:0004e3bd:20100800:00000001:00000000:00000000:00000000:0000000
> 0
> virt_caps : hvm
> total_memory : 8165
> free_memory : 6022
> sharing_freed_memory : 0
> sharing_used_memory : 0
> outstanding_claims : 0
> free_cpus : 0
> xen_major : 4
> xen_minor : 8
> xen_extra : .2
> xen_version : 4.8.2
> xen_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
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset :
> xen_commandline : dom0_mem=2048M,max:2048M cpufreq=xen
> dom0_max_vcpus=1 dom0_vcpus_pin
> cc_compiler : gcc (GCC) 4.6.2 20111027 (Red Hat 4.6.2-1)
> cc_compile_by : mockbuild
> cc_compile_domain : <redacted>
> cc_compile_date : Fri Dec 1 12:00:55 EST 2017
> build_id : 419c922ca399ca987e0d19bef7e8823f5711ee54
> xend_config_format : 4
>
> If I roll back to my 4.6.6 version of xen using the same kernel (4.4.102),
> the guest starts without issue.
>
> Attached is the full output from "xl -vvvv create" when using xen 4.8.2. Any
> suggestions is greatly appreciated.
>
> Best regards,
>
> Alex
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: unable to start VM after xen upgrade to 4.8.2
2017-12-01 9:40 ` Paul Durrant
@ 2017-12-01 21:03 ` Alex Braunegg
0 siblings, 0 replies; 3+ messages in thread
From: Alex Braunegg @ 2017-12-01 21:03 UTC (permalink / raw)
To: 'Paul Durrant', xen-devel
Hi Paul,
> That's QEMU failing to start which is, most likely, an incompatibility
between libxl and the QEMU command line. With any luck you should have a log
> file called /var/log/xen/qemu-dm-<guest name>.log which in which QEMU
should say what it is unhappy about.
On checking the suggested log there is the following entry:
qemu-system-i386: -vnc 0.0.0.0:0,websocket,x509=/etc/pki/xen,password,to=99:
Failed to start VNC server: address resolution failed for 0.0.0.0:on:
Servname not supported for ai_socktype
As I use websockets to present the display via a HTML5 canvas it appears
that I have been hit with a QEMU regression due to the bundled version
(2.7.0) of QEMU with xen 4.8.2:
https://github.com/qemu/qemu/commit/1b1aeb5828c978af2ec4478e552884004f23c470
#diff-446cee24164cdeb527aa48c13210c9c2
Applying that fix resolves the guest failing to start, however websockets is
still not fully functional unlike when using 4.6.6. Will have to downgrade /
upgrade the bundled version of QEMU locally.
Thanks for the advice,
Alex
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-12-01 21:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-12-01 2:00 unable to start VM after xen upgrade to 4.8.2 Alex Braunegg
2017-12-01 9:40 ` Paul Durrant
2017-12-01 21:03 ` Alex Braunegg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).