remove unneeded includes

Use shared netlock to protect ifnet data within vmt_tclo_broadcastip().
Execute vmt_tclo_tick() timeout handler in process context to allow
context switch within vmt_tclo_broadcastip().

ok yasuoka

The maximum length of the value is extended to 64k bytes.

ok yasuoka

Change space character to TAB.

ok tb mlarkin giovanni

Add close vmt.

Modify vmt to use the buffer allocated in pvbus directly instead of
the buffer in the vmt softc when doing RPC for PVBUSIOC_KV{READ|WRITE}
ioctl.

ok asou

Rename global ifnet TAILQ

Naming the list like the struct itself makes for awful grepping.
Call the global variable "ifnetlist" from now on.

There used to be kvm(3) consumers in base picking up thi

Rename global ifnet TAILQ

Naming the list like the struct itself makes for awful grepping.
Call the global variable "ifnetlist" from now on.

There used to be kvm(3) consumers in base picking up this symbol, but those
have long been converted to other interfaces.

A few potential ports users remain, same deal as sys/net/if_var.h r1.116
"Remove struct ifnet's unused if_switchport member": they get bumped.

Previous users pointed out by deraadt
OK bluhm

show more ...

spelling
feedback and ok tb@ jmc@ ok ratchov@

Constify struct cfattach.

Initialize var since it's used in a condition a little bit afterwards.

CID 1501713

ok jmatthew@

Report full IP address information to the host. Contrary to what I wrote
here 10 years ago, xdr isn't scary at all.

ok dlg@

Make vm_rpc_send_rpci_tx_buf() use the buffer passed in, not the buffer
allocated as part of the softc, though it's always been the same buffer
so far.

ok dlg@

put M_ZERO in the right place

ok dlg@

kernel: use gettime(9)/getuptime(9) in lieu of time_second(9)/time_uptime(9)

time_second(9) and time_uptime(9) are widely used in the kernel to
quickly get the system UTC or system uptime as a time_

kernel: use gettime(9)/getuptime(9) in lieu of time_second(9)/time_uptime(9)

time_second(9) and time_uptime(9) are widely used in the kernel to
quickly get the system UTC or system uptime as a time_t. However,
time_t is 64-bit everywhere, so it is not generally safe to use them
on 32-bit platforms: you have a split-read problem if your hardware
cannot perform atomic 64-bit reads.

This patch replaces time_second(9) with gettime(9), a safer successor
interface, throughout the kernel. Similarly, time_uptime(9) is replaced
with getuptime(9).

There is a performance cost on 32-bit platforms in exchange for
eliminating the split-read problem: instead of two register reads you
now have a lockless read loop to pull the values from the timehands.
This is really not *too* bad in the grand scheme of things, but
compared to what we were doing before it is several times slower.

There is no performance cost on 64-bit (__LP64__) platforms.

With input from visa@, dlg@, and tedu@.

Several bugs squashed by visa@.

ok kettenis@

show more ...

dev/rndvar.h no longer has statistical interfaces (removed during various
conversion steps). it only contains kernel prototypes for 4 interfaces,
all of which legitimately belong in sys/systm.h, whi

dev/rndvar.h no longer has statistical interfaces (removed during various
conversion steps). it only contains kernel prototypes for 4 interfaces,
all of which legitimately belong in sys/systm.h, which are already included
by all enqueue_randomness() users.

show more ...

Force a guest info update when we get a Capabilities_Register command.
ESXi doesn't carry the guest info over when a guest gets moved to a
different host, and this appears to be the only hint the gue

Force a guest info update when we get a Capabilities_Register command.
ESXi doesn't carry the guest info over when a guest gets moved to a
different host, and this appears to be the only hint the guest gets
that this has happened.

ok dlg@

show more ...

include sys/sensors.h for sensor use

replace add_*_randomness with enqueue_randomness()

this gets rid of the source annotation which doesn't really add
anything other than adding complexitiy. randomess is generally
good enough that the

replace add_*_randomness with enqueue_randomness()

this gets rid of the source annotation which doesn't really add
anything other than adding complexitiy. randomess is generally
good enough that the few extra bits that the source type would
add are not worth it.

ok mikeb@ deraadt@

show more ...

Implement the VMWare vmbackup protocol using vfs_stall(). This lets you
clone running guests and take disk-only snapshots, most of the time ending
up with a clean filesystem.

ok dlg@ deraadt@

update link to Ken Kato's vmware backdoor protocol documentation
from Seth Jackson

yasuoka@ reported that a "guest shutdown" resulted in a reboot instead
of a shutdown. Correct a mistake in rev 1.11 to make this trigger a
shutdown again.

ok reyk@

Introduce pvbus_reboot() and pvbus_shutdown() to move the repeated
tasks from the PV drivers into a central place. While here, we
figured out that it is not needed to check for allowpowerdown on the

Introduce pvbus_reboot() and pvbus_shutdown() to move the repeated
tasks from the PV drivers into a central place. While here, we
figured out that it is not needed to check for allowpowerdown on the
hypervisor-initiated shutdown requests.

OK mikeb@

show more ...

Use "%s" in vm_rpc_send_rpci_tx() call. Avoids a "format string is not a
string literal" warning from clang.

ok jca@

Increase the RPC buffer once more to 4096 bytes. The guestinfo.ovfEnv
mechanism is used to configure VMs in the VMware vSphere world:
instead of using individual key-value guestinfo.* properties, it

Increase the RPC buffer once more to 4096 bytes. The guestinfo.ovfEnv
mechanism is used to configure VMs in the VMware vSphere world:
instead of using individual key-value guestinfo.* properties, it uses
the guestinfo.ovfEnv value to pass an enterprise-compliant XML file
that includes key-value properties. This file can be rather large,
especially with comments, but 4k ought to be enough for anybody.
Also change a stack buffer to malloc'ed memory in the ioctl path.

OK mikeb@

show more ...

Add a key-value interface to pvbus(4) that allows to get or set values
in the underlying information store of the host from the OpenBSD-VM's
userspace. OpenBSD did not provide access to these stores

Add a key-value interface to pvbus(4) that allows to get or set values
in the underlying information store of the host from the OpenBSD-VM's
userspace. OpenBSD did not provide access to these stores before,
mostly because we did not want to add a custom tool and interface for
each hypervisor. The pvbus(4) interface provides backends for
xen(4)'s XenStore and vmt(4)'s VMware Tools "guestinfo". These
information stores are fairly different, XenStore is a "filesystem"
while vmt is a RPC, and the key-value abstraction limits them a bit
but provides the most wanted functionality.

Discussed with many
OK mikeb@

show more ...