-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all.
I've just upgraded to vbox 1.5, running on a winxp pro host, and I can't start up my debian vm. Let me explain what I did. 1. I ran my debian vm under vbox 1.4, and it ran just fine. I didn't install the vbox guest additions for v1.5 at this point, since I figured I could, and probably should, do that after upgrading to vbox 1.5. 2. I at this point realized that my previous question regarding upgrading would be answered when I tried to upgrade. When attempting to install vbox 1.5 over vbox 1.4, I was told I had to uninstall vbox 1.4 first, so I did that. Then, I installed vbox 1.5, and rebooted just in case. I found that my vm was still there, and that everything was as it is supposed to be. I ran vboxmanage updatesettings -apply , and was told that config files v1.2 couldn't be upgraded to config files v1.2, which is fine of course. Then I added a serial port: vboxmanage modifyvm debian -uart1 0x3f8 4 vboxmanage modifyvm debian -uartmode1 COM2 , and this went fine without errors. Running vboxmanage showvminfo debian, verified that the serial port was added as expected. 3. I now attempted to start the vm. First, I did this with vboxmanage startvm debian, and when that didn't work, I went into the vbox gui, and hit enter to start the debian vm, (I have only 1 virtual machine). Both start-up attempts produced the same results. First, window-eyes read the status as debian powered off, then it read the status as starting the virtual machine, then it read the status as debian running. After a while, window-eyes informed me the pointer had turned into an hour glass, and then it again told me the status as starting the virtual machine. At this point, the system just sat there, and I had to use the reset button both times, ctrl+alt+del wouldn't even bring up the task manager, so that I could kill vbox. The end of vbox.log for the last run reads as follows: 00:03:21.309 Changing the VM state from 'CREATING' to 'CREATED'. 00:03:45.579 Changing the VM state from 'CREATED' to 'RUNNING'. 00:04:03.619 Guest Log: BIOS: VirtualBox 1.5.0 00:04:03.619 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) 00:04:03.652 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0) 00:04:17.580 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=03e10000 w=640 h=480 bpp=8 cbLine=0x280 00:04:54.588 TM: Giving up catch-up attempt at a 63794057885 ns lag; new total: 63794057885 ns If I should post the full log, or send it privately to someone at innotek, please let me know. Any ideas on what I should do here would be much appreciated. Thanks in advance. Greg - -- web site: http://www.romuald.net.eu.org gpg public key: http://www.romuald.net.eu.org/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) - -- Free domains: http://www.eu.org/ or mail [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG3HjY7s9z/XlyUyARAtZkAKC9q0KGO5MTcNiaCSCl7qAQuKf5eQCePlgi ebe+1SFnSF/DnP+9UsqAGnI= =lWX2 -----END PGP SIGNATURE----- _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
