chardev spicevmc,id=charchannel0,name=vdagent \ device isa-serial,chardev=charserial0,id=serial0 \ netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 \ device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \ drive file=/home/chazelas/Downloads/2,format=qcow2,if=none,id=drive-virtio-disk0 \ device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \ device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0圆 \ global kvm-pit.lost_tick_policy=discard \ mon chardev=charmonitor,id=monitor,mode=control \ chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-freebsd11.0/monitor.sock,server,nowait \ machine pc-i440fx-wily,accel=kvm,usb=off \ Instead libvirt would start qemu with some special options that allows to interact with qemu.įor instance, on my system, libvirt started qemu with those parameters for one it its VMs: qemu-system-x86_64 -enable-kvm \ With it, you would not start qemu directly. Libvirt provides with a level of abstraction above things like qemu.
In that framework, you would define virtual machines using any of the hypervisor supported by libvirt including qemu, xen, virtualbox via the management interface. Virsh is the CLI tool to operate the libvirt virtualisation management framework.
0 kommentar(er)
