[Engine-devel] qemu machine type / datacenter machine version

Miki Kenneth mkenneth at redhat.com
Sun Apr 8 06:50:20 UTC 2012



----- Original Message -----
> From: "Andrew Cathrow" <acathrow at redhat.com>
> To: engine-devel at ovirt.org, "Ryan Harper" <ryanh at us.ibm.com>
> Sent: Friday, April 6, 2012 12:50:36 PM
> Subject: Re: [Engine-devel] qemu machine type / datacenter machine version
> 
> It is only configured in the database today.
> A good short term solution would be exposing this in the
> engine-config tool to save users having to hack the database, and
> potentially set this during setup.
> But long term we need to incorporate the notion of per VM config
> versions, right now we take the config version from the cluster,
> which isn't the best approach. We need to merge the two concepts -
> host/cluster capabilities and VM config version.
and combined that with the "deployment profile" and "configuration profile" per VM
(as was mentioned at Foreman/Ovirt presentation)

> 
> 
> Itamar Heim <iheim at redhat.com> wrote:
> 
> On 04/05/2012 06:27 PM, Ryan Harper wrote:
> > I was playing around with ovirt-engine datacenter definitions and I
> > seems that the capatibility version in the gui controls the qemu
> > machine
> > type specified (3.0 ->  pc-0.14).  I was wondering where that's
> > configured setup.
> >
> > I grepped through my deployed system and saw a hit here:
> >
> > [root at f16-engine ovirt-engine]# rpm -qf /usr/share/ovirt-engine
> > ovirt-engine-3.0.0_0001-1.2.fc16.x86_64
> > [root at f16-engine ovirt-engine]# grep -nri "pc-0.14" *
> > db-backups/tmprN1EDt.sql:12119:INSERT INTO vdc_options (option_id,
> > option_name, option_value, version) VALUES (236,
> > 'EmulatedMachine', 'pc-0.14', '3.0');
> > db-backups/tmpj4XRCI.sql:12138:INSERT INTO vdc_options (option_id,
> > option_name, option_value, version) VALUES (236,
> > 'EmulatedMachine', 'pc-0.14', '3.0');
> > dbscripts/upgrade/03_00_0530_update_EmulatedMachine_config_to_pc.sql:2:select
> > fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0');
> > dbscripts/create_db.sh.log:7571:select
> > fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0');
> > dbscripts/create_db.sh.log:25529:select
> > fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0');
> > dbscripts/create_db.sh.log:43487:select
> > fn_db_update_config_value('EmulatedMachine','pc-0.14','3.0');
> >
> > Is there any way to define different compatibiilty versions or edit
> > that?  If I've got a new end-point running qemu-kvm that doesn't
> > have pc-0.14 defined (Say RHEL6.x) the machines won't lauch when
> > you specific -M pc-0.14.
> >
> > Thoughts?
> >
> >
> 
> 
> 
> check this and reply to it:
> http://lists.ovirt.org/pipermail/users/2012-March/001439.html
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
> 



More information about the Devel mailing list