Victor Sudakov wrote on 2019-02-11 17:46:
...
I've preferred disk0_dev="zvol" VMs for aesthetical reasons since
vm-bhyve started supporting them. Those file-based VMs get in the way
while backing up $vm_dir, and their disks are not visible in
"zfs list -t volume"
+1.
--
P Vixie
Frank Leonhardt wrote:
> >
> > vm-bhyve keeps virtual machines on zfs volumes with volmode=dev. How can
> > I access/mount the filesystems within the volume when the virtual host
> > is offline?
> >
> > If I kept virtual disks in raw files, I could access them as devices
> > with mdconfig. But:
>
Paul Webster wrote:
> mdconfig -a -t vnode -f afaik
Sorry, this does not work.
root@newserv:~ # mdconfig -a -t vnode /dev/zvol/zroot/vm/mail/disk0
mdconfig: /dev/zvol/zroot/vm/mail/disk0 is not a regular file
There must be some other way.
> once they are mounted you could dd them
Indeed, I
mdconfig -a -t vnode -f afaik
once they are mounted you could dd them over to the zvols and then resize
them from within the vm
On Mon, 11 Feb 2019 at 17:04, Victor Sudakov wrote:
> Dear Colleagues,
>
> vm-bhyve keeps virtual machines on zfs volumes with volmode=dev. How can
> I access/mount
Dear Colleagues,
vm-bhyve keeps virtual machines on zfs volumes with volmode=dev. How can
I access/mount the filesystems within the volume when the virtual host
is offline?
If I kept virtual disks in raw files, I could access them as devices
with mdconfig. But:
root@newserv:~ # mdconfig -a -f
