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

Re: [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation

  • To: "dinesh chandrasekaran" <dinesh_chan8@xxxxxxxxxxx>
  • From: "Grzegorz Miłoś" <gm281@xxxxxxxxx>
  • Date: Fri, 20 Jun 2008 18:03:20 +0100
  • Cc: xen developers community <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen users community <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 20 Jun 2008 10:03:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=hULN/XGJGgqfmYsog7s3xc5nZSfxNm5yka38teo9XIiewLO6in9JZtwR6sS7OZTacc xfHLnoaTZWgW6gVis487XRQQJ8jg7tO3QYxZuTs7DHwbB0WNTdiWc/pk2eoZQ9TFYE5T p83z4D4W3MX7znoMHhRWwfh4irn8QPowF44Cc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

>> Why do you want to restrict DomU to use frames from certain range
>> only? What's the logic behind that?
> Im trying to allocate memory for domUs from memory behind a PCI device. The
> machine_addr_start is obtained by probing the device (as I know the vendor
> and device info) during xen boot-up.

That's what I was suspecting. I think you should give PCI passthrough
a go first.
PCI passthrough allows a PCI device to be hidden away from Dom0 and
exported to a DomU. You achieve the first by passing
pciback.hide=(XX:XX.X) option to Dom0 kernel and adding pci = [
'XX:XX.X′ ] to DomU config file. You'll also need
DomU and Dom0 kernel configs.

Hope this helps

Xen-devel mailing list



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