[libvirt] [PATCH v2]

Daniel P. Berrange berrange at redhat.com
Thu Apr 8 13:07:39 UTC 2010

On Thu, Apr 08, 2010 at 02:48:35PM +0200, Gerhard Stenzel wrote:
> On Thu, 2010-04-08 at 07:16 -0400, Stefan Berger wrote:
> > Ok, I'll adapt it for the TCK project.
> Some time ago, I started with some libvirt-tck scripts
> - 210-no-mac-spoofing.t
> - 220-no-ip-spoofing.t
> - 230-no-mac-broadcast.t
> - 240-no-arp-spoofing.t
> which try to perform an action (like mac spoofing etc) and verify that
> the filter is working.
> Since the test scripts need to log in to the guest/domain to perform
> that action, they have certain requirements on the guest/domain like
> root password, installed utilities etc.
> Of course, I have a local guest which satisfies those requirements, but
> what is the best way to solve this in a libvirt-tck way?

Currently none of the libvirt TCK tests need to login to the guest OS,
so we just auto-download & boot the basic Fedora anaconda install 
kernel+initrd and create a blank disk image.

Due to licensing complexity we can't distribute pre-built guest images
directly with the TCK. So I think what we'd want todo is to write a 
kickstart file that installs  a bare minimum Fedora guest OS, with a
pre-set root password, ssh daemon  active & known IP address. Then use
that with Rich Jones'  febootstrap script to create the guest image
at runtime. We'd cache the guest image between runs of the TCK, so the
overhead of febootstrap will only be seen the first time.

Then, your test scripts can simply request booting of a guest using this
minimal guest image instead of the normal anaconda kernel/initrd the TCK 

|: Red Hat, Engineering, London    -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org        -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

More information about the libvir-list mailing list