search for: 4cpus

...number of CPUs i get: setvcpus dev --guest 4 error: invalid argument: requested vcpu count is greater than the count of enabled vcpus in the domain: 4 > 2 Strange thing is when i set in the xml file: <vcpu placement='auto' current='4'>4</vcpu> the VM starts with 4CPUs and setting the CPUs works. I can do: setvcpus dev --guest 2 and: setvcpus dev --guest 4 Is this a bug? Should i try to upgrade to 1.2.10? There seem to be a lot of changes in it regarding setvcpus. thanks and cheers t.

...dows guest is Srv2008 R2 x64. Following is my test result HVM guest with pv driver, machines 1cpu and 2cpu 4cpu AMD pass pass Intel pass BSOD It seems the test result is connected with the cpu type and cpu number. AMD environment passed this test case, but Intel environment failed with 4cpus. The BSOD always caused by windows kernel file instead of windows pv driver binaries. And i failed to figure out why Intel environment with 4cpu failed this test case. I tried Xen3.4 and Xen4.0, and got the same results. "xm dmesg" and xend.log does not show any abnormal errors. I gues...

...vcpus in the domain: 4 > 2 > This sets the current number of cpus and that cannot be changed live (unless you have cpu hot(un)plug). >Strange thing is when i set in the xml file: > > <vcpu placement='auto' current='4'>4</vcpu> > >the VM starts with 4CPUs and setting the CPUs works. > Because the max is 4 and you're setting the "current" number. >I can do: > >setvcpus dev --guest 2 > >and: > >setvcpus dev --guest 4 > >Is this a bug? Should i try to upgrade to 1.2.10? There seem to be a lot >of changes...

...#39;>4</vcpu> > (unless you have cpu hot(un)plug). What is neccessary to have that? thanks and cheers t. >>Strange thing is when i set in the xml file: >> >> <vcpu placement='auto' current='4'>4</vcpu> >> >>the VM starts with 4CPUs and setting the CPUs works. >> > > Because the max is 4 and you're setting the "current" number. > >>I can do: >> >>setvcpus dev --guest 2 >> >>and: >> >>setvcpus dev --guest 4 >> >>Is this a bug? Should i try to u...

...ongrel (with 8 puppetmasterd) and this conf works fine. We''d like puppet to run clients all at same time (force a change, i.e.), so we''re testing several things. (Previous conf do not support massive execution). First and most important, is moving our server to a better host: 4cpus 8GB RAM. We also run mongrel there, but now with 4 puppetmasterd, so each one has its own cpu. With first server, we could run up to 40 clients at one time, now, 135. So we''re improving. The error in the nodes where put did not run is: err: Connection timeout calling puppetmaster.getcon...