X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=2019-kvm-forum%2F8000-resize-overview.html;h=6ac13ee2b7f172cdb74bc40b2a5424bcfe3e9ec4;hb=6f34bcd5178f2622d9a15915ad2ca136525f318a;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 @@
Using qcow2 with NBD
- Filler - need to demonstrate:
+
+
+ |
+  |
+  |
+
+
+ | Pro |
+
+
+ - Matches existing use
+
- Server can start with thin qcow2, and grow it as needed
+ with guest activity
+
+ |
+
+
+ - Guest-visible size can be changed
+
- Backing files
+
- Dirty bitmap tracking
+
- Any other qcow2 features...
+
+ |
+
+
+ | Con |
+
+
+ - Guest size is fixed
+
- No access to qcow2 features from client
+
+ |
+
+
+ - Server file must be preallocated, or else guest hits ENOSPC
+
- Internal snapshots are unlikely to work
+
+ |
+
+
-
- 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