Tuesday Jul 26, 2016

Oracle VM 3.4: export Oracle VM Pool informations into a csv report file

The target of this script is to build-up a report of all Oracle VM Servers (OVS) managed by an Oracle VM Manager on one or more Oracle VM Pools. Following script is compatible with Oracle VM 3.2, 3.3 and 3.4.

The output obtained is one csv file containing all the main informations related to all the OVS; the table will be composed of:

  • Oracle VM Pool Name
  • Oracle VM Server Name (hostname)
  • dom0 UUID (Unique identified of dom0)
  • Management IP (IP Address used on Management Network)
  • Status (Running/Stopped/Maintenance)
  • Memory (Amount of total Memory available on the physical system)
  • dom0 Memory (Amount of Memory dedicated to dom0)
  • Socket (number of Socket(s) enabled on the system)
  • Processors (number of CPUs available on the system - core/threads)
  • CPU Compatibility Group (Group to evaluate the possible live-migration of VMs between Host systems)
  • Oracle VM Release (detailed release of Oracle VM Server installed)
  • Manufacturer/Model (Manufacturer and model of the physical server)
  • Server Architecture (x86-64 or Sparc)
  • Hypervisor (OVM/Xen or LDOM)
  • Bios Release (Release of the BIOS installed on the system)
  • Bios Release Date (Release date of the BIOS installed)

Here you can find an example of output generated by this script:

At the same time, into the same package, you'll find an updated version of "ExportVmDetails" script (presented here on June, 29th 2016).

The script has been improved with following enhancements:

  • Status of VM added to the report
  • vDisk space used is now available also on Oracle VM 3.2 Release
  • vDisk space max is now available also on Oracle VM 3.2 Release
  • Physical Disk size is now available also on Oracle VM 3.2 Release

The updated package can be downloaded here.

Please pay attention of file "README_FIRST.txt" that will describe, step-by-step, how to install these scripts and have them configured in a couple of minutes.

As always, feedback and comments are really appreciated.

Friday Jul 15, 2016

Oracle VM VirtualBox 5.1: VBoxBugReport & NVMHCI emulator

On July, 12th Oracle VM VirtualBox 5.1 has been announced.

This new release introduced new capabilities to the product and, between them, I'm going to speak on a couple:

  • Bug Reporting Helper tool
  • NVMHCI storage controller emulation

"Bug Reporting Helper" is a command line utility able to collect all the logs and informations related to:

  • Host operating system where VirtualBox has been installed
  • Guest Virtual Machine logs (specific to one VM or for all VMs)

Syntax of this utility is very simple and we can obtain all the options available by executing the command with the "-h" option:

This type of utility can be very helpful while asking assistance on possible issues on VirtualBox; the same utility can be used to collect logs for "Service Requests" opened by VirtualBox Enterprise Customers on My Oracle Support or, at the same time, used to upload logs to community point-of-contact like VirtualBox Forum or VirtualBox Bug Ticketing System.

"NVMHCI Storage controller emulation" introduced the option to have emulated Flash-Storage on a VirtualBox VM:

This new option allows to emulate different solutions based on systems with NVMe (Non-Volatile Memory express).

Between them, for example, we can also find Oracle solutions like Oracle Exalytics.

Comments and feedback, as usual, are appreciated. 

Wednesday Jun 29, 2016

Oracle VM 3.4: export VMs details into a csv report file (ExportVmDetails)

==> An updated release of this script is available here <==

The idea of this script came up more than one time in the past and target is to build-up a report of all VMs managed by an Oracle VM Manager on one or more Oracle VM Pools. Following script is compatible with Oracle VM 3.2, 3.3 and 3.4.

The output obtained is one csv file containing all the main informations related to all the VMs; the table will be composed of: 
  • Virtual Machine UUID (Unique ID)
  • Virtual Machine Name
  • Memory (amount of RAM allocated to the VM)
  • Max Memory (Max amount of RAM allocable to the VM without reboot)
  • Processors (Number of vCPUs)
  • Max Processors (Max number of vCPUs)
  • Processor Capacity (Increase or decrease the percentage to which the virtual CPUs can receive scheduled time)
  • Processor Priority (The higher the priority, the more physical CPU cycles are given to the virtual machine)
  • High Availability (H/A enabled or not for the VM)
  • Operating System (Descriptive field related to the OS installed on the VM)
  • VM Type (PVM, HVM or HVM with PV drivers)
  • Repository (Oracle VM Repository where vm.cfg file resides)
  • *vDisk Space Used (Disk space used by the vm - virtual-disks)
  • *vDisk Space Max (Disk space allocable by the vm - virtual-disks)
  • *Physical Disk size (Disk space used by the vm - physical-disks)

