Re: NOVA, NUL, snapshotting
"Sartakov A. Vasily" <[email protected]>
| Newsgroups | gmane.comp.micro-kernel.l4.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello. > On Thu, 18 Jul 2013 18:30:46 +0400 Sartakov A. Vasily (SAV) wrote: > > SAV> I have a question about VMCS. How to obtain VMCS data for migration? > SAV> After creation of new VM, migration process should somehow give a > SAV> context of transferring machine to NOVA, am I right? > > User code does not have to care about the details of VMCS/VMCB layout. > Transfer of guest state to/from the microhypervisor happens by means of > the UTCB data area as described in Sections 7.3 and 8.3 of the NOVA > specification. In fact, user code is never given direct access to the > VMCS/VMCB in order to prevent modification of host state. Could you please describe how to get access to a context of virtual machine? How can I modify context of virtual machine from Vancouver? When system switches into Vancouver, for example by pressing a special keyboard key, where is stored context of VM? in allocated VMCB? Can I read and modify its from Vancouver? Thank you. -- Sartakov A. Vasily [email protected] _______________________________________________ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
signature.asc
(application/pgp-signature, 842 B)
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSF0PgAAoJEJl93FGKuRBUQMUQAKSyC1C6OzC24tRa7esyign3 8TOmmtMP3c7alU15FEJK3c+PpiCbLFQxJnZbULm2B8hJKA0K5ldxIah6r/zXCewA 4qoTxt+2KiI7C+0TQSaVid0Cz8J+Ryyc9+msE6sO3qlhQ637zA5uFKD4KAPLs2j8 3AkOYhxOorQ47V5WubtZJ0921XwBG4/OdO+FCrBzY5byL33YeiltOTjJAbe7vgnN kCCM5OAl2j7raArvXKphk5VP2304/owzVotV1c1QEY5VUAsNp8efGT4dDrkKmZt+ AF6qTuxeAasqyeKuJNL85MOtByRxMsuJmAPKX2PVu7qSLo91t29TqVlAepu7FSxh s3hFuDNF4NdNdW14Q2kw3mntKeHU56lcrFHrP9LMh4IN+eHZ2iMNoUs+8bEhF1ib rFD6wkwb3rIOgW3bklglWK4db048AXy+z8pl2PbfklTqoIReTwrnPzd51PO/C2mL +sQjCrqulAAMWEIxcis6MS/TeBDiDf84z5Z+hLg64QuHD4v/8iAb4Y7SGunC0+bF qtr5gTfOKwwZnPpa7wOgcCfb8/VP4AowarD+Wf6+Qyyg9hKUB8Xia508dom+G/11 5CSjDuvDBNjNUHG0cJppw1YP1zYjWKqiM9iDSyyqWEEnXoYSPSRZCMYdcUCnjMVD nL79EoQ9aJfWMSr++Dvv =9NWL -----END PGP SIGNATURE-----