Multiple VM bugs in FN11.2 Beta

[KrisBee]

I found multiple bugs in the creating/using VMs in the FN11.2 Beta.

1. A VNC device can incorrectly be assigned to a VM when the selected boot method is “UEFI-CSM” in the first step of the VM wizard.

2. In step 5 of the wizard, the list of physical interfaces you can attach to includes any virtual devices ( e.g. tap or venet) that exist on the system.

3. In step 7, confirming VM creation, can generate a more than 80% pool use error preventing VM creation.

Error text: [EINVAL] pool_dataset_create.volsize: It is not recommended to use more than 80% of your available space for VOLUME

Apart from the fact that the term VOLUME is supposedly deprecated in this version of FN, this happens after the wizard creates the zvol for you. Is this meant to be just a warning? To prevent VM creation in this way must be wrong.

4. A debian iso created to work via the serial console and be installed using the UEFI-CSM boot method does not work and generates this error:

Code:

Boot Failed. CDROM 0
Boot Failed. Harddisk 1
!!!! X64 Exception Type - 000000000000000D	 CPU Apic ID - 00000000 !!!!
RIP - 000000003FAF0FF5, CS - 0000000000000028, RFLAGS - 0000000000010006
ExceptionData - 0000000000000000
RAX - 0000000000000000, RCX - 0000000000000008, RDX - 0000000000000050
RBX - 000000003F0C0618, RSP - 000000003FBDEA78, RBP - 000000003FBDEDD8
RSI - 00000000C0004120, RDI - 000000003FBDEA78
R8 - 0000000000000001, R9 - 000000003FBDEF7C, R10 - 00000000C0004120
R11 - 0000000000000000, R12 - 0000000000000800, R13 - 0000000000000000
R14 - 0000000000000000, R15 - 0000000000000000
DS - 0000000000000008, ES - 0000000000000008, FS - 0000000000000008
GS - 0000000000000008, SS - 0000000000000008
CR0 - 0000000080000023, CR2 - 0000000000000000, CR3 - 000000003FB7E000
CR4 - 0000000000000668, CR8 - 0000000000000000
DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 000000003FB68E98 000000000000003F, LDTR - 0000000000000000
IDTR - 000000003F6FA018 0000000000000FFF, TR - 0000000000000000
FXSAVE_STATE - 000000003FBDE6D0
!!!! Find PE image /wrkdirs/usr/ports/sysutils/uefi-edk2-bhyve-csm/work/uefi-edk2-0.1/Build/BhyveX64/RELEASE_GCC48/X64/UefiCpuPkg/CpuDxe/CpuDxe/DEBUG/CpuDxe.dll (ImageBase=000000003FAED000, EntryPoint=000000003FAED2AF) !!!!

The same iso has been tested as working with FN 11.1-U5 and does work in FN 11.2 BETA but only if the CLI is used to start the VM, e.g:

Code:

bhyve -c 4 -m 1024M -A -H -P \
-s 0:0,hostbridge \
-s 1:0,lpc \
-s 2::0,ahci-cd,/mnt/NasPool/home/chris/debian-9.4-amd64-CD-1.iso \
-s 3:0,virtio-blk,/dev/zvol/NasPool/VM/debtest-upwfz \
-s 4:0,virtio-net,tap20 \
-l com1,/dev/nmdm20A \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CSM.fd \
debcsm &

 

[Ericloewe]

Have they been reported?

 

[diskdiddler]

Please report any of these, you'd be surprised just how good the support is on the bugtracker to here. They really do take most reports seriously.

https://redmine.ixsystems.com/projects/freenas/issues/new

 

[KrisBee]

Not reported yet as (a) others may wish to comment on, or add to this thread and (b) I'm still finding more bugs.

 

[KrisBee]

More bugs (?):

1. When using the VM wizard you can choose a zvol that's already in use by another VM.

2. If you change the zvol size picked by the wizard this is not reflected in summary text in final step 7.

3. Using the wizard can you choose virtio for nic, but the disk/raw file mode is auto set to achi and you have to wait until vm created and then navigate to VM devices to change disk/raw file mode to virtio.

4. Selecting a serial connection on a running VM auto opens a web shell and executes the correct cu command, but after disconneting with "~." the exit command in the shell does nothing in chrome or firefox and leaves a /usr/bin/bash process running.

5. The wizard allows choice of linux, windows, or FreeBSD for guest OS, so what about openbsd, netbsd, or anything based on the illumos kernel?

6. When creating a "Docker Host" VM, can't add password or change to raw file type to virtio until the VM is created and have to edit it's raw device

7. The hidden directory .bhyve_containers appears in dir/file tree when browsing for file locations whne creating a "Docker Host" VM.

8. A ""Docker Host" VM is still based on a very out of date version of rancheros ( see: https://github.com/rancher/os/releases )

Code:

 [root@rancher ~]# ros version
No help topic for 'version'
[root@rancher ~]# ros os version
v1.1.3
[root@rancher ~]#  ros os list
rancher/os:v1.4.0 remote latest
rancher/os:v1.3.0 remote available
rancher/os:v1.2.0 remote available
rancher/os:v1.1.4 remote available
rancher/os:v1.1.3 remote available running
rancher/os:v1.1.2 remote available
rancher/os:v1.1.1 remote available
rancher/os:v1.1.0 remote available
rancher/os:v1.0.5 remote available
rancher/os:v1.0.4 remote available
rancher/os:v1.0.3 remote available
rancher/os:v1.0.2 remote available
rancher/os:v1.0.1 remote available
rancher/os:v1.0.0 remote available
rancher/os:v0.9.2 remote available
rancher/os:v0.8.1 remote available
rancher/os:v0.7.1 remote available
rancher/os:v0.6.1 remote available
rancher/os:v0.5.0 remote available
rancher/os:v0.4.5 remote available 

 

[KrisBee]

I'm not going to waste anymore time on this as it's clear for even the most cursory of tests that the validation which does exist when using the old UI in FN11.12 BETA has not been carried over to the new UI. Nor has there been any fundamental changes in the approach to creating/using VMs.

The "Docker Host" base remains seriously out of date. FreeNAS chose never to implement the general use of bhyveload or the grub-loader in the FN11 series but instead has relied on the two variants of the bhyve UEFi firmware. The UEFI boot method continues to cause confusion and remains a barrier for some users wanting to create linux VMs. The UEFI-CSM boot method is unusable in FN11.2 BETA, VNC connections still do not work and AFAIK there's no upstream work to fix this. So, to use the UEFI-CSM boot method you must have an install iso which supports a serial console connection. Even then the UEFI-CSM boot method fails to work via the new WEBUI in FN11.2 BETA. I seriously wonder if the devs have ever tested any iso to see if UEFI-CSM can work.

There's also a certain irony that if you wanted to to use FN11.2 BETA (or F11-1-U5) to create a test VM of the beta or nightly, you have to jump thorugh hoops to do it and it's not possible to use the WebUI alone (See: https://forums.freenas.org/index.ph...as-11-2-vm-in-iohyve-bhyve.64005/#post-458658 )

I suspect this last point and the UEFI-CSM failure may be down to how bhyve determines which slots to look at for a bootable device. That's not clearly documented.

 

[diskdiddler]

You could try logging a job, it's worth letting them know. They pay much more attention there.

https://redmine.ixsystems.com/projects/freenas/roadmap

Click the +