From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH] tests: Fix ubuntu.i386 image initialization
Date: Thu, 22 Mar 2018 08:07:38 -0500 [thread overview]
Message-ID: <df8ac9bf-0239-ba4c-bbe4-d79d73c7ad50@redhat.com> (raw)
In-Reply-To: <20180322034753.6301-1-famz@redhat.com>
On 03/21/2018 10:47 PM, Fam Zheng wrote:
> The apt-get commands we run through ssh expect certain features of the
> tty, and refuses to work if /dev/null is used. It is ugly, but easy to
> satisfy.
>
> Actually, there is no reason to hide the output. It just makes things
> harder to diagnose. We can always redirect in the Makefile, so don't do
> it conditionally here.
>
> Reported-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> tests/vm/basevm.py | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
This got the .img initialization a lot further, although the log still
shows that there is still a communication glitch early on:
...
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
cloud-initramfs-growroot
0 upgraded, 1 newly installed, 0 to remove and 25 not upgraded.
Need to get 5,570 B of archives.
After this operation, 23.6 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/universe i386
cloud-initramfs-growroot all 0.27ubuntu1.5 [5,570 B]
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 5,570 B in 1s (4,554 B/s)
Selecting previously unselected package cloud-initramfs-growroot.
...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
acpica-tools autotools-dev binutils build-essential cpp cpp-5 debhelper
device-tree-compiler dh-strip-nondeterminism dpkg-dev g++ g++-5 gcc gcc-5
...
But despite that glitch, the subsequent package updates succeeded, and
the VM eventually progressed to compiling qemu instead of dying early. So
Tested-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-03-22 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 3:47 [Qemu-devel] [PATCH] tests: Fix ubuntu.i386 image initialization Fam Zheng
2018-03-22 8:33 ` Philippe Mathieu-Daudé
2018-03-22 13:07 ` Eric Blake [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=df8ac9bf-0239-ba4c-bbe4-d79d73c7ad50@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.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).