Debian doesn't boot on Windows 7 host

[anamai]

Hello,

I'm new to VirutalBox and Linux in general. Some weeks ago I installed VirtualBox on my working computer (Windows 7, 64bit) together with a Debian (32 bit) vm. The VM Image itself is a bit older (sry I dont know the exact debian version).
It was already in use on other computers, because it is needed for a collegiate project i work on. Yesterday I transfered the image to another Windows 7 64 bit Host. The virtual box version is the same on both computers: Version 5.0.10 r104061. I also downloaded the corresponding guest additions and added the iso file as secondary master (IDE Controller). I tried to boot the system. It displayed the Virtual Box starting screen, the GNU GRUB and than got stuck in a black screen with one blank white cursor in the left top corner. Moreover my mouse pointer disappers if I click on the vm. But well I get it back with Host Key.

In short: the debian vm is not booting. Did I miss something during install?

I already downloaded another vm image. I think it was ubuntu. That worked fine on my pc.

Many thanks for any help in advance. And a merry christmas for all the people that celebrate this annual festivity.

[scottgus1]

Yesterday I transferred the image to another Windows 7 64 bit Host. The virtual box version is the same on both computers

How did you do this? See this tutorial Moving a VM for how to properly copy the guest to the new host.

my mouse pointer disappears if I click on the vm. But well I get it back with Host Key.

This is normal, since your guest is text-only at that moment and the Guest Additions haven't started yet.

Maybe there's unexpected differences between hosts. See this: Minimal information needed to be able to help and post a log from the working guest on the old host and the log from this failed boot on the new host.

[anamai]

Thanks for your reply. Yes, I copied the whole VM Folder to the new pc and followed the steps descripted in the copy manual. Also I attached the VM Log File and the guests settings from the 'problem host'.
Unfortunately I can't provide the files from the working host. My work place is closed during holidays until January.


Oh and here is the amount of memory
host: 16 GB
guest: 2 GB

[loukingjr]

You are getting lots of hardening errors. What anti-virus programs are you running on the host?

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[loukingjr]

Beat ya.

[anamai]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

Uhm I thought that was what I already did. However it is attached here again. Both logs - VBox.log and VBoxHardening.log.
Currently I'm running no Anti-Virus Programm (deinstalled). Don't know if Windows Defender or some other Windows-build-in tool could cause the errors?

[Perryg]

Code: Select all

00:00:00.715476   EnablePAE         <integer> = 0x0000000000000000 (0)

I would expect that PAE should be enabled in the guest settings

Code: Select all

00:00:00.715839 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for both all CPU modes

I would also figure out why you do not have hardware-v enabled. Either in the host bios or something else is using it like Hyper-v or some other package.

[anamai]

Code: Select all

00:00:00.715476   EnablePAE         <integer> = 0x0000000000000000 (0)

I would expect that PAE should be enabled in the guest settings

Code: Select all

00:00:00.715839 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for both all CPU modes

I would also figure out why you do not have hardware-v enabled. Either in the host bios or something else is using it like Hyper-v or some other package.

I enabled PAE in the guest VM (System -> Processor). Also I activated Intel Virtualization in my BIOS. Now the accerleration tab is unlocked in the guest settings. VT-x and Nested Paging are both activated. Unfortunately, that didn't helped. The problem stays the same.

[Perryg]

How about a new log with the changes?

[anamai]

The current logs are attached. I tried to start the vm again today (28.12), but the log doesn't seem to reflect that. Well maybe I overlooked it in the log files or they are not up to date...

[Perryg]

The logs look clean now and show a working guest that was shut down properly.

What is P: drive and what is the exact reason for shutting down the guest?
How long did you leave it and I see that the guest additions are mounted so it did boot at least once?

[anamai]

P: is the device where the vm image is located. I waited approx. 5 minutes before I shut down the VM. The display remained black with the white cursor the whole time.

[Perryg]

Device = a thing made for a particular purpose; an invention or contrivance, especially a mechanical or electrical one.

[anamai]

Sorry my english is bad. I meant drive instead of device. But I still don't get your question:

What is P: drive and what is the exact reason for shutting down the guest?

P: is the drive where the vm is located and I shut down the vm on purpose because it doesn't seem to boot after a long time period. In fact, it didn't do anything. It is the same problem as descripted in my original post:

I tried to boot the system. It displayed the Virtual Box starting screen, the GNU GRUB and than got stuck in a black screen with one blank white cursor in the left top corner.

So, is there anything left I could do to get this vm to work?