-
Notifications
You must be signed in to change notification settings - Fork 566
Closed
Description
Describe the bug
Cannot snapshot for vmm when enabling amx.
To Reproduce
Steps to reproduce the behaviour:
Launch the vmm:
./cloud-hypervisor -vvv --log-file 1.log \
--vsock cid=3,id=_vsock0,socket=v1.sock \
--api-socket api1.sock \
--cpus boot=2,features=amx \
--memory size=8G \
--kernel vmlinux \
--serial tty,file=s.log \
--console off \
--cmdline "root=/dev/vda console=ttyS0 rw highres=off clocksource=kvm-clock quiet earlyprintk=ttyS0" \
--disk path=rootfs.raw
Snapshot:
./ch-remote --api-socket api1.sock snapshot file:///xxx/snapshot
Logs
ch-remote output:
[2025-12-03T09:19:41Z ERROR cloud_hypervisor] Fatal error: HttpApiClient(ServerResponse(InternalServerError, Some("[\"Error from API\",\"The VM could not be snapshotted\",\"Cannot snapshot VM\",\"Failed to snapshot migratable component\",\"Could not get vCPU state GetXsaveState(Invalid argument (os error 22))\"]")))
Error: ch-remote exited with the following chain of errors:
0: http client error
1: Server responded with InternalServerError
2: Error from API
3: The VM could not be snapshotted
4: Cannot snapshot VM
5: Failed to snapshot migratable component
6: Could not get vCPU state GetXsaveState(Invalid argument (os error 22))
Metadata
Metadata
Assignees
Labels
No labels