My centos 7.1 MV will no longer boot on VirtualBox VM 6.1.6 r137129 win.amd64 (Apr 9 2020 19:01:29)

Discussions related to using VirtualBox on Windows hosts.
Post Reply
stewj
Posts: 1
Joined: 14. Sep 2020, 06:27

My centos 7.1 MV will no longer boot on VirtualBox VM 6.1.6 r137129 win.amd64 (Apr 9 2020 19:01:29)

Post by stewj »

Hi All,

My centos 7.1 VM no longer boots. It was working well yesterday, but today it hangs on the boot and I can't ssh into it and the console never gets to the login.

Running: VirtualBox VM 6.1.6 r137129 win.amd64 (Apr 9 2020 19:01:29) on Windows 10

However I can telnet to the ssh port, but nothing displays. So something is listening on that port.

I will upload the VM log and provide a screen shot of the console. ( I had to zip the log, it was too big to upload!)

If someone could provide some help I would greatly appreciate it.

Thank you
Stewart
Attachments
console
console
hangingConsole.PNG (41.25 KiB) Viewed 403 times
kubecombo-2020-09-14-00-44-14.zip
log file
(28.39 KiB) Downloaded 8 times
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: My centos 7.1 MV will no longer boot on VirtualBox VM 6.1.6 r137129 win.amd64 (Apr 9 2020 19:01

Post by scottgus1 »

The guest purrs along to 12 seconds, then bupkis for 19 minutes:
00:00:12.520364 NAT: Link up
00:19:39.935830 Console: Machine state changed to 'Stopping'
00:19:39.936211 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
00:19:39.936492 Changing the VM state from 'RUNNING' to 'POWERING_OFF'
However the guest environment doesn't appear to have a problem stopping the guest from running, except for one thing. You're using the VboxSVGA video card for Windows, not the VMSVGA for Linux. It appears at my uneducated guess that the guest OS can't start the GUI? If this was a recent change try changing it back.

After that, I'd say the guest OS has glitched and needs to be replaced, or fixed inside the guest OS using the OS help channels. Or make a new guest, install the OS again, attach this guest's drive as a secondary disk and gather data over to the new OS. (fwiw I just had my Raspberry Pi glitch in a similar way: text boot, allow vnc remote-in, but no GUI. Not being Linux-skilled, I had to reset the thing.)
Post Reply