You are not logged in.

Pages: 1

#1 2014-12-07 01:40:42

elrengo
Member
From: Argentina
Registered: 2014-11-06
Posts: 56

[SOLVED] - Can not start a virtual machine kvm

Hi! I backup my works vm. This VM is from KVM. I used it in RHEL6. I backup te hard and the XML. I installed the KVM following the wiki step. I create the ln to file because I have a hibrid hard disk, and put the vm in the mechanical hard disk.

When I want to start the VM from virt manager, I have this error:

Error starting domain: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory
Error starting domain: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1358, in startup
    self._backend.create()
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 999, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory

Thanks!

Last edited by elrengo (2014-12-08 03:16:27)

Offline

#2 2014-12-07 12:32:41

rebootl
Member
Registered: 2012-01-10
Posts: 431
Website

Re: [SOLVED] - Can not start a virtual machine kvm

Is the path you get in your error inside this XML ?

I'm not sure, but maybe you can simply correct it, pointing to the machine you want to start, e.g. /usr/bin/qemu-system-x86_64.

(Also see: https://bbs.archlinux.org/viewtopic.php?id=159159)

Personal website: reboot.li
GitHub: github.com/rebootl

Offline

#3 2014-12-07 15:04:23

elrengo
Member
From: Argentina
Registered: 2014-11-06
Posts: 56

Re: [SOLVED] - Can not start a virtual machine kvm

Thanks for the reply!

I create 2 links. HD & XLM:

/var/lib/libvirt/images/Virtual_Client_Windows_7-KVM.qcow2        --> /home/elrengo/VirtualMachines/kvm/libvirt/images/Virtual_Client_Windows_7-KVM.qcow2
/var/lib/libvirt/images/Virtual_Client_Windows_7-KVM.qcow2.type --> /home/elrengo/VirtualMachines/kvm/libvirt/images/Virtual_Client_Windows_7-KVM.qcow2.type

[/var/lib/libvirt/images]
[elrengo@xpsl421x]$ ls -l
total 8,0K
lrwxrwxrwx 1 root root 83 dic  6 08:15 Virtual_Client_Windows_7-KVM.qcow2 -> /home/elrengo/VirtualMachines/kvm/libvirt/images/Virtual_Client_Windows_7-KVM.qcow2
lrwxrwxrwx 1 root root 88 dic  6 08:15 Virtual_Client_Windows_7-KVM.qcow2.type -> /home/elrengo/VirtualMachines/kvm/libvirt/images/Virtual_Client_Windows_7-KVM.qcow2.type
[elrengo@xpsl421x]$ ls -l
total 62G
-rwxrwxr-x 1 elrengo users 62G feb 10  2014 Virtual_Client_Windows_7-KVM.qcow2
-rwxrwxr-x 1 elrengo users  10 dic  6  2013 Virtual_Client_Windows_7-KVM.qcow2.type

/etc/libvirt/qemu/Virtual_Client_Windows_7-KVM.xml  --> /home/elrengo/VirtualMachines/kvm/libvirt/qemu/Virtual_Client_Windows_7-KVM.xml

[elrengo@xpsl421x]$ ls -l
total 8,0K
drwxr-xr-x 3 root root 4,0K nov  3 18:01 networks
lrwxrwxrwx 1 root root   79 dic  6 08:13 Virtual_Client_Windows_7-KVM.xml -> /home/elrengo/VirtualMachines/kvm/libvirt/qemu/Virtual_Client_Windows_7-KVM.xml
[elrengo@xpsl421x]$ ls -l
total 8,0K
-rwxrwxr-x 1 elrengo users 6,0K feb 11  2014 Virtual_Client_Windows_7-KVM.xml

If I run the command in that thread:

$ pacman -Ql qemu | grep /usr/bin
[~]
[elrengo@xpsl421x]$ pacman -Ql qemu | grep /usr/bin
qemu /usr/bin/
qemu /usr/bin/qemu-aarch64
qemu /usr/bin/qemu-alpha
qemu /usr/bin/qemu-arm
qemu /usr/bin/qemu-armeb
qemu /usr/bin/qemu-cris
qemu /usr/bin/qemu-ga
qemu /usr/bin/qemu-i386
qemu /usr/bin/qemu-img
qemu /usr/bin/qemu-io
qemu /usr/bin/qemu-m68k
qemu /usr/bin/qemu-microblaze
qemu /usr/bin/qemu-microblazeel
qemu /usr/bin/qemu-mips
qemu /usr/bin/qemu-mips64
qemu /usr/bin/qemu-mips64el
qemu /usr/bin/qemu-mipsel
qemu /usr/bin/qemu-mipsn32
qemu /usr/bin/qemu-mipsn32el
qemu /usr/bin/qemu-nbd
qemu /usr/bin/qemu-or32
qemu /usr/bin/qemu-ppc
qemu /usr/bin/qemu-ppc64
qemu /usr/bin/qemu-ppc64abi32
qemu /usr/bin/qemu-ppc64le
qemu /usr/bin/qemu-s390x
qemu /usr/bin/qemu-sh4
qemu /usr/bin/qemu-sh4eb
qemu /usr/bin/qemu-sparc
qemu /usr/bin/qemu-sparc32plus
qemu /usr/bin/qemu-sparc64
qemu /usr/bin/qemu-system-aarch64
qemu /usr/bin/qemu-system-alpha
qemu /usr/bin/qemu-system-arm
qemu /usr/bin/qemu-system-cris
qemu /usr/bin/qemu-system-i386
qemu /usr/bin/qemu-system-lm32
qemu /usr/bin/qemu-system-m68k
qemu /usr/bin/qemu-system-microblaze
qemu /usr/bin/qemu-system-microblazeel
qemu /usr/bin/qemu-system-mips
qemu /usr/bin/qemu-system-mips64
qemu /usr/bin/qemu-system-mips64el
qemu /usr/bin/qemu-system-mipsel
qemu /usr/bin/qemu-system-moxie
qemu /usr/bin/qemu-system-or32
qemu /usr/bin/qemu-system-ppc
qemu /usr/bin/qemu-system-ppc64
qemu /usr/bin/qemu-system-ppcemb
qemu /usr/bin/qemu-system-s390x
qemu /usr/bin/qemu-system-sh4
qemu /usr/bin/qemu-system-sh4eb
qemu /usr/bin/qemu-system-sparc
qemu /usr/bin/qemu-system-sparc64
qemu /usr/bin/qemu-system-unicore32
qemu /usr/bin/qemu-system-x86_64
qemu /usr/bin/qemu-system-xtensa
qemu /usr/bin/qemu-system-xtensaeb
qemu /usr/bin/qemu-unicore32
qemu /usr/bin/qemu-x86_64
qemu /usr/bin/virtfs-proxy-helper

The XML File:

<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE 
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
  virsh edit Virtual_Client_Windows_7-KVM
or other application using the libvirt API.
-->

<domain type='kvm'>
  <name>Virtual_Client_Windows_7-KVM</name>
  <uuid>27fa297d-4b59-4398-8be7-e804c5e97fc1</uuid>
  <description>This VM image was created from the Win7 20130226 template</description>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <vcpu placement='static'>2</vcpu>
  <os>
    <type arch='x86_64' machine='rhel6.4.0'>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
    <smbios mode='host'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <cpu mode='custom' match='exact'>
    <model fallback='allow'>SandyBridge</model>
    <vendor>Intel</vendor>
    <feature policy='require' name='erms'/>
    <feature policy='require' name='smep'/>
    <feature policy='require' name='fsgsbase'/>
    <feature policy='require' name='rdrand'/>
    <feature policy='require' name='f16c'/>
    <feature policy='require' name='osxsave'/>
    <feature policy='require' name='pcid'/>
    <feature policy='require' name='pdcm'/>
    <feature policy='require' name='xtpr'/>
    <feature policy='require' name='tm2'/>
    <feature policy='require' name='est'/>
    <feature policy='require' name='smx'/>
    <feature policy='require' name='vmx'/>
    <feature policy='require' name='ds_cpl'/>
    <feature policy='require' name='monitor'/>
    <feature policy='require' name='dtes64'/>
    <feature policy='require' name='pbe'/>
    <feature policy='require' name='tm'/>
    <feature policy='require' name='ht'/>
    <feature policy='require' name='ss'/>
    <feature policy='require' name='acpi'/>
    <feature policy='require' name='ds'/>
    <feature policy='require' name='vme'/>
  </cpu>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/libexec/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/var/lib/libvirt/images/Virtual_Client_Windows_7-KVM.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </disk>
    <disk type='block' device='cdrom'>
      <driver name='qemu' type='qcow2'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' target='0' unit='0'/>
    </disk>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x2'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <interface type='direct'>
      <mac address='52:54:00:2d:10:df'/>
      <source dev='eth0' mode='bridge'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <interface type='network'>
      <mac address='52:54:00:c6:7d:ab'/>
      <source network='isolated'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </interface>
    <interface type='network'>
      <mac address='52:54:00:73:a3:73'/>
      <source network='default'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='pty'>
      <target type='virtio' name='arbitrary.virtio.serial.port.name'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='2'/>
    </channel>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <graphics type='spice' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
    </graphics>
    <sound model='ich6'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </sound>
    <video>
      <model type='qxl' ram='65536' vram='65536' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <vendor id='0x0a5c'/>
        <product id='0x21e6'/>
      </source>
    </hostdev>
    <redirdev bus='usb' type='spicevmc'>
      <address type='usb' bus='0' port='3'/>
    </redirdev>
    <redirdev bus='usb' type='spicevmc'>
      <address type='usb' bus='0' port='4'/>
    </redirdev>
    <redirdev bus='usb' type='spicevmc'>
      <address type='usb' bus='0' port='5'/>
    </redirdev>
    <redirdev bus='usb' type='spicevmc'>
      <address type='usb' bus='0' port='6'/>
    </redirdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
    </memballoon>
  </devices>
</domain>

I Found:

<emulator>/usr/libexec/qemu-kvm</emulator>

but I do not found qemu-kvm in /usr/bin/qemu to reemplace. What command I must remplace?

Thanks in advance!

Last edited by elrengo (2014-12-07 15:07:50)

Offline

#4 2014-12-07 16:02:27

Spider.007
Member
Registered: 2004-06-20
Posts: 1,175

Re: [SOLVED] - Can not start a virtual machine kvm

Read the entire thread rebootl suggested. You could create a symlink as suggested in here or update your xml to point to the correct architecture (probably /usr/bin/qemu-system-x86_64)

Offline

#5 2014-12-07 17:04:34

elrengo
Member
From: Argentina
Registered: 2014-11-06
Posts: 56

Re: [SOLVED] - Can not start a virtual machine kvm

I create a new VM to see what is the emulator in XML

Original XML

<emulator>/usr/libexec/qemu-kvm</emulator>

New XML

<emulator>/usr/sbin/qemu-kvm</emulator>

I copy the permision files create with new VM:

[~/VirtualMachines/kvm/libvirt/qemu]
[elrengo@xpsl421x]$ pwd
/home/elrengo/VirtualMachines/kvm/libvirt/qemu
[~/VirtualMachines/kvm/libvirt/qemu]
[elrengo@xpsl421x]$ ls -l
total 12K
-rw------- 1 root root 6,0K dic  7 13:57 Virtual_Client_Windows_7-KVM.xml
-rw------- 1 root root 3,4K dic  7 13:37 vm-Win8.xml
[~/VirtualMachines/kvm/libvirt/images]
[elrengo@xpsl421x]$ pwd
/home/elrengo/VirtualMachines/kvm/libvirt/images
[~/VirtualMachines/kvm/libvirt/images]
[elrengo@xpsl421x]$ ls -l
total 62G
-rw-r--r-- 1 nobody kvm 62G feb 10  2014 Virtual_Client_Windows_7-KVM.qcow2
-rw-r--r-- 1 nobody kvm  10 dic  6  2013 Virtual_Client_Windows_7-KVM.qcow2.type
-rw-r--r-- 1 nobody kvm 61G dic  7 13:37 vm1.qcow2

After remplace the error:

Error starting domain: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1358, in startup
    self._backend.create()
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 999, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory

I run:

ln -s /usr/bin/qemu-{system-x86_64,kvm}
ln -s /usr/bin/qemu-{system-x86_64,kvm}
sudo ln -s /usr/bin/qemu-{system-x86_64,kvm}

but error continue.

Last edited by elrengo (2014-12-07 17:08:36)

Offline

#6 2014-12-07 17:19:49

elrengo
Member
From: Argentina
Registered: 2014-11-06
Posts: 56

Re: [SOLVED] - Can not start a virtual machine kvm

I reboot the laptop. Adjust some hardware in virt-manager: network config etc.

That is the new error:

Error starting domain: internal error: process exited while connecting to monitor: qemu-kvm: -machine rhel6.4.0,accel=kvm,usb=off: Unsupported machine type
Use -machine help to list supported machines!

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1358, in startup
    self._backend.create()
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 999, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor: qemu-kvm: -machine rhel6.4.0,accel=kvm,usb=off: Unsupported machine type
Use -machine help to list supported machines!
[~]
[elrengo@xpsl421x]$ qemu-kvm -machine
qemu-kvm: -machine: requires an argument
[elrengo@xpsl421x]$ man qemu-kvm
No manual entry for qemu-kvm

Last edited by elrengo (2014-12-07 17:21:52)

Offline

#7 2014-12-07 20:14:39

Spider.007
Member
Registered: 2004-06-20
Posts: 1,175

Re: [SOLVED] - Can not start a virtual machine kvm

Well, the error is pretty clear; you specify machine 'rhel6.4.0' and that is unknown. Choose a different machine-type to fix that. Also, the only reason you are getting this far is because of the symlink...

Offline

#8 2014-12-08 02:15:53

elrengo
Member
From: Argentina
Registered: 2014-11-06
Posts: 56

Re: [SOLVED] - Can not start a virtual machine kvm

Hi! Thanks for you reply! Where I need to change the rhel6.4.0? I do not found where I can read about machine. If symlink does not work why the new VM works fine with simlink? I have not free space in / or /var filesystem to have the vm. Is better a simlink to directory instead off file simlink?

After try a lot of times:

[~/VirtualMachines/kvm/libvirt/qemu]
[elrengo@xpsl421x]$ qemu-kvm -machine help
Supported machines are:
pc-0.13              Standard PC (i440FX + PIIX, 1996)
pc-i440fx-2.0        Standard PC (i440FX + PIIX, 1996)
pc-1.0               Standard PC (i440FX + PIIX, 1996)
pc                   Standard PC (i440FX + PIIX, 1996) (alias of pc-i440fx-2.1)
pc-i440fx-2.1        Standard PC (i440FX + PIIX, 1996) (default)
pc-q35-1.7           Standard PC (Q35 + ICH9, 2009)
pc-1.1               Standard PC (i440FX + PIIX, 1996)
pc-0.14              Standard PC (i440FX + PIIX, 1996)
pc-q35-2.0           Standard PC (Q35 + ICH9, 2009)
pc-i440fx-1.4        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-1.5        Standard PC (i440FX + PIIX, 1996)
pc-0.15              Standard PC (i440FX + PIIX, 1996)
pc-q35-1.4           Standard PC (Q35 + ICH9, 2009)
isapc                ISA-only PC
pc-1.2               Standard PC (i440FX + PIIX, 1996)
pc-0.10              Standard PC (i440FX + PIIX, 1996)
pc-0.11              Standard PC (i440FX + PIIX, 1996)
q35                  Standard PC (Q35 + ICH9, 2009) (alias of pc-q35-2.1)
pc-q35-2.1           Standard PC (Q35 + ICH9, 2009)
pc-i440fx-1.7        Standard PC (i440FX + PIIX, 1996)
pc-i440fx-1.6        Standard PC (i440FX + PIIX, 1996)
none                 empty machine
pc-q35-1.5           Standard PC (Q35 + ICH9, 2009)
pc-q35-1.6           Standard PC (Q35 + ICH9, 2009)
pc-0.12              Standard PC (i440FX + PIIX, 1996)
pc-1.3               Standard PC (i440FX + PIIX, 1996)

What is the better machine? The most of machine supported are old machines.

Last edited by elrengo (2014-12-08 02:35:26)

Offline

#9 2014-12-08 02:49:36

elrengo
Member
From: Argentina
Registered: 2014-11-06
Posts: 56

Re: [SOLVED] - Can not start a virtual machine kvm

I edite the XML remplaced rhel6.4 but in somewhere it persist:

Error starting domain: internal error: process exited while connecting to monitor: qemu-kvm: -machine rhel6.4.0,accel=kvm,usb=off: Unsupported machine type
Use -machine help to list supported machines!

Error starting domain: internal error: process exited while connecting to monitor: qemu-kvm: -machine rhel6.4.0,accel=kvm,usb=off: Unsupported machine type
Use -machine help to list supported machines!


Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1358, in startup
    self._backend.create()
  File "/usr/lib/python2.7/site-packages/libvirt.py", line 999, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor:/b] qemu-kvm: -machine rhel6.4.0,accel=kvm,usb=off: Unsupported machine type
