Dear all, it seems like the solution would be to swich to another driver and to use qemu? In such a case,is it necessary to replace KVM with Xen or anything else?
Could you please recommend me standard way of creating virtual machines in CentOS? I was following CentOS 6 documentation and KVM with Qemu was still included.
Seems like I have to use Xen,but I abandoned Xen due to the reason it was necessary to install kernel 3.10 but suprisingly support for Intel VX virtualization dissappeared in 3.10 (vmx flag) only some hypervisor was present,but I need to run WindowsXP.Is there any way to get back this feature back to 3.10?
I am a newbie in virtualization.
On Jun 23, 2015 3:50 PM, "Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:
On Tue, Jun 23, 2015 at 03:41:45PM +0200, Michal Privoznik wrote:
> On 23.06.2015 14:16, Ivo Hora wrote:
> > Dear Sir,
> >
> > I am facing the same problem you were discussing here:
> > https://www.redhat.com/archives/libvirt-users/2015-January/msg00070.html
> >
> > I am getting this error:
> > Starting install...
> > ERROR internal error: unable to execute QEMU command 'qom-list': The
> > command qom-list has not been found
> > Domain installation does not appear to have been successful.
> > If it was, you can restart your domain by running:
> > virsh --connect qemu:///system start myguest
> > otherwise, please restart your installation.
> > [root@server-topcon horai]#
> >
> > my virtual machine creation script is:
> > #OS="--os-variant=winxp --disk
> > path=/var/lib/libvirt/mages/Windows.iso,device=cdrom"
> > OS="--os-variant=winxp --disk
> > path=/var/lib/libvirt/images/virtio-win-0.1.96.iso"
> > Net="--network model=virtio,bridge=virbr0"
> > Disk="--disk
> > /var/lib/libvirt/images/Name.qcow2,sparse=false,bus=virtio,size=8"
> > Src=""> > >
> > #Gr="--graphics none"
> > Gr="--graphics vnc"
> > Cpu="--vcpus=1"
> > Ram="--ram=768"
> > Name="myguest"
> > virt-install $OS $Net $Disk $Src $Gr $Cpu $Ram --name=$Name
> >
> >
> > I would kindly like to ask you whether you found a solution for this
> > problem or whether you could help me fixing it.
>
> This is likely a result of commit d94b78177 (v1.2.0). I'm not sure if
> there are any attempts to make libvirt work with ancient qemus (pre 1.1
> - the qom_list command was added in b4b12c62). So the only option I can
> think of right now is to update qemu.
We should not be depending on qom-list existing unless the feature being
used only exists in a QEMU which has qom-list. In general we expect to
be able to work with any historical QEMU, so if we've regressed in that
regard we must fix it.
Regards,
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 :|
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
