[PVE-User] Proxmox per VM memory limit

Gilberto Nunes gilberto.nunes32 at gmail.com
Wed Oct 3 14:18:35 CEST 2018


That's ok for RHEL and pure KVM/QEMU.
But I thing Proxmox staff do something to the QEMU code used in Proxmox,
because this friend of mine doesn't get a VM with more than 1 TB of memory
to work properly!

---
Gilberto Nunes Ferreira

(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram

Skype: gilberto.nunes36





Em qua, 3 de out de 2018 às 04:34, dorsy <dorsyka at yahoo.com> escreveu:

> Since it is kvm, you can look at the kvm limits:
>
> https://access.redhat.com/articles/rhel-kvm-limits
>
> On 2018. 10. 03. 5:14, Woods, Ken A (DNR) wrote:
> > I see.  I wonder if that person was confused.
> > XenServer does have a 1TB limit.
> >
> > (But, I’m not staff for them, either. )
> >
> >
> >> On Oct 2, 2018, at 18:32, Gilberto Nunes <gilberto.nunes32 at gmail.com>
> wrote:
> >>
> >> Because somebody told me that Proxmox could not address more than 1TB.
> >> Never mind!
> >>
> >> ---
> >> Gilberto Nunes Ferreira
> >>
> >> (47) 3025-5907
> >> (47) 99676-7530 - Whatsapp / Telegram
> >>
> >> Skype: gilberto.nunes36
> >>
> >>
> >>
> >>
> >>
> >> Em ter, 2 de out de 2018 às 22:23, Woods, Ken A (DNR) <
> ken.woods at alaska.gov>
> >> escreveu:
> >>
> >>> I'm not a staff member.  Just a warning--I might be totally wrong about
> >>> all this.  Or...not.
> >>>
> >>> IIRC, the coded limit is 4TiB per VM (I think there's a QEMU imposed
> limit
> >>> at 42 bits...somebody correct me if I'm wrong.) Which gets into a
> whole big
> >>> off-topic discussion about address paths and the size of page tables
> and
> >>> their structure, so....yeah.  Anyway.
> >>>
> >>> I'm going to guess (given your recent posts) that you don't have that
> much
> >>> available on the hosts, so Mark's answer is still correct--it's as
> much as
> >>> you have in your hosts.
> >>>
> >>> So we can *all* bypass some back and forth:  Are you *really* trying to
> >>> ask about memory over-commitment?
> >>> If so, the short answer is "Please don't do that if you care about
> >>> stability, which we know you do. Use ballooning."
> >>> If not, please ask the question behind "how much memory can I allocate
> to
> >>> a VM?"
> >>> In short:  Why are you asking?
> >>>
> >>> kw
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: pve-user [mailto:pve-user-bounces at pve.proxmox.com] On Behalf Of
> >>> Gilberto Nunes
> >>> Sent: Tuesday, October 02, 2018 4:45 PM
> >>> To: PVE User List
> >>> Subject: Re: [PVE-User] Proxmox per VM memory limit
> >>>
> >>> Good. Nice to hear that.
> >>> But I need someone in the Proxmox staff could answer the question...
> Just
> >>> to be more accurate about it.
> >>> Thanks
> >>>
> >>> Em ter, 2 de out de 2018 17:53, Mark Adams <mark at openvs.co.uk>
> escreveu:
> >>>
> >>>> assuming the OS in the VM supports it, as much as the host hardware
> >>>> can support (no limit).
> >>>>
> >>>> On Tue, 2 Oct 2018 at 19:35, Gilberto Nunes
> >>>> <gilberto.nunes32 at gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Hi there!
> >>>>>
> >>>>> How many memory per VM I get in PVE?
> >>>>> Is there some limit? 1 TB? 2 TB?
> >>>>> Just curious
> >>>>>
> >>>>> Thanks
> >>>>> ---
> >>>>> Gilberto Nunes Ferreira
> >>>>>
> >>>>> (47) 3025-5907
> >>>>> (47) 99676-7530 - Whatsapp / Telegram
> >>>>>
> >>>>> Skype: gilberto.nunes36
> >>>>> _______________________________________________
> >>>>> pve-user mailing list
> >>>>> pve-user at pve.proxmox.com
> >>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__pve.proxmox.com
> >>>>> _cgi-2Dbin_mailman_listinfo_pve-2Duser&d=DwIGaQ&c=teXCf5DW4bHgLDM-H5
> >>>>> _GmQ&r=THf3d3FQjCY5FQHo3goSprNAh9vsOWPUM7J0jwvvVwM&m=O4NomRKToJNrdOw
> >>>>> J3wAO9kcqxCcKNWrsS4za1ErSVTY&s=sKid9Pc9Jybmox9w3K4N93O9EX6JOtzu51KFs
> >>>>> Kxl0Ow&e=
> >>>> _______________________________________________
> >>>> pve-user mailing list
> >>>> pve-user at pve.proxmox.com
> >>>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__pve.proxmox.com_c
> >>>> gi-2Dbin_mailman_listinfo_pve-2Duser&d=DwIGaQ&c=teXCf5DW4bHgLDM-H5_GmQ
> >>>> &r=THf3d3FQjCY5FQHo3goSprNAh9vsOWPUM7J0jwvvVwM&m=O4NomRKToJNrdOwJ3wAO9
> >>>> kcqxCcKNWrsS4za1ErSVTY&s=sKid9Pc9Jybmox9w3K4N93O9EX6JOtzu51KFsKxl0Ow&e
> >>>> =
> >>> _______________________________________________
> >>> pve-user mailing list
> >>> pve-user at pve.proxmox.com
> >>>
> >>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__pve.proxmox.com_cgi-2Dbin_mailman_listinfo_pve-2Duser&d=DwIGaQ&c=teXCf5DW4bHgLDM-H5_GmQ&r=THf3d3FQjCY5FQHo3goSprNAh9vsOWPUM7J0jwvvVwM&m=O4NomRKToJNrdOwJ3wAO9kcqxCcKNWrsS4za1ErSVTY&s=sKid9Pc9Jybmox9w3K4N93O9EX6JOtzu51KFsKxl0Ow&e=
> >>> _______________________________________________
> >>> pve-user mailing list
> >>> pve-user at pve.proxmox.com
> >>>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__pve.proxmox.com_cgi-2Dbin_mailman_listinfo_pve-2Duser&d=DwIGaQ&c=teXCf5DW4bHgLDM-H5_GmQ&r=THf3d3FQjCY5FQHo3goSprNAh9vsOWPUM7J0jwvvVwM&m=2r81_0E8RDPUSCnhh4F6b1qUaFAdLE9NSiUyVU0s5vk&s=8zb236duzJWtRHiLhx8TL0fTMsyKm-v3Pd_jJ00NpoA&e=
> >> _______________________________________________
> >> pve-user mailing list
> >> pve-user at pve.proxmox.com
> >>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__pve.proxmox.com_cgi-2Dbin_mailman_listinfo_pve-2Duser&d=DwIGaQ&c=teXCf5DW4bHgLDM-H5_GmQ&r=THf3d3FQjCY5FQHo3goSprNAh9vsOWPUM7J0jwvvVwM&m=2r81_0E8RDPUSCnhh4F6b1qUaFAdLE9NSiUyVU0s5vk&s=8zb236duzJWtRHiLhx8TL0fTMsyKm-v3Pd_jJ00NpoA&e=
> > _______________________________________________
> > pve-user mailing list
> > pve-user at pve.proxmox.com
> > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>


More information about the pve-user mailing list