[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [BUG 1747]Guest could't find bootable device with memory more than 3600M
- To: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
- From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
- Date: Wed, 12 Jun 2013 16:13:23 -0400
- Cc: Tim Deegan <tim@xxxxxxx>, Yongjie Ren <yongjie.ren@xxxxxxxxx>, yanqiangjun@xxxxxxxxxx, Keir Fraser <keir@xxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, hanweidong@xxxxxxxxxx, Xudong Hao <xudong.hao@xxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, luonengjun@xxxxxxxxxx, qemu-devel@xxxxxxxxxx, wangzhenguo@xxxxxxxxxx, xiaowei.yang@xxxxxxxxxx, arei.gonglei@xxxxxxxxxx, Jan Beulich <JBeulich@xxxxxxxx>, YongweiX Xu <yongweix.xu@xxxxxxxxx>, SongtaoX Liu <songtaox.liu@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
- Delivery-date: Wed, 12 Jun 2013 20:14:21 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
Il 12/06/2013 11:25, George Dunlap ha scritto:
>>> If you have 4GB of RAM it will end at 0x140000000 (or something like
>>> that) and that's where the 64-bit window starts. Of course if you have
>>> no RAM above the PCI hole, the 64-bit window will start at 0x100000000.
>> So there's no provision whatsoever for extending the amount of RAM
>> a guest may see? This is why I'd see any such allocation strategy to
>> start at the end of physical address space, moving downwards.
That'd work too, I guess.
> Is there a mechanism to do memory hot-plug in qemu at the moment? If
> not, then there's no reason to put it anywhere else.
Not yet, but then memory could also be discontiguous as long as you
describe it correctly in the tables.
Paolo
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
