xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>, xen@randomwebstuff.com
Cc: xen-devel@lists.xenproject.org
Subject: Re: pvh+vcpus startup issue
Date: Wed, 28 Feb 2018 09:35:28 +0100	[thread overview]
Message-ID: <6bb59c6e-6026-c244-6645-fb8af4070f77@suse.com> (raw)
In-Reply-To: <20180228082719.bxdbzpqbhpqag4od@MacBook-Pro-de-Roger.local>

On 28/02/18 09:27, Roger Pau Monné wrote:
> On Wed, Feb 28, 2018 at 01:34:31PM +1300, xen@randomwebstuff.com 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@randomwebstuff.com wrote:
>>>> On 22/02/18 6:35 PM, Juergen Gross wrote:
>>>>> On 22/02/18 05:37, xen@randomwebstuff.com 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

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

  reply	other threads:[~2018-02-28  8:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22  4:37 pvh+vcpus startup issue xen
2018-02-22  5:35 ` Juergen Gross
2018-02-22 20:38   ` xen
2018-02-26 11:42     ` Juergen Gross
2018-02-28  0:34       ` xen
2018-02-28  8:27         ` Roger Pau Monné
2018-02-28  8:35           ` Juergen Gross [this message]
2018-02-28 22:04             ` xen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6bb59c6e-6026-c244-6645-fb8af4070f77@suse.com \
    --to=jgross@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xen@randomwebstuff.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).