On 02/23/2012 11:23 AM, James B. Byrne wrote:
>
> On Wed, February 22, 2012 12:25, Todd And Margo Chester
>>
>> Therefore, in your given case, think six not twelve.
>> Common advice is
>> to leave
>> one core for the host OS/scheduler. Which leaves you with
>> 5 physical
>> CPUs to
>> allocate.
>>
On Wed, February 22, 2012 12:25, Todd And Margo Chester
>
> Therefore, in your given case, think six not twelve.
> Common advice is
> to leave
> one core for the host OS/scheduler. Which leaves you with
> 5 physical
> CPUs to
> allocate.
>
Thank you. I never planned to allocate to any guest mo
On 02/21/2012 12:59 PM, James B. Byrne wrote:
> CentOS-6.2
>
> What is the maximum number of cpus can I configure for a
> single vm guest running on a host with this hardware?
>
> # lscpu
> Architecture: x86_64
> CPU op-mode(s):32-bit, 64-bit
> Byte Order:Little Endian
Am 22.02.2012 08:46, schrieb Andreas Reschke:
>> The maximum you can assign to a single VM is the amount of CPUs
>> > visible to the KVM host. So a quad core is shows as 4 CPUs to the OS,
>> > so you could assign 4 vCPUs to a guest. To see how much is available
>> > and seen by KVM run # virsh no
On Tue, Feb 21, 2012 at 2:59 PM, James B. Byrne wrote:
> CentOS-6.2
>
> What is the maximum number of cpus can I configure for a
> single vm guest running on a host with this hardware?
>
> # lscpu
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Litt
CentOS-6.2
What is the maximum number of cpus can I configure for a
single vm guest running on a host with this hardware?
# lscpu
Architecture: x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):4
On-line CPU(s) list: 0-3
Thread(s)
