From: Fam Zheng <famz@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-devel@nongnu.org, berrange@redhat.com,
"Alex Bennée" <alex.bennee@linaro.org>,
pbonzini@redhat.com, stefanha@redhat.com,
"Cleber Rosa" <crosa@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
eblake@redhat.com, "Kamil Rytarowski" <kamil@netbsd.org>
Subject: Re: [Qemu-devel] [PATCH v3 03/10] tests: Add vm test lib
Date: Tue, 22 Aug 2017 22:00:00 +0800 [thread overview]
Message-ID: <20170822140000.GF3210@lemon> (raw)
In-Reply-To: <51a26b62-8ce8-6733-908b-3481a110663e@amsat.org>
On Tue, 08/22 08:19, Philippe Mathieu-Daudé wrote:
> > + def add_source_dir(self, data_dir):
> > + name = "data-" + hashlib.sha1(data_dir).hexdigest()[:5]
> > + tarfile = os.path.join(self._tmpdir, name + ".tar")
> > + logging.debug("Creating archive %s for data dir: %s", tarfile, data_dir)
> > + subprocess.check_call(["tar", "--exclude-vcs",
>
> --exclude-vcs-ignores will process .gitignore,
Sounds useful, thanks!
> you can also list with 'git ls-files',
> or generate tarball with scripts/make-release
They won't handle submodules, will they?
>
> > + "--exclude=tests/vm/*.img",
> > + "--exclude=tests/vm/*.img.*",
> > + "--exclude=*.d",
> > + "--exclude=*.o",
> > + "--exclude=docker-src.*",
> > + "-cf", tarfile, '.'], cwd=data_dir,
> > + stdin=self._devnull, stdout=self._stdout)
> > + self._data_args += ["-drive",
> > + "file=%s,if=none,id=%s,cache=writeback,format=raw" % \
> > + (tarfile, name),
> > + "-device",
> > + "virtio-blk,drive=%s,serial=%s,bootindex=1" % (name, name)]
>
> what about mounting readonly via '-device virtio-9p-pci' (not using
> tarball)?
>
It doesn't work. That way an out-of-tree build is required in the guest, but if
an in-tree build has been done in host side, out-of-tree builds fail. Also the
performance will be much worse, I believe: untar is sequential read, and after
that everything is in the guest page cache; with virtio-9p, there will be a
large amount of "random" requests between guest and host.
Fam
next prev parent reply other threads:[~2017-08-22 14:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 4:41 [Qemu-devel] [PATCH v3 00/10] tests: Add VM based build tests (for non-x86_64 and/or non-Linux) Fam Zheng
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 01/10] gitignore: Ignore vm test images Fam Zheng
2017-08-22 11:07 ` Philippe Mathieu-Daudé
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 02/10] qemu.py: Add "wait()" method Fam Zheng
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 03/10] tests: Add vm test lib Fam Zheng
2017-08-22 11:19 ` Philippe Mathieu-Daudé
2017-08-22 12:33 ` Kamil Rytarowski
2017-08-22 14:00 ` Fam Zheng [this message]
2017-08-22 14:23 ` Philippe Mathieu-Daudé
2017-08-28 17:18 ` Fam Zheng
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 04/10] tests: Add ubuntu.i386 image Fam Zheng
2017-08-24 15:28 ` Cleber Rosa
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 05/10] tests: Add FreeBSD image Fam Zheng
2017-08-24 15:33 ` Cleber Rosa
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 06/10] tests: Add NetBSD image Fam Zheng
2017-08-23 15:15 ` Kamil Rytarowski
2017-08-24 9:25 ` Fam Zheng
2017-08-24 15:37 ` Cleber Rosa
2017-08-25 8:54 ` Fam Zheng
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 07/10] tests: Add OpenBSD image Fam Zheng
2017-08-24 15:34 ` Cleber Rosa
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 08/10] Makefile: Add rules to run vm tests Fam Zheng
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 09/10] MAINTAINERS: Add tests/vm entry Fam Zheng
2017-08-22 4:41 ` [Qemu-devel] [PATCH v3 10/10] tests: Add README for vm tests Fam Zheng
2017-08-22 13:38 ` Stefan Hajnoczi
2017-08-22 14:13 ` Fam Zheng
2017-08-22 7:53 ` [Qemu-devel] [PATCH v3 00/10] tests: Add VM based build tests (for non-x86_64 and/or non-Linux) no-reply
2017-08-22 13:45 ` Stefan Hajnoczi
2017-08-22 13:58 ` Paolo Bonzini
2017-08-22 14:23 ` Kamil Rytarowski
2017-08-22 14:29 ` Fam Zheng
2017-08-22 14:33 ` Kamil Rytarowski
2017-08-24 9:27 ` Fam Zheng
2017-08-24 15:06 ` Cleber Rosa
2017-08-25 9:25 ` Fam Zheng
2017-08-25 10:01 ` Paolo Bonzini
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=20170822140000.GF3210@lemon \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=kamil@netbsd.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).