|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] maximum size of a block device in a domU
To: |
"Jayaraman, Bhaskar" <Bhaskar.Jayaraman@xxxxxxx> |
Subject: |
Re: [Xen-devel] maximum size of a block device in a domU |
From: |
Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx> |
Date: |
Tue, 22 Jul 2008 10:29:28 +0100 |
Cc: |
Sebastian Reitenbach <sebastia@xxxxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
Delivery-date: |
Tue, 22 Jul 2008 02:29:50 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<7F0FB2108857B5449321AEA91CF47903185A7C225C@xxxxxxxxxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
Mail-followup-to: |
Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, "Jayaraman, Bhaskar" <Bhaskar.Jayaraman@xxxxxxx>, Sebastian Reitenbach <sebastia@xxxxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
References: |
<20080721113021.2329B522AD@xxxxxxxxxxxxxxxxxxxxxxxxx> <7F0FB2108857B5449321AEA91CF47903185A7C225C@xxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.5.12-2006-07-14 |
Jayaraman, Bhaskar, le Tue 22 Jul 2008 13:18:23 +0800, a écrit :
> Hi, if I were using Xen 3.2.1 and above and if I were to direct assign a
> block device to a HVM guest will I still play by the rules mentioned below
> for maximum size of the device?
If by "direct assign" you mean setting disk = [ 'phy:sda4,hda,w' ] in
the config file, then yes you are still going through the IDE emulation,
limited to 2^48 sectors, i.e. 2^57B, plus the dom0 limitations (and the
HVM domU limitations of course).
Samuel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|