Virtual Machines Bugs

[inman.turbo]

Error: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 137, in call_method
result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1215, in _call
return await methodobj(*prepared_call.args)
File "/usr/lib/python3/dist-packages/middlewared/service.py", line 469, in create
rv = await self.middleware._call(
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1215, in _call
return await methodobj(*prepared_call.args)
File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1021, in nf
return await f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/vms.py", line 105, in do_create
await self.middleware.run_in_thread(self._check_setup_connection)
File "/usr/lib/python3/dist-packages/middlewared/utils/run_in_thread.py", line 10, in run_in_thread
return await self.loop.run_in_executor(self.run_in_thread_executor, functools.partial(method, *args, **kwargs))
File "/usr/lib/python3/dist-packages/middlewared/utils/io_thread_pool_executor.py", line 25, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/connection.py", line 41, in _check_setup_connection
if not self._is_connection_alive():
File "/usr/lib/python3/dist-packages/middlewared/plugins/vm/connection.py", line 34, in _is_connection_alive
return self.LIBVIRT_CONNECTION and self.LIBVIRT_CONNECTION.isAlive()
File "/usr/lib/python3/dist-packages/libvirt.py", line 4370, in isAlive
if ret == -1: raise libvirtError ('virConnectIsAlive() failed', conn=self)
libvirt.libvirtError: invalid connection pointer in virConnectIsAlive

Also When I did manage to create a debian vm I couldn't run graphical installer through novnc (couldn't connect to display :0). Text installer worked but then vm wanted to keep booting form cdrom after install. I deleted the cdrom (couldn't find a way to change boot devices or boot order). After deleting the cdrom the machine wouldn't boot at all. This was with a machine set to UEFI boot. I tried to do a fresh install on a machine set to bios mode when I ran into the above errors. Will post to Jira in the comming few days.

There is a lot to love here though. The ui design is very nice and I like the NoVNC implementation and the way it is done.

 

[inman.turbo]

https://jira.ixsystems.com/browse/NAS-108996

 

[beagle]

couldn't find a way to change boot devices or boot order

Open your VM details and click on Devices:

Click on the 3 dots next to the device you want to change the order and select Change Device Order:

Then type an Order number to re-order the booting order.

Dragging the devices to re-order them would be more user friendly. Maybe a improvement suggestion?

 

[inman.turbo]

Dragging the devices to re-order them would be more user friendly. Maybe a improvement suggestion?

Yes or labeling it "boot" order I saw the "change device order" but it made no sense to me, it gave me a numerical number in the thousands! Also after removing the cdrom disk entirely why wouldn't it boot from the hard disk? Here is an example from a popular libvirt gui client (virt-manager) . Note that I can not only define the order, but whether the device is a boot device.

.

 

[Samuel Tai]

The boot order starts at 1000 and goes up in sequence. There can't be any breaks in the sequence. This doesn't map inside the VM's boot order, but is the order bhyve orders the devices to the guest. Make sure your boot volume is ordered 1000. Any other devices can be ordered willy-nilly.

 

[inman.turbo]

The boot order starts at 1000 and goes up in sequence. There can't be any breaks in the sequence. This doesn't map inside the VM's boot order, but is the order bhyve orders the devices to the guest. Make sure your boot volume is ordered 1000. Any other devices can be ordered willy-nilly.

Thanks. This isn't bhyve though, this is kvm on SCALE. And the real problem is I couldn't tell from the gui whether the underlying issue was a firmware problem with UEFI, or if the disk simply wasn't marked as a boot device. My only option at that point is to drop into the cli and start perusing xml files. The vm didn't appear to attempt to boot from the NICS either, for instance. But they are also listed in the "Change Device Order" menu. I just land in the uefi dos shell.