Most newer distros inexplicably cause your NIC to have what Icall "random" non-standard name conventions because of systemd. This is a big problem for many people and especially those running servers. Imagine that you have a static IPconfigured for ens33 but then the hard disk is moved to a newer system, the NIC could be anything from ens33 to enp0s1, meaning that manual intervention is required to go and update the NIC config file (eg. /etc/network/interfa........

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........

forcedeth 0000:00:08.0: irq 25 for MSI/MSI-X forcedeth 0000:00:08.0: eth0: MSI enabled forcedeth 0000:00:08.0: eth0: no link during initialization ADDRCONF(NETDEV_UP): eth0: link is not ready forcedeth 0000:00:08.0: eth0: link up ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Dec 1 18:21:32 box15 kernel: forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64. Dec 1 18:21:32 box15 kernel........

Thsi is very handy when doing your own kernel development. -m specifies how much ram (in the example it is 768MB) -kernel specifies the path to the kernel file -net tap,ifname=tap1,script=no (the ifname=tap1 is what you need to change and setup manually). *Run "tunctl -b" to create a tap device and use the one it gives you for ifname= Enable networking to the outside like this: *Note we assume that your bridge is br0 i........