[Bug 959308] Re: kvm does not generate a system uuid by default

[Serge Hallyn]

Quoting Evan Dandrea (evan.dandrea at canonical.com):
> Thanks for chasing this upstream.
> 
> No, an always-changing UUID defeats the purpose for us. We need a means
> of providing a key for users to see their crash data, persisted across
> installs.

A suggestion upstream was to use the uuid of the root filesystem.  I'm
not sure things can happen in the right order for that, but I can give
that a shot.

> > Not all platforms have a notion of platform UUID so as Ubuntu
> > supports more architectures, this problem would have to be dealt
> > with eventually.
> 
> Sure, and in architectures that do not have a platform UUID, such as
> ARM, we'll have to use a combination of other hardware identifiers (such
> as mac addresses) to fill the gap. See bug 963007 for one conversation
> on that.
> 
> But we ultimately need something that ties back to that machine.

If you're going to have to do that anyway, can you use the root fs uuid?
Would that supplant the need for this qemu patch?

You said our end-users need this.  Historically are all of the people
who will need this using either libvirt or testdrive?  Can we simply
hack testdrive to do this for us?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie-daisy in Ubuntu.
https://bugs.launchpad.net/bugs/959308

Title:
  kvm does not generate a system uuid by default

Status in “qemu-kvm” package in Ubuntu:
  Confirmed
Status in “whoopsie-daisy” package in Ubuntu:
  New

Bug description:
  Booting ubuntu_precise-desktop-i386.iso under kvm results in
  /var/log/upstart/whoopsie.log containing:

    Could not open the product uuid file.

  This is because by default kvm does not create a uuid by default. As
  such, there is no /sys/class/dmi/id/product_uuid file which whoopsie
  is attempting to read.

  kvm can generate a uuid by booting it with the --uuid option:

      kvm --uuid <uuid> ...

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: qemu-kvm 1.0+noroms-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
  Uname: Linux 3.2.0-19-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Mon Mar 19 14:05:46 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  KvmCmdLine:
   UID        PID  PPID  C    SZ   RSS PSR STIME TTY          TIME CMD
   james    30178 25913 18 168710 544196 0 13:51 pts/9    00:02:44 kvm -cdrom /home/james/.cache/testdrive/iso/ubuntu_precise-desktop-i386.iso -hda ubuntu-install-testing.kvm -net nic -net user -m 512
  MachineType: LENOVO 2516CTO
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-19-generic-pae root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro acpi_sleep=nonvs console=ttyUSB0,115200n8r console=tty quiet splash vt.handoff=7
  SourcePackage: qemu-kvm
  UpgradeStatus: Upgraded to precise on 2012-01-12 (67 days ago)
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET72WW (1.32 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/959308/+subscriptions