From: Eric Blake Date: Mon, 28 Oct 2019 13:57:08 +0000 (+0100) Subject: 8000: Add pro/con table. X-Git-Url: http://git.annexia.org/?a=commitdiff_plain;h=0f537a329d2a7988e276e14ec680f195f42e236a;p=libguestfs-talks.git 8000: Add pro/con table. --- diff --git a/2019-kvm-forum/8000-resize-overview.html b/2019-kvm-forum/8000-resize-overview.html index 58fc130..92356be 100644 --- a/2019-kvm-forum/8000-resize-overview.html +++ b/2019-kvm-forum/8000-resize-overview.html @@ -5,17 +5,48 @@

Using qcow2 with NBD

- Filler - need to demonstrate: + + + + + + + + + + + + + + + + +
XXX: better header...qemu -> (raw) -> qemu-nbd -> (qcow2) -> image.qcow2qemu -> (qcow2) -> qemu-nbd -> (raw) -> image.qcow2
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 - -

- 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. +

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?

diff --git a/2019-kvm-forum/style.css b/2019-kvm-forum/style.css index e33ca15..360d5be 100644 --- a/2019-kvm-forum/style.css +++ b/2019-kvm-forum/style.css @@ -270,3 +270,12 @@ p.attribution { text-align: right; font-size: 10pt; } + +/* Tables */ +table { + border-collapse: collapse; +} + +table, th, td { + border: 1px solid black; +}