Use -machine help to list supported machines!

The new XML

<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE 
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
  virsh edit Virtual_Client_Windows_7-KVM
or other application using the libvirt API.
-->

<domain type='kvm'>
  <name>Virtual_Client_Windows_7-KVM</name>
  <uuid>27fa297d-4b59-4398-8be7-e804c5e97fc1</uuid>
  <description>This VM image was created from the Win7 20130226 template</description>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <vcpu placement='static'>2</vcpu>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.1'>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
    <smbios mode='host'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <cpu mode='custom' match='exact'>
    <model fallback='allow'>SandyBridge</model>
    <vendor>Intel</vendor>
    <feature policy='require' name='erms'/>
    <feature policy='require' name='smep'/>
    <feature policy='require' name='fsgsbase'/>
    <feature policy='require' name='rdrand'/>
    <feature policy='require' name='f16c'/>
    <feature policy='require' name='osxsave'/>
    <feature policy='require' name='pcid'/>
    <feature policy='require' name='pdcm'/>
    <feature policy='require' name='xtpr'/>
    <feature policy='require' name='tm2'/>
    <feature policy='require' name='est'/>
    <feature policy='require' name='smx'/>
    <feature policy='require' name='vmx'/>
    <feature policy='require' name='ds_cpl'/>
    <feature policy='require' name='monitor'/>
    <feature policy='require' name='dtes64'/>
    <feature policy='require' name='pbe'/>
    <feature policy='require' name='tm'/>
    <feature policy='require' name='ht'/>
    <feature policy='require' name='ss'/>
    <feature policy='require' name='acpi'/>
    <feature policy='require' name='ds'/>
    <feature policy='require' name='vme'/>
  </cpu>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/sbin/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/var/lib/libvirt/images/Virtual_Client_Windows_7-KVM.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </disk>
    <disk type='block' device='cdrom'>
      <driver name='qemu' type='qcow2'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' target='0' unit='0'/>
    </disk>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x2'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <interface type='direct'>
      <mac address='52:54:00:2d:10:df'/>
      <source dev='eth0' mode='bridge'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

I restart the machine after editing because the error persist.

Offline

#10 2014-12-08 03:16:03

elrengo
Member
From: Argentina
Registered: 2014-11-06
Posts: 56

Re: [SOLVED] - Can not start a virtual machine kvm

I do the machinet works. I resolve config in XML but for a one reason the simlink was broken. The I create a new simlink edit the XML and the Machine boot. Thanks for yours time!

Offline

Pages: 1

Board footer

Powered by FluxBB