Cannot start VM/Cannot change settings

[alaiya]

Hey there,

I've run into a problem with a VM. I am using the CentOS6.2 VM from Sourceforge and so far everything has been fine.

But I just restarted my PC because of some windows hiccup and suddenly was unable to start both the CentOS VMs I have. (They are in different folders of course)

With both I get the error message Cannot connect file "/home/tom/Downloads/CentOS-6.2-x84_64-LiveCD.iso" as a CD-ROM image: Could not find the file

Now of course there is no file "home/tom" because my PC itself runs Windows. But indeed the CD-ROM now suddenly features that file. Only problem is: When I go to Settings, I cannot change it. The entire setting window is greyed out, so I cannot change a thing.

What has happened? What can I do?

I need that VM. I am working on a project for university and my entire progress is on that VM.

[a_p_]

Welcome to the Community,

please post a list of complete files from one of the VM's folders and attach that VM's .vmx file as well as its latest vmware.log to a reply post.

André

[alaiya]

Of course.

06.02.2016  22:24	<DIR>	.
06.02.2016  22:24	<DIR>	..
06.02.2016  20:36	4.009.754.624 centos-6.2-x64-virtual-machine-org-c8c5a9e6.vmem
06.02.2016  20:36	1.603.877 centos-6.2-x64-virtual-machine-org-c8c5a9e6.vmss
06.02.2016  20:32	2.128.216.064 centos-6.2-x64-virtual-machine-org-s001.vmdk
06.02.2016  20:32	2.062.942.208 centos-6.2-x64-virtual-machine-org-s002.vmdk
06.02.2016  20:32	871.170.048 centos-6.2-x64-virtual-machine-org-s003.vmdk
06.02.2016  20:32	531.562.496 centos-6.2-x64-virtual-machine-org-s004.vmdk
06.02.2016  20:32	99.811.328 centos-6.2-x64-virtual-machine-org-s005.vmdk
06.02.2016  20:32	84.344.832 centos-6.2-x64-virtual-machine-org-s006.vmdk
06.02.2016  20:32	466.681.856 centos-6.2-x64-virtual-machine-org-s007.vmdk
06.02.2016  20:32	366.084.096 centos-6.2-x64-virtual-machine-org-s008.vmdk
06.02.2016  20:32	204.865.536 centos-6.2-x64-virtual-machine-org-s009.vmdk
06.02.2016  20:32	51.052.544 centos-6.2-x64-virtual-machine-org-s010.vmdk
06.02.2016  20:32	275.841.024 centos-6.2-x64-virtual-machine-org-s011.vmdk
06.02.2016  20:32	90.439.680 centos-6.2-x64-virtual-machine-org-s012.vmdk
06.02.2016  19:58	589.824 centos-6.2-x64-virtual-machine-org-s013.vmdk
06.02.2016  15:02	524.288 centos-6.2-x64-virtual-machine-org-s014.vmdk
06.02.2016  15:02	393.216 centos-6.2-x64-virtual-machine-org-s015.vmdk
06.02.2016  15:03	458.752 centos-6.2-x64-virtual-machine-org-s016.vmdk
06.02.2016  15:03	393.216 centos-6.2-x64-virtual-machine-org-s017.vmdk
06.02.2016  15:03	393.216 centos-6.2-x64-virtual-machine-org-s018.vmdk
06.02.2016  15:03	393.216 centos-6.2-x64-virtual-machine-org-s019.vmdk
06.02.2016  15:03	393.216 centos-6.2-x64-virtual-machine-org-s020.vmdk
06.02.2016  15:03	655.360 centos-6.2-x64-virtual-machine-org-s021.vmdk
06.02.2016  15:03	458.752 centos-6.2-x64-virtual-machine-org-s022.vmdk
06.02.2016  19:58	589.824 centos-6.2-x64-virtual-machine-org-s023.vmdk
06.02.2016  15:03	393.216 centos-6.2-x64-virtual-machine-org-s024.vmdk
06.02.2016  15:03	393.216 centos-6.2-x64-virtual-machine-org-s025.vmdk
06.02.2016  15:03	393.216 centos-6.2-x64-virtual-machine-org-s026.vmdk
06.02.2016  20:17	702.480.384 centos-6.2-x64-virtual-machine-org-s027.vmdk
06.02.2016  15:03	327.680 centos-6.2-x64-virtual-machine-org-s028.vmdk
06.02.2016  15:03	327.680 centos-6.2-x64-virtual-machine-org-s029.vmdk
06.02.2016  15:03	327.680 centos-6.2-x64-virtual-machine-org-s030.vmdk
06.02.2016  15:03	65.536 centos-6.2-x64-virtual-machine-org-s031.vmdk
06.02.2016  20:37	8.684 centos-6.2-x64-virtual-machine-org.nvram
06.02.2016  20:27	2.460 centos-6.2-x64-virtual-machine-org.vmdk
06.02.2016  15:03	0 centos-6.2-x64-virtual-machine-org.vmsd
06.02.2016  21:48	3.079 centos-6.2-x64-virtual-machine-org.vmx
06.02.2016  21:55	<DIR>	centos-6.2-x64-virtual-machine-org.vmx.lck
06.02.2016  20:32	396 centos-6.2-x64-virtual-machine-org.vmxf

[Ahmed_Selim]

Hey Alaiya,

It seems that your virtual machine in the suspended state and you cannot configure or remove the drive while the virtual machine is suspended.

Try to change the virtual machine to shutdown state and try to link the cdrom to the new ISO file

Best Regards,

Ahmed

[a_p_]

I agree with Ahmed_Selim‌, the VM is in suspended state and - for whatever reason - wants to access the configured .iso in order to resume. Since the VM errors out when you try to resume it, the only option is to delete the VM's .vmss and .vmem file, which is like pulling the power plug for a physical system, i.e. any unsaved data will be lost, and there might be a need to check the guest file system once the VM is powered on again.

If you are unsure and/or the VM contains important data, I'd suggest you backup all the VM's files to have a way back if something doesn't work as expected.

Once the two files are deleted you should be able to edit the VM's settings. This might be a good time set the VM's CD-ROM drive to "Use physical drive", and disable connect at power on (if enabled). Note that you may need to close VMware Workstation or at least the the VM's tab.

André

[alaiya]

Okay. I now saved the files elsewhere and had the machine in proper power down, so I was able to change the CD-ROM.

Yet, the VM still won't power up normally. As before it will load CentOS (the blue bar filling up white) but after that the VM will go to black and won't load the user login screen. I just waited for twenty minutes and the entire thing still stayed black.

Mind you, this is only the case for the machine, on which my progress is saved. The other one now boots up normally.

It there anything I can do?

I once again attach those two files (the log and the other one). Maybe it tells you more then it tells me.

[a_p_]

I don't run CentOS myself. Anyway, please check whether the VM is alive, i.e. pingable. Also hit CTRL-ALT-F1/F2/F3/F4 while the VM has the focus to see whether it responds to any of these combinations.

André

[Ahmed_Selim]

Can you load the machine in single user mode so you can make file system check ?

[wila]

Hi,

In addition to what has been said.

When CentOS is booting with the white bar filling up on the blue screen, if you press Escape you normally get a screen with text updates on what it is doing at that moment.

There might be a hint on when it locks up or what it is trying to do.

--

Wil