This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] GPLPV and LUN's on a storage

To: Klaus Steinberger <klaus.steinberger@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] GPLPV and LUN's on a storage
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Tue, 27 Oct 2009 00:07:41 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 26 Oct 2009 15:08:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AE5B22F.6060305@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4AE5B22F.6060305@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Mon, Oct 26, 2009 at 03:29:03PM +0100, Klaus Steinberger wrote:
> Hi,
> just a information:
> I did run into big troubles running Windows HVM VM's with GPLPV driver on 
> LUN's on a storage system. (In my case a CX4 from EMC).
> What happened:
> After e.g. Windows Updates the VM's rendered unbootable
> What causes this:
> My assumption is:  Windows boots from the Qemu device until some point 
> there it switches over from the QEMU device to the PV System device. But 
> qemu uses the VM Caches from DOM0, but with the PV driver the LUN is 
> accessed directly.
> Now it happens after a reboot that the VM caches are preloaded from 
> previous boots, but the LUN contains really already different data. This 
> leds to curious crashes.
> My solution to avoid that:
> Dropping caches with "echo 1 > /proc/sys/vm/drop_caches"
> This could also be added to the xm definition files, as they are just 
> python:
> os.system('echo 1 >/proc/sys/vm/drop_caches');
> I already had a similar problem with paravirtualized linux VM's on a Redhat 
> System and external LUN's. pygrub did show old boot entrys, different from 
> what the VM has. Same reason. Dropping vm_caches in this case also helped. 
> There is currently a bug open on redhat's Bug Tracker.
> Bug #466681
> They work on direct I/O for at least pygrub.

Do you use phy:, file: or tap:aio: ? 

-- Pasi

Xen-users mailing list