All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valtteri Kiviniemi <mailinglists@dataproof.fi>
To: xen-devel@lists.xensource.com
Subject: Re: Which disk backend to use in domU?
Date: Fri, 11 Jun 2010 20:53:30 +0300	[thread overview]
Message-ID: <4C12781A.7060603@dataproof.fi> (raw)
In-Reply-To: <4C127584.6070801@dataproof.fi>

Hi,

Ah, misunderstanding sorry, you were talking about disk images :)

Valtteri Kiviniemi kirjoitti:
> Hi,
> 
> I am also using phy: with LVM-partitions, and I also would like to know 
> if there is a better or more preferred way.
> 
> - Valtteri Kiviniemi
> 
> Neobiker kirjoitti:
>> Hello Jeremy,
>>
>>
>> Jeremy Fitzhardinge wrote:
>>> Using phy: in your config file?  That really isn't recommended 
>>> because it
>>> has poor integrity; the writes are buffered in dom0 so writes can be
>>> reordered or lost on crash, and the guest filesystem can't maintain any
>>> of its own integrity guarantees.
>>>
>>> tap:aio: is more resilient, since the writes go directly to the device
>>> without buffering.
>>
>> Do you mean that using tap:aio with a disk.image is prefered against 
>> using
>> phy: with LVM-device?
>>
>> Best Regards
>> Jens Friedrich aka Neobiker (www.neobiker.de)
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-06-11 17:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 21:02 Xen pv_ops dom0 2.6.32.13 issues greno
2010-06-09 22:37 ` Jeremy Fitzhardinge
2010-06-09 23:27 ` greno
2010-06-09 23:37   ` Jeremy Fitzhardinge
2010-06-11 17:06     ` Which disk backend to use in domU? Neobiker
2010-06-11 17:42       ` Valtteri Kiviniemi
2010-06-11 17:53         ` Valtteri Kiviniemi [this message]
2010-06-11 18:11           ` Neobiker
2010-06-14 10:49             ` Jeremy Fitzhardinge
2010-06-14 10:57               ` Daniel Stodden
2010-06-14 11:01               ` Pasi Kärkkäinen

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=4C12781A.7060603@dataproof.fi \
    --to=mailinglists@dataproof.fi \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.