All of lore.kernel.org
 help / color / mirror / Atom feed
From: Astarta <astarta@rat.ru>
To: xen-devel@lists.xen.org
Cc: David Vrabel <david.vrabel@citrix.com>
Subject: Re: [BUG] Xen vm kernel crash in get_free_entries.
Date: Thu, 17 Oct 2013 23:04:29 +0400	[thread overview]
Message-ID: <526034BD.90709@rat.ru> (raw)
In-Reply-To: <525FA61A.9080907@rat.ru>

On 10/17/2013 12:55 PM, Astarta wrote:
> On 10/16/2013 06:17 PM, Pasi Kärkkäinen wrote:
>> On Wed, Oct 16, 2013 at 02:29:07PM +0100, David Vrabel wrote:
>>> On 16/10/13 07:28, Astarta wrote:
>>>> Hello,
>>>>
>>>> This is a some kind of a follow up to the
>>>> http://lists.xen.org/archives/html/xen-devel/2013-09/msg03109.html (
>>>> Linux 3.11.1 HVM guest kernel crash when started with xl
>>>> (get_free_entries)).
>>>>
>>>> Looks like we've here the similar issue.
>>>>
>>>> Xen VM with 3.8.13 kernel crashes in get_free_entries (kernel BUG at
>>>> drivers/xen/grant-table.c:1181!), i.e in:
>>>> BUG_ON(grefs_per_grant_frame == 0);. 3.11.5 kernel behaves in exactly
>>>> the same way.
>>>>
>>>> Whole kernel log is attached. It does not contain  any "Grant tables
>>>> using version" message.
>>>>
>>>> Seems that gnttab_request_version() has was never executed, so
>>>> grefs_per_grant_frame was never set.
>>>>
>>>> Could you please advice on this issue?
>>> I think you're missing the platform pci device required for PVHVM.
>>> What's your VM's xl.cfg?
>>>
>> Yes, exactly, I had "xen_platform_pci=0" in my VM's xl.cfg,
>> and I assume Astarta has aswell.
>>
>> That is because I wanted to test *without* PVHVM, and that is a valid 
>> configuration imho..
>> (and works OK with xm/xend).
>>
>> -- Pasi
>
> Thanks for the suggestion, but there is no xl.cfg in /etc/xen/ (we're 
> using Citrix XenServer Host 6.2.0-70446c
>  on rhel 6.2), so there is no where to edit xen_platform_pci option.
>
> I've attached output from xe vm-list params=all for one of the problem 
> vm. Hope its also ok.
>
> Also 3.6 kernel works well with that configuration. I can provide it's 
> boot log if needed.
>
> Please suggest.
>
> -- 
> Marina


will answer by myself. Setting platform:device_id to 1 manually helps 
the 3.11.5 kernel to boot.
I used xe command for this in the below way.
xe vm-param-set uuid=<VM UUID> platform:device_id=0001

The issue that platform:device_id is 0002 for citrix xen by default and 
the latest kernel doesnt boot in this configuration...

Where do we go from there?

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

  reply	other threads:[~2013-10-17 19:04 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16  6:28 [BUG] Xen vm kernel crash in get_free_entries Astarta
2013-10-16 13:29 ` David Vrabel
2013-10-16 14:17   ` Pasi Kärkkäinen
2013-10-17  8:55     ` Astarta
2013-10-17 19:04       ` Astarta [this message]
2013-10-17 19:28         ` Pasi Kärkkäinen
2013-10-18  9:31           ` David Vrabel
2013-10-18  9:46             ` Ian Campbell
2013-10-18 10:31               ` Astarta
2013-10-18 11:34                 ` Paul Durrant
2013-10-18 11:06               ` Paul Durrant
2013-10-18 11:08                 ` Astarta
2013-10-18 11:27                 ` Sander Eikelenboom
2013-10-18 11:33                   ` Paul Durrant
2013-10-18 14:15               ` Pasi Kärkkäinen
2013-10-18 14:19                 ` Ian Campbell
2013-10-18 14:27                   ` Pasi Kärkkäinen
2013-10-18 23:14                   ` Sander Eikelenboom
2013-10-19 10:51                     ` Astarta
2013-10-19 11:03                       ` Ian Campbell
2013-10-19 11:58                         ` Sander Eikelenboom
2013-10-21 10:55                           ` Matt Wilson
2013-11-07  5:20                             ` Astarta
2013-11-07 13:47                               ` Ian Campbell
2013-11-12 15:56                                 ` Konrad Rzeszutek Wilk
2013-11-13  9:40                                   ` Ian Campbell
2013-11-13 12:39                                     ` Ian Campbell
2013-11-26 20:08                                     ` Konrad Rzeszutek Wilk
2013-11-26 22:00                                       ` Sander Eikelenboom
2013-11-26 22:15                                         ` Sander Eikelenboom
2013-11-26 22:55                                         ` Sander Eikelenboom
2013-11-26 23:05                                           ` Konrad Rzeszutek Wilk
2013-11-26 23:14                                             ` Sander Eikelenboom
2013-11-27  9:36                                       ` Ian Campbell
2013-11-27 14:24                                         ` Konrad Rzeszutek Wilk
2013-11-27 15:58                                           ` Ian Campbell
2013-11-27 16:40                                             ` Konrad Rzeszutek Wilk
2013-11-28 14:56                                       ` Stefano Stabellini
2013-11-29  3:26                                         ` Konrad Rzeszutek Wilk
2013-11-29 11:54                                           ` Stefano Stabellini
2013-12-09 12:57                                             ` Sander Eikelenboom
2013-12-10 15:07                                               ` Konrad Rzeszutek Wilk
2013-10-21 10:29                         ` Matt Wilson
2013-10-21 10:46                           ` David Vrabel

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=526034BD.90709@rat.ru \
    --to=astarta@rat.ru \
    --cc=david.vrabel@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.