Now older versions of qemu-kvm didn't throw this error say if you just had "-video cirrus" when starting qemu-kvm. But newer versions do care. And this probably only applies to you if you are running from bash/terminal with remote kvm images. What you need to do is remove the "-video" part and just add -vnc :5 eg. this would fix the error: qemu-system-x86_64 -enable-kvm -boot order=cd,once=dc -m 1024 -drive........

The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs. qemu-kvm command: /usr/libexec/qemu-kvm -version QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard ........

WARNING: Image format was not specified for '/mnt/space/cucm12.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. #you should manually specify the format q........

This is a common issue that I haven't seen many answers for on the internet. When you are using Linux as your host machine and you are connecting to another Linux machine over VNC you CANNOT use Ctrl+Alt+F1 to change virtual consoles as it sends the keys to your actual local machine. In many versions of Linux you can cycle through virtual terminals including over VNC using this: Alt + Left Arrow or Alt + Right Arrow This........

The key thing is that you must use a "machine"id of "pc-1.3" or it will say your hardware is not supported. Additionally you MUST use a virtio disk or you will get a ks_pre.sh error as soon as the install starts (a look at logs will show it can't find a disk). This is funny because even though the OS finds the disk and an fdisk -l shows it, it looks like the script looks for a /dev/vda device (virtio) and nothing else, so if you didn't use Virtio as you........

This command in Debian/Ubuntu/Mint will get everything need installed for most Java based KVM viewers: sudo apt install icedtea-netx The following additional packages will be installed: ca-certificates-java icedtea-netx-common openjdk-8-jre openjdk-8-jre-headless It seems every other updated version of Java or Icedtea breaks things and I will save the frustration of Java for another post.........

pxe-32 tftp open timeout The solution was to enable tftp in xinetd with "chkconfig tftp on". See the troubleshooting below: chkconfig --list NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off acpid 0:off&n........

The normal solution would be as follows: export DISPLAY=:0.0 /usr/lib/vino/vino-server & But what happens if that doesn't work? I haven't been able to find much documentation about how to find the list of displays and how their numbering works in Xorg. Sometimes you'll get this error when trying to restart vino: Cannot open display: For some reason my display is not on 0.0........

Basic Port ListingHopefully someone finds this useful or at least interesting. http://www.sans.org/top20/#u9 Name Port Protocol Description Small services ........