The OpenNebula project is proud to announce the availability of OpenNebula 5.0 ‘Wizard’ Beta. This major update comes with several improvements in different subsystems and components, with minimal changes in the API and the VM life-cycle states, which embodies long overdue changes but implemented to minimize the impact and ensure backwards compatibility as far as possible.
Read the blog post for more information.
This topic is now a banner. It will appear at the top of every page until it is dismissed by the user.
Hi!
VMs not boot. (No bootable device).
VMs stop DEPLOY and freezes in PENDING state.
Can’t create virtual router (no templates).
OpenvSwitch not working .
Commands are searching openvswitch instead of ovswitch .
Thu May 19 15:57:54 2016 [Z0][VMM][I]: Command execution fail: /var/tmp/one/vnm/openvswitch/pre PFZNPjxJRD4zPC9JRD48REVQTE9ZX0lELz48VEVNUExBVEU+PFNFQ1VSSVRZX0dST1VQX1JVTEU+PFBST1RPQ09MPjwhW0NEQVRBW0FMTF1dPjwvUFJPVE9DT0w+PFJVTEVfVFlQRT48IVtDREFUQVtPVVRCT1VORF1dPjwvUlVMRV9UWVBFPjxTRUNVUklUWV9HUk9VUF9JRD48IVtDREFUQVswXV0+PC9TRUNVUklUWV9HUk9VUF9JRD48U0VDVVJJVFlfR1JPVVBfTkFNRT48IVtDREFUQVtkZWZhdWx0XV0+PC9TRUNVUklUWV9HUk9VUF9OQU1FPjwvU0VDVVJJVFlfR1JPVVBfUlVMRT48L1RFTVBMQVRFPjxURU1QTEFURT48U0VDVVJJVFlfR1JPVVBfUlVMRT48UFJPVE9DT0w+PCFbQ0RBVEFbQUxMXV0+PC9QUk9UT0NPTD48UlVMRV9UWVBFPjwhW0NEQVRBW0lOQk9VTkRdXT48L1JVTEVfVFlQRT48U0VDVVJJVFlfR1JPVVBfSUQ+PCFbQ0RBVEFbMF1dPjwvU0VDVVJJVFlfR1JPVVBfSUQ+PFNFQ1VSSVRZX0dST1VQX05BTUU+PCFbQ0RBVEFbZGVmYXVsdF1dPjwvU0VDVVJJVFlfR1JPVVBfTkFNRT48L1NFQ1VSSVRZX0dST1VQX1JVTEU+PC9URU1QTEFURT48SElTVE9SWV9SRUNPUkRTPjxISVNUT1JZPjxIT1NUTkFNRT52cHMuY2xvdWQuYWU8L0hPU1ROQU1FPjwvSElTVE9SWT48L0hJU1RPUllfUkVDT1JEUz48SElTVE9SWV9SRUNPUkRTPjxISVNUT1JZPjxWTV9NQUQ+PCFbQ0RBVEFba3ZtXV0+PC9WTV9NQUQ+PC9ISVNUT1JZPjwvSElTVE9SWV9SRUNPUkRTPjxURU1QTEFURT48TklDPjxBUl9JRD48IVtDREFUQVswXV0+PC9BUl9JRD48QlJJREdFPjwhW0NEQVRBW2JyMF1dPjwvQlJJREdFPjxDTFVTVEVSX0lEPjwhW0NEQVRBWzBdXT48L0NMVVNURVJfSUQ+PElQPjwhW0NEQVRBWzEwLjI1NC4yNTQuMTc1XV0+PC9JUD48TUFDPjwhW0NEQVRBWzAyOjAwOjBhOmZlOmZlOmFmXV0+PC9NQUM+PE5FVFdPUks+PCFbQ0RBVEFbSVBULU5FVF1dPjwvTkVUV09SSz48TkVUV09SS19JRD48IVtDREFUQVswXV0+PC9ORVRXT1JLX0lEPjxOSUNfSUQ+PCFbQ0RBVEFbMF1dPjwvTklDX0lEPjxTRUNVUklUWV9HUk9VUFM+PCFbQ0RBVEFbMF1dPjwvU0VDVVJJVFlfR1JPVVBTPjxUQVJHRVQ+PCFbQ0RBVEFbb25lLTMtMF1dPjwvVEFSR0VUPjxWTl9NQUQ+PCFbQ0RBVEFbb3BlbnZzd2l0Y2hdXT48L1ZOX01BRD48L05JQz48L1RFTVBMQVRFPjwvVk0+ Thu May 19 15:57:54 2016 [Z0][VMM][I]: bash: line 2: /var/tmp/one/vnm/openvswitch/pre: No such file or directory Thu May 19 15:57:54 2016 [Z0][VMM][I]: ExitCode: 127 Thu May 19 15:57:54 2016 [Z0][VMM][I]: Failed to execute network driver operation: pre.
You have to import “alpine” from “App” section and follow documentation for virtual router templates .
Hi
THANKS a lot for the feedback,
Issue for the Openvswtich:
http://dev.opennebula.org/issues/4470
Solved in master. Meanwhile just update VN_MAD to ovswtich
Hi,
Compared to 4.14 , VM deployment is pretty lag . PROLOG and BOOT taking long time.
Also vm log refresh is not working . After refreshing log , its rotating , rotating …no result.
Is this an interface problem? Could you refresh without cache or try in an
incognito window? In order to get the actual prolog/boot times you can
check the vm log file, and compare them to 4.14… it should not be any
significant differences in that area…
Hi Ruben,
I have tried this from Firefox and chrome as well , but still the same . Restarted sunstone service , but no hope .
Another problem im facing is , none of the “App” imported machines are working . Its saying “No bootable device” . Tried to change driver to “qcow2” , DEVICE_PREFIX to “vd” , “hd” and “sd” . Nothing happend.
But when using CDROM installation its working fine . Volatile disk is taking as “/dev/sda” . Any hope in this side?
For the “no bootable device” problem:
my datastores:
ID NAME SIZE AVAIL CLUSTERS IMAGES TYPE DS TM STAT
0 system 0M - 0 0 sys - qcow2 on
1 default 98.3G 98% 0 4 img fs qcow2 on
2 files 98.3G 98% 0 0 fil fs shared on
I imported Debian 8.2 KVM from marketplace:
IMAGE 3 INFORMATION
ID : 3
NAME : Debian 8.2 - KVM
USER : nebula
GROUP : oneadmin
DATASTORE : default
TYPE : OS
REGISTER TIME : 05/18 17:02:22
PERSISTENT : No
SOURCE : /var/lib/one//datastores/1/1a04d9b5d3f3eea41892d81336edfb5e
PATH : http://marketplace.opennebula.systems//appliance/56040c398fb81d7410000006/download/0
FSTYPE : raw
SIZE : 10G
STATE : used
RUNNING_VMS : 1
PERMISSIONS
OWNER : um-
GROUP : ---
OTHER : ---
IMAGE TEMPLATE
DEV_PREFIX="hd"
FORMAT="qcow2"
FROM_APP="36"
FROM_APP_NAME="Debian 8.2 - KVM"
MD5="db80fc7ec841a0504dcb2242bef77458"
The image is stored as qcow2:
qemu-img info /var/lib/one//datastores/1/1a04d9b5d3f3eea41892d81336edfb5e
image: /var/lib/one//datastores/1/1a04d9b5d3f3eea41892d81336edfb5e
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 296M
cluster_size: 65536
Format specific information:
compat: 0.10
refcount bits: 16
With the VM template:
TEMPLATE 2 INFORMATION
ID : 2
NAME : Debian 8.2 - KVM
USER : nebula
GROUP : oneadmin
REGISTER TIME : 05/18 17:02:22
PERMISSIONS
OWNER : um-
GROUP : ---
OTHER : ---
TEMPLATE CONTENTS
CONTEXT=[
NETWORK="YES",
SSH_PUBLIC_KEY="$USER[SSH_PUBLIC_KEY]" ]
CPU="1"
DISK=[
IMAGE_ID="3" ]
GRAPHICS=[
LISTEN="0.0.0.0",
TYPE="vnc" ]
LOGO="images/logos/debian.png"
MEMORY="768"
OS=[
ARCH="x86_64" ]
But the deployement.0 reference the image as raw instead of qcow2:
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
<name>one-10</name>
<cputune>
<shares>1024</shares>
</cputune>
<memory>786432</memory>
<os>
<type arch='x86_64'>hvm</type>
</os>
<devices>
<emulator><![CDATA[/usr/bin/qemu-system-x86_64]]></emulator>
<disk type='file' device='disk'>
<source file='/var/lib/one//datastores/0/10/disk.0'/>
<target dev='hda'/>
<driver name='qemu' type='raw' cache='none'/>
</disk>
<disk type='file' device='cdrom'>
<source file='/var/lib/one//datastores/0/10/disk.1'/>
<target dev='hdb'/>
<readonly/>
<driver name='qemu' type='raw'/>
</disk>
<graphics type='vnc' listen='0.0.0.0' port='5910'/>
</devices>
<features>
<acpi/>
</features>
<metadata>
<system_datastore><![CDATA[/var/lib/one//datastores/0/10]]> </system_datastore>
</metadata>
</domain>
Regards.
We have detected that the upgrades under certain conditions will lead to a broken OpenNebula with unusable clusters. We recommend that you don’t upgrade for the time being until we publish a fix.
If you want to upgrade from 4.14, please follow this procedure:
Replace:
/usr/lib/one/ruby/onedb/fsck.rb with https://raw.githubusercontent.com/OpenNebula/one/86244bfc560c7d24b07fe4ba8bc243e6bfa2d068/src/onedb/fsck.rb
/usr/lib/one/ruby/onedb/local/4.13.85_to_4.90.0.rb with https://raw.githubusercontent.com/OpenNebula/one/86244bfc560c7d24b07fe4ba8bc243e6bfa2d068/src/onedb/local/4.13.85_to_4.90.0.rb
Then you can upgrade from 4.14 to 5.0. If you have already upgraded, you will need to revert to the 4.14 DB and redo the upgrade procedure, otherwise when upgrading to 5.0 final it will be broken.
A new beta was released (beta 2). The package repositories have the same URL. In case you want to download the tar.gz with the packages you can head to:
Hello,
I tried to upgrade the packages on my Ubuntu Xenial but I got:
dpkg: erreur de traitement de l'archive /var/cache/apt/archives/opennebula_4.90.5-1_amd64.deb (--unpack) :
tentative de remplacement de « /etc/one/auth/x509_auth.conf », qui appartient aussi au paquet ruby-opennebula 4.90.0-1
This mean that there is something in the dependencies, a file was moved from one package to another without proper dependency relations.
Next, I manage to finish the update with apt-get -f install.
Regards.
We moved configuration files from ruby-opennebula package to opennebula (server). From the documentation linked I can not figure out the best way to do this. Maybe this in opennebula package?
Replaces: ruby-opennebula (<< 4.90.5)
Breaks: ruby-opennebula (<< 4.90.5)
Javi Fontán forum@opennebula.org writes:
We moved configuration files from
ruby-opennebulapackage to
opennebula(server). From the documentation linked I can not figure
out the best way to do this. Maybe this inopennebulapackage?Replaces: ruby-opennebula (<< 4.90.5) Breaks: ruby-opennebula (<< 4.90.5)
Yes.
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
Can’t start VM with CDROM.
]
Tue May 31 16:07:28 2016 [Z0][VM][I]: New state is ACTIVE
Tue May 31 16:07:28 2016 [Z0][VM][I]: New LCM state is PROLOG
Tue May 31 16:07:29 2016 [Z0][VM][I]: New LCM state is BOOT
Tue May 31 16:07:29 2016 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/19/deployment.0
Tue May 31 16:07:30 2016 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Tue May 31 16:07:30 2016 [Z0][VMM][I]: ExitCode: 0
Tue May 31 16:07:30 2016 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Tue May 31 16:07:30 2016 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy ‘/var/lib/one//datastores/105/19/deployment.0’ ‘node01’ 19 node01
Tue May 31 16:07:30 2016 [Z0][VMM][I]: error: Failed to create domain from /var/lib/one//datastores/105/19/deployment.0
Tue May 31 16:07:30 2016 [Z0][VMM][I]: error: unsupported configuration: readonly ide disks are not supported
Tue May 31 16:07:30 2016 [Z0][VMM][E]: Could not create domain from /var/lib/one//datastores/105/19/deployment.0
Tue May 31 16:07:30 2016 [Z0][VMM][I]: ExitCode: 255
Tue May 31 16:07:30 2016 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Tue May 31 16:07:30 2016 [Z0][VMM][E]: Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/105/19/deployment.0
Tue May 31 16:07:30 2016 [Z0][VM][I]: New LCM state is BOOT_FAILURE
Антон Зубков forum@opennebula.org writes:
Can’t start VM with CDROM.
]
Tue May 31 16:07:28 2016 [Z0][VM][I]: New state is ACTIVE
Tue May 31 16:07:28 2016 [Z0][VM][I]: New LCM state is PROLOG
Tue May 31 16:07:29 2016 [Z0][VM][I]: New LCM state is BOOT
Tue May 31 16:07:29 2016 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/19/deployment.0
Tue May 31 16:07:30 2016 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Tue May 31 16:07:30 2016 [Z0][VMM][I]: ExitCode: 0
Tue May 31 16:07:30 2016 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Tue May 31 16:07:30 2016 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy ‘/var/lib/one//datastores/105/19/deployment.0’ ‘node01’ 19 node01
Tue May 31 16:07:30 2016 [Z0][VMM][I]: error: Failed to create domain from /var/lib/one//datastores/105/19/deployment.0
Tue May 31 16:07:30 2016 [Z0][VMM][I]: error: unsupported configuration: readonly ide disks are not supported
I managed to do so, but it looks like you set the CDROM as read-only,
you shouldn’t.
Regards.
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
I not set CD-ROM as read-only. I can’t install OS. Upload iso to DS. Create “datablock” image and template. It’s all.
Hi
I was checking the new oned.conf from ONED Configuration — OpenNebula 5.0.2 documentation and the new conf file provided by the rpm package, I found this change in DATASTORE_MAD section:
DATASTORE_MAD = [
EXECUTABLE = “one_datastore”,
ARGUMENTS = “-t 15 -d dummy,fs,lvm,ceph,dev,iscsi_libvirt,vcenter -s shared,ssh,ceph,fs_lvm”
]
Are these aguments ok?, it seems that ceph appears twice and vcenter has also a parameter, is that done on purpose or its just a typo?
btw the new 5.0 release looks great! 
Thanks a lot!
Alvaro