Hey all, I have a bhyve VM I'm trying to resize the root partition of using a gparted iso. At first I was getting only a black screen from the VNC console, but was able to fix that by switching the bootrom to UEFI. However, after X starts, the mouse is unusable.

natefoo: Yeah, there's a known issue that affects the mouse driver.

d'oh

Any workarounds?

In general the vnc console is only intended for auxiliary access when the instance is inaccessible via the network.

So something like X display forwarding will still work.

I don't think that's an option for the gparted live CD?

Can you use gparted from the command line?

Oh, yeah, well, I can presumably figure out (non-g)parted.

Well, I broke something, possibly trying to start bhyve by hand: vm_open: No such file or directory

prctl: 61a99139-0148-4da0-8d6c-903c1554e7d3: No controllable process found in task, project, or zone.

Yeah, that's not going to work.

bhyve runs with extremely limited permissions. It's part of our "double hulled" virtualization technology.

This is now when trying to start it the normal way from vmadm (after trying to start it by hand)

Unfortunately not knowing exactly what you did to get into this situation, it's difficult to say how to remedy it.

Even if you destroyed the partition table on the zvol you should still be able to get the bhyve process to start and say there's no bootable media.

I hope you had a back up?

So it was booting ok (without the mouse) to the CD image just after updating bootrom and bhyve_extra_args, afaik the only thing I did after that was to attempt to run the bhyve command (grabbed from ps) from the command line

I made a snapshot of disk0 before I started

maybe your extra args are causing the problem?

# ls -l /zones/61a99139-0148-4da0-8d6c-903c1554e7d3/root/usr/

total 0

No idea how I did that...

Well, hooray for snapshots

Oh, I guess that would be mounted by vmadmd at start?

Yeah, it's empty if the zone isn't booted.

Weird, ok. What does the ENOENT up there from vm_open refer to?

i.e. what is missing?

I'm not sure.

There might be some more detailed information in the zone_bh log

That'll be /var/log/zone_bh.<uuid> on the compute node.

I have quite a few zone_bh files in there but not one for this uuid and most are from 2019

Ok, dunno, but I got it back by creating a new empty VM and zfs cloning the snapshot over as the disk

And successfully resized with cli parted

Thanks bahamat

natefoo: That's good to hear.