From: Paolo Bonzini <pbonzini@redhat.com>
To: William Heath <wgheath@gmail.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Question about suspended virtual machine resources on a kvm hypervisor
Date: Tue, 11 Mar 2014 08:49:33 +0100 [thread overview]
Message-ID: <531EC00D.4000900@redhat.com> (raw)
In-Reply-To: <CAAcUL6nCqd4fAc-8ArGJSPaLvhKY8_wbPFX3umZPnK=yPYhx2A@mail.gmail.com>
Il 10/03/2014 21:33, William Heath ha scritto:
> Hi All,
>
> I am working with OnApp for a cloud solution. In order to do billing
> correctly, I am curious what resources are freed up when a virtual
> machine is suspended on a kvm hypervisor. Are cpu, ram, and disk all
> freed up or what is reallocated to other virtual machines etc...?
A suspended VM uses no CPU. It still uses RAM, and files are still open
even though no I/O should happen.
Paolo
next prev parent reply other threads:[~2014-03-11 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 20:33 Question about suspended virtual machine resources on a kvm hypervisor William Heath
2014-03-11 7:49 ` Paolo Bonzini [this message]
2014-03-11 8:10 ` William Heath
2014-03-11 8:37 ` Paolo Bonzini
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=531EC00D.4000900@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=wgheath@gmail.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