On Thu, Oct 11, 2012 at 01:17:37PM +0200, Olaf Hering wrote:
 On Thu, Oct 11, Daniel P. Berrange wrote:
 
 > On Thu, Oct 11, 2012 at 01:10:16PM +0200, Olaf Hering wrote:
 > > However, adding 'olaf' into group 'kvm' does not help to run
 > > libguestfs-test-tool, its still a 'qemu' guest.
 > Did you login + logout and restart libvirtd after adding yourself
 > to the kvm group ?
 
 Yes, id shows the new group.
  
 > This is peculiar - it doesn't show any QEMU guests at all.
 > What does 'virsh -c qemu:///system capabilities' report ?
 
 I think a user has not enough permissions per default.
 
 root@stein-schneider:~ # virsh -c qemu:///system capabilities
 <capabilities>
 
   <host>
     <uuid>1269ce01-fe8f-11d5-90fd-00265523ecea</uuid>
     <cpu>
       <arch>x86_64</arch>
       <model>Nehalem</model>
       <vendor>Intel</vendor>
       <topology sockets='1' cores='4' threads='2'/>
       <feature name='rdtscp'/>
       <feature name='dca'/>
       <feature name='pdcm'/>
       <feature name='xtpr'/>
       <feature name='tm2'/>
       <feature name='est'/>
       <feature name='vmx'/>
       <feature name='ds_cpl'/>
       <feature name='monitor'/>
       <feature name='dtes64'/>
       <feature name='pbe'/>
       <feature name='tm'/>
       <feature name='ht'/>
       <feature name='ss'/>
       <feature name='acpi'/>
       <feature name='ds'/>
       <feature name='vme'/>
     </cpu>
     <power_management>
       <suspend_disk/>
     </power_management>
     <migration_features>
       <live/>
       <uri_transports>
         <uri_transport>tcp</uri_transport>
       </uri_transports>
     </migration_features>
     <topology>
       <cells num='1'>
         <cell id='0'>
           <cpus num='8'>
             <cpu id='0'/>
             <cpu id='1'/>
             <cpu id='2'/>
             <cpu id='3'/>
             <cpu id='4'/>
             <cpu id='5'/>
             <cpu id='6'/>
             <cpu id='7'/>
           </cpus>
         </cell>
       </cells>
     </topology>
     <secmodel>
       <model>none</model>
       <doi>0</doi>
     </secmodel>
     <secmodel>
       <model>dac</model>
       <doi>0</doi>
     </secmodel>
   </host>
 
   <guest>
     <os_type>hvm</os_type>
     <arch name='i686'>
       <wordsize>32</wordsize>
       <emulator>/usr/bin/qemu-kvm</emulator>
       <machine>pc-1.1</machine>
       <machine canonical='pc-1.1'>pc</machine>
       <machine>pc-1.0</machine>
       <machine>pc-0.15</machine>
       <machine>pc-0.14</machine>
       <machine>pc-0.13</machine>
       <machine>pc-0.12</machine>
       <machine>pc-0.11</machine>
       <machine>pc-0.10</machine>
       <machine>isapc</machine>
       <domain type='qemu'>
       </domain>
       <domain type='kvm'>
         <emulator>/usr/bin/qemu-kvm</emulator>
       </domain>
     </arch>
     <features>
       <cpuselection/>
       <deviceboot/>
       <pae/>
       <nonpae/>
       <acpi default='on' toggle='yes'/>
       <apic default='on' toggle='no'/>
     </features>
   </guest>
 
   <guest>
     <os_type>hvm</os_type>
     <arch name='x86_64'>
       <wordsize>64</wordsize>
       <emulator>/usr/bin/qemu-kvm</emulator>
       <machine>pc-1.1</machine>
       <machine canonical='pc-1.1'>pc</machine>
       <machine>pc-1.0</machine>
       <machine>pc-0.15</machine>
       <machine>pc-0.14</machine>
       <machine>pc-0.13</machine>
       <machine>pc-0.12</machine>
       <machine>pc-0.11</machine>
       <machine>pc-0.10</machine>
       <machine>isapc</machine>
       <domain type='qemu'>
       </domain>
       <domain type='kvm'>
         <emulator>/usr/bin/qemu-kvm</emulator>
       </domain>
     </arch>
     <features>
       <cpuselection/>
       <deviceboot/>
       <acpi default='on' toggle='yes'/>
       <apic default='on' toggle='no'/>
     </features>
   </guest>
 
 </capabilities> 
Ah interesting. So this machine only has the qemu-kvm binary installed,
none of the other non-KVM binaries.
What is the version of libvirt that you have ? Until fairly recently
libvirt would not detect the fact that /usr/bin/qemu-kvm was able to
support non-KVM modes, which could be causing some of the pain here.
Daniel
-- 
|: 
http://berrange.com      -o-    
http://www.flickr.com/photos/dberrange/ :|
|: 
http://libvirt.org              -o-             
http://virt-manager.org :|
|: 
http://autobuild.org       -o-         
http://search.cpan.org/~danberr/ :|
|: 
http://entangle-photo.org       -o-       
http://live.gnome.org/gtk-vnc :|