This is odd. If there isn't much load on the box, then it
shouldn't matter very much which scheduler is being used.
Since BVT was removed from unstable some time ago, I assume
that your transition from BVT to Credit involved other changes
or perhaps that you're running an older version of the credit
scheduler. As Ian pointed out, there have been a few changes
in the credit scheduler recently and many since BVT was
removed which may be relevant here.
What version of BVT and credit are you running?
On Fri, Nov 03, 2006 at 07:07:07PM +0100, Hans-Christian Armingeon wrote:
> Hi,
>
> I am having the following problem: I am sending faxes via HylaFax over a
> FritzCard USB in a domU. The Card is attached to an USB controller, which is
> passed to the domU.
>
> I had the bvt scheduler, and had no Problems with it. I switched to the
> credit scheduler a few weeks ago. Now I have the problem, that sometimes
> faxes don't get transmitted complete.
>
> The box has a very low load - none of the domains has much to do, and it is a
> dual Opteron. Sending faxes is time critical - AVM implements the capi in the
> kernel space, to have lower latency.
>
> I know, that virtualization is very bad for latency critical tasks.
>
> I tried to set the weigh of the fax sending domain to a very high level
> (4000) and the other domains to 128, but it didn't help.
>
> How can I grant a given latency to a domU? Or yould it be best, to put the
> capi stuff in dom0? I don't like to put this into dom0, because rebooting
> dom0 is much more difficult, than domU.
>
> Johnny
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home