* = these options are only available on Oracle VM releases 3.3 and 3.4; on Oracle VM 3.2 release these three columns will be valued with "N/A".

The script, the install package and README file can be downloaded here

Installation process is pretty easy; just execute command "install.sh" and follow the interactive shell:

Last message of the installation package should be something similar to:

"OVMCLI Session successfully connected with key-based authentication!!!

like in the following picture:

The script "ExportVmDetails", available for default under path "/usr/local/bin" won't need any option and will supply an output similar to the following picture:

Obviously the same approach can be taken to generate further csv reports with all the informations related to an Oracle VM Pool.

As usually, feedback and comments are very welcome. 

If you need further informations, please visit:

Tuesday Jun 28, 2016

Oracle VM 3.2.11 maintenance release now available!

Preamble: it's important to remember that today our latest Oracle VM 3.4 release has to be chosen while installing new environments and/or creating new architectures; that said, it's also important to know that we just released a maintenance update for Oracle VM 3.2 to deliver improved performance, security patches and to provide bug-fixes. 

Oracle VM 3.2.11 updates are available for download from My Oracle Support. Oracle VM Server packages are also available from the Oracle Unbreakable Linux Network (Oracle VM Server 3.2 Latest Channel). The patch updates include all the cumulative bug fixes that have been integrated since the base 3.2.1 release.  

Oracle VM 3.2.11 Download Information

· Oracle VM Server for x86 3.2.11 server ISO, search patch ID 16410428; and will also available from ULN - https://linux.oracle.com

· Oracle VM Manager 3.2.11 upgrade, search patch ID 16410417

· Oracle VM Agent 3.2.11 for SPARC, search patch ID 16694949

The software is also available from the Oracle Software Delivery Cloud

Review the download instructions at: http://www.oracle.com/technetwork/server-storage/vm/downloads/index.html

Additional Information

New customers are encouraged to use the latest Oracle VM 3.4, release that introduces further features, improved stability and performance.

Oracle VM documentation is available on the Oracle Technology Network (OTN):http://www.oracle.com/technetwork/server-storage/vm/documentation/index.html.

For the latest information, best practices white papers and webinars, please visit http://oracle.com/virtualization.

Friday Jun 03, 2016

Oracle VM 3.4: identify orphan vdisks on repositories (find-vorph)

Identify orphan virtual-disks on repository can be a nightmare; mostly if you have more repositories and many virtual-disks to check.

  • What is it an orphan virtual-disk ?
==> An orphan virtual-disk is a virtual-device that is not associated to any virtual machine <==
  • Why do I need to identify them ?

==> Identify orphan virtual-disk can help to reclaim disk-space available on Oracle VM Repositories <==

So, like on many other examples, scripting with Oracle VM CLI can help us; here you can find a script able to identify all orphan virtual-disks; and you have two different options:

  • verify orphan virtual-disk on a specific repository
  • verify orphan virtual-disk on all repositories managed by Oracle VM Manager

The script is also able to supply the amount of disk-space recovered by deleting all orphan virtual-disks on a specific repository; output of the script will also present the Oracle VM CLI commands to execute to remove all orphan virtual-disks.

Script is compatible, able to interact and has been tested with:

  • Oracle VM 3.2
  • Oracle VM 3.3
  • Oracle VM 3.4 

Here you can find some execution examples:

  • Script executed on a specific repository (orphan virtual-disks identified and recoverable space specified)

  • Script executed on a specific repository (no orphan virtual-disks)

  • Script executed on all repositories (no repository specified)

To proceed to the setup pay attention to the README file attached to the download. 

Feedback and comments are, as always, appreciated. 


Simon Coter (@scoter80) is a Principal Product Manager for Oracle VM and VirtualBox.



« August 2016