CSS Corp Open Source Services

[Eucalyptus Beginner’s Guide – UEC edition] Chapter 4 – Image Management

with 22 comments

Chapter 3
Web Interface
Chapter 5
Instance Management

Eucalyptus Machine Image(EMI)

A Eucalpyptus Machine Image(EMI) is a combination of a virtual disk image(s), kernel and ramdisk images as well as an xml file containing meta data about the image. These images reside on WS3 and used as templates for creating instances on UEC. Each Linux EMI is a combination of the following:

  • An XML file with a name like “karmic.img.manifest.xml” with information about one or more hard disk images, a kernel image and a ram disk image (id – emi-65440E7E)
  • An XML file with a name like “vmlinuz-2.6.28-11-server.manifest.xml” with information about the corresponding kernel image(id – eki-39FC1244)
  • An XML file with a name like “initrd.img-2.6.28-11-server.manifest.xml” with information about the corresponding ramdisk image(id – eri-71ED1322)

Each of these images has its own ID that can be used while running the instances. More on this in the chapter on “Managing Instances”

From the web interface of Eucalyptus, you can view a list of EMIs in the “Store” tab of the web UI. These are the EMIs listed from Canonical or partners. You can choose to download and install any of these images directly from Canonical’s site.

Since most enterprise/individual users of Eucalyptus have a need for bringing up instances based on custom images, image management plays a key role in Eucalyptus administration. Such images could be based on a preferred version/variant of a preferred OS distribution with a set of required applications pre-installed.

Bundling an EMI is a multi-step process involving the following:

  1. creating a virtual disk image
  2. installing the OS
  3. installing required applications
  4. making the OS ready to run under UEC
  5. registering the images with UEC
  6. testing the image etc.

Bundling process differs between Linux and Windows images and we will discuss the process in both cases in some detail below.

Bundling Linux Image

We will use Client1 for the purpose of working on creation of the image. Please note that we had installed KVM on Client1.

Creating a new disk Image

This will represent the main HDD of the virtual machine, so make sure to give it as much space as you will need. Since we are building a kvm image, we can use a qcow2 format for disk images. Qcow2 is an expandable image format, so it will only occupy as much storage space as is actually filled by the data within the image.

uecadmin@client1:~$ kvm-img create -f qcow2 image.img 5G

OS Installation

Download the iso file of the Linux distribution you want installed in the image. The example below refers to creating a Karmic 64-bit server image.

uecadmin@client1:~$ wget http://releases.ubuntu.com/karmic/ubuntu-9.10-server-amd64.iso

And start the installation process:

uecadmin@client1:~$ sudo kvm -m 256 -cdrom ubuntu-9.10-server-amd64.iso -drive file=image.img,if=scsi,index=0 -boot d \
-net nic -net user -nographic -vnc :0

If your installation process requires more than 256MB of RAM change the -m option, and if you need more processors available, you can use the ‘-c’ option.
The command above will boot a new KVM instance, with the disk image you’ve created as the primary HDD and the iso as the first bootable device. Also the ‘-nographic’ option will not display any graphical output. You can connect to the instance through VNC (use display number :0) and finish the installation.

For Ex: vncviewer A.B.C.D :0, where A.B.C.D is the IP address of Client1.

After finishing the installation, relaunch the VM by executing the following command.

uecadmin@client1:~$ sudo kvm -m 256 -drive file=image.img,if=scsi,index=0,boot=on -boot c \
-net nic -net user -nographic -vnc :0

At this point you can add all the packages you want to have installed, update the installation, add users and any settings that need to be present in your new UEC instances.

$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get install mediawiki

Integrating with Eucalyptus

An instance running under Eucalyptus needs to know what IP it has and also, it needs to have the public key of the user allowed to do a passwordless access through SSH. This is accomplished by using a restful interface provided by the cloud. The interface is available under this URL: http://169.254.169.254/latest/meta-data and accessible from within the Instance.

