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-devel

[Xen-devel] [PATCH] [XM-TEST] Add support for VMX guests in xm-test

To: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] [XM-TEST] Add support for VMX guests in xm-test
From: Daniel Stekloff <dsteklof@xxxxxxxxxx>
Date: Wed, 07 Dec 2005 14:04:38 -0800
Cc: Dan Smith <danms@xxxxxxxxxx>, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>
Delivery-date: Wed, 07 Dec 2005 22:05:29 +0000
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Here's a patch to add initial support for vmx guests in xm-test. This
patch applies to changeset 8272:b215584242c4.

I've run it on both vmx and non-vmx guests. I got the following report
for running with vmx enabled:

Xm-test execution summary:
  PASS:  69
  FAIL:  23
  XPASS: 0
  XFAIL: 1
 
 
Details:
 
 FAIL: 01_block_attach_device_pos
         Device is not actually connected to the domU
 
 FAIL: 02_block_attach_file_device_pos
         Device is not actually connected to the domU
 
 FAIL: 04_block_attach_device_repeatedly_pos
         Device is not actually attached to domU
 
 FAIL: 05_block_attach_and_dettach_device_repeatedly_pos
         Failed to attach block device /proc/partitions does not show
that!
 
 FAIL: 09_block_attach_and_dettach_device_check_data_pos
         Failed to dettach block device /proc/partitions still showing
that!
 
 FAIL: 03_block-list_anotherbd_pos
         Failed to verify that block dev is attached on DomainU
 
 FAIL: 06_block-list_checkremove_pos
         hda1 still shown in block-list after detach!
 
 FAIL: 01_block-destroy_btblock_pos
         domU reported block device still connected!
 
 FAIL: 02_block-destroy_rtblock_pos
         block-detach failed to detach block device
 
 FAIL: 05_block-destroy_byname_pos
        Unknown reason
 
 FAIL: 06_block-destroy_check_list_pos
         block-list does not show that hda1 was removed
 
 FAIL: 11_create_concurrent_pos
         [4] Failed to attach console to 11_create_4
 
 FAIL: 12_create_concurrent_stress_pos
         Timed out waiting for console
 
 FAIL: 13_create_multinic_pos
         (9 nics) Console didn't respond probably crashed!
 
 FAIL: 01_memset_basic_pos
         The DomU command 'cat /proc/xen/balloon' failed.
 
 FAIL: 03_memset_random_pos
         Invalid domU meminfo line
 
 FAIL: 01_network_attach_pos
         Network device is not actually connected to domU
 
 FAIL: 02_network_attach_detach_pos
         Network device is not actually connected to domU
 
XFAIL: 03_network_attach_detach_multiple_pos
         Network device is not actually connected to domU
 
 FAIL: 01_shutdown_basic_pos
         Guest domain failed to shutdown
 
 FAIL: 02_sysrq_sync_pos
         Sync SysRq not delivered
 
 FAIL: 03_sysrq_withreboot_pos
         sysrq failed with 256 != 0

Attachment: xm-test-add-vmx.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel