Hello I've just updated from VBox 3.0.8 to 3.0.10 and I got surprised when starting my WinXP guest, IT DOES NOT BOOT ANY LONGER
The problem is before booting windows, it gets stuck at LILO (MY GUEST HAS NO LILO!) like when the filesystem partitions change, and it only shows LI 99 99 99 99 99 ... 99 99 99 99 99 99 ... 99 99 99 99 99 99 ... 99 99 99 99 99 99 ... Technical notes: 1. I use RAW partition: hda1:winxp hda2:swap hda3:ext3 $ VBoxManage internalcommands createrawvmdk -filename /home/alphaomega/VirtualDisks/Compaq.vmdk -rawdisk /dev/hda -partitions 1,2,3 * Note that this configuration has been in use since VBox 3.0.0 2. As far as I understand, the virtual machine accesses a virtual partition and MBR, so any change does not affect the host partitions/mbr. Compaq-pt.vmdk and Compaq.vmdk are created and this way I have used windows since VBox 3.x so it is not the problem 3. After installing VBox 3.0.10 it accesses the HOST MBR AND LILO, not the "virtual partitions" at *.vmdk and in consequence it gets stuck. Note that normally it starts from the virtual MBR and the WinXP boot sector. 4. I thought my raw partition could get damaged or corrupted, so I restored my winxp full partition image (clonezilla) and by hand forced to rewrite the MBR by calling "fdisk /mbr" INSIDE THE VBOX to avoid writing the real MBR, the record is updated but when I reebot get again "LI 99 99 99..." 5. I uninstalled VBox 3.0.10 and reinstalled back 3.0.8 ... everything is working back... so the problem is on the new version... My doubts are: - Why does it happen? - Will I be unable to update VBox to ensure my WinXP keeps working? - I have a software with license installed there, and it is registered with my VBox system/network configuration, it is not option to reinstall since I will lose the license and will have to buy a new one! so I have to make my WinXP work again AS IS. In some stage from VBox 2.x to 3.x an older windows installation stopped working and had to reinstall, but now I have software with licenses that can not lose, please help me. Apparently, the problem is that the guest accesses the host MBR/LILO instead of the virtual VMDK MBR and WinXP boot sector, that is working with my VBox 3.0.8 Thanks for any help _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
