From: "Gémes Géza" <geza.gemes@gmail.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, George Dunlap <george.dunlap@citrix.com>
Subject: Re: [raisin] Using cirros for tests???
Date: Wed, 15 Mar 2017 21:13:25 +0100 [thread overview]
Message-ID: <d0b660ed-e475-3177-6f3b-c3d8baeb0e47@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1703131251180.3116@sstabellini-ThinkPad-X260>
2017-03-13 22:31 keltezéssel, Stefano Stabellini írta:
> On Thu, 9 Mar 2017, Gémes Géza wrote:
>> Hi,
>>
>> I've sent my last couple of days on trying to make raisin tests run on
>> different distributions. Tried Ubuntu 16.04, Ubuntu 14.04, CentOS 7 and CentOS
>> 6.8 so far. The tests fail because of different reasons on these
>> distributions:
>>
>> 1. bussybox-pv passes on Ubuntu 14.04 and 16.04, it fails on Centos 7 (there
>> is no bussybox in the default repositories, enabling EPEL might be too
>> intrusive), it also fails on Centos6 (I haven't track that down yet)
>>
>> 2. bussybox-hvm fails on all the tried distros. On Ubuntu and CentOS 7 (all of
>> them have grub 2.0.2) grub fails to find the filesystem with stage2 and at
>> boot stops at grub-rescue> with no partitions recognized. In addition on
>> Ubuntu 16.04 the lopartsetup script fails to set up the partition correctly,
>> which could be quite easily get fixed.
>>
>> My idea is that instead of trying to fix the tests (and to continue to do so
>> for upcoming distro releases) we could start using cirros images for the
>> tests.
>>
>> I'd start transforming the existing tests to use cirros if you agree with the
>> proposal.
> We need both pv and hvm tests, because they test different hypervisor
> functionalities. But it would be fine to replace our hand crafted VM
> filesystem based on busybox with Cirros. In other words, it is fine by
> me, but we need both cirros-pv and cirros-hvm tests.
Hi Stefano,
I've started creating the cirros tests. So far have three pv tests:
separate-kernel, pygrub and pvgrub2. On Ubuntu 14.04 with xen installed
by raisin the pygrub test fail due to pygrub failure to find a python
lib, which I'm going to investigate later on. The other two tests pass.
I'll prepare patches soon.
Cheers,
Geza
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-03-15 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 16:43 [raisin] Using cirros for tests??? Gémes Géza
2017-03-13 21:31 ` Stefano Stabellini
2017-03-15 20:13 ` Gémes Géza [this message]
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=d0b660ed-e475-3177-6f3b-c3d8baeb0e47@gmail.com \
--to=geza.gemes@gmail.com \
--cc=george.dunlap@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).