[one-users] Unable to see on the fly disk in KVM VMs

[Duverne, Cyrille]

Hello,

I'm having quite an issue when creating VMs with an attached datablock
:

I'm running OpenNebula 3.4 with KVM + Sunstone.

Here below my VM template :

CONTEXT=[
  FILES=/nebuladata/scripts/init.sh,
  HOSTNAME=\"VM-\"$VMID,
  IP_PUBLIC="$NIC[IP, NETWORK=\"Big Network\"]",
  TARGET=vdb ]
CPU=0.2
DISK=[
  IMAGE=UbuntuContext,
  TARGET=vda ]
DISK=[
  FORMAT=ext3,
  SIZE=40000,
  TARGET=vde,
  TYPE=fs ]
FEATURES=[
  ACPI=yes ]
GRAPHICS=[
  TYPE=VNC ]
MEMORY=512
NAME=ubuntu
NIC=[
  NETWORK="Big Network" ]
OS=[
  ARCH=x86_64,
  BOOT=hd ]
TEMPLATE_ID=20

Here below what happens in ONE when creating the VM :

Fri Aug 24 14:07:05 2012 [DiM][I]: New VM state is ACTIVE. Fri Aug 24
14:07:05 2012 [LCM][I]: New VM state is PROLOG. Fri Aug 24 14:07:39
2012 [TM][D]: tm_clone.sh:
inferno:/var/lib/one/images/b1240e874bec231c993568433c5a314a
orthanc.local:/var/lib/one//121/images/disk.0 Fri Aug 24 14:07:39 2012
[TM][D]: tm_clone.sh: DST: /var/lib/one//121/images/disk.0 Fri Aug 24
14:07:39 2012 [TM][I]: tm_clone.sh: Creating directory
/var/lib/one//121/images Fri Aug 24 14:07:39 2012 [TM][I]:
tm_clone.sh: Executed "mkdir -p /var/lib/one//121/images". Fri Aug 24
14:07:39 2012 [TM][I]: tm_clone.sh: Executed "chmod a+w
/var/lib/one//121/images". Fri Aug 24 14:07:39 2012 [TM][I]:
tm_clone.sh: Cloning
/var/lib/one/images/b1240e874bec231c993568433c5a314a Fri Aug 24
14:07:39 2012 [TM][I]: tm_clone.sh: Executed "cp -r
/var/lib/one/images/b1240e874bec231c993568433c5a314a
/var/lib/one//121/images/disk.0". Fri Aug 24 14:07:39 2012 [TM][I]:
tm_clone.sh: Executed "chmod a+rw /var/lib/one//121/images/disk.0".
Fri Aug 24 14:07:39 2012 [TM][I]: ExitCode: 0 Fri Aug 24 14:07:57 2012
[TM][I]: tm_mkimage.sh: Executed "mkdir -p /var/lib/one//121/images".
Fri Aug 24 14:07:57 2012 [TM][I]: tm_mkimage.sh: Executed "dd
if=/dev/zero of=/var/lib/one//121/images/disk.1 bs=1 count=1
seek=40000M". Fri Aug 24 14:07:57 2012 [TM][I]: tm_mkimage.sh:
Executed "mkfs -t ext3 -F /var/lib/one//121/images/disk.1". Fri Aug 24
14:07:57 2012 [TM][I]: tm_mkimage.sh: Executed "chmod a+rw
/var/lib/one//121/images/disk.1". Fri Aug 24 14:07:57 2012 [TM][I]:
ExitCode: 0 Fri Aug 24 14:07:58 2012 [TM][I]: tm_context.sh: Executed
"mkdir -p /var/lib/one//121/images/isofiles". Fri Aug 24 14:07:58 2012
[TM][I]: tm_context.sh: Executed "cp -R /var/lib/one/121/context.sh
/var/lib/one//121/images/isofiles". Fri Aug 24 14:07:58 2012 [TM][I]:
tm_context.sh: Executed "cp -R /nebuladata/scripts/init.sh
/var/lib/one//121/images/isofiles". Fri Aug 24 14:07:58 2012 [TM][I]:
tm_context.sh: Executed "genisoimage -o
/var/lib/one//121/images/disk.2 -J -R
/var/lib/one//121/images/isofiles". Fri Aug 24 14:07:58 2012 [TM][I]:
tm_context.sh: Executed "rm -rf /var/lib/one//121/images/isofiles".
Fri Aug 24 14:07:58 2012 [TM][I]: ExitCode: 0 Fri Aug 24 14:07:58 2012
[LCM][I]: New VM state is BOOT Fri Aug 24 14:07:58 2012 [VMM][I]:
Generating deployment file: /var/lib/one/121/deployment.0 Fri Aug 24
14:07:58 2012 [VMM][I]: ExitCode: 0 Fri Aug 24 14:07:58 2012 [VMM][I]:
Successfully execute network driver operation: pre. Fri Aug 24
14:08:00 2012 [VMM][I]: ExitCode: 0 Fri Aug 24 14:08:00 2012 [VMM][I]:
Successfully execute virtualization driver operation: deploy. Fri Aug
24 14:08:00 2012 [VMM][I]: ExitCode: 0 Fri Aug 24 14:08:00 2012
[VMM][I]: Successfully execute network driver operation: post. Fri Aug
24 14:08:01 2012 [LCM][I]: New VM state is RUNNING

Here below a df -h result in the VM :

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ENX-root 2.3G 914M 1.3G 42% /
udev 237M 4.0K 237M 1% /dev
tmpfs 99M 232K 99M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 246M 0 246M 0% /run/shm
/dev/vda1 228M 25M 192M 12% /boot

The result of a sudo fdisk -l :

Disk /dev/vdb: 0 MB, 374784 bytes
16 heads, 63 sectors/track, 0 cylinders, total 732 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/vdb doesn't contain a valid partition table

Disk /dev/vdc: 41.9 GB, 41943040000 bytes
16 heads, 63 sectors/track, 81269 cylinders, total 81920000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/vdc doesn't contain a valid partition table

Disk /dev/mapper/ENX-root: 2424 MB, 2424307712 bytes
255 heads, 63 sectors/track, 294 cylinders, total 4734976 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

-----------

I tried to use it in a non-LVM VM, which was the same.
Tried to use hd or sd instead of vd and nothing worked...

Please help, this is driving me crazy...

Thanks in advance
CyD


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120824/e5c41988/attachment-0002.htm>