virtualbox.org

OraOra, could you please check if VBoxTray.exe process is running in the old VM where seamless is not working? You should see the process in the guest's Task Manager.

sunlover wrote:OraOra, could you please check if VBoxTray.exe process is running in the old VM where seamless is not working? You should see the process in the guest's Task Manager.

Too late, sorry. I got rid of the entire folder with the old VDI in it, created a new one with a new Guest and then also did a host OS restore to the latest image where everything works perfect with the version of VB I am using, see signature.

Is there anything I can check now for you to get necessary info perhaps?

I am still trying out one last thing to see if that messes up the VDI and will report back once I have finished that test.

Basically I did try out a rouge OSX iso in a VM and think that that might have influenced the graphics settings of the entire VDI, meaning it messed up all VMs in that VDI. Though as previously mentioned I do not understand how this would be possible and pray that in fact it is not because that would mean that VMs can be tampered with from outside. This is pure speculation at this point, I am reporting back once finished with the test.

Just so we are all on the same page, a VDI is the virtual hard drive of a VM. VM means virtual machine or guest, It's highly unlikely you have multiple VMs on one VDI.

Yes, thank you for your clarification!

The VMs I had all had their ownVDI, yes, it is just that the main VM I was using had the VDI file in the folder right in it, while that others did not (or had them somewhere else, perhaps a subfolder?) what lead to me thinking the VDI is shared among VMs, though this is not logical of course, I guess I was too fast to assume this and hence it is incorrect.

I think I even cloned the first Windows Guest, so perhaps that is why I thought the VMs only had one VDI. I assume when a clone of a Guest is made it also gets a new VDI?

So yeah, basically I had to delete all VDIs and VMs. Now running a Windows Guest with Seamless Mode working fine on a spanking new VDI.

Will report about that rogue OSX iso and if that causes Seamless Mode to break with the current VM and respective VDI.

OraOra, no, nothing you can check now. But if seamless will stop working again, please check VBoxTray.exe. I can't tell from the log if it was running or not, but the log content suggests that most likely VBoxTray.exe did not start for some reason.

All guests should have a .vdi file in their respective folders.

As far as the OSX issue, it had nothing to do with your problem but, running OSX on non-Apple hardware violates Apple's SLA.
Important notice regarding Mac OS X as Guest

sunlover wrote:OraOra, no, nothing you can check now. But if seamless will stop working again, please check VBoxTray.exe. I can't tell from the log if it was running or not, but the log content suggests that most likely VBoxTray.exe did not start for some reason.

Will do.

loukingjr wrote:All guests should have a .vdi file in their respective folders.

Got that, meaning regardless of a VM being cloned or not, each VM has their own VDI, makes sense, thank you!

loukingjr wrote:As far as the OSX issue, it had nothing to do with your problem..

Are you 100% sure?

I am going to give this another shot since this is really the ONLY thing that changed regarding VB, VMs and VDIs, absolutely nothing else was changed on the host besides that.

FYI, once I found my ideal host configuration after lots of restores and more creation of clean working host OS images I leave it untouched, do my work and am happy with that.

Not the kind that just tries out some MP3 downloader that then pollutes the registry and shoots the OS, no thanks, quite careful and aware of all the bad stuff one can get to the host in no time. This is also why I am giving this whole OSX stuff another shot since really nothing else has been done with the host OS and VB. Posting results soon..

OraOra wrote: This is also why I am giving this whole OSX stuff another shot since really nothing else has been done with the host OS and VB. Posting results soon..

Did you not read the link I posted? If you try and install OSX on non-Apple hardware and ask questions about it here, you could get yourself banned from this forum.

Try this one
OSX on Windows hosts

No further mention of OS X please.

Well in that case I am glad I could solve the issue by deleting all my VMs and VDIs and starting from scratch with those.
Edit: Is there a way to backup the state and files of the VM folder alongside VB settings and registry entries alone, so that loosing the VMs and VDIs can be circumvented in the future?

At least the host OS image, including the VB installation, were not affected.

Will not go through with that other routine any more to check if that caused the error. Thought it might be of interest to devs of VB but don't want to get into trouble for providing info, also not a single question about that asked on my part, case closed.

Really super glad the hardware is not affected and that things run smooth again.
Thank you all tremendously for your help here. Much appreciated.