6.8 - cannot start new VM - UEFI Shell ??

[Tom3]

 

This is moved from the New 6.8 release topic to General Support.

Thaks to boneinl for his assistance so far.

Above is the link to that thread.

 

To summarize:  Prior to 6.8 no VM issues.

After updating to 6.8 Release, able to create a new VM, but it does not start correctly.

VNC correctly attaches to the VM, but the screen is blank (waiting >30 minutes for the VM to start).

 

After changing the processor type from Q35-4 to Q35-3.1 and assuring no overlap in

CPU cores/threads assigned with 0/1,   starting the new VM brings up a UEFI Interactive shell in VNC.

That Shell provides no option to start the ISO image.

 

-- Tom

 

 

[bonienl]

Can you create a new VM and choose "SeaBIOS" as BIOS. This lets the VM start in legacy mode instead of UEFI mode.

[Tom3]

4 minutes ago, bonienl said:

Can you create a new VM and choose "SeaBIOS" as BIOS. This lets the VM start in legacy mode instead of UEFI mode.

That brings up the Ubuntu splash screen with dots underneath.  About 5 seconds,

then the VNC screen goes black ~5 minutes waiting. Heavy CPU activity (50%) on the VM-assigned cores,

but nothing on the VNC except black. Keystrokes / Mouse on the VNC screen does

nothing.

 

VM Log:

 

-uuid a5aa82ff-759f-e574-4d98-098d71496f49 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=33,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=utc,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \
-device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \
-device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \
-device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
-device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \
-drive file=/mnt/user/domains/Ubuntu-19.10-Desktop/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback \
-device virtio-blk-pci,scsi=off,bus=pci.3,addr=0x0,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \
-drive file=/mnt/user/isos/ubuntu-19.10-desktop-amd64.iso,format=raw,if=none,id=drive-sata0-0-0,readonly=on \
-device ide-cd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2 \
-netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:65:ec:5c,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=37,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-vnc 0.0.0.0:0,websocket=5700 \
-k en-us \
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \
-device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2019-12-11 21:02:54.243+0000: Domain id=15 is tainted: high-privileges
2019-12-11 21:02:54.243+0000: Domain id=15 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)

 

-- Tom

 

 

 

 

[bonienl]

Have you tried another ISO?

 

I am using https://ubuntu.com/download/desktop

[Tom3]

1 hour ago, bonienl said:

Have you tried another ISO?

 

I am using https://ubuntu.com/download/desktop

HI bonienl - thank you for your continued help !

 

1.  I copied the 19.10 ISO back to the Linux host it came from and did a binary file compare.

The original ISO and the one from the Unraid system are bit-identical  (linux cmp command).

That ISO correctly builds and runs under VirtualBox on that independent Linux host. It is the

stock Canonical 19.10 Desktop AMD64 distribution ISO from the download page.

 

2. I built from 19.04 ISO already on the Unraid server that previously built and ran correctly

as a VM under Unraid 6.7.    Under 6.8 it builds and runs correctly when the VIRT Disk size

is 50G, but fails (like 19.10 fails) when the Virt Disk size is 64G.  It uses OVMF BIOS.

 

3. I tried to build and run 19.10 with Virt DIsk =  50G.  Tried both SeaBIOS and OVMF but

it fails the same way as previous postings.

 

-- Tom

 

 

[Fizzyade]

Set the graphics card to cirrus rather than QXL and try again.

[Tom3]

1 hour ago, Fizzyade said:

Set the graphics card to cirrus rather than QXL and try again.

Thanks,  does not fix the issue.    I have noticed however that the VM's created under 6.7 have listed

on the Virtual Machines status page GRAPHICS: VNC:auto while the one created under 6.8 lists  GRAPHICS: VNC:5900

That's the only difference I can see.

 

The SHA256SUM of the 19.10 ISO on the Unraid disk is the same as the SHA256 downloaded from

the Canonical download site. So I'm pretty confident that the ISO is good.

 

-- Tom