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


[Xen-devel] about the virtual disk of DomU

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] about the virtual disk of DomU
From: "Yuming fang" <fangyuming.leo@xxxxxxxxx>
Date: Wed, 3 Sep 2008 18:22:00 +0800
Cc: samuel.thibault@xxxxxxxxxxxxx
Delivery-date: Wed, 03 Sep 2008 03:23:16 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type; bh=G65kLYne3zmtbtdntHjVk1V2AN4nkdKxDeoEfRSGuao=; b=fn/UPKls14XVO32pby3XyBzd+LcEdze/TOm4sVURYMCF6btZBYB+k1FHfRQlTfGfQe vGXmz2JigXUO6wIciGVwbBswEEAbds0Z3IzXDQgQl8qhfO+5UPBY075NVT4jB3YADorL aH6cA508BR7HGa2HsHQjH3ZEuT2eBvqo3iCWY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type; b=jn30M6puoTRiFCXpGd5Am7OGEstqnceYTlGU4t1Oiyld2YrtytqyfnBNM5d2653tIe ab2DtSQEhNWUcSHtNpN7u3hY5bYNTd2QYPt+x5FC6KWJalUwoZEAnyAtZbWd/Vw7Cwfr 1IT4HgwpgqhjYdD7lDNz3PIkiO/JCiU1EZJYc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi, everyone,
I want to modify the code of Xen to do some experiments about virtual disk. I know the disk access of domU is implemented through the communication between frontend driver and backend driver. But there are some problems for me to understand the virtual disk of Xen.
1. When the dom0 create a domU, how does it distribute disk space to the domU? Is the space sequential in the physical disk address?
2. After distributing the disk space for the domU, how is the virtual disk implemented? The virtual disk has its own logical address like virtual memory? As I know, the domU could not access the physical disk directly, is its file system built on 'virtual disk'?
3. In some documents about Xen, I found that I could add the disk scheduling algorithm in dom0. I think I could add the algorithm in backend driver of dom0 using the event channels, then in this way I could avoid modifying the disk scheduling algorithm in linux kernel. Do I understand correctly?
I would appreciate it if anyone could give me some help.
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] about the virtual disk of DomU, Yuming fang <=