I took a look on the screenshots you have on your other thread (should have looked before). Your problem may be because of the version of QEMU you are using, since you use Gutsy. I had some problems booting my VM when I upgraded to Gutsy, and had to "downgrade" the qemu packages to Feisty to have QEMU working again. Take a look here about this problem: https://bugs.launchpad.net/ubuntu/+s...mu/+bug/144368.
To do it (worked for me):
- Removed the kqemu module:
Code:
sudo modprobe --remove kqemu
- Uninstalled qemu gutsy packages:
Code:
sudo apt-get remove qemu kqemu-sources kqemu-common kqemu-modules
- Opened my sources.list file with sudo permissions
Code:
gksudo gedit /etc/apt/sources.list &
- Replaced every "gutsy" word with "feisty" and saved the file (don't close gedit).
- Updated APT to use Feisty repositories:
Code:
sudo apt-get update
- Installed qemu back again from Feisty repository:
Code:
sudo apt-get install qemu kqemu-source
- Installed qemu again as described here (make sure you remove the actual kqemu module from memory and load the new one).
- IMPORTANT: changed back the repositories. In the text editor (gedit), click "Undo" until you have replaced all "feisty" back to "gutsy". Save the file and close gedit.
- Open Synaptic and click "Update". You should have some updates for qemu. Don't upgrade! Block this feisty version. Select both packages "qemu" and "kqemu-source" and in Synaptic menu select "Package"->"Block version". Now feisty qemu packages will not be upgraded.
Then try to boot Debian again.
If Debian still fails to boot, with the "busybox" error, even with "-no-acpi" option in QEMU, (with Feisty packages, this should not happen) then consider using VirtualBox OSE (on the repositories).
Bookmarks