[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-cim] Testing with own kernel and ramdisk


  • To: <xen-cim@xxxxxxxxxxxxxxxxxxx>
  • From: "Szymanski, Lukasz K" <Lukasz.Szymanski@xxxxxxxxxx>
  • Date: Thu, 2 Aug 2007 15:48:36 -0400
  • Delivery-date: Thu, 02 Aug 2007 12:46:11 -0700
  • List-id: xen-cim mailing list <xen-cim.lists.xensource.com>
  • Thread-index: AcfS1mTabMaaf/SGTYWFFOFHO9TO7gCW1WkA
  • Thread-topic: Testing with own kernel and ramdisk

Jim -

Just a thought from our discussion this morning ... If a user does not
wish to run with the xm test kernel and ramdisk, but has their own
ramdisk and kernel they are willing to expose to the rigors of our
testing - then that should work too.  I think that would solve your
problem of not wanting to have xm-test but having vm's on a box.  So the
logic would go something like this:

If (no xm-test)
        Do you want to run xm-test?
        If (no)
                Do you want to run this test with your own vm's?
                If (yes)
                        Enter kernel, ramdisk, disk
                If (no)
                        Just run extrinsics.

Thoughts?  If we go with this approach, does the 'make runtest' solution
still make the most sense?

Luke

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.