sure, Normally I use "vm start <vm>". root@foxden:/home/sky # zfs list NAME USED AVAIL REFER MOUNTPOINT tank 76.4G 193G 19K /tank tank/vm 76.4G 193G 10.6G /tank/vm tank/vm/mail 13.0G 193G 13.0G /tank/vm/mail tank/vm/mail0 52.6G 195G 50.2G - zroot 65.0G 179G 96K /zroot zroot/ROOT 12.0G 179G 96K none zroot/ROOT/default 12.0G 179G 12.0G / zroot/tmp 112K 179G 112K /tmp zroot/usr 664M 179G 96K /usr zroot/usr/home 140K 179G 140K /usr/home zroot/usr/ports 663M 179G 663M /usr/ports zroot/usr/src 96K 179G 96K /usr/src zroot/var 752K 179G 96K /var zroot/var/audit 96K 179G 96K /var/audit zroot/var/crash 96K 179G 96K /var/crash zroot/var/log 272K 179G 272K /var/log zroot/var/mail 96K 179G 96K /var/mail zroot/var/tmp 96K 179G 96K /var/tmp zroot/virtualworld 52.3G 179G 5.93G /zroot/virtualworld zroot/virtualworld/fortress 36.1G 214G 1.37G -
tank = on SAS drives zroot = on single SSD root@foxden:/zroot/virtualworld/fortress # cat fortress.conf loader="bhyveload" cpu=4 memory=6G network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="/dev/zvol/zroot/virtualworld/fortress" disk0_dev="custom" uuid="acdee15c-08c9-11e7-9640-f04da20ab066" network0_mac="58:9c:fc:0e:f1:2e" --- ----------------------- Virtual Machine: fortress ------------------------ state: bootloader (30327) datastore: default loader: bhyveload uuid: acdee15c-08c9-11e7-9640-f04da20ab066 uefi: no cpu: 4 memory: 6G memory-resident: 0 (0.000B) network-interface number: 0 emulation: virtio-net virtual-switch: public fixed-mac-address: 58:9c:fc:0e:f1:2e fixed-device: - active-device: tap4 desc: vmnet-fortress-0-public mtu: 1500 bridge: bridge0 bytes-in: 0 (0.000B) bytes-out: 0 (0.000B) virtual-disk number: 0 device-type: custom emulation: virtio-blk options: - system-path: /dev/zvol/zroot/virtualworld/fortress --- root@foxden:/zroot/virtualworld/fortress # ls /dev/zvol/zroot/virtualworld/ fortress ----- Original Message ----- From: "Allan Jude" <allanj...@freebsd.org> To: "freebsd-virtualization" <freebsd-virtualization@freebsd.org> Sent: Tuesday, March 14, 2017 5:25:20 PM Subject: Re: bhyveloader / userboot - VM installation fails On 2017-03-14 12:59, Paw Nishi wrote: > Currently playing with bhyve on bare metal with vm-bhyve > > Created a zvol > Setup the zvol as disk0 in config > Installed VM with FreeBSD-11.0-bootonly ISO > Select ZFS as type with encryption. > Install successful > Restart VM, > > Displays following: > Consoles: userboot > > FreeBSD/amd64 User boot, Revision 1.1 > (r...@releng2.nyi.freebsd.org, Thu Sep 29 01:38:36 UTC 2016) > - > can't load 'kernel' > > Type '?' for a list of commands, 'help' for more detailed help. > > OK lsdev > host devices: > host0: Host filesystem > disk devices: > disk0: Guest drive image > disk0p1: FreeBSD boot > disk0p2: FreeBSD swap > disk0p3: FreeBSD ZFS > zfs devices: > > What is the next to get it to boot, or can I only use UFS when running in > bhyve? > I did read a previous mail from 2012 > (https://lists.freebsd.org/pipermail/freebsd-virtualization/2012-December/001031.html) > - it's now 2017 and this still an issue? > > thxs > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" > I don't think your issue is related to the 2012 post. Can you provide mode details about your setup, like the zvol device, and the invocation of bhyve-load? -- Allan Jude _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"