From: Stefan <proxmox@qwertz1.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Allowing VM all cores
Date: Fri, 24 Nov 2023 07:03:40 +0100 [thread overview]
Message-ID: <E403CF2A-0098-46CE-9B38-50565F5F9CD0@qwertz1.com> (raw)
In-Reply-To: <MW3PR16MB38040D3C446088A6E61CFEFDBAB9A@MW3PR16MB3804.namprd16.prod.outlook.com>
Just leave it empty to assign all cores
Am 23. November 2023 23:47:44 MEZ schrieb Ed Tump <ed@squaretfarmllc.com>:
>Hey folks,
>I'm learning this as a hobby for my radio work.
>I understand what could happen, but how can I share all cores with my VMs please?
>Do I just set each VM at the 4 cores that I have?
>Thank you,
>Ed
>
>_______________________________________________
>pve-user mailing list
>pve-user@lists.proxmox.com
>https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
prev parent reply other threads:[~2023-11-24 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 22:47 Ed Tump
2023-11-24 6:03 ` Stefan [this message]
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=E403CF2A-0098-46CE-9B38-50565F5F9CD0@qwertz1.com \
--to=proxmox@qwertz1.com \
--cc=pve-user@lists.proxmox.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox