X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=2019-kvm-forum%2F8000-resize-overview.html;h=6ac13ee2b7f172cdb74bc40b2a5424bcfe3e9ec4;hb=abde52a439efefe4371ad1f99d288e94163e1308;hp=58fc13033ee3b4b01fccbf917beaf484aff61a6a;hpb=d247f3c2cbab75f1f57ac54c6ee8d797d3c4c926;p=libguestfs-talks.git diff --git a/2019-kvm-forum/8000-resize-overview.html b/2019-kvm-forum/8000-resize-overview.html index 58fc130..6ac13ee 100644 --- a/2019-kvm-forum/8000-resize-overview.html +++ b/2019-kvm-forum/8000-resize-overview.html @@ -5,17 +5,52 @@
- Filler - need to demonstrate: +
+ | + | + |
---|---|---|
Pro | +
+
|
+
+
|
+
Con | +
+
|
+
+
|
+
- qemu -> (raw) -> qemu-nbd -> (qcow2) -> image.qcow2 - qemu -> (qcow2) -> qemu-nbd -> (raw) -> image.qcow2 -- - maybe a table of pro/con for each +
Can we merge the best of both worlds, giving the client access to + all qcow2 features, but permitting resize of the underlying file on + the host? +
-- Exposing qcow2 over NBD is too risky without resize, forcing - existing documentation to favor raw over NBD, even though this loses - out on the other benefits of qcow2. +
+ Clipart of computer http://clipart-library.com/clipart/76irEkBcK.htm