NISHIGUCHI Naoki wrote:
> I understand what you mean.
> I doubt whether the rest of cpu not used by RT guest is reflected to
> credit of non-RT guests. If RT guest might monopolize the whole cpu, I
> think the rest of cpu is nothing, therefore non-RT guests have no
> credit.
>
Yes, it's an issue need to be addressed for client virtualization case, due to
the primary guest(e,g Windows) is not a trusted guest.
When detecting one RT guest is monopolize cpu for a while(e.g. 1-2minute), one
can:
1. kill the RT guest...
2. lower its priority for a while, give other guests the opportunity to run,
then restore its previous priority
Any ideas?
> As you sad, I set dom0 and HVM to RT priority(1) and tested.
> Regretfully, HVM does not work well.
>
> Attached file is output of "xm debug-keys r".
>
Oh, forgot to mention you need to pin the RT guest, or try the attached patch.
If you set one guest as high priority, it increases the chance that its vcpus
are migrated back and forth, because the priority is fixed and higher than
OVER.
Don't migrate the RT guest in practice. It's the same with Bcredit from my
previous experience, isn't it?
> Best regards,
> Naoki Nishiguchi
Best Regards,
Disheng, Su
dont_migrate_for_rt_dom.patch
Description: dont_migrate_for_rt_dom.patch
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home