[virt-tools-list] a qemu/kvm version problem
Anton Protopopov
aspsk at altlinux.org
Fri Oct 9 09:49:22 UTC 2009
2009/10/9 Mark McLoughlin <markmc at redhat.com>
> On Fri, 2009-10-09 at 13:14 +0400, Anton Protopopov wrote:
> > 2009/10/9 Mark McLoughlin <markmc at redhat.com>
> >
> > On Fri, 2009-10-09 at 12:45 +0400, Anton Protopopov wrote:
> > > 2009/10/9 Mark McLoughlin <markmc at redhat.com>
> > > Hi Anton,
> > >
> > >
> > > On Thu, 2009-10-08 at 17:58 +0400, Anton Protopopov
> > wrote:
> > > > Hi, all.
> > > >
> > > > When I trying to create a kvm machine using
> > virt-manager, I
> > > get the
> > > > following error message:
> > > >
> > > > Unable to complete install '<class
> > 'libvirt.libvirtError'>
> > > internal
> > > > error unable to start guest: Supported machines
> > are:
> > > > pc Standard PC (default)
> > > > isapc ISA-only PC
> > > >
> > > > The problem is that virt-manager uses "M=pc-0.11"
> > parameter
> > > in kvm
> > > > command line, while
> > > > # virsh -c qemu:///system capabilities
> > > > ...
> > > > <domain type='kvm'>
> > > > <emulator>/usr/bin/kvm</emulator>
> > > > <machine>pc</machine>
> > > > <machine>isapc</machine>
> > > > </domain>
> > > > ...
> > > > so it should be "M=pc" there.
> > > >
> > > > The similar problem was in libvirt recenlty, but
> > it was
> > > solved in
> > > > 0.7.1. See the following
> > > > discussion:
> > > >
> > >
> > http://www.mail-archive.com/libvir-list@redhat.com/msg16154.html
> > >
> > >
> > > Do you mean this still happens even with the fixed
> > version of
> > > libvirt?
> > > Exactly. I can create a machine using libvirt, but I can't
> > create a
> > > machine
> > > using virt-manager. My versions are:
> > > # rpm -q libvirt python-module-libvirt
> > python-module-virtinst
> > > virt-manager
> > > libvirt-0.7.1-alt2
> > > python-module-libvirt-0.7.1-alt2
> > > python-module-virtinst-0.500.0-alt1
> > > virt-manager-0.8.0-alt1
> >
> >
> > Could you post your ~/.virt-manager/virt-manager.log?
> > Reading ~/.virt-manager/virt-manager.log I understand what
> > is actually happens: The machine description is
> > ...<os>
> > <type arch='x86_64'>hvm</type>
> > ...
> > ...</os>
> > And libvirt dies on that (setting machine="pc-0.11").
> > If I manually add machine='pc' here, then all works fine.
> >
> > So is it a libvirt bug or virt-manager must write a "machine='smth'"
> > to description?
>
> Posting the full log might help ...
>
> Is there an <emulator> tag ? If there is and it's /usr/bin/kvm, then it
> sounds like a libvirt bug that it's picking pc-0.11
>
Yes, it is looking so. If I take a machine, created by libvirt that is
working fine and change
<os>
<type arch='x86_64' machine='pc'>hvm</type>
<boot dev='hd'/>
</os>
to
<os>
<type arch='x86_64'>hvm</type>
<boot dev='hd'/>
</os>
then, libvirt fails:
virsh # start DD
error: Failed to start domain DD
error: internal error unable to start guest: Supported machines are:
pc Standard PC (default)
isapc ISA-only PC
So, it is a libvirt bug, isn't it? Will you post it to libvirt list or
should I do it myself?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/virt-tools-list/attachments/20091009/a0f6eec0/attachment.htm>
More information about the virt-tools-list
mailing list