From: Stefan Hajnoczi <stefanha@gmail.com>
To: yue-kvm <kvmluck@163.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] how to know qemu devices topology
Date: Mon, 10 Jun 2013 10:50:12 +0200 [thread overview]
Message-ID: <20130610085012.GF5308@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <76dc6b74.74fe.13f27664473.Coremail.kvmluck@163.com>
On Sun, Jun 09, 2013 at 01:26:21PM +0800, yue-kvm wrote:
> 1. how could i know how many devices qemu support and hardware topology of all of them?
>
> 2.the quantitativerestriction of guest's devices. vcpu,disk,ethernet,memory?
Some resources are limited by the bus (e.g. PCI slots). The details
depend on the machine type because the emulated busses are different.
Other resources may be limited on guest factors like firmware tables or
device tree.
Others may be limited only by host hardware resources.
Your question is very broad and you need to look into specifics to find
the answers. If you want a quick solution, I suggest looking at vendor
documentation - for example, look what distros shipping KVM say about
x86 guest limits.
Stefan
prev parent reply other threads:[~2013-06-10 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 5:26 [Qemu-devel] how to know qemu devices topology yue-kvm
2013-06-10 8:50 ` Stefan Hajnoczi [this message]
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=20130610085012.GF5308@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=kvmluck@163.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).