Re: [Xen-devel] devel/for-linus-3.14 branch: dom0 BUG: soft lockup - CPU#1 stuck for 22s! RIP: e030:[<ffffffff81109a58>] [<ffffffff81109a58>] generic_exec_single+0x88/0xc0 xen_destroy_contiguous_region+0x160/0x160

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Tue, Jan 07, 2014 at 05:30:09PM +0100, Sander Eikelenboom wrote:
> 
> Tuesday, January 7, 2014, 3:43:55 PM, you wrote:
> 
> > On Tue, Jan 07, 2014 at 02:01:38PM +0000, David Vrabel wrote:
> >> On 07/01/14 11:53, Sander Eikelenboom wrote:
> >> > Hi Konrad,
> >> > 
> >> > A new year and a new linux merge window looming, so i thought i would 
> >> > try out the "devel/for-linus-3.14" branch.
> >> > But dom0 seems to blow up for me .. (without this branch pulled it works 
> >> > ok)
> 
> > Hot damm! Thank you for testing so quickly!
> 
> Hrmm PVH doesn't seem to be available on AMD systems yet ?

Correct.
> 
> Just tried the "pvh=1" on a (former) PV guest, but it seems it can't create 
> the guest:
> 
> xl -vvvvvvvvvvv create /etc/xen/domU/production/media.cfg
> Parsing config from /etc/xen/domU/production/media.cfg
> libxl: debug: libxl_create.c:1315:do_domain_create: ao 0x17c8a30: create: 
> how=(nil) callback=(nil) poller=0x17c9230
> libxl: error: libxl_create.c:484:libxl__domain_make: domain creation fail
> libxl: error: libxl_create.c:728:initiate_domain_create: cannot make domain: 
> -3
> libxl: error: libxl.c:1388:libxl__destroy_domid: non-existant domain -1
> libxl: error: libxl.c:1352:domain_destroy_callback: unable to destroy guest 
> with domid 4294967295
> libxl: error: libxl_create.c:1293:domcreate_destruction_cb: unable to destroy 
> domain 4294967295 following failed creation
> libxl: debug: libxl_event.c:1560:libxl__ao_complete: ao 0x17c8a30: complete, 
> rc=-3
> libxl: debug: libxl_create.c:1329:do_domain_create: ao 0x17c8a30: inprogress: 
> poller=0x17c9230, flags=ic
> libxl: debug: libxl_event.c:1532:libxl__ao__destroy: ao 0x17c8a30: destroy
> xc: debug: hypercall buffer: total allocations:11 total releases:11
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
> xc: debug: hypercall buffer: cache current size:2
> xc: debug: hypercall buffer: cache hits:9 misses:2 toobig:0
> 
> XL doesn't seem to be too helpful as to *why* though ..

Not at all.

> but xl dmesg does give a clearer error message (but perhaps xl also should ?):
> 
> (XEN) [2014-01-07 16:26:08] Attempt to create a PVH guest on a system without 
> necessary hardware support
> 
> --
> Sander
> 
> 
> # xl info
> host                   : serveerstertje
> release                : 3.13.0-rc7-20140107-xendevel+
> version                : #1 SMP Tue Jan 7 10:02:55 CET 2014
> machine                : x86_64
> nr_cpus                : 6
> max_cpu_id             : 5
> nr_nodes               : 1
> cores_per_socket       : 6
> threads_per_core       : 1
> cpu_mhz                : 3200
> hw_caps                : 
> 178bf3ff:efd3fbff:00000000:00001300:00802001:00000000:000037ff:00000000
> virt_caps              : hvm hvm_directio
> total_memory           : 20479
> free_memory            : 12050
> sharing_freed_memory   : 0
> sharing_used_memory    : 0
> outstanding_claims     : 0
> free_cpus              : 0
> xen_major              : 4
> xen_minor              : 4
> xen_extra              : -unstable
> xen_version            : 4.4-unstable
> 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          : Tue Jan 7 15:09:42 2014 +0100 git:81b1c7d-dirty
> xen_commandline        : dom0_mem=1536M,max:1536M loglvl=all loglvl_guest=all 
> console_timestamps vga=gfx-1280x1024x32 cpuidle cpufreq=xen debug lapic=debug 
> apic_verbosity=debug apic=debug iommu=on,verbose,debug,amd-iommu-debug 
> ivrs_ioapic[6]=00:14.0 ivrs_hpet[0]=00:14.0 com1=38400,8n1 console=vga,com1
> cc_compiler            : gcc-4.7.real (Debian 4.7.2-5) 4.7.2
> cc_compile_by          : root
> cc_compile_domain      : dyndns.org
> cc_compile_date        : Tue Jan  7 15:50:32 CET 2014
> xend_config_format     : 4
> 
> 
> >> > 
> >> > Xen: latest xen-unstable
> >> 
> >> The FIFO-based event channel ABI is broken in current xen-unstable.
> >> 
> >> You need the two patches from:
> >> 
> >> http://lists.xen.org/archives/html/xen-devel/2013-12/msg01458.html
> >> 
> >> You can also disable the use the FIFO ABI by the guest using the
> >> xen.fifo_events = 0 kernel command line option.
> >> 
> >> David
> 
> 

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