On Tue, Jun 16, 2009 at 01:57:55PM -0400, Bill McGonigle wrote: > On 06/15/2009 11:33 PM, Luke S Crawford wrote: > > xm sched-credit -d 0 60000 > > Ah, ha! This appears to work. I didn't need to reserve a CPU for the > dom0 (knock on wood). Much obliged, Luke. > > I'm academically curious, though - I seem to have created a CPU deadlock > of some sort, yet in 'xm top' none of the CPU's were pegged. I've got > no reason to not give dom0 utmost priority - that makes perfect sense to > me - but I'm surprised the Xen scheduler would allow me to get into this > situation by default. > Well, you have pretty weird storage setup.. dom0 iSCSI initiator depends on domU iSCSI target, which again depends on disks on dom0.. -- Pasi _______________________________________________ CentOS-virt mailing list CentOS-virt@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-virt
