Closed BasToTheMax closed 1 week ago
Hi @BasToTheMax ! Thanks for reporting the issue.
From our initial analysis, it looks like the block device fails to restore, because the device layout in memory is not correct.
Could you provide a reproducible test that demonstrates the issue including the following if possible:
Alternatively, we have a test that exercises differential snapshots: https://github.com/firecracker-microvm/firecracker/blob/641b37573c66ff524b73997471da3849a630b634/tests/integration_tests/functional/test_snapshot_basic.py#L128 . You could modify it in the way it is closer to your setup and see if it starts failing (testing readme).
Additionally, is running a docker inside the VM a principal part of the reproduction steps? Does the same sequence not fail without a docker inside?
Hi @BasToTheMax were you able to solve your issue? If not can you provide a series of commands as mentioned in @kalyazin's comment?
Closing this for now. @BasToTheMax please feel free to reopen and post your discoveries if you still experience the issue.
Hello.
I am having issues while trying to resume my vm.
What I am doing:
Please note: I am running docker in my vm
Snapshot command:
Firecracker logs:
Host kernel:
Linux bttm 6.2.0-39-generic #40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
(uname -a
) Guest kernel:vmlinux-5.10.bin
Download script used:
To give more context:
If you need more details, feel free to ask :wink:.
I hope someone can help me fix the issue. I will probably also ask in the slack server.
Originally posted by @BasToTheMax in https://github.com/firecracker-microvm/firecracker/issues/2888#issuecomment-1869049388