Opened 13 years ago
Closed 5 years ago
#7923 closed bug (no change required)
haiku's vmdks share their disk UUIDs
| Reported by: | jrabbit | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Build System | Version: | R1/Development |
| Keywords: | vmdk vmware | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
http://dev.haiku-os.org/browser/haiku/trunk/build/scripts/build_haiku_image#L246 we don't specify a uuid that http://dev.haiku-os.org/browser/haiku/trunk/src/tools/vmdkimage/vmdkimage.cpp will use so it uses the hardcoded one. This leads to issues if you want to use more than one nightly vmdk inside virtualbox, it will error unless you modify the UUID yourself.
Build-O-matic should also use whatever method is defined for the jamrule to specify a random UUID. (Or make this the default behaviour everywhere.)
Change History (2)
comment:1 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 5 years ago
| Resolution: | → no change required |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
After doing some research, the default behavior of having the same uuid is intentional. When you build Haiku yourself, you don't want virtualbox/vmware to complain that the UUID has changed everytime you run a build.
For the buildbots this would be different, but due to disk space concerns, the buildbots now only ship the anyboot image.