| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
| |
Open all fds first before sending messages to the vmm process.
This prevents some intermediate state from being generated that
will confuse vmm if it gets further messages.
Also make sure that vmctl gets the right error reason later by saving
errno upon a failure.
ok reyk@ mlarkin@
|
|
|
|
|
|
|
|
|
|
|
| |
If a VM exits, terminate it and remove it from the list of
available VMs. That allows a VM with name `foo' to be restarted
after it has exited.
This changes structures shared between vmd and vmctl. You need to
rebuild vmctl also.
ok mlarkin@
|
|
|
|
|
| |
counter has to be in sync in the parent and vmm processes. This fixes
reload after a previous load error.
|
|
|
|
|
| |
while others return (errno) on error. We probably have to agree on
something.
|
|
|
|
|
|
|
|
| |
instances of the same configuration will be handled in a different way
later. It is also not a good idea to use the same writeable disk
with multiple VMs at the same time.
As discussed with mlarkin@
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
the configuration in vmctl directly, it now sends a (re)load request
to vmd. The reload also resets the existing configuration status -
this doesn't do much difference yet but a future change will compare
if a specified VM is already running. "load" will allow to add
configuration, while "reload" resets the state before loading.
|
|
|
|
|
|
|
| |
vmm.conf(5) in vmmctl. For a short time, both vmd and vmmctl will
support a configuration file, but vmmctl will be changed to send
"load" requests to vmd instead of loading and parsing the file
directly.
|
| |
|
|
"vmm" with reduced privileges:
- the "parent" opens fds (disks, ifs, etc.) but runs as root but pledged as
"stdio rpath wpath proc tty sendfd".
- the "vmm" process handles the creation and supervision of vm processes,
and the primary communication with the vmm(4) subsystem. It runs as _vmd
in the chroot but does not use pledge, as the vmm ioctls are not allowed
by any pledge model yet.
With this change, vmd starts to track the configuration state of VMs
in vmd and will allow other things later (like terminating a vm by
name, moving the configuration parser to vmd, ...). More incremental
changes will follow.
|