When I attempt to create an ubuntu VM After loading up the VNC Monitor, and going to install Ubuntu when I press enter on Install. It stalls on a black screen?

Any ideas?

Bump for assist, if theres any information missing please let me know and I will update accordingly.

 

not sure, but i would start sharing the diagnostics and a bit of background.

for example, only this distro having issue? first time creating a VM and encountering this issue?

passingthrough anything to that VM?

have you tried with both seabios and ovmf?

can you try selecting different options for the VNC?

 

On 4/7/2019 at 6:11 PM, GVarley said:

When I attempt to create an ubuntu VM After loading up the VNC Monitor, and going to install Ubuntu when I press enter on Install. It stalls on a black screen?

Any ideas?

I have seen cases where using a different VNC client can be better rather than the web based one built into Unraid.    I personally tend to use realVNC running on Windows or a Raspberry Pi as my client.

Okay, A few things since I got two answers.

First, I have made VM's work with Unraid before. Its just recently they seem to be being weird. No pass through. Currently using most up to date version of Ubuntu to try and do this, but also tried an Iso of WinServer 2016 still with no luck, both of which using the default settings given by Unraid.

Will spool up a new VM running ubuntu's latest version, and run an external VNC Client and get back to you.

Okay, update.

using UltraVNC as a viewer made no difference alas.
Are there any diagnostics I can pull from Unraid regarding what the VM is doing when trying to load up?
Tried using Seabios, not certain if any difference was made.

Try the different VNC video options available.

2 hours ago, jonathanm said:

Try the different VNC video options available.

No change as a result of this.

2019-04-10 02:04:31.572+0000: starting up libvirt version: 4.7.0, qemu version: 3.0.0, kernel: 4.18.20-unRAID, hostname: Melchior
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=SteamServ,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-17-SteamServ/master-key.aes -machine pc-q35-3.0,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/fadfecf9-1d7b-371a-014d-032e356dbfec_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 5120 -realtime mlock=off -smp 2,sockets=1,cores=2,threads=1 -uuid fadfecf9-1d7b-371a-014d-032e356dbfec -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=25,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,porotindex=2 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:37:0f:cd,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=29,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-04-10 02:04:31.573+0000: Domain id=17 is tainted: high-privileges
2019-04-10 02:04:31.573+0000: Domain id=17 is tainted: host-cpu
2019-04-10T02:04:31.647466Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)

Log for VM is as above.
If theres anything else I can use to help, please let me know.

Also, if possible, can I request this thread be moved to the VM Support board, I accidentally put this thread here, instead of there. Thats entirely my mistake

do you have older vm's that are still working?

or experiencing issues with all your current vm's?

diagnostics are available in tools menu.

Older VM's were wiped a while ago unfortunately.
As for diagnostics. Will have a look

 

Could not find VM Specific diagnostics tools.

 

Had the same issue, but noticed on the dashboard that the assigned CPU cores are doing their business so I guessed maybe I should wait a little. After a minute or 2 the ubuntu install came in. Just be patient. Make yourself a coffee after starting the VM.