[one-users] Help with datastore feature
Robert Schweikert
rjschwei at suse.com
Fri May 4 15:06:24 PDT 2012
Hi,
I am running into some issues with my test setup to verify that the
packages I am building in OBS work, at least on a basic level.
Switching to 3.4.1 I am back to getting node registration (this happens
automatically in my test setup and the changes to onehost create tripped
me up at first ;) ). Now I am stuck with getting a guest image to run.
I have a test configuration as follows:
-> cat startTestVM
#!/bin/bash
export ONE_AUTH=/var/lib/one/.one/one_auth
/usr/bin/oneimage create testVM.one
# System needs time to copy the image
sleep 10
/usr/bin/onevm create testVM.vmd
This script basically is setup to just launch a VM, once the VM is
running I am happy and call it a day and push my packages from :Testing
into the main project (Virtualization:Cloud:OpenNebula) on OBS.
With the changes to the way storage is done in 3.4 I changed the script
to have a "-d 1" at the end "oneimage create" call, i.e. the whole think
looks like this:
-> cat startTestVM
#!/bin/bash
export ONE_AUTH=/var/lib/one/.one/one_auth
/usr/bin/oneimage create testVM.one -d 1
# System needs time to copy the image
sleep 10
/usr/bin/onevm create testVM.vmd
This appears to be OK but the guest is failing to start. I suspect I am
missing something in the configuration along the way.
-> cat testVM.one
NAME = "openSUSE test image"
PATH = "/home/ctester/suse-12.1-SUSENebula-guest.x86_64-1.0.0.qcow2"
PUBLIC = YES
DESCRIPTION = "A test image to test the basic functionality of the
openSUSE based OpenNebula setup"
-> cat cloud_head/root/home/ctester/testVM.vmd
NAME = suse-test
MEMORY = 512
CPU = 1
OS = [ ARCH = x86_64,
BOOT = hd,
ROOT = sda1 ]
DISK = [ IMAGE_ID = 0,
DRIVER = qcow2 ]
NIC = [ MAC = "00:16:3e:7e:18:26",
BRIDGE = br0 ]
GRAPHICS = [ TYPE = "vnc",
LISTEN = "0.0.0.0",
PORT = "5905" ]
The cloud node is KVM based and I can run the guest image using qemu-kvm.
The intention for this test setup is to simply store the image on the
disk that is local to the head node machine.
Running onevm list repeatedly shows the status of the guest changing
from boot to fail.
Help is apprecaited.
Thanks,
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center LINUX
Tech Lead
rjschwei at suse.com
rschweik at ca.ibm.com
781-464-8147
More information about the Users
mailing list