I have a machine with 8 CPU's (2 quad xeons). (Centos 5.4 currently).
Currently, I am running 2 domUs. One with 4 CPUs and another with 2. 2
remain unused. I am using routed networking.
On the one machine with 4 CPU's, there is a cronjob at 4am which
utilizes the CPU/disk pretty heavily. It is
- "Ken Bass" wrote:
> It sounds like the domU is impacting the overall Xen performance. Is
> there anything I can do to tune this? It kinda defeats the whole Xen
> virtualization concept if a single CPU messes up the network. I am
> going
> to try to add a 'nice' to the crontab for the 4am
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 environmen
Not trying to take this off-topic, I think it is relevant.
Christopher: When I booted up with dom0-cpus 1, Windows 2008 could not
"find" its second cpu. However, once up, I can "xm or virt-manager" it
down to 1 cpu on cup 0 and everything is fine.
Is this a unique issue or do you have a tweak o
Ben M. wrote:
> Not trying to take this off-topic, I think it is relevant.
>
> Christopher: When I booted up with dom0-cpus 1, Windows 2008 could not
> "find" its second cpu. However, once up, I can "xm or virt-manager" it
> down to 1 cpu on cup 0 and everything is fine.
>
> Is this a unique issu
- "Ben M." wrote:
> Not trying to take this off-topic, I think it is relevant.
>
> Christopher: When I booted up with dom0-cpus 1, Windows 2008 could not
> "find" its second cpu. However, once up, I can "xm or virt-manager" it
> down to 1 cpu on cup 0 and everything is fine.
>
> Is this a u
- "Ken Bass" wrote:
> Ben M. wrote:
> I also went into each of my guest configs and added a 'cpus="x-y"'
> line to tell the guest which CPUs it was pinned to. I made sure to exclude
> the one dom0 was running on.
If you have your guest provisioning set up with scripts or you do it manually
Haven't loaded up win 2003 vms yet. So I don't have a good test case yet.
I haven't tried to repeat it in the last two kernel updates, in part
because I didn't think it was an issue, I thought it was a matter that
if you are going to do smp, you need at least two cpus booting up and
coming into
Christopher G. Stach II wrote:
>
> If you have your guest provisioning set up with scripts or you do it manually
> with virt-install, also add --cpuset= to the arguments.
>
I use a config file located in /etc/xen that I have symlinked in the
auto directory.
Its been a while since I set it up
