It should be the same as the VM UUID, which is a pseudo-random UUID.
On 12/10/13 10:59 AM, "Bryan Whitehead" wrote:
>(Sorry, meant to say Cloudstack 3.0.x boxes are running CentOS6.2
>still...)
>
>
>On Tue, Dec 10, 2013 at 10:59 AM, Bryan Whitehead
>wrote:
>
>> In all cases these are CentOS boxe
(Sorry, meant to say Cloudstack 3.0.x boxes are running CentOS6.2 still...)
On Tue, Dec 10, 2013 at 10:59 AM, Bryan Whitehead wrote:
> In all cases these are CentOS boxes. The 3.0.x boxes are still in
> CentOS6.x land but the 4.1 Cloudstack boxes are 6.4+updates (as of 6months
> ago).
>
> I don'
In all cases these are CentOS boxes. The 3.0.x boxes are still in CentOS6.x
land but the 4.1 Cloudstack boxes are 6.4+updates (as of 6months ago).
I don't know if the UUID internal to the VM is generated by cloudstack,
libvirtd, or qemu-kvm. Since the mac addresses have never had a collision I
sus
What is the OS of the KVM host?
I believe vm uuids are type 4 uuids and are hence independent of time.
http://docs.oracle.com/javase/6/docs/api/java/util/UUID.html
On 12/9/13 12:01 PM, "Bryan Whitehead" wrote:
>I have 3 independent Cloudstack installs. One is 3.0.x and the others are
>4.1.0.
>
I have 3 independent Cloudstack installs. One is 3.0.x and the others are
4.1.0.
Using KVM (i'm only using KVM so I don't have anything else for
comparison), between 3.0.x and 4.1.0 I'm getting instances with UUID's that
are the same.
I get the UUID by running this on the console (CentOS):
dmide
