Victor Sudakov wrote: > Dan Ritter wrote: > > Here's a typical non-libvirtd qemu/kvm invocation: > > > > cd /var/spool/kvm > > export VNAME=virtualmachinename > > export CPUS=2 > > export RAM=4096 > > export MAC=00:15:f1:c1:a2:01 > > export VNC=:1 > > export IMAGE=/var/spool/kvm/images/$VNAME.img > > > > kvm -m $RAM -smp $CPUS -name $VNAME -rtc base=utc -boot menu=on -drive > > file=$IMAGE,if=none,id=drive-virtio-disk0,boot=on,cache=writeback -device > > virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 > > -device virtio-net-pci,vlan=0,id=net0,mac=$MAC,bus=pci.0,addr=0x3 -net > > tap -usbdevice tablet -vnc $VNC & > > The "kvm" run in the line above is just a wrapper script that runs "qemu > -enable-kvm", isn't it?
$ cat /usr/bin/kvm #! /bin/sh exec qemu-system-x86_64 -enable-kvm "$@" -dsr-
