move some argument checking from vmmaction() to start_vm()

from a diff posted to tech@ by Fabien Siron, thanks.

typo in comment

Introduce memory ranges to support VMs with >= 4G RAM

Kernel bits:
- When creating a VM, a list of memory ranges has to be specified,
similar to the BIOS memory map. This is necessary for VMs with

Introduce memory ranges to support VMs with >= 4G RAM

Kernel bits:
- When creating a VM, a list of memory ranges has to be specified,
similar to the BIOS memory map. This is necessary for VMs with
RAM sizes approaching 4G because we'll need PCI MMIO space in
the higher parts of the 32 bit address space.

vmctl and vmd bits:
- Construct appropriate memory ranges to create a VM with a given
RAM size
- Construct a corresponding BIOS memory map from the memory ranges
and update the boot params page accordingly.
- Make sure that all variables that represent guest physical addresses
match the address width of the target CPU instead of using uint32_t.
- Fix some integer promotion glitches that actually restricted VM
RAM size to 2G.

This changes the VM create ioctl interface, so update your kernel,
vmd, and vmctl.

ok mlarkin@

show more ...

lseek() + write() can be replaced by a slightly shorter ftruncate()
call. Note that using ftruncate() to extend a file is not portable
(POSIX allows either zero-filling until the given size is reache

lseek() + write() can be replaced by a slightly shorter ftruncate()
call. Note that using ftruncate() to extend a file is not portable
(POSIX allows either zero-filling until the given size is reached, or
alternatively erroring out), but that shouldn't be a proble as vmm(4)
isn't cross-platform either. unlink() the image file when extending
it fails for consistency with the other error case (the file can't be
created).

From Martin Natano
OK mlarkin@

show more ...

Update the comments in vmctl.c that are describing function arguments.

track used memory in each VM. This is passed back to vmctl status.

ok reyk@, beck@, mpi@

The vmctl "id" argument can now be a number of or a vm name, eg.
vmctl stop 3
vmctl stop "openbsd.vm"

Add "vmctl console" to connect to a specified VM console by id.

Requested by mlarkin@

use O_EXCL rather than a race

Print the TTY in the vmctl status output.

When a new vm is created with VMM_IOC_CREATE, the kernel assigns a
unique id to it. This happens in the vm child process and has to be
communicated to the parent processes to track the vm. Knowing

When a new vm is created with VMM_IOC_CREATE, the kernel assigns a
unique id to it. This happens in the vm child process and has to be
communicated to the parent processes to track the vm. Knowing the vm
id in the parent and vmm processes also allows to remove vm from the
daemons list on terminate requests later.

show more ...

Add OpenBSD Id

Align columns to printed output in "vmctl status"

Add -c option to "vmctl start" to automatically connect to the VM
console after startup. This calls 'cu -l $TTY -s 9600' internally -
a "safe mode" for cu is proposed by tedu@.

Requested by mlarkin

Add -c option to "vmctl start" to automatically connect to the VM
console after startup. This calls 'cu -l $TTY -s 9600' internally -
a "safe mode" for cu is proposed by tedu@.

Requested by mlarkin@
OK tedu@ on the execl/cu chunk

show more ...

Replace vmmctl with vmctl. Also remove parse.y from the "new" vmctl.

As discussed with mlarkin@ and deraadt@