xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Łukasz Oleś" <lukaszoles@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: [vt-d][xen4-rc6] Hangs on startup
Date: Wed, 17 Mar 2010 22:48:28 +0100	[thread overview]
Message-ID: <cb0d70421003171448s4e45c007ta343a261d274473d@mail.gmail.com> (raw)
In-Reply-To: <20100317201446.GA7785@phenom.dumpdata.com>

2010/3/17 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:
> On Wed, Mar 17, 2010 at 07:20:19PM +0100, Łukasz Oleś wrote:
> This is troubling:
> # (XEN) mm.c:859:d0 Error getting mfn 40100 (pfn 5555555555555555) from L1
> entry 8000000040100473 for l1e_owner=0, pg_owner=32753

It's happening durring dom0 start with and without iommu enabled.

> You need to run Linux kernel with more debugging. Use 'debug
> loglevel=10' to see it conjoined with Xen.

I need to recompile kernel, then I will post new logs.

> Also can you try to boot your machine _without_ using X?

You mean dom0 without XWindow? I don't have XWindow.
Or you mean dom0 without Xen? It works ok.
Or you mean domU without XWindow? I will try.

> When is this happening?
> # (XEN) mm.c:859:d2 Error getting mfn 40010 (pfn 5555555555555555) from L1
> entry 0000000040010037 for l1e_owner=2, pg_owner=2

It starts to show after xm create and stops after xm destroy when I
try to pass-through devices. Without pci=[ <devices>] option there is
no such error.

> At what point does this happen in the
> guest? Can you attach the screenshot of your guest when this is
> happening?

My vnc shows only white screen. xm console doesn't work. I have no
access to guest.

Without pci option guest works fine and I can connect to it.

Regards,
Łukasz Oleś

  reply	other threads:[~2010-03-17 21:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 23:41 [vt-d][xen4-rc6] Hangs on startup Łukasz Oleś
2010-03-16 23:55 ` Konrad Rzeszutek Wilk
2010-03-17  8:21   ` Keir Fraser
2010-03-17 12:46     ` Ross Philipson
2010-03-17  8:02 ` Cui, Dexuan
2010-03-17  8:43   ` Cui, Dexuan
2010-03-17 18:20 ` Łukasz Oleś
2010-03-17 20:14   ` Konrad Rzeszutek Wilk
2010-03-17 21:48     ` Łukasz Oleś [this message]
2010-03-18 14:19       ` Konrad Rzeszutek Wilk
2010-03-21 22:30         ` Łukasz Oleś
2010-03-22 19:50           ` Konrad Rzeszutek Wilk
2010-03-22 21:06             ` Nadolski, Ed
2010-03-22 20:54               ` Konrad Rzeszutek Wilk
2010-03-22 22:11                 ` Nadolski, Ed
2010-03-22 22:05                   ` Konrad Rzeszutek Wilk
2010-03-22 22:57                   ` Sander Eikelenboom
2010-03-22 21:56             ` Łukasz Oleś
2010-03-22 21:54               ` Konrad Rzeszutek Wilk

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=cb0d70421003171448s4e45c007ta343a261d274473d@mail.gmail.com \
    --to=lukaszoles@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.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).