Customized workspace launch problem

Submitted by Subhra Sarkar on Tue, 25 Sep 2012, 17:22:51 GMT

Nimbus

Hi,
I am new to FutureGrid. As part of my project, I created a customized CentOS 5.8 (x86_64) image using XEN hypervisor. The VM has the following disk partition setup -

*****************FDISK O/P************************
[root@localhost ~]# fdisk -l

Disk /dev/hda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 523 4200966 83 Linux
/dev/hda2 524 785 2104515 83 Linux
/dev/hda3 786 1044 2080417+ 82 Linux swap / Solaris
[root@localhost ~]#

Moreover, it has the directory /root/.ssh present in it.

Once done with the creation of this VM image, I transferred it to Cumulus repo (with Hotel & Sierra's configuration). Its being displayed in the list of available VMs just fine. However, when tried launching the VM, it threw the following error log -

******************************ERROR LOG**********************************
[sarkar@alexander:nimbus-cloud-client-021]$ bin/cloud-client.sh --conf conf/sierra.conf --run --name testCentOS.img --hours 1

Launching workspace.

Workspace Factory Service:
https://s83r.idp.sdsc.futuregrid.org:8443/wsrf/services/WorkspaceFactory...

Creating workspace "vm-009"... done.

   IP address: 198.202.120.127
     Hostname: vm-33.sdsc.futuregrid.org
   Start time: Fri Sep 21 13:21:46 EDT 2012
Shutdown time: Fri Sep 21 14:21:46 EDT 2012

Termination time: Fri Sep 21 14:23:46 EDT 2012

Waiting for updates.

Problem with vm-009: Problem with workspace driver, error executing request operation (but validation succeeded)
STDERR: libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName
2012-09-21 10:25:32,784 - ERROR - problem running command: '/usr/bin/sudo /opt/nimbus/libexec/workspace-control/mount-alter.sh one /scratch/nimbus/secureimages/wrksp-76693/tmpiLPlDlRepo__VMS__68db528a-f3b7-11e1-a91d-02215ecdd0ff__testCentOS.img /opt/nimbus/var/workspace-control/mnt/wrksp-76693 /opt/nimbus/var/workspace-control/tmp/4f70c588-c6e4-47c9-bec2 /root/.ssh/authorized_keys' ::: return code: 1280 ::: output:
/opt/nimbus/libexec/workspace-control/mount-alter.sh received these arguments:
- subcommand: one
- imagefile: /scratch/nimbus/secureimages/wrksp-76693/tmpiLPlDlRepo__VMS__68db528a-f3b7-11e1-a91d-02215ecdd0ff__testCentOS.img
- mountpoint: /opt/nimbus/var/workspace-control/mnt/wrksp-76693
- datafile: /opt/nimbus/var/workspace-control/tmp/4f70c588-c6e4-47c9-bec2
- datatarget: /root/.ssh/authorized_keys

Checking input:
- IMAGE_DIR: /scratch/nimbus/secureimages/
OK: /scratch/nimbus/secureimages/wrksp-76693/tmpiLPlDlRepo__VMS__68db528a-f3b7-11e1-a91d-02215ecdd0ff__testCentOS.img
- MOUNTPOINT_DIR: /opt/nimbus/var/workspace-control/mnt/
OK: /opt/nimbus/var/workspace-control/mnt/wrksp-76693
- FILE_DIR: /opt/nimbus/var/workspace-control/tmp/
OK: /opt/nimbus/var/workspace-control/tmp/4f70c588-c6e4-47c9-bec2
- target OK: /root/.ssh/authorized_keys

Altering image (dryrun = false):

command = /bin/mount -o loop,noexec,nosuid,nodev,noatime,sync /scratch/nimbus/secureimages/wrksp-76693/tmpiLPlDlRepo__VMS__68db528a-f3b7-11e1-a91d-02215ecdd0ff__testCentOS.img /opt/nimbus/var/workspace-control/mnt/wrksp-76693
mount: you must specify the filesystem type
Traceback (most recent call last):
File "/opt/nimbus2.9/src/python/workspacecontrol/main/wc_core.py", line 79, in core
_core(vm_name, action, p, c)
File "/opt/nimbus2.9/src/python/workspacecontrol/main/wc_core.py", line 168, in _core
wc_core_creation.create(vm_name, p, c, async, editing, images, kernels, localnet, netbootstrap, netlease, netsecurity, persistence, platform)
File "/opt/nimbus2.9/src/python/workspacecontrol/main/wc_core_creation.py", line 16, in create
_create_local(vm_name, p, c, async, editing, images, kernels, localnet, netbootstrap, netlease, netsecurity, persistence, platform)
File "/opt/nimbus2.9/src/python/workspacecontrol/main/wc_core_creation.py", line 31, in _create_local
_common(local_file_set, vm_name, p, c, editing, kernels, localnet, netbootstrap, netlease, netsecurity, persistence, platform, justprint=justprint)
File "/opt/nimbus2.9/src/python/workspacecontrol/main/wc_core_creation.py", line 54, in _common
editing.process_after_procurement(local_file_set)
File "/opt/nimbus/src/python/workspacecontrol/defaults/ImageEditing.py", line 250, in process_after_procurement
self._doMountCopyTasks(rootdisk, vm_name, mnttask_list, hdimage)
File "/opt/nimbus/src/python/workspacecontrol/defaults/ImageEditing.py", line 420, in _doMountCopyTasks
self._doOneMountCopyTask(imagepath, src, task[1], mntpath, hdimage)
File "/opt/nimbus/src/python/workspacecontrol/defaults/ImageEditing.py", line 432, in _doOneMountCopyTask
raise error
IncompatibleEnvironment: problem running command: '/usr/bin/sudo /opt/nimbus/libexec/workspace-control/mount-alter.sh one /scratch/nimbus/secureimages/wrksp-76693/tmpiLPlDlRepo__VMS__68db528a-f3b7-11e1-a91d-02215ecdd0ff__testCentOS.img /opt/nimbus/var/workspace-control/mnt/wrksp-76693 /opt/nimbus/var/workspace-control/tmp/4f70c588-c6e4-47c9-bec2 /root/.ssh/authorized_keys' ::: return code: 1280 ::: output:
/opt/nimbus/libexec/workspace-control/mount-alter.sh received these arguments:
- subcommand: one
- imagefile: /scratch/nimbus/secureimages/wrksp-76693/tmpiLPlDlRepo__VMS__68db528a-f3b7-11e1-a91d-02215ecdd0ff__testCentOS.img
- mountpoint: /opt/nimbus/var/workspace-control/mnt/wrksp-76693
- datafile: /opt/nimbus/var/workspace-control/tmp/4f70c588-c6e4-47c9-bec2
- datatarget: /root/.ssh/authorized_keys

Altering image (dryrun = false):

Exiting with error code: 3

Workspace "vm-009" did NOT reach target state "Running"

Problem running 'vm-009'.

Got the same error on both Hotel & Sierra. Strangely enough, I'm able to launch VMs from the repo list (e.g. hello-cloud) without any problem. Could anyone please suggest where I'm doing it wrong?

Thanks in advance.

Best regards,
Sarkar

Customized workspace launch problem

About

Support

Community

Projects