From: Avi Kivity <avi@redhat.com>
To: "Alberto Treviño" <alberto@byu.edu>,
"Anthony Liguori" <anthony@codemonkey.ws>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] kvm-78 release
Date: Thu, 06 Nov 2008 18:11:57 +0200 [thread overview]
Message-ID: <4913174D.8050706@redhat.com> (raw)
In-Reply-To: <200811021352.48970.alberto@byu.edu>
Alberto Treviño wrote:
> On Sunday 02 November 2008 01:39:41 am Avi Kivity wrote:
>
>> Changes from kvm-77:
>> - merge qemu-svn
>> - new live migration implementation
>> - migration fixes
>>
>
> Can anyone tell me if these migration fixes now allow for live migration of
> VM's with more than 4 GB of RAM?
>
I think the new migration code fixes this. Anthony, is this right?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-06 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 7:39 [ANNOUNCE] kvm-78 release Avi Kivity
2008-11-02 20:52 ` Alberto Treviño
2008-11-06 16:11 ` Avi Kivity [this message]
2008-11-06 16:20 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2008-11-05 2:00 john cooper
2008-11-05 9:09 ` Avi Kivity
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=4913174D.8050706@redhat.com \
--to=avi@redhat.com \
--cc=alberto@byu.edu \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
/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