Centos 7 Spice Console Black Screen #137
Comments
|
Hello, you should look at VM process You can enable debug logging here: kvm-vdi/KVM/hypervisors/config Line 37 in a6a40b6 |
|
I don't see any password setup in the process string root@CentOS7 ~]# ps axwww|grep debian I have tried opening virt-manger and launching virt-viewer from there using the same password when virsh creates the VM [Fri Oct 05 16:23:24.503670 2018] [php7:notice] [pid 9623] [client 192.168.122.209:36134] Executing: sudo virt-install --name='debian9' --disk path='/data/debian9-5bb742a38fd34.qcow2',format=qcow2,bus=virtio,cache=none --disk path='/var/lib/libvirt/images/debian-9.5.0-amd64-xfce-CD-1.iso',device=cdrom,target=hdc,perms=ro --soundhw=ac97 --vcpus='2',cores='2',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-type='linux' --os-variant='debiansqueeze' --graphics spice,listen=0.0.0.0,password=C5oug6RAqSLdh --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 , referer: http://192.168.122.209/kvm-vdi/dashboard.php still shows a black scree |
|
Take a look at your vm XML config file in /etc/libvirt/qemu. |
|
qemu apparently
|
|
Okay, it's using correct emulator |
|
do you want me to disable it completely or will permissive mode do, cause i tried that before, its still shows a black screen |
|
will disable selinux completely, and get back to you. |
|
You should disable it completely and reboot server. Basically, vm should have SPICE password visible in VM process section like this: |
|
sestatus nope still a black screen |
|
so how do i force qemu to use the wrapper ?? |
|
I dont think it's a password issue, cause when i launch virt-manger and use the same password it still shows a black screen. |
|
this is a VM running perfectly fine |
|
using virt-viewer directly, with the generated password still the same |
|
It may not be password issue, but a problem with kvm-vdi installation. |
|
Is there any way to find out, or am i on my on on this one ?, don't mint starting from scratch but would be a lot better if i really knew what was actually going on in the backend. |
|
can it be a permission issue in someways ? what other log can i check apart from the "error_log" ? |
|
wow, dont't know what just happened it just works now |
|
man i'm scratching my head, wtf ?? bug ?? I swear didn't don anything ?? |
|
Edited : this was irrelevant as i figured out that this wasn't the problem. the black screen issue still persists if make changes to the cpu/memory allocation while deploying the VM. |
|
could you please explain what does this mean ? Oct 5 21:32:58 CentOS7 journal: Allocating size to SpiceDisplay 0x55879196a3c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? |
|
Ok so I found out that if i playaround with the cpu & memory allocation it gives me the blackscreen issue, but if i just leave to its defaults it works, now how this is related to spice i do not know. |
|
Not sure, how this could affect SPICE. Perhaps this is somehow related to hypervisor being run in virtualised environment. Is there enough cpu/memory allocated for hypervisor? |
|
Yes 6 cores and 4GB of RAM |
|
It's the same with the windows host. black screen if i change cpu/mem. also I've notice the VM installation takes very long. |
|
Yup, can confirm this a CentOS issue, setup the whole thing on Debian 9 (Virtual ) and everything is working can allocate more core/mem no problem. |
|
The main difference between those 2 distributions is that Centos uses SELinux. It must be completely disabled and server rebooted. |
|
After Enabling Nested VM for KVM & host-passthrough in virt-manager, the CentOS Black Screen issue is fixed, it's working fine now, I can allocate more resources without any problem. |
|
same problem here trying to install debian on centos host |
|
did you activated by BIOS the required option for virtualization? you can check it by issuing dmesg | grep kvm |
Hi,
I am able to create VMs via the dashboard but when i launch the spice console, i'm presented with a black screen in virt-viewer, checking the running processes shows that the VM is running. also no errors are generated. spice works fine when i create the VM from virt-manager.
Fri Oct 05 00:57:45.058252 2018] [core:notice] [pid 12887] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0 [Fri Oct 05 00:57:45.058981 2018] [suexec:notice] [pid 12887] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.122.209. Set the 'ServerName' directive globally to suppress this message [Fri Oct 05 00:57:45.076830 2018] [auth_digest:notice] [pid 12887] AH01757: generating secret for digest authentication ... [Fri Oct 05 00:57:45.077460 2018] [lbmethod_heartbeat:notice] [pid 12887] AH02282: No slotmem from mod_heartmonitor [Fri Oct 05 00:57:45.103266 2018] [mpm_prefork:notice] [pid 12887] AH00163: Apache/2.4.6 (CentOS) PHP/7.2.10 configured -- resuming normal operations [Fri Oct 05 00:57:45.103305 2018] [core:notice] [pid 12887] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND' [Fri Oct 05 00:59:24.693830 2018] [php7:notice] [pid 13801] [client 192.168.122.209:40060] Executing: sudo virsh list --all, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 00:59:25.236048 2018] [php7:notice] [pid 13801] [client 192.168.122.209:40060] Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 00:59:25.688674 2018] [php7:notice] [pid 13801] [client 192.168.122.209:40060] Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 00:59:43.037104 2018] [php7:notice] [pid 12897] [client 192.168.122.209:40068] Executing: sudo ls /var/lib/libvirt/images|grep -i .iso, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:12.949216 2018] [php7:notice] [pid 12896] [client 192.168.122.209:40072] Executing: sudo qemu-img create -f qcow2 -o size='10'G '/data/debian-5bb66a44e7aa1.qcow2', referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:13.554815 2018] [php7:notice] [pid 12896] [client 192.168.122.209:40072] Formatting '/data/debian-5bb66a44e7aa1.qcow2', fmt=qcow2 size=10737418240 encryption=off cluster_size=65536 lazy_refcounts=off \n, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:13.554958 2018] [php7:notice] [pid 12896] [client 192.168.122.209:40072] Executing: sudo virt-install --name='debian' --disk path='/data/debian-5bb66a44e7aa1.qcow2',format=qcow2,bus=virtio,cache=none --disk path='/var/lib/libvirt/images/debian-9.5.0-amd64-xfce-CD-1.iso',device=cdrom,target=hdc,perms=ro --soundhw=ac97 --vcpus='2',cores='2',sockets='1' --ram='2048' --network bridge='br0',model=virtio --os-type='linux' --os-variant='debiansqueeze' --graphics spice,listen=0.0.0.0,password=2PnDx9pRSicrj --redirdev usb,type=spicevmc --video qxl --noreboot --wait=0 , referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:14.629721 2018] [php7:notice] [pid 12896] [client 192.168.122.209:40072] WARNING KVM acceleration not available, using 'qemu'\n, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:14.645006 2018] [php7:notice] [pid 12896] [client 192.168.122.209:40072] Executing: sudo /usr/local/VDI//vdi-xmledit -name 'debian', referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:14.842168 2018] [php7:notice] [pid 12896] [client 192.168.122.209:40072] /usr/local/VDI//vdi-xmledit:40: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead.\n if image_path:\n, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:14.975446 2018] [php7:notice] [pid 12896] [client 192.168.122.209:40072] Executing: sudo virsh list --all |tail -n +3|head -n -1|awk '{print $2" "$3}', referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:33.031391 2018] [php7:notice] [pid 13806] [client 192.168.122.209:40084] Executing: sudo virsh domdisplay debian, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:33.728976 2018] [php7:notice] [pid 13806] [client 192.168.122.209:40084] Executing: sudo virsh screenshot debian /tmp/debian.ppmbugfix, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:34.200645 2018] [php7:notice] [pid 13806] [client 192.168.122.209:40084] Executing: sudo virsh screenshot debian /tmp/debian.ppm, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:34.359102 2018] [php7:notice] [pid 13806] [client 192.168.122.209:40084] Executing: sudo cat /tmp/debian.ppm, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:34.541222 2018] [php7:notice] [pid 13806] [client 192.168.122.209:40084] Executing: sudo rm /tmp/debian.ppmbugfix, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:34.618494 2018] [php7:notice] [pid 13806] [client 192.168.122.209:40084] Executing: sudo rm /tmp/debian.ppm, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:47.910328 2018] [php7:notice] [pid 13802] [client 192.168.122.209:40090] PHP Notice: Undefined index: client_logged in /var/www/html/kvm-vdi/functions/functions.php on line 63, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:00:59.588128 2018] [php7:notice] [pid 13805] [client 192.168.122.209:40092] Executing: sudo virsh domdisplay debian, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:01:00.292036 2018] [php7:notice] [pid 13805] [client 192.168.122.209:40092] Executing: sudo virsh screenshot debian /tmp/debian.ppmbugfix, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:01:00.754569 2018] [php7:notice] [pid 13805] [client 192.168.122.209:40092] Executing: sudo virsh screenshot debian /tmp/debian.ppm, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:01:00.923094 2018] [php7:notice] [pid 13805] [client 192.168.122.209:40092] Executing: sudo cat /tmp/debian.ppm, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:01:01.094044 2018] [php7:notice] [pid 13805] [client 192.168.122.209:40092] Executing: sudo rm /tmp/debian.ppmbugfix, referer: http://192.168.122.209/kvm-vdi/dashboard.php [Fri Oct 05 01:01:01.182848 2018] [php7:notice] [pid 13805] [client 192.168.122.209:40092] Executing: sudo rm /tmp/debian.ppm, referer: http://192.168.122.209/kvm-vdi/dashboard.phpAlso is there any way i can make the Hypervisor Agent log more verbose ?
The text was updated successfully, but these errors were encountered: