> Date: Thu, 28 Nov 2019 03:48:04 +0100
> From: Klemens Nanni
>
> On Thu, Nov 28, 2019 at 01:05:43AM +0100, Klemens Nanni wrote:
> > With that, the next step is to implement `ldomctl console guest01' in
> > analogy to vmctl(8).
> Here's a complete diff for updating the status output and implement
On Thu, Nov 28, 2019 at 03:48:04AM +0100, Klemens Nanni wrote:
> I've tested this diff on a T4-2 machine with all possible invocations
> of `ldomctl status [domain]' and `ldomctl console [domain]': it always
> prints and attaches to the correct serial console respectively, whether
> I pass an expl
On Thu, Nov 28, 2019 at 01:05:43AM +0100, Klemens Nanni wrote:
> With that, the next step is to implement `ldomctl console guest01' in
> analogy to vmctl(8).
Here's a complete diff for updating the status output and implementing
the console command, mainly to ease testing and review. I do want to
On Thu, Nov 28, 2019 at 01:05:43AM +0100, Klemens Nanni wrote:
> t4-2# ./obj/ldomctl status
> primary -running OpenBSD running
> 0%
> guest01 ttyV0running OpenBoot Primary Boot Loader
> 50%
> guest02
Each logical domain has a serial port that is always present no matter
the domain's state.
Currently, one has to infer the minor number from the domain's position
in the running configuration, e.g. with ldom.conf(5)
domain "primary" {
vcpu 64
memory 64G