Eucalyptus node controller is set up to prevent automatic key injection if the system is in MANAGED or MANAGED-NOVLAN mode. Instead, it is assumed that the instance will use the above meta-data service to retrieve the public keys when running in these modes. You will need to facilitate this by installing curl and adding a script that will run on each boot.

Install curl on the VM.

$ sudo apt-get install curl

Now add the following lines to /etc/rc.local of the image.

depmod -a
modprobe acpiphp

# simple attempt to get the user ssh key using the meta-data service
# assuming “user” is the username of an account that has been created

mkdir -p /home/user/.ssh
echo >> /home/user/.ssh/authorized_keys
curl -m 10 -s http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key | grep 'ssh-rsa' >> \
                          /home/user/.ssh/authorized_keys
echo "AUTHORIZED_KEYS:"
echo "************************"
cat /home/user/.ssh/authorized_keys
echo "************************"

Add the above lines before the “exit 0” in /etc/rc.local

Also remove the network persistent rules from /etc/udev/rules.d, so that the instance always comes up with eth0 as the interface name as expected by eucalyptus.

$ sudo rm -rf /etc/udev/rules.d/70-persistent-net.rules

This completes the process of customizing the OS installed as a reference image.

Registering with Eucalyptus

The last step would be to upload the images to Eucalyptus. The files that need to be uploaded for the above sample setup are: vmlinuz-2.6.28-11-server, initrd.img-2.6.28-11-server, image.img.

Copy the kernel and the initrd image from the VM image to some place outside. These will be used later for creating and uploading a complete virtual image to Eucalyptus.

$ scp /boot/initrd.img-2.6.28-11-server user@A.B.C.D:
$ scp /boot/vmlinuz-2.6.28-11-server user@A.B.C.D:

Before starting the upload process shut down the VM.

Registering kernel image

Execute the following commands to bundle and register the kernel image (vmlinuz-2.6.28-11-server)

uecadmin@client1:~$ euca-bundle-image -i vmlinuz-2.6.28-11-server --kernel true
uecadmin@client1:~$ euca-upload-bundle -b mybucket -m /tmp/vmlinuz-2.6.28-11-server.manifest.xml
uecadmin@client1:~$ euca-register mybucket/vmlinuz-2.6.28-11-server.manifest.xml

Save the output produced by the last command above (eki-XXXXXXXX), which will be needed while registering the disk image.

Registering ramdisk image

Execute the following commands to bundle and register the ramdisk image (initrd.img-2.6.28-11-server)

uecadmin@client1:~$ euca-bundle-image -i  initrd.img-2.6.28-11-server
uecadmin@client1:~$ euca-upload-bundle -b mybucket -m /tmp/initrd.img-2.6.28-11-server.manifest.xml
uecadmin@client1:~$ euca-register mybucket/initrd.img-2.6.28-11-server.manifest.xml

Save the output produced by the last command above (eri-XXXXXXXX), which will be needed while registering the disk image.

Registering disk image

Execute the following commands to bundle and register the ramdisk image (image.img)

uecadmin@client1:~$ euca-bundle-image -i image.img --kernel eki-XXXXXXXX --ramdisk eri-XXXXXXXX
uecadmin@client1:~$ euca-upload-bundle -b mybucket -m /tmp/image.img.manifest.xml
uecadmin@client1:~$ euca-register mybucket/image.img.manifest.xml

Replace eki-XXXXXXXX and eri-XXXXXXXX with the exact values you have saved earlier.

Image Listing

The new images that have been uploaded can be seen by using euca-describe-images command.

For Ex:

uecadmin@client1:~$ euca-describe-images
IMAGE   emi-70B70EC0    mybucket/image.img.manifest.xml                     admin   available        public  x86_64  machine
IMAGE   eri-A2BE13EC    mybucket/initrd.img-2.6.28-11-server.manifest.xml   admin    available       public  x86_64  ramdisk
IMAGE   eki-685F1306    mybucket/vmlinuz-2.6.28-11-server.manifest.xml      admin    available       public  x86_64  kernel

