From: "Alwin Antreich" <ml-alwin@antreich.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-docs]: update link qemu documentation
Date: Wed, 10 Feb 2021 08:24:01 +0000 [thread overview]
Message-ID: <4c2f0c682f512ac71909755524315c95@antreich.com> (raw)
In-Reply-To: <20210210071616.26122-1-m.almalat@proxmox.com>
Hi Moayad,
February 10, 2021 8:16 AM, "Moayad Almalat" <m.almalat@proxmox.com> wrote:
> Signed-off-by: Moayad Almalat <m.almalat@proxmox.com>
> ---
> qm.adoc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qm.adoc b/qm.adoc
> index 333b2e6..1108908 100644
> --- a/qm.adoc
> +++ b/qm.adoc
> @@ -203,7 +203,7 @@ either the *raw disk image format* or the *QEMU image format*.
> format does not support thin provisioning or snapshots by itself, requiring
> cooperation from the storage layer for these tasks. It may, however, be up to
> 10% faster than the *QEMU image format*. footnote:[See this benchmark for details
> - http://events.linuxfoundation.org/sites/events/files/slides/CloudOpen2013_Khoa_Huynh_v3.pdf]
> +
> https://web.archive.org/web/20171027194629/https://events.linuxfoundation.org/sites/events/files/sli
> es/CloudOpen2013_Khoa_Huynh_v3.pdf]
> * the *VMware image format* only makes sense if you intend to import/export the
> disk image to other hypervisors.
It seems that the PDF still exists on the linuxfoundation site.
https://events.static.linuxfound.org/sites/events/files/slides/CloudOpen2013_Khoa_Huynh_v3.pdf
--
Cheers,
Alwin
next prev parent reply other threads:[~2021-02-10 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 7:16 Moayad Almalat
2021-02-10 7:51 ` Alwin Antreich
2021-02-10 8:24 ` Alwin Antreich [this message]
2021-02-11 6:58 ` Moayad Almalat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c2f0c682f512ac71909755524315c95@antreich.com \
--to=ml-alwin@antreich.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.