All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: pci passthrough kills qemu-xen
Date: Thu, 28 Jul 2016 08:15:05 +0200	[thread overview]
Message-ID: <20160728061505.GA7365@aepfle.de> (raw)
In-Reply-To: <20160728010729.GC2861@char.us.oracle.com>


[-- Attachment #1.1: Type: text/plain, Size: 1053 bytes --]

On Wed, Jul 27, Konrad Rzeszutek Wilk wrote:

> On Mon, Jul 25, 2016 at 11:56:40AM +0200, Olaf Hering wrote:
> > device_model_override="/vm_images/xen_images/bug989250/dm.sh"
> Why that over-write? Does it call the right qemu-binary? Does that binary
> construct an /var/log/xen/qemu.. something?

To obtain the strace for qemu, which is attached to this report.

> Why not just:
> bios="seabios"

What would that do, isnt that the default?

> Anhyow I also see:
> 
> >  Xen 4.7.20160704T103633.a492556-1.xen47
> > (XEN) Xen version 4.7.20160704T103633.a492556-1.xen47 (abuild@) (gcc (SUSE Linux) 4.8.5) debug=n Mon Jul  4 12:36:33 UTC 2016
> 
> Could you recompile it with debug=y?

I will run the debug binary and report back.

> > (XEN) HVM2 restore: CPU 0
> 
> .. Huh? Where is hvmloader?
> Is it even being loaded? 

I have no idea, and was surprised by such output as well.

> May have a bit more help if you compile it with debug=y and we can
> see where hvmloader gets stuck.

Ok, thanks for the reply.

Olaf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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

  reply	other threads:[~2016-07-28  6:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25  9:56 pci passthrough kills qemu-xen Olaf Hering
2016-07-28  1:07 ` Konrad Rzeszutek Wilk
2016-07-28  6:15   ` Olaf Hering [this message]
2016-08-08 14:33   ` Olaf Hering

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=20160728061505.GA7365@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=konrad.wilk@oracle.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.