Your message dated Fri, 14 Aug 2015 09:04:00 +0200
with message-id <20150814070400.ga7...@bogon.m.sigxcpu.org>
and subject line Re: Bug#683313: libvirtd8) does not generate valid RFC 4122
UUIDs
has caused the Debian Bug report #683313,
regarding libvirtd8) does not generate valid RFC 4122 UUIDs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
683313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-bin
Version: 0.9.12-3
When viewing the contents of the /etc/libvirt/qemu/*.xml files, the UUID
strings should be conformant to RFC 4122, which states that the version
bit should be one of 1, 2, 3, 4, or 5 and the variant bit should be one of
8, 9, a, or b. However, I have the following UUIDs for VMs, none of which
are valid: http://ae7.st/p/5z7.
According to a discussion I had in #virt on OFTC:
<eblake> right now, libvirt is just using a random-number generator on
every single bit
<eblake> since rfc 4122 has restrictions on certain bits, then there's
obviously a patch waiting to be written
Because the UUIDs are randomly generated, they should be version 4 strings
then. Thus, they should have the format of:
XXXXXXXX-XXXX-4XXX-YXXX-XXXXXXXXXXXX
where '4' is statically set, and 'Y' should be one of '8', '9', 'a', or
'b'. The /proc/sys/kernel/random/uuid random number generator could work as
a source for those running the Linux kernel.
While it may not be technically hurting anything at this point, it should
still conform to the RFCs.
--
. o . o . o . . o o . . . o .
. . o . o o o . o . o o . . o
o o o . o . . o o o o . o o o
pgpQ_10Fozrhd.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: libvirt/1.2.9-9
Hi,
On Mon, Jul 30, 2012 at 11:28:57AM -0600, Aaron Toponce wrote:
> Package: libvirt-bin
> Version: 0.9.12-3
>
> When viewing the contents of the /etc/libvirt/qemu/*.xml files, the UUID
> strings should be conformant to RFC 4122, which states that the version
> bit should be one of 1, 2, 3, 4, or 5 and the variant bit should be one of
> 8, 9, a, or b. However, I have the following UUIDs for VMs, none of which
> are valid: http://ae7.st/p/5z7.
>
> According to a discussion I had in #virt on OFTC:
>
> <eblake> right now, libvirt is just using a random-number generator on
> every single bit
> <eblake> since rfc 4122 has restrictions on certain bits, then there's
> obviously a patch waiting to be written
>
> Because the UUIDs are randomly generated, they should be version 4 strings
> then. Thus, they should have the format of:
>
> XXXXXXXX-XXXX-4XXX-YXXX-XXXXXXXXXXXX
>
> where '4' is statically set, and 'Y' should be one of '8', '9', 'a', or
> 'b'. The /proc/sys/kernel/random/uuid random number generator could work as
> a source for those running the Linux kernel.
>
> While it may not be technically hurting anything at this point, it should
> still conform to the RFCs.
Very true. Fixed in Jessie already.
-- Guido
--- End Message ---
