better upgrading machine types
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Server Guide |
Fix Released
|
Undecided
|
Christian Ehrhardt | ||
qemu (Ubuntu) |
Fix Released
|
High
|
Christian Ehrhardt |
Bug Description
Opening a bug in reference to the discussion at https:/
We should consider
- adding more documentation to https:/
- what are machine types TL;DR
- how to handle updates (why manually, best practise, ...)
- what to do when old type is no more around
- on qemu/libvirt upgrade scan for old-now-unsupported types and in case prompt the user to follow the documentation to consider updating as suitable for him
- that scanning might be hard and error prone so be careful
- we have a fallback by making the libvirt error more readable and by that it should show up whenever anything is started via libvirt (maybe even point to the doc)
Related branches
Changed in qemu (Ubuntu): | |
status: | New → Confirmed |
Changed in serverguide: | |
status: | New → Confirmed |
Changed in qemu (Ubuntu): | |
importance: | Undecided → High |
Changed in serverguide: | |
status: | Confirmed → Fix Committed |
Changed in serverguide: | |
status: | Fix Committed → Fix Released |
I further extended the doc on upgrading the type that I already had at the wiki: https:/ /wiki.ubuntu. com/QemuKVMMigr ation#Upgrade_ machine_ type
I adapted the serverguide to contain that and some related missing libvirt content which is now up for review at https:/ /code.launchpad .net/~paelzer/ serverguide/ serverguide- 16.04-enhance- virt/+merge/ 309849
Now looking into the experiment if there could be a more "readable" error message.