From mboxrd@z Thu Jan 1 00:00:00 1970 From: jd Subject: Re: KVM status and dynamic mem/cpu question. Date: Sun, 13 Jul 2008 17:23:40 -0700 (PDT) Message-ID: <694075.20097.qm@web35804.mail.mud.yahoo.com> References: <4874DCF6.2080708@mair-family.org> Reply-To: jdsw2002@yahoo.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: KVM List To: David Mair Return-path: Received: from web35804.mail.mud.yahoo.com ([66.163.179.173]:27667 "HELO web35804.mail.mud.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754505AbYGNAXl (ORCPT ); Sun, 13 Jul 2008 20:23:41 -0400 In-Reply-To: <4874DCF6.2080708@mair-family.org> Sender: kvm-owner@vger.kernel.org List-ID: Thanks David. I tried the cpu_set command... it exits the VM :( (kvm-70 on Fedora) -- 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 wrote: > From: David Mair > Subject: Re: KVM status and dynamic mem/cpu question. > To: > Cc: "KVM List" > 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 majordomo@vger.kernel.org > More majordomo info at > http://vger.kernel.org/majordomo-info.html