On Thu, Jul 12, 2012 at 09:22:14AM +0200, Gerd Hoffmann wrote:
> On 07/11/12 18:45, Vasilis Liaskovitis wrote:
> > Hi,
> >
> > On Wed, Jul 11, 2012 at 01:56:19PM +0200, Gerd Hoffmann wrote:
> >> On 07/11/12 12:31, Vasilis Liaskovitis wrote:
> >>> In order to hotplug memory between RamSize and BUIL
On 07/11/12 18:45, Vasilis Liaskovitis wrote:
> Hi,
>
> On Wed, Jul 11, 2012 at 01:56:19PM +0200, Gerd Hoffmann wrote:
>> On 07/11/12 12:31, Vasilis Liaskovitis wrote:
>>> In order to hotplug memory between RamSize and BUILD_PCIMEM_START, the pci
>>> window needs to start at BUILD_PCIMEM_START (0x
Hi,
On Wed, Jul 11, 2012 at 01:56:19PM +0200, Gerd Hoffmann wrote:
> On 07/11/12 12:31, Vasilis Liaskovitis wrote:
> > In order to hotplug memory between RamSize and BUILD_PCIMEM_START, the pci
> > window needs to start at BUILD_PCIMEM_START (0xe000).
> > Otherwise, the guest cannot online new
On 07/11/12 12:31, Vasilis Liaskovitis wrote:
> In order to hotplug memory between RamSize and BUILD_PCIMEM_START, the pci
> window needs to start at BUILD_PCIMEM_START (0xe000).
> Otherwise, the guest cannot online new dimms at those ranges due to pci_root
> window conflicts. (workaround for l
In order to hotplug memory between RamSize and BUILD_PCIMEM_START, the pci
window needs to start at BUILD_PCIMEM_START (0xe000).
Otherwise, the guest cannot online new dimms at those ranges due to pci_root
window conflicts. (workaround for linux guest is booting with pci=nocrs)
Signed-off-by:
