From: Tamas K Lengyel <tamas.lengyel@intel.com>
To: xen-devel@lists.xenproject.org
Cc: "Kevin Tian" <kevin.tian@intel.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Tamas K Lengyel" <tamas.lengyel@intel.com>,
"Jun Nakajima" <jun.nakajima@intel.com>, "Wei Liu" <wl@xen.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Tamas K Lengyel" <tamas@tklengyel.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Anthony PERARD" <anthony.perard@citrix.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH v19 for-4.14 00/13] VM forking
Date: Mon, 1 Jun 2020 06:21:34 -0700 [thread overview]
Message-ID: <cover.1591017086.git.tamas.lengyel@intel.com> (raw)
The following patches are part of the series that implement VM forking for
Intel HVM guests to allow for the fast creation of identical VMs without the
assosciated high startup costs of booting or restoring the VM from a savefile.
JIRA issue: https://xenproject.atlassian.net/browse/XEN-89
The fork operation is implemented as part of the "xl fork-vm" command:
xl fork-vm -C <config> -Q <qemu-save-file> <parent_domid>
By default a fully functional fork is created. The user is in charge however to
create the appropriate config file for the fork and to generate the QEMU save
file before the fork-vm call is made. The config file needs to give the
fork a new name at minimum but other settings may also require changes. Certain
settings in the config file of both the parent and the fork have to be set to
default. Details are documented.
The interface also allows to split the forking into two steps:
xl fork-vm --launch-dm no \
-m <max-vcpus> \
-p <parent_domid>
xl fork-vm --launch-dm late \
-C <config_file_for_fork> \
-Q <qemu_save_file> \
<fork_domid>
The split creation model is useful when the VM needs to be created as fast as
possible. The forked VM can be unpaused without the device model being launched
to be monitored and accessed via VMI. Note however that without its device
model running (depending on what is executing in the VM) it is bound to
misbehave or even crash when its trying to access devices that would be
emulated by QEMU. We anticipate that for certain use-cases this would be an
acceptable situation, in case for example when fuzzing is performed of code
segments that don't access such devices.
Launching the device model requires the QEMU Xen savefile to be generated
manually from the parent VM. This can be accomplished simply by connecting to
its QMP socket and issuing the "xen-save-devices-state" command. For example
using the standard tool socat these commands can be used to generate the file:
socat - UNIX-CONNECT:/var/run/xen/qmp-libxl-<parent_domid>
{ "execute": "qmp_capabilities" }
{ "execute": "xen-save-devices-state", \
"arguments": { "filename": "/path/to/save/qemu_state", \
"live": false} }
The series has been tested with Windows VMs and functions as expected. Linux
VMs when forked from a running VM will have a frozen VNC screen. Linux VMs at
this time can only be forked with a working device model when the parent VM was
restored from a snapshot using "xl restore -p". This is a known limitation due
to Linux VMs having to be made aware of being saved/migrated.
New in v19:
Including all the patches currently outstanding into the series
Breaking up libxl/xl patch to many sub-patches to make it easier to review
libxl/xl is now reduced to the bare essential to launch QEMU for a VM fork
Tamas K Lengyel (13):
x86/mem_sharing: block interrupt injection for forks
tools/libxc: xc_memshr_fork with interrupts blocked
tools/libxl: Split libxl__domain_make
tools/libxl: populate xenstore entries when launching dm for VM fork
tools/libxl: Add checks for dm_restore_file
tools/libxl: adjust domcreate_bootloader_done
tools/libxl: Adjust libxl__build_pre
tools/libxl: Adjust libxl__build_post
tools/libxl: libxl__build_hvm_fork
tools/libxl: set QEMU saved_state from dm_restore_file
tools/libxl: Add VM forking public functions
tools/xl: Add xl fork-vm command
tools/xl: document fork-vm command
docs/man/xl.1.pod.in | 39 +++++++++
tools/libxc/include/xenctrl.h | 3 +-
tools/libxc/xc_memshr.c | 4 +-
tools/libxl/libxl.h | 10 +++
tools/libxl/libxl_create.c | 134 +++++++++++++++++++++++++------
tools/libxl/libxl_dm.c | 2 +-
tools/libxl/libxl_dom.c | 59 +++++++++++---
tools/libxl/libxl_internal.h | 5 +-
tools/libxl/libxl_types.idl | 1 +
tools/xl/Makefile | 2 +-
tools/xl/xl.h | 4 +
tools/xl/xl_cmdtable.c | 13 +++
tools/xl/xl_forkvm.c | 122 ++++++++++++++++++++++++++++
tools/xl/xl_vmcontrol.c | 13 +++
xen/arch/x86/hvm/vmx/intr.c | 6 ++
xen/arch/x86/mm/mem_sharing.c | 6 +-
xen/include/asm-x86/hvm/domain.h | 2 +-
xen/include/public/memory.h | 3 +
18 files changed, 383 insertions(+), 45 deletions(-)
create mode 100644 tools/xl/xl_forkvm.c
--
2.25.1
next reply other threads:[~2020-06-01 13:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 13:21 Tamas K Lengyel [this message]
2020-06-01 13:21 ` [PATCH v19 for-4.14 01/13] x86/mem_sharing: block interrupt injection for forks Tamas K Lengyel
2020-06-02 7:43 ` Paul Durrant
2020-06-02 10:26 ` Wei Liu
2020-06-09 23:44 ` Tian, Kevin
[not found] ` <MWHPR11MB16457D9235F56F9F10BDFE358C820@MWHPR11MB1645.namprd11.prod.outlook.com>
2020-06-09 23:53 ` Tian, Kevin
2020-06-09 23:54 ` Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 02/13] tools/libxc: xc_memshr_fork with interrupts blocked Tamas K Lengyel
2020-06-02 7:44 ` Paul Durrant
2020-06-02 10:26 ` Wei Liu
2020-06-01 13:21 ` [PATCH v19 for-4.14 03/13] tools/libxl: Split libxl__domain_make Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 04/13] tools/libxl: populate xenstore entries when launching dm for VM fork Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 05/13] tools/libxl: Add checks for dm_restore_file Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 06/13] tools/libxl: adjust domcreate_bootloader_done Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 07/13] tools/libxl: Adjust libxl__build_pre Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 08/13] tools/libxl: Adjust libxl__build_post Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 09/13] tools/libxl: libxl__build_hvm_fork Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 10/13] tools/libxl: set QEMU saved_state from dm_restore_file Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 11/13] tools/libxl: Add VM forking public functions Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 12/13] tools/xl: Add xl fork-vm command Tamas K Lengyel
2020-06-01 13:21 ` [PATCH v19 for-4.14 13/13] tools/xl: document " Tamas K Lengyel
2020-06-01 15:07 ` [PATCH v19 for-4.14 00/13] VM forking Paul Durrant
2020-06-01 17:11 ` George Dunlap
2020-06-01 18:37 ` Tamas K Lengyel
2020-06-02 7:37 ` Paul Durrant
2020-06-02 9:38 ` Jan Beulich
2020-06-15 19:27 ` Tamas K Lengyel
2020-06-16 7:07 ` Jan Beulich
2020-06-16 8:32 ` Jan Beulich
2020-06-16 13:05 ` Tamas K Lengyel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1591017086.git.tamas.lengyel@intel.com \
--to=tamas.lengyel@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tamas@tklengyel.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).