From: Paolo Bonzini <pbonzini@redhat.com> To: George Dunlap <george.dunlap@eu.citrix.com> Cc: Tim Deegan <tim@xen.org>, Yongjie Ren <yongjie.ren@intel.com>, yanqiangjun@huawei.com, Keir Fraser <keir@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>, hanweidong@huawei.com, Xudong Hao <xudong.hao@intel.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, luonengjun@huawei.com, qemu-devel@nongnu.org, wangzhenguo@huawei.com, xiaowei.yang@huawei.com, arei.gonglei@huawei.com, Jan Beulich <JBeulich@suse.com>, YongweiX Xu <yongweix.xu@intel.com>, SongtaoX Liu <songtaox.liu@intel.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> Subject: Re: [Qemu-devel] [Xen-devel] [BUG 1747]Guest could't find bootable device with memory more than 3600M Date: Wed, 12 Jun 2013 16:13:23 -0400 [thread overview] Message-ID: <51B8D663.70503@redhat.com> (raw) In-Reply-To: <51B892D8.5040401@eu.citrix.com> 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
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com> To: George Dunlap <george.dunlap@eu.citrix.com> Cc: Tim Deegan <tim@xen.org>, Yongjie Ren <yongjie.ren@intel.com>, yanqiangjun@huawei.com, Keir Fraser <keir@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>, hanweidong@huawei.com, Xudong Hao <xudong.hao@intel.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, luonengjun@huawei.com, qemu-devel@nongnu.org, wangzhenguo@huawei.com, xiaowei.yang@huawei.com, arei.gonglei@huawei.com, Jan Beulich <JBeulich@suse.com>, YongweiX Xu <yongweix.xu@intel.com>, SongtaoX Liu <songtaox.liu@intel.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> Subject: Re: [Xen-devel] [BUG 1747]Guest could't find bootable device with memory more than 3600M Date: Wed, 12 Jun 2013 16:13:23 -0400 [thread overview] Message-ID: <51B8D663.70503@redhat.com> (raw) In-Reply-To: <51B892D8.5040401@eu.citrix.com> 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
next prev parent reply other threads:[~2013-06-12 20:13 UTC|newest] Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-07 9:20 [BUG 1747]Guest could't find bootable device with memory more than 3600M Xu, YongweiX 2013-06-07 12:15 ` Stefano Stabellini 2013-06-07 15:42 ` George Dunlap 2013-06-07 15:56 ` Stefano Stabellini 2013-06-08 7:27 ` Hao, Xudong 2013-06-10 11:49 ` George Dunlap 2013-06-11 17:26 ` [Qemu-devel] [Xen-devel] " Stefano Stabellini 2013-06-11 17:26 ` Stefano Stabellini 2013-06-12 7:25 ` [Qemu-devel] " Jan Beulich 2013-06-12 7:25 ` Jan Beulich 2013-06-12 8:31 ` [Qemu-devel] " Ian Campbell 2013-06-12 8:31 ` Ian Campbell 2013-06-12 9:02 ` [Qemu-devel] " Jan Beulich 2013-06-12 9:02 ` Jan Beulich 2013-06-12 9:22 ` [Qemu-devel] " Ian Campbell 2013-06-12 9:22 ` Ian Campbell 2013-06-12 10:07 ` [Qemu-devel] [Xen-devel] " Jan Beulich 2013-06-12 10:07 ` Jan Beulich 2013-06-12 11:23 ` [Qemu-devel] " Ian Campbell 2013-06-12 11:23 ` Ian Campbell 2013-06-12 11:56 ` [Qemu-devel] " Jan Beulich 2013-06-12 11:56 ` Jan Beulich 2013-06-12 11:59 ` [Qemu-devel] " Ian Campbell 2013-06-12 11:59 ` Ian Campbell 2013-06-12 10:05 ` [Qemu-devel] " George Dunlap 2013-06-12 10:05 ` George Dunlap 2013-06-12 10:11 ` [Qemu-devel] " Jan Beulich 2013-06-12 10:11 ` Jan Beulich 2013-06-12 10:15 ` [Qemu-devel] " George Dunlap 2013-06-12 10:15 ` George Dunlap 2013-06-12 13:23 ` [Qemu-devel] " Paolo Bonzini 2013-06-12 13:23 ` Paolo Bonzini 2013-06-12 13:49 ` [Qemu-devel] " Jan Beulich 2013-06-12 13:49 ` Jan Beulich 2013-06-12 14:02 ` [Qemu-devel] " Paolo Bonzini 2013-06-12 14:02 ` Paolo Bonzini 2013-06-12 14:19 ` [Qemu-devel] " Jan Beulich 2013-06-12 14:19 ` Jan Beulich 2013-06-12 15:25 ` [Qemu-devel] " George Dunlap 2013-06-12 15:25 ` George Dunlap 2013-06-12 20:13 ` Paolo Bonzini [this message] 2013-06-12 20:13 ` Paolo Bonzini 2013-06-13 13:44 ` [Qemu-devel] " Stefano Stabellini 2013-06-13 13:44 ` Stefano Stabellini 2013-06-13 13:54 ` [Qemu-devel] " George Dunlap 2013-06-13 13:54 ` George Dunlap 2013-06-13 14:50 ` [Qemu-devel] " Stefano Stabellini 2013-06-13 14:50 ` Stefano Stabellini 2013-06-13 15:06 ` [Qemu-devel] [Xen-devel] " Jan Beulich 2013-06-13 15:06 ` Jan Beulich 2013-06-13 15:29 ` [Qemu-devel] [Xen-devel] " George Dunlap 2013-06-13 15:29 ` George Dunlap 2013-06-13 16:13 ` [Qemu-devel] " Stefano Stabellini 2013-06-13 16:13 ` Stefano Stabellini 2013-06-13 15:34 ` [Qemu-devel] " Ian Campbell 2013-06-13 15:34 ` Ian Campbell 2013-06-13 16:55 ` [Qemu-devel] " Stefano Stabellini 2013-06-13 16:55 ` Stefano Stabellini 2013-06-13 17:22 ` [Qemu-devel] " Ian Campbell 2013-06-13 17:22 ` Ian Campbell 2013-06-14 10:53 ` [Qemu-devel] " George Dunlap 2013-06-14 10:53 ` George Dunlap 2013-06-14 11:34 ` [Qemu-devel] [Xen-devel] " Ian Campbell 2013-06-14 11:34 ` Ian Campbell 2013-06-14 14:14 ` [Qemu-devel] " George Dunlap 2013-06-14 14:14 ` George Dunlap 2013-06-14 14:36 ` [Qemu-devel] " George Dunlap 2013-06-14 14:36 ` George Dunlap 2013-06-13 14:54 ` [Qemu-devel] " Paolo Bonzini 2013-06-13 14:54 ` Paolo Bonzini 2013-06-13 15:16 ` [Qemu-devel] [Xen-devel] " Ian Campbell 2013-06-13 15:16 ` Ian Campbell 2013-06-13 15:30 ` [Qemu-devel] [Xen-devel] " George Dunlap 2013-06-13 15:30 ` George Dunlap 2013-06-13 15:36 ` [Qemu-devel] " Ian Campbell 2013-06-13 15:36 ` Ian Campbell 2013-06-13 15:40 ` [Qemu-devel] " George Dunlap 2013-06-13 15:40 ` George Dunlap 2013-06-13 15:42 ` [Qemu-devel] " Ian Campbell 2013-06-13 15:42 ` Ian Campbell 2013-06-13 15:40 ` [Qemu-devel] " Stefano Stabellini 2013-06-13 15:40 ` Stefano Stabellini
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=51B8D663.70503@redhat.com \ --to=pbonzini@redhat.com \ --cc=Ian.Campbell@citrix.com \ --cc=JBeulich@suse.com \ --cc=arei.gonglei@huawei.com \ --cc=george.dunlap@eu.citrix.com \ --cc=hanweidong@huawei.com \ --cc=keir@xen.org \ --cc=luonengjun@huawei.com \ --cc=qemu-devel@nongnu.org \ --cc=songtaox.liu@intel.com \ --cc=stefano.stabellini@eu.citrix.com \ --cc=tim@xen.org \ --cc=wangzhenguo@huawei.com \ --cc=xen-devel@lists.xensource.com \ --cc=xiaowei.yang@huawei.com \ --cc=xudong.hao@intel.com \ --cc=yanqiangjun@huawei.com \ --cc=yongjie.ren@intel.com \ --cc=yongweix.xu@intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.