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-bugs] [Bug 625] New: xm-test FAIL: 02_block_attach_file_device_pos.

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 625] New: xm-test FAIL: 02_block_attach_file_device_pos.test
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 19 Apr 2006 13:34:15 -0700
Delivery-date: Wed, 19 Apr 2006 13:34:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: xm-test FAIL: 02_block_attach_file_device_pos.test
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: dbarrera@xxxxxxxxxx
                CC: pl@xxxxxxxxxx, hohnbaum@xxxxxxxxxx

xm-test 02_block_attach_file... is failing. 

Change 9668. 

IBM HS20 Blade, x86_64 and other xSeries boxes, including IA32.

** Test 02_block_attach_file_device_pos started at Wed Apr 19 07:06:17 2006
CDT[dom0] Running `xm create /tmp/xm-test.conf'
Using config file "/tmp/xm-test.conf".
Started domain 02_block_attach_file_device_pos-1145448377
Console executing: ['/usr/sbin/xm', 'xm', 'console',
[02_block_attach_file_device_pos-1145448377] Sending `input'
[02_block_attach_file_device_pos-1145448377] Sending `ls'
[02_block_attach_file_device_pos-1145448377] Sending `echo $?'
[dom0] Running `xm block-attach 02_block_attach_file_device_pos-1145448377
file:/dev/ram1 sdb2 w'

[02_block_attach_file_device_pos-1145448377] Sending `cat /proc/partitions'
[02_block_attach_file_device_pos-1145448377] Sending `echo $?'
[dom0] Running `xm shutdown 02_block_attach_file_device_pos-1145448377'

REASON: Device is not actually connected to the domU
FAIL: 02_block_attach_file_device_pos.test


This is the console output from the domain to which a block device is being

@%@%> Registering block device major 8
register_blkdev: cannot get major 8 for sd
xen_blk: can't get major 8 with name sd
vbd vbd-2066: 19 xlvbd_add at /local/domain/0/backend/vbd/4/2066

@%@%> cat /proc/partitions
major minor  #blocks  name


Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 625] New: xm-test FAIL: 02_block_attach_file_device_pos.test, bugzilla-daemon <=