WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-changelog

[Xen-changelog] [xen-unstable] xm-test, acm: Use xvda* device name inste

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] [xen-unstable] xm-test, acm: Use xvda* device name instead of sdb* device inside guest domain.
From: Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 26 Feb 2007 03:50:36 -0800
Delivery-date: Mon, 26 Feb 2007 04:20:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User kfraser@xxxxxxxxxxxxxxxxxxxxx
# Date 1172481230 0
# Node ID 2d3ceb082114bdc77e53b5710a076a1827254710
# Parent  bfd188f0cf5d7f31cfd52b56603ebff4e07841a9
xm-test, acm: Use xvda* device name instead of sdb* device inside guest domain.
Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>
---
 tools/xm-test/tests/security-acm/06_security-acm_dom_block_attach.py |   18 
+++++-----
 1 files changed, 9 insertions(+), 9 deletions(-)

diff -r bfd188f0cf5d -r 2d3ceb082114 
tools/xm-test/tests/security-acm/06_security-acm_dom_block_attach.py
--- a/tools/xm-test/tests/security-acm/06_security-acm_dom_block_attach.py      
Mon Feb 26 09:12:55 2007 +0000
+++ b/tools/xm-test/tests/security-acm/06_security-acm_dom_block_attach.py      
Mon Feb 26 09:13:50 2007 +0000
@@ -43,7 +43,7 @@ except ConsoleError, e:
 
 # Explicitly label the 1st resource
 ACMLabelResource(resource1, resourcelabel1)
-block_utils.block_attach(domain, resource1, "sdb1")
+block_utils.block_attach(domain, resource1, "xvda1")
 
 try:
        run1 = console.runCmd("cat /proc/partitions")
@@ -54,10 +54,10 @@ ACMLabelResource(resource2, resourcelabe
 ACMLabelResource(resource2, resourcelabel2)
 #Cannot call block_attach here since we legally may fail the command
 status, output = traceCommand("xm block-attach %s %s %s w" %
-                               (domain.getName(), resource2, "sdb2" ))
+                               (domain.getName(), resource2, "xvda2" ))
 
 for i in range(10):
-    if block_utils.get_state(domain, "sdb2") == 4:
+    if block_utils.get_state(domain, "xvda2") == 4:
         break
     time.sleep(1)
 
@@ -72,11 +72,11 @@ domain.closeConsole()
 # Stop the domain (nice shutdown)
 domain.stop()
 
-if not re.search("sdb1",run1["output"]):
-    FAIL("Labeled device 'sdb1' is not actually connected to the domU")
+if not re.search("xvda1",run1["output"]):
+    FAIL("Labeled device 'xvda1' is not actually connected to the domU")
 
-if not re.search("sdb1",run2["output"]):
-    FAIL("Labeled device 'sdb1' has disappeared?!")
+if not re.search("xvda1",run2["output"]):
+    FAIL("Labeled device 'xbvda1' has disappeared?!")
 
-if re.search("sdb2",run2["output"]):
-    FAIL("Labeled device 'sdb2' is connected to the domU but should not be")
+if re.search("xvda2",run2["output"]):
+    FAIL("Labeled device 'xvda2' is connected to the domU but should not be")

_______________________________________________
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] xm-test, acm: Use xvda* device name instead of sdb* device inside guest domain., Xen patchbot-unstable <=