kvm does not generate a system uuid by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
goget-ubuntu-touch (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
qemu-kvm (Ubuntu) |
Won't Fix
|
High
|
Serge Hallyn | ||
testdrive (Ubuntu) |
Fix Released
|
Low
|
Andres Rodriguez | ||
whoopsie-daisy (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Booting ubuntu_
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/
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
ProcVersionSign
Uname: Linux 3.2.0-19-
NonfreeKernelMo
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/
MachineType: LENOVO 2516CTO
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=fr_CA.UTF8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
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.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 2516CTO
dmi.product.
dmi.sys.vendor: LENOVO
tags: | added: patch |
Changed in testdrive (Ubuntu): | |
assignee: | nobody → Andres Rodriguez (andreserl) |
importance: | Undecided → Low |
status: | New → In Progress |
Changed in testdrive (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in whoopsie-daisy (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in goget-ubuntu-touch (Ubuntu): | |
assignee: | Dimitri John Ledkov (xnox) → nobody |
This is of importance to the crash database. We want to offer users the ability to review crashes they have submitted, and we do this by passing a SHA-512 hash of the system UUID when submitting crashes.