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. -Bill -- Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 http://www.bfccomputing.com/ Cell: 603.252.2606 Twitter, etc.: bill_mcgonigle Page: 603.442.1833 Email, IM, VOIP: bill@xxxxxxxxxxxxxxxx Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf _______________________________________________ CentOS-virt mailing list CentOS-virt@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-virt
