virtualbox.org

Hi;
I've recently installed VB on my winXP pro pc (2.4mHz/2G RAM) using a Fedora based appliance (CS50 Appliance 19. I 'saved' a recent session, and closed the VM, but I tried to re-open, and it fails to open, with errmsg:
"Failed to open a session for the virtual machine CS50 Appliance 19_1.

Failed to load unit 'PATM' (VERR_SSM_FIELD_NOT_CONSECUTIVE).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Couple of possibly significant things I find on VB is
1) a flag on the "VB-Settings" window, which states:
Invalid settings detected'
Network: Host-only networks page Host Interface VB Host-only Ethernet adapter #4 does not have a valid IPv4 network mask.
2) After installation, whenever I reboot my pc, I get msg of "found new hardware .NET". I don't know what this means, as I haven't installed anything new except for VB. Does the OS consider a VM "hardware"? Additionally, my pc is unable to "find" any supporting software. Has everything gotten screwed up?

This is not the first time that this has happened, and I don't recall what I had to do to restore the function.(I think that I removed the app and downloaded again).
Can anyone explain what might be wrong, and what might be done to correct this.

Oh! Just realized that it would not start properly because appliance was in "saved" state. After discarding the "saved" state, the app opened up properly.
Perhaps someone can tell me what does "saved" mean, and how should I properly close this app so that I don't have this problem.
Thanks

The reported error is a bug in v4.3.0, it will likely be fixed in the next maintenance release. If you want to avoid this then shut down the guest PC properly, don't suspend it.

mpack wrote:The reported error is a bug in v4.3.0, it will likely be fixed in the next maintenance release. If you want to avoid this then shut down the guest PC properly, don't suspend it.

Well, what is the difference between shutting it down "properly" vs. suspending it? Do I lose anything in the process? But thanks for the simple solution instructions.

Shutting it down properly means shutting it down per the instructions in your guest OS documentation. It is assumed that disk caches will be flushed, ports closed, network connections do a "friendly disconnect", licenses are returned to the lease server etc - delete all that are not applicable. Suspending can be faster, hence less technical users prefer it since they are blissfully unaware of the possible downsides.

where do I fing the "guest OS documentation"?

The same place you found the guest OS.

Please try to restrict your questions to VirtualBox matters, and in this particular forum, only to VBox matters as they pertain to Windows Hosts. On both counts it isn't appropriate to have a discussion here on how to operate a Fedora PC.