[one-users] infinite boot loop

[Jurgen Weber]

Some more on this. I reduced the template to the following:

CPU="2"
DISK=[
   DRIVER="qcow2",
   IMAGE="Debian 6.0.5",
   IMAGE_UNAME="rocket" ]
GRAPHICS=[
   LISTEN="172.20.1.100",
   TYPE="vnc" ]
MEMORY="4GB"
OS=[
   ARCH="x86_64" ]
RAW=[
   TYPE="kvm" ]

Same problem. I then grabbed the process/command and reduced it to the 
below:

/usr/bin/kvm /var/lib/one/datastores/0/40/disk.0 -vnc 172.20.1.100:41

it works great.

How can I get opennebula to drop all of its command? something outside 
of the default that it is using is breaking it for me.

Thanks

Jurgen
On 08/08/12 13:26, Jurgen Weber wrote:
> Hi
>
> I am struggling with a new OpenNebula install, I have only dealt with 
> VMWare previosuly and do not have much 'vm + cloud' experience, so it 
> has been a learning process over the last week to understand all of 
> the concepts and what not... That said, I have a problem with 
> OpenNebula + SunStone. My system so far:
>
> # uname -a
> Linux chaos 3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012 x86_64 
> GNU/Linux
>
> ii  opennebula 3.4.1-3+b1                           controller which 
> executes the OpenNebula cluster services
> ii  opennebula-common 3.4.1-3                              empty 
> package to create OpenNebula users and directories
> ii  opennebula-sunstone 3.4.1-3                              web 
> interface to which executes the OpenNebula cluster services
> ii  opennebula-tools 3.4.1-3 Command-line tools for OpenNebula Cloud
> ii  ruby-opennebula 3.4.1-3                              Ruby bindings 
> for OpenNebula Cloud API (OCA)
> ii  kvm 1:1.1.0+dfsg-3                       dummy transitional 
> package from kvm to qemu-kvm
> ii  qemu-kvm 1.1.0+dfsg-3                         Full virtualization 
> on x86 hardware
> ii  libvirt-bin 0.9.12-3                             programs for the 
> libvirt library
> ii  libvirt0 0.9.12-3                             library for 
> interfacing with different virtualization systems
> ii  python-libvirt 0.9.12-3                             libvirt Python 
> bindings
>
> System Template:
>
> CPU="2"
> DISK=[
>   BUS="ide",
>   DRIVER="qcow2",
>   IMAGE="Debian 6.0.5",
>   IMAGE_UNAME="rocket",
>   TARGET="hda",
>   TYPE="DISK" ]
> GRAPHICS=[
>   LISTEN="172.20.1.100",
>   TYPE="vnc" ]
> MEMORY="4GB"
> NAME="aether"
> NIC=[
>   NETWORK="eth1-vlan100",
>   NETWORK_UNAME="rocket" ]
> NIC=[
>   NETWORK="eth1-vlan200",
>   NETWORK_UNAME="rocket" ]
> OS=[
>   ARCH="x86_64",
>   BOOT="hd",
>   ROOT="hda1" ]
> RAW=[
>   TYPE="kvm" ]
> VCPU="2"
>
> ps axwwww of system:
> /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 4 -smp 
> 2,sockets=2,cores=1,threads=1 -name one-33 -uuid 
> 37c0f915-b756-78b3-912a-04cb3118c469 -nodefconfig -nodefaults -chardev 
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/one-33.monitor,server,nowait 
> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc 
> -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 
> -drive 
> file=/var/lib/one//datastores/0/33/disk.0,if=none,id=drive-ide0-0-0,format=qcow2 
> -device 
> ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 
> -netdev tap,fd=22,id=hostnet0 -device 
> rtl8139,netdev=hostnet0,id=net0,mac=02:00:ac:14:01:6a,bus=pci.0,addr=0x3 
> -netdev tap,fd=24,id=hostnet1 -device 
> rtl8139,netdev=hostnet1,id=net1,mac=02:00:ac:14:02:6a,bus=pci.0,addr=0x4 
> -vnc 172.20.1.100:33 -vga cirrus -device 
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
>
> So, I followed the instructions found at this link: 
> http://wiki.debian.org/OpenNebula/PreparingDebianVmImage and created 
> an image, I did not do the contexualization part, I just create the 
> disk image, booted off the CD and installed, restarted, it booted up 
> again. All is well.
>
> I then added these images into sunstone, and setup my template using 
> them.
>
> I am now trying to boot from this image, you will note the template 
> and processor info above.
>
> This machine, just goes into an infinite loop. It boots, it posts... I 
> see "GRUB Loading. Welcome to Grub!" and then it starts all over 
> again. After a while (10 minutes or so) it will stop and say "error: 
> out of memory.".
>
> I am really looking forward to getting this run, any ideas on how to 
> make the VM boot up?
>
> Thanks
>

-- 
Jurgen Weber

Systems Engineer
IT Infrastructure Team Leader

THE ICONIC | E jurgen.weber at theiconic.com.au | www.theiconic.com.au