* [Qemu-devel] how to know qemu devices topology
@ 2013-06-09 5:26 yue-kvm
2013-06-10 8:50 ` Stefan Hajnoczi
0 siblings, 1 reply; 2+ messages in thread
From: yue-kvm @ 2013-06-09 5:26 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 192 bytes --]
hi,all
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?
thanks you all
[-- Attachment #2: Type: text/html, Size: 516 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] how to know qemu devices topology
2013-06-09 5:26 [Qemu-devel] how to know qemu devices topology yue-kvm
@ 2013-06-10 8:50 ` Stefan Hajnoczi
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Hajnoczi @ 2013-06-10 8:50 UTC (permalink / raw)
To: yue-kvm; +Cc: qemu-devel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-06-10 8:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-09 5:26 [Qemu-devel] how to know qemu devices topology yue-kvm
2013-06-10 8:50 ` Stefan Hajnoczi
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).