Created a Pop! OS VM.  Went through the install successfully.  After restart, VNC remoting shows dashed lines across the top of the screen with the OS unresponsive.

 

Not much in the logs that would indicate any type of error...

 

-m 4096 \
-overcommit mem-lock=off \
-smp 2,sockets=1,cores=1,threads=2 \
-uuid 4e6878f9-79f6-9093-f806-b41ecd6f6408 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=37,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 ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/Pop! OS 2/vdisk1.img","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=libvirt-2-format,id=virtio-disk2,bootindex=1,write-cache=on \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/pop-os_20.04_amd64_intel_5.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \
-device ide-cd,bus=ide.0,unit=0,drive=libvirt-1-format,id=ide0-0-0,bootindex=2 \
-netdev tap,fd=39,id=hostnet0,vhost=on,vhostfd=40 \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:3e:61:a4,bus=pci.0,addr=0x3 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=41,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:2,websocket=5702 \
-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=pci.0,addr=0x2 \
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2020-05-11 12:50:48.716+0000: Domain id=5 is tainted: high-privileges
2020-05-11 12:50:48.716+0000: Domain id=5 is tainted: host-cpu
char device redirected to /dev/pts/2 (label charserial0)

Have you created other VMs successfully?

Are you able to ping the VM once it's started?

I have.  Currently have Windows 10 and Catalina running.  Have had other Linux distros running as well in the past.

Bump. So I also just tried to install POP_OS. The ISO loads fine and am able to start the installation process as well as enter my password for disk encryption. However after installation is complete and it asks to reboot the system reboots to black screen with horizontal white dashes at the top of the screen. (This is using VNC). Not sure if anyone has yet found a fix for this?

@VI510N If you see the horizontal lines, enter your encryption key and the login screen should come up. Some distros with disc encryption enabled show this behaviour that you can't see the screen to enter your passphrase for the disk encryption via vnc

I would avoid naming (including vdisk folder path) that uses special characters like an exclamation mark. I know this can cause issues with bash, so might be the problem here.

@bastl Yup looks like that was it, just couldn’t see it requesting for the encryption. Much appreciated.