From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: live saving of domU Date: Wed, 10 May 2006 20:32:59 -0500 Message-ID: <4462944B.3090407@us.ibm.com> References: <871640aa0605100840t14a9f9deqf5c9be99f56917b7@mail.gmail.com> <20060510163213.GF4954@leeni.uk.xensource.com> <44621BDD.9060401@us.ibm.com> <871640aa0605101206h2742f0d1o70c356bad797747c@mail.gmail.com> <44623F3A.9040308@us.ibm.com> <871640aa0605101829m1736134bi9c167a6f74f8aeb8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <871640aa0605101829m1736134bi9c167a6f74f8aeb8@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jayesh Salvi Cc: xen-devel , Ewan Mellor List-Id: xen-devel@lists.xenproject.org Jayesh Salvi wrote: > > On a little different note, it is amusing to note that VMWare has to > do some tricky dance of junction point/snapshot, etc. May be VMWare > virtual machines principally use loopback file systems for virtual > disk - that's why they have problem in viewing the same file system > from dom0 and domU (consistent or inconsistent). Xen allows devices to > be used as boot disk. Hence the file system is visible from dom0 and > domU the same way (at least RO from dom0). I might be wrong. Correct > me if you think so. Keep in mind, VMware and Xen are very different. VMware emulates a device. That device has state, I presume that they need to get their device into a well defined state. We don't have this problem as we can just detach and reattach all of the devices. Of course, VMware is advantaged in that they use shadowing paging so they do not have any of the canonicalization problems that we have. Regards, Anthony Liguori > > -- > Jayesh > ------------------------------------------------------------------------ > Everything you can imagine is real