All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com, Bruce Edge <bruce.edge@gmail.com>
Subject: Re: PCI devices missing from domU in pv kernel, hvm OK.
Date: Fri, 11 Jun 2010 09:38:58 -0400	[thread overview]
Message-ID: <20100611133857.GB4594@phenom.dumpdata.com> (raw)
In-Reply-To: <20100611060936.GM17817@reaktio.net>

On Fri, Jun 11, 2010 at 09:09:36AM +0300, Pasi Kärkkäinen wrote:
> On Thu, Jun 10, 2010 at 04:25:54PM -0700, Bruce Edge wrote:
> > I had hvm domU working fine. This problem is specific to my pv-ops
> > config. I'm not seeing any PCI devices after I bring up the domU. I
> > was able to get this working as an hvm instance, but not pv.
> > I'd appreciate if anyone could offer some insight as to why I can't
> > see the PCI devices in domU.
> > 
> > I've gone through these
> > http://wiki.xensource.com/xenwiki/XenPCIpassthrough
> > 
> 
> It seems you're missing the required kernel parameters for the domU kernel..
> They're described on that wiki page.
> 
> 
> > 
> > Here's the domU boot log:
> >         root       = /dev/nfs
> >         nfs_server = 135.149.75.134
> >         nfs_root   = /home/root,tcp
> >         initrd     = /import/root/boot/initrd.img-2.6.32.14.nfs
> >         builder      = linux
> >         kernel       =
> > /import/kaan/bedge/dev_kaan_kernel.kaan.debug/root/boot/vmlinuz-2.6.32.14
> >         memory       = 4096

And also there is a bug where we can't do PCI in PV guests when guest
has more than 3GB.

  reply	other threads:[~2010-06-11 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 23:25 PCI devices missing from domU in pv kernel, hvm OK Bruce Edge
2010-06-11  6:09 ` Pasi Kärkkäinen
2010-06-11 13:38   ` Konrad Rzeszutek Wilk [this message]
2010-06-11  7:12 ` Sander Eikelenboom

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=20100611133857.GB4594@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=bruce.edge@gmail.com \
    --cc=pasik@iki.fi \
    --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 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.