drop when creating snapshot (#17550)

[GetA]

---

[ModEdit; related ticket: #17550: drop when creating snapshot]

---

System: ubuntu 16.04 (latest)
Virtualbox: 5.2.6 (off repository)
Guest System: Windows 8.1 latest

Guest Additions: 5.2.6

Kernel info: Linux FirstEmpty 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

At an uptime of more than 40 minutes and the creation of a snapshot (instead of shutting down) - the virtual machine drops!

01:49:28.306340 GIM: HyperV: Resetting MMIO2 regions and MSRs
01:49:28.307849 Changing the VM state from 'DESTROYING' to 'TERMINATED'
01:49:28.310970 Console: Machine state changed to 'Saved'
01:49:59.308109 AssertLogRel /home/vbox/vbox-5.2.6/src/VBox/VMM/VMMR3/VM.cpp(2592) void vmR3DestroyUVM(PUVM, uint32_t): RT_SUCCESS_NP(rc2)
01:50:08.149769 iCpu=0 rc=VERR_TIMEOUT

00:43:37.423573 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:43:37.426432 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:43:37.433702 Console: Machine state changed to 'Saved'
00:44:08.426807 AssertLogRel /home/vbox/vbox-5.2.6/src/VBox/VMM/VMMR3/VM.cpp(2592) void vmR3DestroyUVM(PUVM, uint32_t): RT_SUCCESS_NP(rc2)
00:44:33.446952 iCpu=0 rc=VERR_TIMEOUT
00:44:33.998557 GUI: Passing request to close Runtime UI from machine-logic to UI session.

[socratis]

Partial logs are not that helpful I'm afraid. Please ZIP and attach the full log. See the "Upload attachment" tab below the reply form.

[GetA]

Simply excellent ... A similar problem is on 5.1.32

Full log:

vbox.zip

(23.53 KiB) Downloaded 22 times

[GetA]

Ready to try anything, any experiments. If only it worked - saving the current state (snapshot)


Latest log:

latest_5.1.32_vbox.zip

(25.14 KiB) Downloaded 13 times

[mpack]

One log is sufficient work, thank you. I ignored the second one.

According to the log it seems to me that you are suspending the VM (saving state), not creating a snapshot.

[GetA]

I do nothing more. Sometimes it persists, but in most cases it does not.

1.png (8.62 KiB) Viewed 5374 times

I even see the process of saving the "taskbar", and in the end, at the very end, when there should be a snapshot - I see 'saved' (in front of the virtual machine) - 'dropped' (or something like this).
But sometimes the snapshot persists

[mpack]

As I said, that dialog refers to saving the machine state (and shutting down the VM - notice the big caption on the dialog). That dialog does not refer to creating a snapshot, and never has.

[GetA]

As I said, that dialog refers to saving the machine state (and shutting down the VM - notice the big caption on the dialog). That dialog does not refer to creating a snapshot, and never has.

Well, I understood the essence ... Thank you

[GetA]

Still, I can not agree

I'm doing a snapshot. It's done successfully.
I start the car, I work. After some time, I do a snapshot back. There is a process of creation.
Cry, there is no snapshot.

Why do you need this function?
If it does not snapshot.

Although she has an explicit description of "save the current state", but instead the machine simply turns off.

[erdeslawe]

@GetA,

It seems you have a mind block.

See:

- VirtualBox User Manual Section 1.8.6, which describes what "Save the machine State" is/does. It does NOT produce a Snapshot!
- VirtualBox User Manual Section 1.1.0, which describes what Snapshots are and how you create them. Completely different from SAVED STATE!

[GetA]

Then why this button?

if

1. I click it and get the process of creating a snapshot
2. There is a process of creating a .sav file in the folder snapshots
3. Closes the virtual machine
4. Assigned to "saved" status

This button works!

else

We try again. Run the machine from the saved snapshot and the created .sav file and repeat the action

1. I click it and get the process of creating a snapshot
2. There is a process of creating a .sav file in the folder snapshots
3. Closes the virtual machine
4. Assigned to saved status "Aborted"
5. ls -l blablabla/snapshots
EMPTY, there is no snapshot

And is that normal?

When I'm in the process of saving a snapshot and instead of snapshots I get an empty folder and the status is "aborted", instead of "saved"

[socratis]

@GetA
Please start talking about "saved states" instead of "snapshots" when you use the "Save VM state". If you are doing a "Snapshot", then talk about "Snapshots". You need to be exact and accurate. That dialog saves the VM state. It does NOT create a snapshot.

1. It does NOT create a snapshot. It saves the VM state. Not the same thing.
2. The ".sav" file are the memory contents, the hardware state, etc.
3, 4. Yes.

else

1. You click to "Save the VM state".
2, 3. OK
4. Something went wrong and the save state failed.
5. Empty because the "save" failed. No, it's not "normal". But...

You may run out of space on your host or something similar. Unless we can reproduce it, we can't do anything.

'/media/root/JOB_FLASH!!!/Windows 8.1 for developer/Windows 8.1.vdi' is fuse

That's where you save. That's a USB stick. Not a good idea. And with a FUSE filesystem, what is it? NTFS? exFAT? Try to save to the hard disk and then copy to the stick. And to top it all off, you're running as 'root'. Not a very smart move...

[GetA]

@socratis

NTFS
USB drive on 128Gb, and the machine on 73Gb. For me it is convenient.
Well, I'll try with a disk and without spaces.
root is needed to run some proprietary software

[socratis]

Root is not needed to run VirtualBox. It's a bad idea. And so every software that need to be run as root. In any event...
Is this reproducible?
Does it happen all the time or sometimes?
What does "dmesg" on the host show at the time that you save the VM state?

[GetA]

@socratis

Intel Parallel Studio, or rather some components, work incorrectly under sudo.
I do not have time to deal with this and conduct dialogues with developers, I just need it to work.

1. I assume that yes.
But, I'll try more options:

Run from under Windows.
Running with the kernel 4.4, not 4.13.

2. Sometimes.
3. At the moment I do not have the answer to this question. I'll try to start with point 1.