I don't at this point know if this is a Cloudmin issue -- it almost looks more like a CentOS issue -- but --
I have a CentOS 5 Xen host happily running CentOS 5 guests. I've built a CentOS 6 64-bit guest on this system recently, and it runs fine with one exception -
I can set the virtual CPU's on the CentOS 5 guests from Cloudmin and pin them to individual CPU's. The CentOS 6 guest host only appears to have one physical cpu (I'ts a 4-core machine). I've tried setting the number of CPU's manually in the Xen .cfg file for the virtual host, and still no joy - it only has one cpu after booting.
SO -- my question is -- is this just a CentOS 6 thing (I cannot seem to find any docs that say it's supposed to work that way) or is it something else, like a Cloudmin issue?
Comments
Submitted by JamieCameron on Sat, 05/04/2013 - 16:25 Comment #1
Would it be possible for you to attach the Xen .cfg file for the CentOS 6 guest to this bug?
Also, I'd be interested to see the output from the
dmesgcommand..Submitted by cruiskeen on Sat, 05/04/2013 - 19:37 Comment #2
Hmm --- Give me a little while here - I am at this point pretty sure it's some form of operator error -
If I build a DIFFERENT virtual machine from the same image that I built, it seems to work fine. So - something non-obvious is up.
Submitted by cruiskeen on Sat, 05/04/2013 - 19:59 Comment #3
Oh --- THAT"s interesting. It depends on what server I install it on. One of these servers seems to have decided that it only has one core - all of my other servers of the same model still believe they have 4 - at least if I cat the /proc/cpuinfo that's what I get.
I've actually seen this before on these IBM servers, but didn't realize that was the issue. Usually rebooting makes the server realize it has 4 cores again.
Sorry for the red herring.
Submitted by JamieCameron on Sat, 05/04/2013 - 20:31 Comment #4
Ok, glad you got it figured out!
Submitted by Issues on Sat, 05/18/2013 - 23:21 Comment #5
Automatically closed -- issue fixed for 2 weeks with no activity.