Those VMs should be able to boot with on a Linux installation with a KVM hypervisor with no issues, provided that you have the images (or can grab them from Glance) and can create a .xml definition file for each. For the xml definitions, you can cheat a little by creating a blank new KVM VM using tools such as virt-manager and copy the resulting .xml configs or use virsh to dump an existing one and editing details in them to point where your VMs root fs and other resources are located ... See more related information here: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html On Wed, Apr 23, 2014 at 5:04 PM, Michael Monette <mmonette at 2keys.ca> wrote: > Hey all > > I know I will get the usual "don't use dev stack in prod" lecture. > Hopefully we can skip that part. I know now. > > We had setup openstack just as a cool project using dev stack. We had to > move offices and now realized there is some good work in some of the VMS. > > I'm locked out of horizon right now and I don't really care about making > openstack work. I just need to bring up the vms to pul off some data. > (postgres database). Then I can get rid of all the vms > > Is there a way to launch these vms without openstack dashboard? Could I > use virt manager to start these bad boys? > > I have full root on the system. I'm tired of fighting with horizon now I > just want the vms. Hopefully something can be done. > > Yes I know dev stack shouldn't be run in prod :p > > Mike > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140423/96e9438a/attachment.html>