On Mon, Oct 24, 2016 at 07:36:48PM -0500, Ax0n wrote:
> I suppose I'll ask here since it seems on-topic for this thread. Let me
> know if I shouldn't do this in the future. I've been testing vmm for
> exactly a week on two different snapshots. I have two VMs: One running the
> same snapshot (amd64, Oct 22) I'm running on the host vm, the other running
> amd64 6.0-RELEASE with no patches of any kind.
>
> For some reason, the vm running a recent snapshot locks up occasionally
> while I'm interacting with it via cu or occasionally ssh. Should I expect a
> ddb prompt and/or kernel panic messages via the virtualized serial console?
> Is there some kind of "break" command on the console to get into ddb when
> it appears to hang? A "No" or "Not yet" on those two questions would
> suffice if not possible. I know this isn't supported, and appreciate the
> hard work.
>
> Host dmesg:
> http://stuff.h-i-r.net/2016-10-22.Aspire5733Z.dmesg.txt
>
> VM (Oct 22 Snapshot) dmesg:
> http://stuff.h-i-r.net/2016-10-22.vmm.dmesg.txt
>
These look fine. Not sure why it would have locked up. Is the associated vmd
process idle, or spinning like mad?
-ml
> Second:
> I'm using vm.conf (contents below) to start the aforementioned snapshot vm
> at boot.
> There's a "disable" line inside vm.conf to keep one VM from spinning up
> with vmd. Is there a way to start this one with vmctl aside from passing
> all the options to vmctl as below?
>
> doas vmctl start -c -d OBSD-RELa -i 1 -k /home/axon/obsd/amd64/bsd -m 512M
>
> I've tried stuff along the lines of:
> doas vmctl start OBSD-RELa.vm
>
> vm "obsdvmm.vm" {
> memory 512M
> kernel "bsd"
> disk "/home/axon/vmm/OBSD6"
> interface tap
> }
> vm "OBSD-RELa.vm" {
> memory 512M
> kernel "/home/axon/obsd/amd64/bsd"
> disk "/home/axon/vmm/OBSD-RELa"
> interface tap
> disable
> }
>
I think this is being worked on, but not done yet.
-ml
