virtualbox.org

Hi guys,

Wednesday evening I updated from Mavericks to Yosemite. Since then when I try to launch VB (4.3.18) I get an error message about not being able to find an XML file for my Windows guest installation, which was working under Mavericks.

Any quick suggestions as to what may have gone wrong? Could it be a permissions/access control thing.

I did have the virtual disk image in a shared folder so that VB/Windows could be used by different users on my Mac.

I've tried re-connecting to the VD file but it said it was already assigned to a different definition.

I am hoping it's a quick fix, rather than a lengthy investigation or re-installation of VB and my Windows OS.

Thank you in anticipation.

Ted

See this Minimum information needed for assistance

In theory I suppose while installing 10.10 it moved one or more files to the Incompatible Software folder.

There have been many versions of VirtualBox since it's used an .xml file btw.

Thank you for your response.

I acknowledge the reminder for minimum information, but at this stage I just wondered if others had problems with updating to Yosemite.

Given I cannot get the guest to launch, there's not much of a log.

I am away from my Mac so cannot recall the exact file VB claims to be unable to access.

I've been using VB & updating it since v2, I think, so it maybe a legacy thing with the XML file.

I'll return with more details or news that I've solved it.

Thanks again

Ted

welcome. I've been running VirtualBox on Yosemite since the developer previews and I have the release version on three different Macs and I haven't had any issues. That doesn't mean you aren't of course. Looking forward to seeing the log.

Hi,

I reinstalled VB (probably unnecessary), created a new guest instance, connected to original VDI and it worked.

I then removed the inaccessible one.

Thanks for your patience.

Regards

Ted