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

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

Yeah milos,
                  But the PCI  device should be allowed access by all DomUs.
Hiding the device from Dom0 is not what I really want to achieve.
I have to stick to xen source code (and not dom0 or domU) to make this possible.

As ou said in the previous mail, Im working on the populate
_physmap() to force xen allocate memory for all domUs from the memory available
behind the PCI device.

I could not understand how hiding the PCI device from Dom0 related to my goal.

Thanks alot,
Dinesh C

> Date: Fri, 20 Jun 2008 18:03:20 +0100
> From: gm281@xxxxxxxxx
> To: dinesh_chan8@xxxxxxxxxxx
> Subject: Re: [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation
> CC: xen-devel@xxxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
> >> 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
> Gr(z)egor(z)

CoolHotmail : Your crazy personality deserves a unique email identity like yourname@xxxxxxxxxxxx Choose from this and hundreds other unique email ids now Try it!

Placements ? No Problem. Register Here! Try it!
Xen-devel mailing list



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