You can dump whole struct just a binary array(don't look into it in your
program), and get sizeof(vmxctx) via ioctl return. It should enough to
suspend/resume.
Then if AMD SVM mode will have different values on the structure, your
implementation won't break.
Does it make sense? Peter, Neel
Hi all,
I couldn't spare much time to consider about this topic because I have
to move to new house, but now I'm OK.
I'm implementing registers-save feature including:
1. libvmmapi with get_vmxctx
2. kernel supports of 1.
3. user-land hack using 1, that saves registers and some
You can dump whole struct just a binary array(don't look into it in your
program), and get sizeof(vmxctx) via ioctl return. It should enough to
suspend/resume.
Then if AMD SVM mode will have different values on the structure, your
implementation won't break.
Does it make sense? Peter, Neel
And,
Hi,
I had some discussion with Iori about the project since last year, and now I'm
suggesting him to apply Google Summer of Code'13 with the project.
(GSoC'13 will start next month)
For this, I think those below must be implemented.
- virtual machine state command interface
- saving
Hi,
A brute force way of figuring out all the state must be saved is to
look at all the initialization functions that are called when a vm and
a vcpu are created. So, this would be vm_create() and vcpu_init() in
the kernel module.
I think these things are need to dump by resume action:
-
Hello.
I'm thinking of adding suspend/resume features on BHyVe.
For this, I think those below must be implemented.
- virtual machine state command interface
- saving registers per CPU
- dumping physical memory
- saving virt-io and other device emulation state
To save registers
Hi Lori,
On Mon, Mar 25, 2013 at 11:53 AM, Iori YONEJI fivo.11235...@gmail.com wrote:
Hello.
I'm thinking of adding suspend/resume features on BHyVe.
Fantastic!
For this, I think those below must be implemented.
- virtual machine state command interface
- saving registers per CPU
