Re: [Xen-devel] pvh+vcpus startup issue

[xen@xxxxxxxxxxxxxxxxxx]

On 28/02/18 9:35 PM, Juergen Gross wrote:
> On 28/02/18 09:27, Roger Pau Monné wrote:
> > On Wed, Feb 28, 2018 at 01:34:31PM +1300, xen@xxxxxxxxxxxxxxxxxx wrote:
> > > Regards, Peter
> > > http://ri.mu Startups start here.  Hosting.  DNS.  Offsite backups.  
> > > Monitoring.  Email.
> > >
> > > On 27/02/18 12:42 AM, Juergen Gross wrote:
> > > > On 22/02/18 21:38, xen@xxxxxxxxxxxxxxxxxx wrote:
> > > > > On 22/02/18 6:35 PM, Juergen Gross wrote:
> > > > > > On 22/02/18 05:37, xen@xxxxxxxxxxxxxxxxxx wrote:
> > > > > > > Hi.  I have a domU.  Its params file has: vcpus = 8.  It will start with
> > > > > > > pv, but not type="pvh".  It will not start (on pvh) with vcpus = 7 or 6
> > > > > > > or 5.  It does start with vcpus = 4.
> > > > > > >
> > > > > > > I diffed the xl -v create logs, no difference there on either startup.
> > > > > > >
> > > > > > > I grabbed the domU console output for a vcpus = 5 start (attached).  It
> > > > > > > dies right after:
> > Dies as in crashes? Or simply gets stuck and there's no further output?
> >
> > > domU console:
> > >
> > > [    0.001000] cpu 0 spinlock event irq 5
> > > [    0.001000] Performance Events: unsupported p6 CPU model 23 no PMU driver, 
> > > software events only.
> > > [    0.001000] Hierarchical SRCU implementation.
> > > [    0.001249] smp: Bringing up secondary CPUs ...
> > > [    0.001582] installing Xen timer for CPU 1
> > > [    0.001642] x86: Booting SMP configuration:
> > > [    0.001653] .... node  #0, CPUs:      #1
> > > [    0.003157] cpu 1 spinlock event irq 11
> > > [    0.003305] installing Xen timer for CPU 2
> > > [    0.003385]  #2
> > > [    0.005152] cpu 2 spinlock event irq 17
> > > [    0.005311] installing Xen timer for CPU 3
> > > [    0.005375]  #3
> > > [    0.007107] cpu 3 spinlock event irq 23
> > > [    0.007341] installing Xen timer for CPU 4
> > Which exact kernel version is this, and can you also send the .config
> > Linux kernel file?
> >
> > > Xen domU params file:
> > >
> > > cat /home/users/ot.glenn/params
> > > kernel = "/home/users/ot.glenn/linux"
> > > memory = 2000
> > > swap = 128
> > This is not a xl option.
> >
> > > name = "ot.glenn"
> > > ipaddr = "72.x.x.x"
> > Same here.
> >
> > > disk = [ 'phy:/dev/users/ot.glenn+centos6-x86_64-4.ext3,xvda1,w', 
> > > 'phy:/dev/users/ot.glenn+swapfs.swp,xvda9,w' ]
> > > root = "/dev/xvda1 ro"
> > > restart = 'onreboot'
> > > console = 50089
> > And here.
> >
> > > type = "pvh"
> > > vcpus = 5
> > > vif = [ 'mac=aa:00:0b:67:50:64,bridge=br0' ]
> Please add:
>
> on_crash="preserve"
>
> to your domain config file and after the domain crashed call:
>
> /usr/lib/xen/bin/xenctx -C -s <kernel-with-syms> -a <domid>
>
>
> Juergen
I commented out the non-standard options from the params file. (That did 
not appear to change any behavior).
After the vm is started it just quits/exits.  When I look at the domU 
console the last thing I see is:
[    0.007151] cpu 3 spinlock event irq 23
[    0.007341] installing Xen timer for CPU 4

The domU stays in the xl list output after the on_crash preserve option 
is added and I see this:
[root@host713 ~]# /usr/lib/xen/bin/xenctx -C -s 
/opt/xen/kernels/4.14.22-rh30-20180225201441.xenU.x86_64  -a 8
vcpu0 offline

vcpu1 offline

vcpu2 offline

vcpu3 offline

vcpu4:
rip: ffffffff810013a8
flags: 00000012 nz a
rsp: ffffffff82603e18
rax: 0000000000000000    rcx: 0000000000000000    rdx: 0000000000000040
rbx: 0000000000000040    rsi: ffffffff82603e24    rdi: 0000000000000002
rbp: 0000000000000000     r8: ffffffffffffffff     r9: 0000000000000000
r10: ffff88007a418248    r11: 00180000000000ff    r12: 0000000000000000
r13: 0000000000000000    r14: ffffffff82d03680    r15: ffffc9000038fe78
 cs: 0010     ss: 0000     ds: 0000     es: 0000
 fs: 0000 @ 0000000000000000
 gs: 0000 @ ffff88007a400000/0000000000000000 +0x7a400000/

cr0: 0000000080050033
cr2: 0000000000000000
cr3: 0000000002624000
cr4: 00000000000406a0

dr0: 0000000000000000
dr1: 0000000000000000
dr2: 0000000000000000
dr3: 0000000000000000
dr6: 00000000ffff0ff0
dr7: 0000000000000400
Code (instr addr ffffffff810013a8)
cc cc cc cc cc cc cc cc cc cc cc cc cc b8 1d 00 00 00 0f 01 c1 <c3> cc 
cc cc cc cc cc cc cc cc cc
Config to the domU kernel is attached.  Since this is pvh I am not able 
to try too many different kernels (e.g. an old 2.6 or 3.0 kernel or even 
a 4.4 kernel) since those are not supported by pvh.

Attachment: config
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel