This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/467
** Changed in: qemu
Status: New => Expired
** Bug
Save/restore with TrustZone enabled is stil broken.
** Changed in: qemu
Status: Expired => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1839807
Title:
Snapshots freeze guest
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1839807
Title:
Snapshots
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then
That property doesn't exist for the sabrelite board, it's only on some
of the others like vexpress or virt.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1839807
Title:
Snapshots freeze guest
Hello again,
I have tried to disable TrustZone using argument mentioned in comment #5
by changing -M sabrelite to -M sabrelite,secure=off, but I get error
"qemu-system-arm: Property '.secure' not found". It works with virt
though. Is there any other way to disable it?
Thank you,
...
--
You
The underlying cause of this is that we're not migrating the Secure
banked cp15 register contents. So boards which don't enable TrustZone or
where the guest runs in the NonSecure state (like the virt board, etc)
can save/restore fine, but since the imx6 happens to run the guest in
the Secure state
