7:55 a.m.
Hi all,
I upgraded qemu-kvm and libvirt to the new versions
qemu-kvm at : 1.0
libvirt at : git version 0.9.10
I lost the original machines but the xml files were are all present (it
is not showing up in virsh list --all)
But when I import an xml I get an error: Attached is some information
which might be helpful
Can someone help please ?
If this is a compatibility issue please can someone tell me which is the
latest version of qemu-kvm and libvirt combination which will work ?
I cannot use qemu plain since it does not yet support boot from scsi
thanks
-----------------------------------------------
$ sudo virsh list --all
Id Name State
----------------------------------------------------
$ lsmod | grep kvm
kvm_intel 112920 0
kvm 280656 1 kvm_intel
$ /usr/local/sbin/libvirtd --version
/usr/local/sbin/libvirtd (libvirt) 0.9.10
$ ./qemu-system-x86_64 --version
QEMU emulator version 1.0-bcv (qemu-kvm-1.0), Copyright (c) 2003-2008
Fabrice Bellard
$ sudo virsh define ./debian.xml
error: Failed to define domain from ./debian.xml
error: unknown OS type hvm
$ cat debian.xml
<domain type='kvm'>
<name>debian</name>
<uuid>0aab8869-ff87-14ce-a00b-944cdca7acf7</uuid>
<memory>524288</memory>
<currentMemory>524288</currentMemory>
<vcpu cpuset='6-7'>2</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='6'/>
<vcpupin vcpu='1' cpuset='7'/>
</cputune>
<os>
<type arch='x86_64' machine='pc-0.14'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<cpu match='exact'>
<model>core2duo</model>
<vendor>Intel</vendor>
<topology sockets='1' cores='2' threads='1'/>
<feature policy='disable' name='lahf_lm'/>
</cpu>
<clock offset='localtime'>
<timer name='hpet' tickpolicy='catchup'/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/local/bin/kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/VIRT/disks/DEBIAN'/>
<target dev='sda' bus='scsi'/>
<address type='drive' controller='0' bus='0'
unit='0'/>
</disk>
<disk type='block' device='cdrom'>
<driver name='qemu' type='raw'/>
<target dev='hdc' bus='ide'/>
<readonly/>
<address type='drive' controller='0' bus='1'
unit='0'/>
</disk>
<controller type='scsi' index='0'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x04'
function='0x0'/>
</controller>
<controller type='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x01'
function='0x1'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:71:62:f3'/>
<source bridge='virt'/>
<model type='e1000'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x03'
function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes'
keymap='en-gb'/>
<sound model='ich6'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x06'
function='0x0'/>
</sound>
<video>
<model type='cirrus' vram='9216' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x02'
function='0x0'/>
</video>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x05'
function='0x0'/>
</memballoon>
</devices>
</domain>
--
Bhasker C V
8:36 a.m.
On 02/25/2012 06:55 AM, Bhasker C V wrote:
Hi all,
I upgraded qemu-kvm and libvirt to the new versions
qemu-kvm at : 1.0
libvirt at : git version 0.9.10
Which distro are you using? Did you self-build libvirt?
I lost the original machines but the xml files were are all present (it
is not showing up in virsh list --all)
This might be a case of virsh picking up a different default URI, based
on what support you built into libvirt.
Try 'virsh uri' to see what your default URI is. If it is not
'qemu:///system', then that explains your symptoms, and using 'virsh -c
qemu:///system list --all' will restore your listing abilities. You can
export VIRSH_DEFAULT_CONNECT_URI so you don't have to use virsh -c every
time.
But when I import an xml I get an error: Attached is some information
which might be helpful
Can someone help please ?
If this is a compatibility issue please can someone tell me which is the
latest version of qemu-kvm and libvirt combination which will work ?
The versions you have listed should be compatible (there was an issue
where older libvirt didn't like the newer qemu 1.0 versioning scheme,
but that has been fixed).
$ /usr/local/sbin/libvirtd --version
/usr/local/sbin/libvirtd (libvirt) 0.9.10
$ ./qemu-system-x86_64 --version
That's a different executable...
QEMU emulator version 1.0-bcv (qemu-kvm-1.0), Copyright (c)
2003-2008
Fabrice Bellard
$ sudo virsh define ./debian.xml
error: Failed to define domain from ./debian.xml
error: unknown OS type hvm
$ cat debian.xml
<domain type='kvm'>
...
<devices>
<emulator>/usr/local/bin/kvm</emulator>
...than what you are testing here. It may be that you are telling
libvirt to use the wrong binary, and that might be the source of your
error message.
Also, you may want to check out the troubleshooting wiki page, to see if
anything there helps your situation (and if not, feel free to add a page
as we figure out what's happening for you):
http://wiki.libvirt.org/page/Troubleshooting
--
Eric Blake eblake(a)redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
9:57 a.m.
Hi Eric
Thanks for replying ...
On 25/02/12 14:36, Eric Blake wrote:
On 02/25/2012 06:55 AM, Bhasker C V wrote:
> Hi all,
>
> I upgraded qemu-kvm and libvirt to the new versions
> qemu-kvm at : 1.0
> libvirt at : git version 0.9.10
Which distro are you using? Did you self-build libvirt?
Debian squeeze
> I lost the original machines but the xml files were are all present (it
> is not showing up in virsh list --all)
This might be a case of virsh picking up a different default URI, based
on what support you built into libvirt.
Try 'virsh uri' to see what your default URI is. If it is not
'qemu:///system', then that explains your symptoms, and using 'virsh -c
qemu:///system list --all' will restore your listing abilities. You can
export VIRSH_DEFAULT_CONNECT_URI so you don't have to use virsh -c every
time.
I did try using differnt URIs but did not get this working. I could not
see any machines in --all option
$ type virsh
virsh is aliased to `virsh --connect qemu:///system'
$
> But when I import an xml I get an error: Attached is some information
> which might be helpful
> Can someone help please ?
>
> If this is a compatibility issue please can someone tell me which is the
> latest version of qemu-kvm and libvirt combination which will work ?
The versions you have listed should be compatible (there was an issue
where older libvirt didn't like the newer qemu 1.0 versioning scheme,
but that has been fixed).
I am still seeing issues. I just downloaded the git
version and the
qemu-kvm-1.0 but when compiled did not work
Did not work is in the sense as told above
The virsh capabilities does not show hvm in the list
> $ /usr/local/sbin/libvirtd --version
> /usr/local/sbin/libvirtd (libvirt) 0.9.10
>
> $ ./qemu-system-x86_64 --version
That's a different executable...
> QEMU emulator version 1.0-bcv (qemu-kvm-1.0), Copyright (c) 2003-2008
> Fabrice Bellard
>
> $ sudo virsh define ./debian.xml
> error: Failed to define domain from ./debian.xml
> error: unknown OS type hvm
>
> $ cat debian.xml
> <domain type='kvm'>
...
> <devices>
> <emulator>/usr/local/bin/kvm</emulator>
...than what you are testing here. It may be that you are telling
libvirt to use the wrong binary, and that might be the source of your
error message.
Also, you may want to check out the troubleshooting wiki page, to see if
anything there helps your situation (and if not, feel free to add a page
as we figure out what's happening for you):
http://wiki.libvirt.org/page/Troubleshooting
Hah I forgot to tell kvm is linked to qemu-system-x86_64
I just went back to libvirt 0.9.1 with qemu-kvm 0.14.1 and thingss are
back to normal ; atleast in working condition
The main reason I wanted to move to newer versions is that I wanted to
use USB 2.0 rather than forced to use USB1.0 in case of the versions
of qemu and libvirt i specified.
Since this is a production system I think I have to create a backup
system and try it out to see if I am able to get this working ...
--
Bhasker C V
8:49 a.m.
On Sat, Feb 25, 2012 at 13:55:08 +0000, Bhasker C V wrote:
Hi all,
I upgraded qemu-kvm and libvirt to the new versions
qemu-kvm at : 1.0
libvirt at : git version 0.9.10
I lost the original machines but the xml files were are all present (it
is not showing up in virsh list --all)
But when I import an xml I get an error: Attached is some information
which might be helpful
Can someone help please ?
If this is a compatibility issue please can someone tell me which is the
latest version of qemu-kvm and libvirt combination which will work ?
I cannot use qemu plain since it does not yet support boot from scsi
thanks
-----------------------------------------------
$ sudo virsh list --all
Id Name State
----------------------------------------------------
$ lsmod | grep kvm
kvm_intel 112920 0
kvm 280656 1 kvm_intel
$ /usr/local/sbin/libvirtd --version
/usr/local/sbin/libvirtd (libvirt) 0.9.10
$ ./qemu-system-x86_64 --version
QEMU emulator version 1.0-bcv (qemu-kvm-1.0), Copyright (c) 2003-2008
Fabrice Bellard
Hmm, I suspect "1.0-bcv" version is not in the form we expect it to be. The
"-bcv" suffix causes this binary to be detected as qemu only, i.e., not kvm
capable... Which is wrong, btw, we should be detecting kvm capability by
checking -enable-kvm or -disable-kvm options since even plain qemu can use
kvm.
Jirka
4680
days inactive
4684
days old
3 comments
3 participants
participants (3)
-
Bhasker C V -
Eric Blake -
Jiri Denemark