For a lot of reasons, it may be convenient to detach or attach live disks to a running VM without having to reboot it. Sure, you can use some network based storage, but when performance counts, attaching a new virtual disk will usually give you better throughput and lower latency in a quick testing situation. This doesn't work, why not? drive_add 0 if=virtio,file=/tmp/vm.qcow2,if=virtio,format=qcow2,id=rtt Can't hot-ad........

If you've come here, don't be embarraassed, working in IT, this is the MOST common computer problem that almost everyone will encounter. The reason why I'm doing this post is because I've seen an increase from colleagues and admins having this problem and many times it's not even your fault. A common scenario is that someone acquires a new or used computer which they weren't given the password for. Fortunately Ihave a detailed list of all the options whether free or pa........

/usr/libexec/qemu-kvm -enable-kvm -boot order=cd,once=dc -vga cirrus -m 4096 -drive file=~/23815135.img,if=virtio -usbdevice tablet -net nic,macaddr=DE:AD:BE:EF:D4:AB -netdev bridge,br=br0,id=net0 qemu-kvm: -usbdevice tablet: '-usbdevice' is deprecated, please use '-device usb-...' instead access denied by acl file qemu-kvm: bridge helper failed [root@CentOS-82-64-minimal 23815135]# /usr/libexec/qemu-kvm -enable-kvm -boot order=cd,once=dc -vga cirrus -........

Iam going to build this based on a series of small howto QEMU / KVMposts I've made as I feel much of the information is actually hard to find and piece together from the rest of the web. What I'm going to focus on is how to use virtio as the NIC because if you don't you get very slow NIC speeds but with the virtio NIC model you basically get host speeds. /usr/libexec/qemu-kvm -enable-kvm -smp 8 -m 16000 -net user -net nic,model=virtio -drive file=ubuntu-gpt2l........

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

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 is useful if you are installing Windows and need virtio but of course Windows needs the virtio driver which is on a second iso. This is the line of code you would add to your kvm startup script and then you get this iso as second cdrom you can browse to for your Windows install of virtio driver's or whatever other use you need it for. -drive file=/kvmtemplates/virtio-win-0.1-94.iso,media=cdrom........

I messed up the bootloader by accident on a standard Centos 6.3 install because I turned the /dev/vda1 boot partition into an mdadm raid 1. This was all done correctly aside from one point Ididn't realize was an issue metadata=00.90 is the only thing that will allow you to boot (otherwise grub won't work and you won't boot). So the next step is rescue mode from a CD right? The problem you will find is that grub does not detect your hard drives, this is Ibelieve is be........

http://realtechtalk.com/downloads/virtio-win-0.1-74.iso Current Direct stable URL from Fedora: https://fedoraproject.org/wiki/Windows_Virtio_Drivers Direct Downoad of Stable Virtio: https://fedorap........