Christopher G. Stach II wrote: > In high I/O environments or ones with a lot of unpredictable guests, it's a good idea to pin dom0's CPU(s) to physical cores and exclude those cores from the guests. I find that dom0 usually only needs one CPU (pinned to one core) in almost every environment. For example, on an 8 core box, dom0 gets CPU 0 (dom0-cpus 1) and all of the guests us Thanks alot for the suggestion. I went ahead and did just as you mentioned. I'll see if this fixes my networking issue when the guest runs its 4am cronjob.