Re: [Xen-devel] unable to start VM after xen upgrade to 4.8.2

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf
> Of Alex Braunegg
> Sent: 01 December 2017 02:01
> To: xen-devel@xxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel