On Wed, Apr 22, 2009 at 03:22:54PM +0300, Avi Kivity wrote: > ????????? wrote: > >Hello folks, > >In the past, it was said KVM would like to treat the guest OS threads > >differently in scheduling. However, till now, the qemu thread is regarded > >as a conventional user thread. Therefore, it is hard to control how much > >CPU slices one guest OS can utilize. I don't think a computing cloud > >provider likes this idea.
Although the standard scheduler tunables are per thread, it is possible to put each QEMU process into a separate CGroup, and use the cpu_shares tunable to control scheduling priority of the guest as a whole, instead of individual threads. Not sure it this is sufficient for what you want, but it is one possible option for guest scheduling.. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
