VMware Communities
mermade
Contributor
Contributor

Vmware player 3.0 XP Mode compatibility

Can't get vmware player 3.0 (build 203739) to play / import / convert the Microsoft Virtual PC virtual machine containing the XP Mode installation.

I just get an error "Failed to open virtual machine: Failed to query source for information".

Vmware player isn't installed in a directory containing non-ASCII characters (as per the known issue in the release notes) it's in the default install location C:\Program Files\VMware\VMware Player

Doesn't seem to be much in the UI log file, just:

Oct 30 12:07:44.235: player| PlayerFrame::UpdateActiveFullScreen: action=0

Oct 30 12:07:44.235: player| PlayerFrame::UpdateActiveFullScreen: Ungrab MKS

Oct 30 12:07:54.531: player| PlayerFrame::UpdateActiveFullScreen: action=0

Oct 30 12:07:54.531: player| PlayerFrame::UpdateActiveFullScreen: Ungrab MKS

Oct 30 12:07:54.531: player| PlayerFrame::UpdateActivePlayer: m_bActive=1

Oct 30 12:08:01.170: player| VMDlg::ShowDialog: Failed to open virtual machine: Failed to query source for information.

Oct 30 12:08:01.170: player| PlayerFrame::UpdateActiveFullScreen: action=0

Oct 30 12:08:01.170: player| PlayerFrame::UpdateActiveFullScreen: Ungrab MKS

Oct 30 12:08:03.733: player| PlayerFrame::UpdateActiveFullScreen: action=0

Oct 30 12:08:03.733: player| PlayerFrame::UpdateActiveFullScreen: Ungrab MKS

Oct 30 12:08:03.733: player| PlayerFrame::UpdateActivePlayer: m_bActive=1

Oct 30 12:08:05.498: player| PlayerFrame::UpdateActiveFullScreen: action=0

Oct 30 12:08:05.498: player| PlayerFrame::UpdateActiveFullScreen: Ungrab MKS

Oct 30 12:08:10.638: player| PlayerFrame::UpdateActivePlayer: m_bActive=0

Should the XP mode virtual machine be completely untouched, i.e. not started by Windows 7, or should it be configured / activated etc before being imported into vmware?

Reply
0 Kudos
4 Replies
luby
Enthusiast
Enthusiast

Could you please upload the VMware Converter logs for further investigation?

Typical location of the logs: c:\Windows\Temp\vmware-temp\vmware-converter-*.log

Please reproduct the failure and retrieve the logs at time of failure. Thanks!

mermade
Contributor
Contributor

My bad! The converter log pointed me to the cause of the problem. I'd made a copy of the .vhd file so I could restore back to the original state / compare the vmware and virtual PC implementations but made a typo when updating the copied .vmc file. Player does open the virtual machine now that's corrected. Sorry for the noise.

Reply
0 Kudos
luby
Enthusiast
Enthusiast

Good to know. Thanks for getting back to us.

Reply
0 Kudos
admin
Immortal
Immortal

Good to know.

mermade: I am sure you found this out already, but just for everyone else following this thread: Player and Workstation do not modify the original XP mode VHD. The VHD is read-only and we do not modify its contents or protection level. We create a linked clone of the VHD where we write all the changes.

Reply
0 Kudos