All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Juergen Gross" <jgross@suse.com>,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: PV guest with PCI passthrough crash on Xen 4.8.3 inside KVM when booted through OVMF
Date: Mon, 19 Feb 2018 17:49:37 +0000	[thread overview]
Message-ID: <0f4e78eb-40b3-6b45-61fc-9eb76825e6ae@citrix.com> (raw)
In-Reply-To: <00be020c-7fe9-0862-5ba5-b87eea8e3c1b@suse.com>

On 19/02/18 17:46, Juergen Gross wrote:
> On 19/02/18 18:29, Marek Marczykowski-Górecki wrote:
>> On Mon, Feb 19, 2018 at 06:23:40PM +0100, Juergen Gross wrote:
>>> On 16/02/18 20:54, Marek Marczykowski-Górecki wrote:
>>>> Just before the BUG(), there is a call to xen_raw_console_write(). But
>>>> apparently it was too early...
>>> Depends.
>>>
>>> With a debug enabled hypervisor and appropriate log levels set
>>> (guest_loglvl=all) you should see the message in the hypervisor log.
>> I've tried with guest_loglvl=all, but there was nothing. Wouldn't it
>> make sense to enable this functionality also in non-debug builds - only
>> guarded by guest_loglvl=all option?
> Hmm, I think this is on purpose to avoid the possibility of a guest
> flooding the hypervisor log.
>
> Maybe adding a new option (e.g. guest_messages=on/off) switchable at
> runtime only via "xl set-parameters" would avoid the general flooding
> problem while enabling diagnosis of such problems?

You want to recompile with CONFIG_VERBOSE, which you need EXPERT mode to
introduce into a release build.

~Andrew

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

  reply	other threads:[~2018-02-19 17:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 17:48 PV guest with PCI passthrough crash on Xen 4.8.3 inside KVM when booted through OVMF Marek Marczykowski-Górecki
2018-02-16 17:52 ` Andrew Cooper
2018-02-16 18:51   ` Marek Marczykowski-Górecki
2018-02-16 19:02     ` Andrew Cooper
2018-02-16 19:54       ` Marek Marczykowski-Górecki
2018-02-19 17:23         ` Juergen Gross
2018-02-19 17:29           ` Marek Marczykowski-Górecki
2018-02-19 17:46             ` Juergen Gross
2018-02-19 17:49               ` Andrew Cooper [this message]
2018-02-16 21:35       ` Rich Persaud
2018-02-19 17:13         ` Roger Pau Monné
2018-02-19 17:30       ` Juergen Gross
2023-11-26 14:51         ` [Xen-devel] " Marek Marczykowski-Górecki
     [not found]           ` <CACHz=ZiWufUenyw_wg+QuK86+gU5RZNkuJNzX9-K1UM5P3m8+Q@mail.gmail.com>
2023-11-27 11:26             ` Marek Marczykowski-Górecki
2023-11-27 15:56               ` Jason Andryuk
2023-11-27 16:05                 ` Juergen Gross

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=0f4e78eb-40b3-6b45-61fc-9eb76825e6ae@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=jgross@suse.com \
    --cc=marmarek@invisiblethingslab.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.