public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "Marcus White" <roastedseaweed.k@gmail.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Some more basic questions..
Date: Thu, 29 May 2014 14:45:14 +0800	[thread overview]
Message-ID: <201405291445129559886@sangfor.com> (raw)
In-Reply-To: CALAJOd1VBbe6XFwa3QabxQRSJDG-0Agq1eK56OBopYMvnnSOyg@mail.gmail.com

> Hello,
> Some more basic questions..
> 
> 1. How can I ensure that memory for the a guest is available and
> reserved? In other words, I bring up a Linux VM which has 4G
> allocated, I want to make sure it has all the 4G available right away.
> I saw references to balloon driver, it seemed like that was more for
> dynamic memory exchange between host and guest. In my case, it is a
> Linux guest with a Linux VM.
> 
Try -realtime mlock=on, this option ensure that all the memory allocated for VM  is available right away.

> 2. Does the host reclaim pages from guest if it needs it without a
>balloon driver?
> 
Yes, just consider the memory of VM as that of QEMU(user-process).

> 3. This might be a very basic question, please bear with me:) If I use
> virtio for say network and block, does network and block traffic still
> go through QEMU? Is the host part of virtio basically QEMU or is it
> something that runs in the host kernel. If QEMU, does every IO still
> pass through it? Found some conflicting information, so not a 100%
> sure. Found this, not sure if it is 100% accurate? Trying to
> understand the flow through different layers, and what the layers are.
> http://events.linuxfoundation.org/sites/events/files/slides/MasakiKimura_LinuxConNorthAmerica2013_1.pdf
> 
> 
It depends on whether you enable the vhost or something.
 
> Thank you in Advance:)
> --


  parent reply	other threads:[~2014-05-29  6:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 20:59 Some more basic questions Marcus White
2014-05-29  6:04 ` Venkateswara Rao Nandigam
2014-05-29  6:45 ` Zhang Haoyu [this message]
2014-05-30  4:06   ` Marcus White
2014-05-30  6:48     ` Zhang Haoyu
2014-06-02 21:19       ` Marcus White
2014-06-03  3:43         ` Zhang Haoyu
2014-06-03  4:53           ` Marcus White
2014-06-03  6:47             ` Zhang Haoyu
2014-06-03  6:54         ` Venkateswara Rao Nandigam
2014-06-03 11:00         ` Zhang Haoyu
2014-06-03 11:25           ` Venkateswara Rao Nandigam
2014-06-04  1:08             ` Marcus White
2014-06-05  4:42               ` Marcus White
2014-06-12 18:48                 ` Marcus White
2014-06-03 12:51           ` Zhang Haoyu

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=201405291445129559886@sangfor.com \
    --to=zhanghy@sangfor.com \
    --cc=kvm@vger.kernel.org \
    --cc=roastedseaweed.k@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