Centos7 fails to boot on host after Windows 10 OS update

[faseyikuoos]

Guys,

Please help out. I was having everything running smoothly until my Windows 10 Pro system had a major upgrade on Sept 10, 2020. After this the system crashed and I managed to get it up again after running xfs repair. It was stable for about two days and then I saw "Guru meditating" and the Linux VM froze. I simply killed the process and left the system. When I came back to restart it, I found out that none of my Linux VMs would start. I have about 8 different flavours ranging from Ubuntu to Centos7, Centos 8 and RHEL. The most important of these is my Centos7 as it contains several development work I was doing and many critical stuff.

When I try to start a VM, it simply stays in starting state without really booting up at all.

I have checked all the Hyper-V settings and not of the Windows Hyper-V is enabled
I also checked the BIOS virtualisation and it is enabled.

I am enclosing the logs.

[scottgus1]

my Windows 10 Pro system had a major upgrade on Sept 10, 2020. After this the system crashed and I managed to get it up again after running xfs repair

Googling 'xfs repair' indicates it is related to Red Hat and XFS filesystems, probably not the kind of tool to use on Windows.

[faseyikuoos]

Hi

I didn't mean that I used "xfs_repair" on the Windows host. I meant that when the I first experienced issues with the Linux OS Guest after the the Windows update, I resolved it with xfs_repair. The xfs_repair was done on the Centos7 Linux Guest at the time. I hope it is clearer now and I am sorry if the way I wrote the post suggested otherwise.

[faseyikuoos]

I am posting two attachments, one showing my current Windows Features. Hyper-V and related services are all disabled/
The second is how far the boot process gets and hangs indefinitely.

[mpack]

Please confirm that you uninstalled and then reinstalled VirtualBox after you had these problems. Otherwise you seem to have some kind of hardware problem:

00:27:06.377711 VMMDev: Guest Log: 19:14:01.631141 vminfo Error: Unable to connect to system D-Bus (1/3): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
00:27:11.421222 VMMDev: Guest Log: 19:14:06.679895 vminfo Error: Unable to connect to system D-Bus (2/3): Failed to connect to socket /run/dbus/system_bus_socket: Connection refused
00:27:16.547969 VMMDev: Guest Log: 19:14:11.811870 vminfo Error: Unable to connect to system D-Bus (3/3): Failed to connect to socket /run/dbus/system_bus_socket: Connection refused
00:35:05.109331 Console: Machine state changed to 'Stopping'

I confess that I don't recognize the "unable to connect to system D-bus" message. On Googling I can only find it in the context of Docker, which I believe is a third party fork and hence not supported here.

[faseyikuoos]

Hi

I confirm that I have uninstalled and re-installed like 3 times. I am sure this is something to do with the upgrade. Unfortunately for me, I have so much stuff inside the VM.

[mpack]

I'll need a response to my comment about Docker.

You won't lose your data. Worst case is that you mount the drive in another VM and read the data out.

[faseyikuoos]

Thanks.

The Docker stuff is confusing to me as well. While I have docker installed within the Linux Guest itself, I do not have Docker in Windows because that needs me to enable Container and Hyper-V features. About six months ago, I had to remove the Docker on Windows stuff just because of compatibility. After that time I wasn't using docker in my windows environment.

I do have a few other VMs one of which was named something like OpenShiftRhelDocker. But I have not used that VM for at least three months because I was not working on OpenShift for a while. So I am a bit taken aback as you are.

Just as an aside, what I have decided to do to get going for now was to try and convert the VM from Virtualbox to VHD so I can read it in Hyper-V. I am in that process but I will prefer to come back to my Virtualbox environment as I am more comfortable in VirtualBox than I am on Hyper-V. (My first attempt to write the new VDI into my Drive I failed so I am getting it to write to C: instead and I will move it thereafter. That is why the errors were show. Right now the conversion is progressing and almost 70%.