From: Oguz Bektas <o.bektas@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-qemu] update to QEMU 5.1
Date: Thu, 20 Aug 2020 13:56:56 +0200 [thread overview]
Message-ID: <20200820115656.GA14512@gaia.proxmox.com> (raw)
In-Reply-To: <20200820094836.GB298249@gaia.proxmox.com>
hi,
i've tested:
- live migration
- backup & restore (also with pbs)
- snapshot & rollback
- pending changes
- disk hotplugging
unfortunately couldn't test pci passthrough because of conflicts in
iommu groups on my machine.
Tested-by: Oguz Bektas <o.bektas@proxmox.com>
On Thu, Aug 20, 2020 at 11:48:36AM +0200, Oguz Bektas wrote:
> i'm testing this on my cluster, will update once i'm done
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
next prev parent reply other threads:[~2020-08-20 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 8:42 Stefan Reiter
2020-08-20 9:48 ` Oguz Bektas
2020-08-20 11:56 ` Oguz Bektas [this message]
2020-08-20 11:58 ` [pve-devel] applied: " Thomas Lamprecht
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=20200820115656.GA14512@gaia.proxmox.com \
--to=o.bektas@proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox