|
|
|
|
|
|
|
|
|
|
xen-changelog
[Xen-changelog] [xen-unstable] docs: vbd-interface.txt: correct behaviou
# HG changeset patch
# User Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
# Date 1297972085 0
# Node ID acec8a17879633d26e83b869f9db036a16ff74f2
# Parent 946962830c450eb471db342ead2ca55eee4084db
docs: vbd-interface.txt: correct behaviour for modern Linux pv-on-hvm
Modern PV on HVM kernels map hd* devices to corresponding xvd*.
Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
---
docs/misc/vbd-interface.txt | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff -r 946962830c45 -r acec8a178796 docs/misc/vbd-interface.txt
--- a/docs/misc/vbd-interface.txt Thu Feb 17 19:40:17 2011 +0000
+++ b/docs/misc/vbd-interface.txt Thu Feb 17 19:48:05 2011 +0000
@@ -114,9 +114,10 @@ in the guest.
in the guest.
For Linux HVM guests using PV-on-HVM drivers, users are recommended to
-supply as few hd* devices as possible and use pure xvd* devices for
-the rest. Modern PV-on-HVM drivers will map the hd* devices to
-/dev/xvdHDa etc.
+supply as few hd* devices as possible, and for the rest of the disks,
+to use pure xvd* devices starting at xvde. Modern PV-on-HVM drivers
+will map provided hd* devices to the corresponding /dev/xvd* (for
+example, hda is presented also as /dev/xvda).
Some Linux HVM guests with broken PV-on-HVM drivers do not cope
properly if both hda and hdc are supplied, nor with both hda and xvda,
_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-changelog] [xen-unstable] docs: vbd-interface.txt: correct behaviour for modern Linux pv-on-hvm,
Xen patchbot-unstable <=
|
|
|
|
|