Mention psp(4) in vm.conf(5) man page.

from hshoexer@; OK mlarkin@

Implement AMD SEV support in vmd(8).

To launch a guest with AMD SEV enabled, vmd needs to do a few things:
- retrieve ASID used by guest on VM creation
- provide ASID to psp(4)
- let psp(4) encrypt

Implement AMD SEV support in vmd(8).

To launch a guest with AMD SEV enabled, vmd needs to do a few things:
- retrieve ASID used by guest on VM creation
- provide ASID to psp(4)
- let psp(4) encrypt memory used intially by guest
- run guest
- release resources held by psp(4) on guest shutdown
To enable SEV for a guest use the parameter "sev" in the guest's vm
section in vm.conf.

from hshoexer@; OK mlarkin@

show more ...

staggered deployment parallelism defaults to number of *online* CPUs

vmd looks at hw.ncpuonline not hw.ncpu[found], which can differ w/o SMT.

describe what qcow2 is, in sufficient simple terms

some macro fixes, mostly Cm -> Ic;
from josiah frentsos

macro tweaks; from josiah frentsos
ok deraadt

Add (partial) support for agentx in vmd.

Metrics can be found under mib-2.236 and VM-MIB (RFC7666).

Stress tested by and happy noises from Mischa Peters
OK dv@

SWITCH section in ifconfig(8) no longer exists; point people at VEB instead

switch(4) is being retired, sthen@ already removed the bits in the code
adjust the man page as well.
OK sthen@ kn@ patrick@

Document veb(4) support

Feedback jmc
OK dlg

Revert agentx support for now, we're too close to release.

requested by deraadt@

Add support for agentx to vmd.

This is based around VM-MIB from RFC7666,but does not export the full
spec. People more knowledgeable of vmd are encouraged to expand on this.

Backout "DHCP is configured on the first interface only"

I completely missed that part from vmctl.5's "LOCAL INTERFACES" section.
Reading `-L's description itself and the fact that it functions as a

Backout "DHCP is configured on the first interface only"

I completely missed that part from vmctl.5's "LOCAL INTERFACES" section.
Reading `-L's description itself and the fact that it functions as a
boolean switch contrary to how `-i' expects a number, I made the wrong
assumption that it can only work for the first interface.

"vmctl -Li2" configures two interfaces, one witch DHCP and one without.
"vmctl -L -L" however configures two interfaces with DHCP IPs each.

My second mistake was to imply analogue behaviour for the configuration.
Now that you stated the obvious about `local' being per `interface' line,
it makes absoloutely no sense to above mentioned behaviour for static VM
definitions.

Pointed out by tb

show more ...

DHCP is configured on the first interface only

A VM can have multiple interfaces, but only the first one gets DHCP
if "-L" (vmctl) or "local" (vm.conf) is specified.

Positive feedback Mike Larkin

briefly mention /etc/examples/ in the FILES section of all the
manual pages that document the corresponding configuration files;
OK jmc@, and general direction discussed with many

Guest VMs require some resources that are managed outside of vmm(4), so
try to document and enumerate them.

This is most helpful when you try to assign the 5th interface to a guest,
and are confused

Guest VMs require some resources that are managed outside of vmm(4), so
try to document and enumerate them.

This is most helpful when you try to assign the 5th interface to a guest,
and are confused why vmd(8) won't start the guest when only 4 tap devices
exist.

OK jmc@, kn@, pamela@

show more ...

"allow instance {...}" requires options

The parameter block must not be omitted, so remove the Op markup.

kn pointed out that the changes i made to "socket owner" can be
applied to "owner" too;

combine "socket owner user[:group]" and "socket owner :group"
into one logical item;

ok pd

tweak previous; ok pd

vmd: start vms defined in vm.conf in a staggered fashion

This addresses 'thundering herd' problem when a lot of
vms are configured in vm.conf. A lot of vms booting in parallel can
overload the host

vmd: start vms defined in vm.conf in a staggered fashion

This addresses 'thundering herd' problem when a lot of
vms are configured in vm.conf. A lot of vms booting in parallel can
overload the host and also mess up tsc calibration in openbsd guests as
it uses PIT which doesn't fire reliably if the host is overloaded.

We default to starting vms with parallelism of ncpuonline and a delay 30 seconds
between batches. This is configurable in vm.conf.

ok mlarkin@ (also addressed comments from cheloha@)

show more ...

Delete some .Sx macros that were used in a wrong way.
Part of a patch from Stephen Gregoratto <dev at sgregoratto dot me>.

Add support for `boot device' to vm.conf grammar which is the `-B device'
counterpart from vmctl.

ok mlarkin@

Clarify that VM names must start with a letter

`start' requires an alphanumeric VM name, must not be a number and in fact
must not start with a digit. Improve and simplify the current requirements

Clarify that VM names must start with a letter

`start' requires an alphanumeric VM name, must not be a number and in fact
must not start with a digit. Improve and simplify the current requirements
as starting with a letter directly implies all of the above.

OK mlarkin, feedback jmc

show more ...

avoid unwanted double space;