From: Paul Brook <paul@codesourcery.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Filip Navara <filip.navara@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] make windows notice media change
Date: Thu, 30 Jul 2009 13:27:12 +0100 [thread overview]
Message-ID: <200907301327.13715.paul@codesourcery.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907301307021.13932@kaball-desktop>
> Think about a sysadmin that kept his server running for the last X years
> in a VM using xen (or kvm) and now wants to upgrade his host.
> Is he supposed to reboot the VM as well?
> Are we seriously suggesting that everytime the hypervisor is upgraded
> the sysadmin must reboot all his VMs?
I'd expect that stable branches would make effort to not break the
snapshot/migration format.
I think it's entirely reasonable to require a VM reboot when you do a major
hypervisor upgrade. I'd expect this to be the least of your problems.
Paul
next prev parent reply other threads:[~2009-07-30 12:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 12:07 [Qemu-devel] [PATCH] make windows notice media change Gleb Natapov
2009-07-29 13:50 ` [Qemu-devel] [PATCH v2] " Gleb Natapov
2009-07-29 14:22 ` Avi Kivity
2009-07-29 14:21 ` Gleb Natapov
2009-07-29 14:44 ` Avi Kivity
2009-07-29 14:35 ` Filip Navara
2009-07-29 14:40 ` Gleb Natapov
2009-07-29 14:59 ` Stefano Stabellini
2009-07-29 19:11 ` Paul Brook
2009-07-29 19:18 ` Filip Navara
2009-07-29 19:24 ` Filip Navara
2009-07-29 19:34 ` Anthony Liguori
2009-07-29 19:52 ` Paul Brook
2009-07-29 19:56 ` Filip Navara
2009-07-29 20:05 ` Paul Brook
2009-07-29 20:14 ` Gleb Natapov
2009-07-30 12:14 ` Stefano Stabellini
2009-07-30 12:27 ` Paul Brook [this message]
2009-07-29 19:33 ` Anthony Liguori
2009-07-29 19:44 ` [Qemu-devel] " Juan Quintela
2009-07-29 20:05 ` Anthony Liguori
2009-07-29 20:09 ` Juan Quintela
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=200907301327.13715.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=filip.navara@gmail.com \
--cc=gleb@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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;
as well as URLs for NNTP newsgroup(s).