More details on managing the instances in later chapters.

Bundling Windows Image

Creating new disk image

This will represent the main HDD of the virtual machine, so make sure to give it as much space as you will need. Since we are building a kvm image, we can use a qcow2 format for disk images. Qcow2 is an expandable image format, so it will only occupy as much storage space as is actually filled by the data within the image.

uecadmin@client1:~$ kvm-img create -f qcow2 win-2k3.img 20G

OS Installation

Create an ISO image of the relevant Windows installation CD. And start the installation process.

uecadmin@client1:~$ sudo kvm -m 1024 -cdrom Win2003ServerR2x86_cd1.iso -drive file=win-2k3.img,if=scsi,boot=on -nographic -vnc :0

After finishing the installation and in case you need to install from the 2nd CD as well, reboot the VM and launch the VM by the following command.

uecadmin@client1:~$ sudo kvm -m 1024 -boot c -cdrom Win2003ServerR2x86_cd2.iso -drive file=win-2k3.img,if=scsi,boot=on -nographic -vnc :0

Once installation is complete, we need to create the boot disk needed for Windows 2003 server

For Windows XP bundling

While bundling Windows XP, the OS doesn’t recognize SCSI driver during installation process.

The following workaround is suggested:
1. Attach the disk as IDE disk.

$ sudo kvm -m 1024 -cdrom winxpcd.iso -drive file=winxp.img,boot=on -nographic -vnc :0

2. Finish the installation of Windows XP.
3. Now create another disk image using kemu-img

$ kvm-img create -f qcow2 newdisk.img 5G

4. Start the instance by attaching the second disk as SCSI disk.

$ sudo kvm -m 1024 -drive file=winxp.img,boot=on -drive file=newdisk.img,if=scsi -nographic -vnc :0

5. After Windows XP boots, it detects and installs the driver for the SCSI disk (sys_hi.sys)

The remaining procedure is same as that of bundling Windows 2003 Server.

Copying the boot files

Re-launch the VM using the following command, so that we can access the first CD, in order to copy some files from it.

uecadmin@client1:~$ sudo kvm -m 1024 -boot c -cdrom Win2003ServerR2x86_cd1.iso -drive file=win-2k3.img,if=scsi,boot=on -nographic -vnc :0

Copy the following files to a specific location to create the boot disk, say C:\bootfiles

  • ntldr
  • ntdetect.com
  • sym_hi.sys

Rename sym_hi.sys to Ntbootdd.sys (SCSI driver needed to boot the hard disk).

In case, sym_hi.sys is not present in the CD, copy it from the following location of the installation

C:\WINDOWS\system32\drivers

Write the following lines to a new file and save it as Boot.ini in the same location, i.e, C:\bootfiles

[boot loader]
timeout=30
Default= multi(0)disk(0)rdisk(0)partition(1)\Windows

[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003"

Shut down the VM and proceed for the boot disk creation

Boot disk creation

Execute the following command to create the boot disk.

uecadmin@client1:~$ dd bs=512 count=2880 if=/dev/zero of=win-boot.img

Now attach this disk as a floppy disk and start the Windows VM.

uecadmin@client1:~$ sudo kvm -m 1024 -boot c -drive file=win-2k3.img,if=scsi,boot=on,index=1 -fda win-boot.img -nographic -vnc :0

On the Windows VM, format the floppy disk and copy all the files from C:\bootfiles to the floppy.
Shutdown the VM and test the boot disk created with the following command

uecadmin@client1:~$ sudo kvm -m 1024 -boot a -drive file=win-2k3.img,if=scsi,boot=on,index=1 -fda win-boot.img -nographic -vnc :0

This should boot you into windows, if you have rightly created the boot floppy.

Network Configuration

Now you need to download the e1000 drivers, since e1000 is the default interface that is supported by Eucalyptus. You can download the drivers from the following location:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldId=8659&lang=ENG

For 32-bit VM, download PRO2KXP.exe
For 64-bit Vm, download PROEM64T .exe

Once the download is finished, shutdown the VM and restart the VM with the following command.

uecadmin@client1:~$ sudo kvm -m 1024 -boot a -drive file=win-2k3.img,if=scsi,boot=on,index=1 -fda win-boot.img \
-net nic,model=e1000 -net tap -nographic -vnc :0

The above command tell the VM to make use of e1000 model as its NIC.
After executing the above command, you will get this warning.

Warning: vlan 0 is not connected to host network

You can safely ignore this warning message.

After the VM boots, install the network drivers.

Enable remote desktop for all users on the VM. This is very important. As this is the only way, without installing a third party tool, you allow get access to a Windows instance running on UEC. You can enable remote desktop by navigating to Start → Settings → Control Panel → System → Remote and selecting Remote Desktop option for all users. This completes the Windows disk setup. Shut down the VM.

Memdisk

The kernel memdisk is needed to load Windows. The default syslinux memdisk could be used for this purpose. If you cannot locate memdisk on CC, you need to install syslinux.

uecadmin@client1:~$ sudo apt-get install syslinux

After installing, memdisk will be found in /usr/lib/syslinux

uecadmin@client1:~$ cd /usr/lib/syslinux
uecadmin@client1:/usr/lib/syslinux$ ls -l memdisk
-rw-r--r-- 1 root root 20068 2008-07-15 20:25 memdisk

Copy it to the location where you have all windows files.

Registering with Eucalyptus

The last step would be to upload the images to UEC. The files that need to be uploaded are:

  • memdisk
  • win-boot.img
  • win-2k3.img

Registering memdisk

Execute the following commands to bundle and register the memdisk.

uecadmin@client1:~$ euca-bundle-image -i memdisk --kernel true
uecadmin@client1:~$ euca-upload-bundle -b win2k3_bucket -m /tmp/memdisk.manifest.xml
uecadmin@client1:~$ euca-register win2k3_bucket/memdisk.manifest.xml

Save the output produced by the last command above (eki-XXXXXXXX), which will be needed while registering the disk image.

Registering boot disk

Execute the following commands to bundle and register the boot disk (win-boot.img).

uecadmin@client1:~$ euca-bundle-image -i win-boot.img --ramdisk true
uecadmin@client1:~$ euca-upload-bundle -b win2k3_bucket -m /tmp/win-boot.img.manifest.xml
uecadmin@client1:~$ euca-register win2k3_bucket/win-boot.img.manifest.xml

Save the output produced by the last command above (eri-XXXXXXXX), which will be needed while registering the disk image.

Registering disk image

Execute the following commands to bundle and register the disk image (win-2k3.img)

uecadmin@client1:~$ euca-bundle-image -i win-2k3.img --kernel eki-XXXXXXXX --ramdisk eri-XXXXXXXX
uecadmin@client1:~$ euca-upload-bundle -b win2k3_bucket -m /tmp/win-2k3.img.manifest.xml
uecadmin@client1:~$ euca-register win2k3_bucket/win-2k3.img.manifest.xml

Replace eki-XXXXXXXX and eri-XXXXXXXX with the exact values as noted down earlier.

Image Listing

The new images that have been uploaded can be seen by using euca-describe-images command.
For Ex:

uecadmin@client1:~$ euca-describe-images
IMAGE   emi-55470DE2    win-2k3/win-2k3.img.manifest.xml        admin   available    public  x86_64  machine
IMAGE   eki-2BC30D1B    win-2k3/memdisk.manifest.xml    admin   available   public   x86_64  kernel
IMAGE   eri-76C20ED5    win-2k3/win-boot.img.manifest.xml       admin   available    public  x86_64  ramdisk

Running instance of custom image

To launch a new instance of the custom image, execute euca-run-instances command.

uecadmin@client1:~$ cd .euca
uecadmin@client1:~/.euca$ euca-run-instances  emi-55470DE2 -k mykey -t c1.xlarge

Since this is a windows instance the VM type is specified as c1.xlarge, which has 20GB of hard disk space.

The above procedure for bundling Windows images worked on Ubuntu 9.10 (Karmic Koala). But it fails on Ubuntu 10.04(Lucid Lynx). Please refer to Chapter 11 for a hack to get Windows images running on Lucid Lynx.

Chapter 3
Web Interface
Chapter 5
Instance Management
Advertisements

22 Responses

Subscribe to comments with RSS.

  1. You’re installing the linux image on Client1.
    Isn’t this wrong then?
    “For Ex: vncviewer A.B.C.D :0, where A.B.C.D is the IP address of the CC.”
    IP address is of Client1.

    Rainer

    June 15, 2010 at 6:23 pm

    • Rainer,

      Thanks for pointing out the mistake. It should be the IP address of Client1. This has been corrected now.

      Kiran

      kiranmurari

      June 15, 2010 at 7:02 pm

  2. I want to get a MySQL prepackaged image.
    And I wan to know how to make such an image.

    I tried to make such an image following ‘Problem while following instructions “Install a service into an EBS volume”‘.
    I think this trial got success.
    But I cloud not access to MySQL inside instance created from this image.

    Only SQLyog(with ability of SSH communication)could access to this MySQL instance.
    How to solve this?

    Sotohiro Terashima

    November 5, 2010 at 8:36 am

  3. Hello Mr.Kiran Murari,

    Thank You for Creating this Knowledge Base Blog, we made use of this blog when we’re in trouble. but we could not able to understand, how does the Created VM’s can be accessed from Remote Place or (web). We had successfully created CC, CLC, WS. in one Node (eth1-192.168.1.7) and Nodal Controller (192.168.1.8) using Ubuntu 10.04 Server (GUI-Converted) and Created VM Using Virtual Box and installed Ubuntu 10.10 on VM (192.168.1.13) All the nodes (CC, NC, & VM) are configured and bridged and it is communicating. we are also having 1 static(WAN) IP and it is already configured to eth0 of CC.
    Other Misc Configurations
    >.Configured Hybrid Fox and it is showing VM’s Status Up/Running

    My Question is – How can we access Ubuntu 10.10 VM from remote place.

    srinivas

    March 13, 2011 at 8:43 pm

    • You need to have real public IP addresses provided by your ISP, so that you can assign that IP to the running instance. You also need to look at DNS resolution and FW configuration for accessing the VM from external world. This is like converting the existing Eucalyptus private cloud to Eucalyptus public cloud.

      kiranmurari

      May 7, 2011 at 2:52 am

  4. […] steps are described in detail (including commands) in the following guides on bundling Windows: Eucalyptus Beginners Guide running-windows-on-eucalyptus running-windows-on-eucalyptus-improved […]

  5. What is the point of the SCSI driver for Windows XP? Why do you need it to make an image for eucalyptus? Wouldn’t IDE work just as well? If not, why?

    Linux...Is...EPIC

    July 8, 2011 at 7:32 pm

    • Also… Why do you have the user create newdisk.img in the tutorial for Windows XP? Is it to force Windows to install the scsi driver so you can boot the original hdd using scsi instead of ide? It would be much appreciated if someone could update this tutorial explaining that step. It took me awhile to figure it out on my own…

      Linux...Is...EPIC

      July 8, 2011 at 8:29 pm

  6. Hi kiran

    I think that there are a couple of errors wtih the copied part of the manual (below);

    OS Installation

    Download the iso file of the Linux distribution you want installed in the image. The example below refers to
    creating a Jaunty Jackalope 64-bit server image.

    1 uecadmin@client1:~$ wget http://releases.ubuntu.com/karmic/ubuntu-9.04-server-amd64.iso

    The first issue is that the URL links top a version of karmic, not jaunty.
    Secondly as a continuation of issue one, Ubuntu Relases contains no record of a 9.04 edition of karmic
    Thus when I run:

    wget http://releases.ubuntu.com/karmic/ubuntu-9.04-server-amd64.iso

    nothing installs and I get the following error message:

    HTTP request sent, awaiting response… 404 Not Found
    2011-8-8 14:45:47 ERROR 404: Not Found.

    However, when I run the comand:

    wget http://releases.ubuntu.com/karmic/ubuntu-9.10-server-amd64.iso

    the package installs. Can you advise / fix this, thanks?

    501st scout

    August 8, 2011 at 8:04 pm

    • Thanks for pointing it out. It is fixed to use Karmic release.

      — Kiran

      kiranmurari

      August 16, 2011 at 2:04 pm

  7. the section “Integrating with Eucalyptus” it says to use http://169.254.169.254/latest/meta-data
    to access the VM, but how is it going to access it? if the connection (vm) is just thru vncviewer?

    jose

    September 22, 2011 at 10:37 pm

  8. i think my previous link got deleted…. Thanks for the tutorial… but there is one thing i don’t get
    what link is this http://169.254.169.254/latest/meta-data from the “client1” or from the image that is running in the client1?

    can’t get it, can you help me thanks.

    jose

    September 24, 2011 at 10:41 am

  9. My friend. When i’ve used the command:

    euca-bundle-image -i vmlinuz-2.6.28-11-server –kernel true
    I had this>

    cert must be specified.
    private key must be specified.
    user must be specified.
    ec2cert must be specified.

    Bundles an image for use with Eucalyptus or Amazon EC2.

    euca-bundle-image -i, –image image_path -u, –user user [-c, –cert cert_path]
    [-k, –privatekey private_key_path] [-p, –prefix prefix] [–kernel kernel_id]
    [–ramdisk ramdisk_id] [-B, –block-device-mapping mapping]
    [-d, –destination destination_path] [–ec2cert ec2cert_path]
    [-r, –arch target_architecture] [–batch] [-h, –help] [–version] [–debug]

    REQUIRED PARAMETERS

    -i, –image Path to the image file to bundle.

    -u, –user User ID (12-digit) of the user who is bundling the image.

    OPTIONAL PARAMETERS

    -c, –cert Path to the user’s PEM encoded certificate.

    -k, –privatekey Path to the user’s PEM encoded private key.

    -p, –prefix The prefix for the bundle image files. (default: image name).

    –kernel The kernel to be associated with the bundled image.

    –ramdisk The ramdisk to be associated with the bundled image.

    -B, –block-device-mapping Default block device mapping for the image (comma-separated list of key=value pairs).

    -d, –destination Directory to store the bundled image in (default: “/tmp”). Recommended.

    –ec2cert The path to the Cloud’s X509 public key certificate.

    -r, –arch Target architecture for the image (‘x86_64’ or ‘i386’ default: ‘x86_64’).

    –batch Run in batch mode (compatibility only. has no effect).

    -a, –access-key User’s Access Key ID.

    -s, –secret-key User’s Secret Key.

    -U, –url URL of the Cloud to connect to.

    –config Read credentials and cloud settings from the
    specified config file (defaults to $HOME/.eucarc or /etc/euca2ools/eucarc).

    -h, –help Display this help message.

    –version Display the version of this tool.

    –debug Turn on debugging.

    Euca2ools will use the environment variables EC2_URL, EC2_ACCESS_KEY, EC2_SECRET_KEY, EC2_CERT, EC2_PRIVATE_KEY, S3_URL, EUCALYPTUS_CERT by default.

    What’s going on?
    Thanks.

    Sandrigo Oliveira

    September 30, 2011 at 7:01 am

  10. Another question. At this command>

    Now attach this disk as a floppy disk and start the Windows VM.
    view source
    print?
    uecadmin@client1:~$ sudo kvm -m 1024 -boot c -drive file=win-2k3.img,if=scsi,boot=on,index=1 -fda win-boot.img -nographic -vnc :0
    On the Windows VM, format the floppy disk and copy all the files from C:\bootfiles to the floppy.

    Can i use a pen drive instand of floppy disk? If yes, how can i do it?

    thanks!

    Sandrigo Oliveira

    September 30, 2011 at 7:03 am

  11. Hi My name is Raoul I am building a cloud lab based on eucalyptus i have been following the steps found on this page and i encountered a problem.when i type this command: euca-upload-bundle -b mybucket -m /tmp/karmic_initrd.manifest

    i get this problem:
    Checking bucket: mybucket
    Creating bucket: mybucket
    Traceback (most recent call last):
    File “/usr/bin/euca-upload-bundle”, line 231, in
    main()
    File “/usr/bin/euca-upload-bundle”, line 214, in main
    bucket_instance = ensure_bucket(conn, bucket, canned_acl)
    File “/usr/bin/euca-upload-bundle”, line 92, in ensure_bucket
    bucket_instance = create_bucket(connection, bucket, canned_acl)
    File “/usr/bin/euca-upload-bundle”, line 81, in create_bucket
    return connection.create_bucket(bucket, policy=canned_acl)
    File “/usr/lib/pymodules/python2.6/boto/s3/connection.py”, line 321, in create_bucket
    raise S3ResponseError(response.status, response.reason, body)
    boto.exception.S3ResponseError: S3ResponseError: 403 Forbidden
    AccessDeniedAccess Deniedmybucket42ed3a3c-8e31-4462-bf22-e446d30e9167

    Please tell em where to go to fix it;

    Also on my hybridfox i cannot access my walrus regions it always complains saying:ec2 reponded with an error for describe instances.i manage to access the eucalyptus region without any problem.

    Thanx in advance for your time.

    quimissus

    November 16, 2011 at 3:19 pm

  12. hi kiran

    rider@server:~/eucalyptus/euca-ubuntu-9.04-i386/kvm-kernel$ euca-register ubuntu/vmlinuz-2.6.28-11-server.manifest.xml
    Warning: failed to parse error message from AWS: :1:0: syntax error
    None: None

    how to solve this problem

    rider

    April 11, 2012 at 6:32 pm

  13. Hello there, I have been following this tutorial an was able to start a test cloud, however, since I’m still new to linux I have met a problem when it comes to copying the files inside the VMs using “scp /boot/initrd.img-2.6.28-11-server user@A.B.C.D:”, since ssh will not allow me to connect to the host machine.

    How do i bypass this, to allow me to copy the said file, and bundle the image. Thanks.

    Jov Felarca

    April 30, 2012 at 8:14 pm

  14. euca-upload-bundle -b mybucket -m /tmp/vmlinuz-2.6.28-11-server.manifes. in this command i am getting error connection refused .i dont know what to do.i creating ubuntu 12.04 image

    amit khoth

    August 31, 2012 at 2:17 pm

  15. Hello Mr. Kiran Murari,
    I have installed a private cloud with ubuntu-10.04 UEC for my project with 2 servers, Server 1 has Cloud Controller, Walrus storage service, Cluster Controller & Storage Controller, while Server 2 has Node Controller only. Now, I am getting some error while registering the Eucalyptus Machine Image (EMI).
    For registering i used command “euca-register mybucket/vmlinuz-2.6.32-38-server.manifest.xml” on Client Terminal Window,
    but i am getting output as “None: Failure: 500 Internal Server Error” instead of something like “eki-XXXXXXXX”.
    Any solution for remove this error?

    Vaibhav Chauthmal

    April 6, 2013 at 11:22 am

  16. hi,
    I succesfully uploaded the image, the kernel and the ramdisk on my Eucalyptus Cloud. But when I try to start an instance with the new image it stays for some time in “pending” mode and then terminates. I have checked the nc.log file and here its output:

    2014-03-12 11:50:44 INFO | downloaded 99.8% of http://11.11.3.220:8773/services/Walrus/image-bucket-LB2/LB2.img.manifest.xml
    2014-03-12 11:50:45 INFO | downloaded /var/lib/eucalyptus/instances/cache/emi-F7213CC8-8480fe74/blocks
    2014-03-12 11:50:45 INFO | [i-EE203EF8] copying/cloning blob emi-F7213CC8-8480fe74 to blob HJXXSZMDZURRVNAN3IG3D/i-EE203EF8/emi-F7213CC8-8442c6d3
    2014-03-12 11:50:46 INFO | [i-EE203EF8] tuning root file system on disk 0 partition 1
    2014-03-12 11:50:46 ERROR | bad return code from cmd ‘//usr/lib/eucalyptus/euca_rootwrap /sbin/tune2fs /dev/mapper/euca-HJXXSZMDZURRVNAN3IG3D-i-EE203EF8-emi-F7213CC8-8442c6d3 -c 0 -i 0 2>&1′
    2014-03-12 11:50:46 ERROR | cannot tune file system on ‘/dev/mapper/euca-HJXXSZMDZURRVNAN3IG3D-i-EE203EF8-emi-F7213CC8-8442c6d3′
    2014-03-12 11:50:46 WARN | [i-EE203EF8] failed to tune root file system: blobstore.c:4499 file access only supported for uncloned blockblobs
    2014-03-12 11:50:46 INFO | [i-EE203EF8] injecting the ssh key
    2014-03-12 11:50:46 ERROR | bad return code from cmd ‘//usr/lib/eucalyptus/euca_rootwrap //usr/lib/eucalyptus/euca_mountwrap mount /dev/mapper/euca-HJXXSZMDZURRVNAN3IG3D-i-EE203EF8-emi-F7213CC8-8442c6d3 /tmp/euca-mount-VxRFSg 2>&1′
    2014-03-12 11:50:46 ERROR | cannot mount device ‘/dev/mapper/euca-HJXXSZMDZURRVNAN3IG3D-i-EE203EF8-emi-F7213CC8-8442c6d3′ on ‘/tmp/euca-mount-VxRFSg’
    2014-03-12 11:50:46 ERROR | [i-EE203EF8] failed to mount ‘/dev/mapper/euca-HJXXSZMDZURRVNAN3IG3D-i-EE203EF8-emi-F7213CC8-8442c6d3′ on ‘/tmp/euca-mount-VxRFSg’
    2014-03-12 11:50:46 ERROR | [i-EE203EF8] failed to create artifact emi-F7213CC8-8442c6d3 (error=1, may retry) on try 1
    2014-03-12 11:50:46 ERROR | [i-EE203EF8] failed to provision dependency emi-F7213CC8-8442c6d3 for artifact dsk-F7213CC8-d2432afe (error=1) on try 1
    2014-03-12 11:50:46 ERROR | [i-EE203EF8] failed to provision dependency dsk-F7213CC8-d2432afe for artifact i-EE203EF8 (error=1) on try 1
    2014-03-12 11:50:46 ERROR | [i-EE203EF8] failed to implement backing for instance
    2014-03-12 11:50:46 ERROR | [i-EE203EF8] failed to prepare images for instance (error=1)
    2014-03-12 11:50:50 WARN | libvirt: Domain not found: no domain with matching name ‘i-EE203EF8′ (code=42)
    2014-03-12 11:50:50 INFO | [i-EE203EF8] cleaning up state for instance
    2014-03-12 11:50:50 INFO | [i-EE203EF8] stopping the network (vlan=26)
    2014-03-12 11:51:06 ERROR | [i-EE203EF8] failed to write instance XML to /var/lib/eucalyptus/instances/work/HJXXSZMDZURRVNAN3IG3D/i-EE203EF8/instance.xml
    2014-03-12 11:53:51 INFO | [i-EE203EF8] forgetting about instance

    I cannot figure whats preventing instance from running. Please can you help whats going wrong in this?

    Gaurav Sadhwani

    March 12, 2014 at 12:13 pm


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: