Ask Your Question
1

Non-Ubuntu Images from VirtualBox not running correctly

asked 2013-07-18 15:52:23 -0500

OldParrothead gravatar image

I have several VMDKs that I brought over from VirtualBox. They all run fine on VirtualBox. They are set up to run DHCP from eth1 and pulls everything just fine from VBox. I shut down the images on VBox, import the .VMDK files into OpenStack using glance via command line, or from the GUI, and the images load without errors. All images are set up with Bridged adapters.

To start, using a Centos image... I bring it up, no networking. Removed the HWADDR from the ifcfg-eth1 file, and deleted the 70-persistent-net.rules file. Rebooted and same thing. I checked my Vbox image and it is configured to have a Bridged Adapter, same as my 30-40 Ubuntu images which work with no issues.

I am running Quantum/Openvswitch on Grizzly.

This has to be something simple and stupid, so someone must've solved this already.

Also, I am having trouble with Windows 2012. That image just stays in the spawning mode forever.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
1

answered 2013-07-22 16:10:58 -0500

medhat gravatar image

the only issue that we had with centos images was it couldn't communicate meta data service , so we could not access the instance with ssh keys if that your issue to try to disable apipa by doing

vi /etc/sysconfig/network

Append the following directive: NOZEROCONF=yes

re upload your image it should communicate with meta service as expected and get instance information hostname and ssh keys

edit flag offensive delete link more

Comments

Thanks. This worked.

OldParrothead gravatar imageOldParrothead ( 2013-07-23 07:20:43 -0500 )edit
0

answered 2013-07-29 08:59:55 -0500

OldParrothead gravatar image

FYI.... Windows 2012 and Windows 2008 were licensing issues (sorry if I forgot that Microsoft is such a pain about that). They took close an hour to start up, then went into a state where all they would do is basically display a "fix me" screen. Then, it couldn't fix itself, so I was stuck in an endless loop. Somebody else I know had had this before, and fixed it by building everything on Openstack.

Centos issues were fixed with answers above.

Haven't cleared up Solaris, yet, but hear that will be a field day. None of the suggested solution on the net have worked for this yet.

Thanks, all.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-07-18 15:52:23 -0500

Seen: 240 times

Last updated: Jul 29 '13