[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Source of guest-physical address in PCI BAR for HVM domain?

  • To: "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx>, "David Stone" <unclestoner@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "David Stone" <unclestoner@xxxxxxxxx>
  • Date: Fri, 4 Jan 2008 13:25:47 -0500
  • Delivery-date: Fri, 04 Jan 2008 10:26:13 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qkgTHkUqK5DV8UPHZpujyw7EWSTpf+j86sqcEaQoRfApSa7rs+CBC/xB1iHk4D1Gyst89jizGqW8T/+B0rS4yqm88LBJmzquYJnoj7F3WiIhm+eAkOKm3YS2+AZn3IyNoTIY1aOF61JGz6U+d9kUjFmVUrU/lv2g0zzPErrKnJE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Thanks for your response.

> > So I guess this the PCI config-space write to set the BAR is passed to
> > qemu-dm as a command from the hypervisor
> Yes.

But doesn't qemu act as the BIOS for HVM domains?  Why would the
hypervisor be doing the initial PCI BAR setup?

> > If so, shouldn't the early PCI configuration from the BIOS be coming
> > from qemu itself?
> It is. It's odd you have troubles so early in the boot, is your
> configuration a bit special in any way?

Yes, I didn't mention the most important part: the device in question
is a physical PCI device (a PCI Express graphics card) that I am
passing through to the Windows 2003 guest domain via VT-d.  (The VT-d
support generally works for me because I can pass a PCI NIC through no
problem.)  (I realize VT-d'ing a PCI-XP graphics card is
experimental...but that's what I'm doing, experimenting...).


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.