On Sun, Jul 13, 2008 at 9:23 PM, jd <[EMAIL PROTECTED]> wrote:
> Thanks David.
>
> I tried the cpu_set command... it exits the VM :( (kvm-70 on Fedora)
cpu_set does not have this meaning. It is just issues ACPI commands
for hot-adding/removing the cpu.

But it shouldn't exit the VM anyway. It sounds like a bug. Can you
please open a detailed bug report about this, if this is the case?

> -- What about memory ?
> -- Any one else on paused state at least ? (can I look at CPU reg.. or 
> something ?)
>
> Thanks
> /Jd
>
>
>
> --- On Wed, 7/9/08, David Mair <[EMAIL PROTECTED]> wrote:
>
>> From: David Mair <[EMAIL PROTECTED]>
>> Subject: Re: KVM status and dynamic mem/cpu question.
>> To:
>> Cc: "KVM List" <[email protected]>
>> Date: Wednesday, July 9, 2008, 8:44 AM
>> jd wrote:
>> > hi
>> >
>> > 1.   It there away to know various states of a VM via
>> console (or any other means?) ?
>> >        -- Running
>> >        -- Paused
>> >        -- Booting/Shutting down
>> >        -- crashed
>> >       etc ?
>> >     I cant find any console command that can tell
>> that. If this is not available, is there a plan to add it ?
>>
>> I don't think booting and shutting down have any
>> meaning to qemu. It's just a
>> physical PC for these purposes. Booting and shutting down
>> are runtime that only
>> means something to the software running on the PC. As far
>> as the PC is concerned it
>> feels pretty much either on or off.
>>
>> The same is almost true for crashed IMO. Crashed is a
>> runtime state for the software
>> running on the PC, not a state of the hardware - except for
>> a small number of cases.
>>
>> That leaves you with running or paused. I can't find a
>> way to tell those states from
>> the console.
>>
>> > 2. Is there a way to shrink/expand memory or VCPUs for
>> a running VM ?
>>
>>
>> I've never tried it but in the qemu console:
>>
>> (qemu) help
>>       .
>>       .
>>       .
>> cpu_set cpu [online|offline] -- change cpu state
>>       .
>>       .
>>       .
>>
>> As described, it won't let you add CPUs above what you
>> specified on the command line
>> that started the VM but it will let you do effectively the
>> same thing as removing
>> and adding CPUs from/to the guest.
>>
>> ---
>> David.
>> --
>> To unsubscribe from this list: send the line
>> "unsubscribe kvm" in
>> the body of a message to [EMAIL PROTECTED]
>> More majordomo info at
>> http://vger.kernel.org/majordomo-info.html
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Glauber Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to