Yes, that should be enough for both approached... I am not sure why you need step 1, but I guess it may be needed in some scenarios. If you go for the DB don't forget to backup and stop oned first.
Cheers On Wed, Nov 6, 2013 at 1:59 PM, Karsten Nielsen <[email protected]> wrote: > OK, > > If I am to avoid that. > > Then I see my steps as: > 1. Create new images from the running vm and make them permanent. > 2. Create a new template that has the right bus and target prefixes set > 3. Create a vm from that template > > Am I mission something ? > > > If I change the DB then > <DEV_PREFIX><![CDATA[hd]]></DEV_PREFIX><DISK_ID><![CDATA[ > 0]]></DISK_ID><IMAGE><![CDATA[root-20130726]]></IMAGE>< > IMAGE_ID><![CDATA[49]]></IMAGE_ID><PERSISTENT><![CDATA[ > YES]]></PERSISTENT><READONLY><![CDATA[NO]]></READONLY><SAVE> > <![CDATA[YES]]></SAVE><SOURCE><![CDATA[sata/one-49]]></ > SOURCE><TARGET><![CDATA[hda]]></TARGET><TM_MAD><![CDATA[ > ceph]]></TM_MAD><TYPE><![CDATA[RBD]]></TYPE></DISK>< > DISK><CLONE><![CDATA[NO]]></CLONE><CLUSTER_ID><![CDATA[100]]></CLUSTER_ID> > > Should be changed to > <DEV_PREFIX><![CDATA[vd]]></DEV_PREFIX><DISK_ID><![CDATA[ > 0]]></DISK_ID><IMAGE><![CDATA[root-20130726]]></IMAGE>< > IMAGE_ID><![CDATA[49]]></IMAGE_ID><PERSISTENT><![CDATA[ > YES]]></PERSISTENT><READONLY><![CDATA[NO]]></READONLY><SAVE> > <![CDATA[YES]]></SAVE><SOURCE><![CDATA[sata/one-49]]></ > SOURCE><TARGET><![CDATA[vda]]></TARGET><TM_MAD><![CDATA[ > ceph]]></TM_MAD><TYPE><![CDATA[RBD]]></TYPE></DISK>< > DISK><CLONE><![CDATA[NO]]></CLONE><CLUSTER_ID><![CDATA[100]]></CLUSTER_ID> > > > - Karsten > > On 06/11/13 13:13, Ruben S. Montero wrote: > >> I'm afraid you can't. The template used to instantiate the VM is used to >> generate a detailed VM description (that includes the bus prefix and >> target's). You'd need to modify that directly in the DB, but I'd try to >> avoid that. >> >> Cheers >> >> >> On Wed, Nov 6, 2013 at 1:06 PM, Karsten Nielsen <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi, >> >> I have a vm running from a template that has set the wrong disk >> prefix therefore the vm uses scsi driver for the disk and not the >> virtio driver. >> >> Can I change that just by stopping the vm edit the template that it >> was created from and start it again ? >> >> I am running opennebula 4.2 with kvm hosts >> >> - Karsten >> _________________________________________________ >> Users mailing list >> [email protected] <mailto:[email protected]> >> http://lists.opennebula.org/__listinfo.cgi/users-opennebula.__org >> <http://lists.opennebula.org/listinfo.cgi/users-opennebula.org> >> >> >> >> >> -- >> -- >> Ruben S. Montero, PhD >> Project co-Lead and Chief Architect >> OpenNebula - Flexible Enterprise Cloud Made Simple >> www.OpenNebula.org <http://www.OpenNebula.org> | >> [email protected] <mailto:[email protected]> | @OpenNebula >> > -- -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | [email protected] | @OpenNebula
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
