Hello,
Did anyone get the time to look at this ?
Thanks in advance.
CyD
Vendredi 24/08/2012 à 14:24 Duverne, Cyrille a écrit:
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 :
Hi
It is normal not to see a partition table, note that the disk is made of a
raw file, and then is given ext3 format. The devices are shown in your VM,
so just mount them
mount -t ext3 /dev/vdc /mnt
Cheers
Ruben
On Sun, Aug 26, 2012 at 11:12 AM, Duverne, Cyrille
cyrille.duve...@euranova.eu
Thanks a lot Ruben,
Indeed, this was that simple, I tried so much different config that I
lost the basics.
But, I configured this datablock to be mapped to vde and it's mapped
to vdc, why ?
Thanks in advance.
CyD
Dimanche 26/08/2012 à 20:59 Ruben S. Montero a écrit:
Hi
It is normal not to
Hi
The final mapping of devices are made by libvirt, and depending on the
version, for example it will not left any gap in the bus. Note also
that the guest may present the device under different forms...
OpenNebula has some automatic target naming (check [1]) so I think
that it is better to
Indeed :)
Thanks a lot Ruben, that solved a lot of questions.
Kind regards
CyD
Dimanche 26/08/2012 à 23:38 Ruben S. Montero a écrit:
Hi
The final mapping of devices are made by libvirt, and depending on the
version, for example it will not left any gap in the bus. Note also
that the guest may
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
