All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Bucicoiu <mihai.bucicoiu@trust.cased.de>
To: George Dunlap <dunlapg@umich.edu>
Cc: Ian Jackson <Ian.Jackson@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: osstest - howTo
Date: Tue, 16 Jul 2013 11:08:34 +0200	[thread overview]
Message-ID: <51E50D92.4010104@trust.cased.de> (raw)
In-Reply-To: <CAFLBxZbbHGtAtfobGa98Xo2Pxt0dFx-qXycGEB089i7nTboZaA@mail.gmail.com>

On 7/15/2013 4:33 PM, George Dunlap wrote:
> On Mon, Jul 15, 2013 at 1:08 PM, Mihai Bucicoiu
> <mihai.bucicoiu@trust.cased.de> wrote:
>> Hi,
>>
>> I'm trying to figure out how can Xen be tested. As far as I could find out
>> there is a testing framework that can be used, called osstest. [1]
> What are you trying to accomplish with the testing?
This is a very good question that I don't really have an answer to it.
>> But this, if I got it right,this requires a reboot of the tested host, while
>> we need to test Xen without rebooting it. There seems also to be a local
>> version ("OSSTEST_JOB=<job> ./ts-debian-install host=bedbug" from README)
>> but it only tests if a VM can be started.
> Why do you not want to reboot the host?
We are building a live update system for Xen, and after the patch is 
applied we do not want to reboot, we want to test if everything is still 
functional. We tested our system in the sense the the VMs are still 
running and the services (we only tried a simple web server) inside the 
VM still run. New VMs can also be started. But the question is are the 
other services that Xen provide still available (e.g., can dom0 do all 
the hypercalls in a proper way).

- Mihai

  reply	other threads:[~2013-07-16  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 12:08 osstest - howTo Mihai Bucicoiu
2013-07-15 14:33 ` George Dunlap
2013-07-16  9:08   ` Mihai Bucicoiu [this message]
2013-07-16  9:14     ` Wei Liu
2013-07-16  9:16       ` Mihai Bucicoiu
2013-07-17  9:53         ` George Dunlap
2013-07-17 10:01 ` Ian Campbell
2013-07-17 10:33   ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51E50D92.4010104@trust.cased.de \
    --to=mihai.bucicoiu@trust.cased.de \
    --cc=Ian.Jackson@citrix.com \
    --cc=dunlapg@umich.edu \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.