Yesterday I updated both of my OVM servers using the OVM Manger method. This resulted in a problem. The OVM Server kept booting from the wrong default image in grub and ended in single user mode with a corrupt file system (/1). To fix I had to manually select the 3.2.7 image at boot time, once I did this it appears to be running fine as 3.2.7.
Has this happened to anyone else or is it just my environment?
That didn't happen to me on any of the OVMS, that I updated through OVMM.