This content has been marked as final. Show 11 replies
Found my issue, thanks to Dr Google.
Basically, setting in BIOS "MPS Table Mode", disabling it allowed the machine to boot normally.
Worth pointing out however, that the DL 380G6 is not compatible...
Oracle has downgraded the CCISS drivers from OVM 3.0.3 (CCISS v3.6.28) to OVM 3.1.1 (CCISS v3.6.26), which apparently changes how CCISS devices show up to the OS, because now, I have /dev/cciss/c0d1 device (my old local SR) that was previously a /dev/sdb device (and functioned fine). Now my SR is not detected by multipath (even with adding a device directive to allow it)... its a mess. In order to boot my vms I had to manually mount the cciss device, and manually run xm create..
Same issue here, 3.0.1 used /dev/sd[a-z], now with 3.1.1 the devices are /dev/cciss/cxdx
now, how to get OVM to use my existing local repository.
411seeker see my previous post regarding manually mounting the cciss device in the same place it used to be, and running xm create on the VM's cfg file. The other option is to downgrade to 3.0.3 and let Oracle do something about it
the plan is to go back to 3.0.3 and then sit and wait, and wait, ...... (too frustrating)
I only updated to 3.1.1 to hopefully resolve intermittant hangs randomly occuring on the 16 servers I have.
I was able to rebuild kernel from official Oracle kerenel source rpm with CONFIG_X86_MPPARSE=n and now ovm 3.1.1 work perfect. I can see all cpus.
Edited by: user9326326 on Jun 14, 2012 10:24 AM
got the same issue that only one CPU is showing. I know I need the RPM's from ULN but can you give some pointers on what needs to be installed and the process.
Did anybody get any luck with this ?
you need "Oracle VM Server 3.1.1 SDK Template" from edelivery, then start virtual machine end rebuild kernel from source rpm with CONFIG_X86_MPPARSE=n on that virtual machine and then install new rpm to ovm server
Hi, I have an issue with OVM 3.1.1 on a X2200 M2 server, when put the iso to boot up the server I have an error:
(XEN) Early fatal page fault at e008:ffff82c48017b38....
(XEN) Stack dump: ffff82f601c00000......bla bla bla......
Just btw. The kernel on 3.2.1 fixed this issue for me ;)