From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: QEMU devel <qemu-devel@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] [Qemu test report] Autotest | Job ID: 1997 "Upstream qemu.git sanity 10-30-2011 00:05:01" | Status: 1 Completed | Success Rate: 53.85 %
Date: Mon, 31 Oct 2011 00:01:07 -0200 [thread overview]
Message-ID: <4EAE0163.20303@redhat.com> (raw)
In-Reply-To: <201110301350.p9UDowl9028582@int-mx01.intmail.prod.int.phx2.redhat.com>
Hi folks, sending this to QEMU devel to inform the current problems we
are able to reproduce on the current master branch.
So, qemu.git is presenting problems as of latest master. None of the
problems mentioned is happening on qemu-kvm.git.
-------- Original Message --------
Subject: Autotest | Job ID: 1997 "Upstream qemu.git sanity 10-30-2011
00:05:01" | Status: 1 Completed | Success Rate: 53.85 %
Date: Sun, 30 Oct 2011 09:50:58 -0400
From: kvm-autotest@redhat.com
To: lmr@redhat.com, crosa@redhat.com
Job ID: 1997
Job name: Upstream qemu.git sanity 10-30-2011 00:05:01
Summary: Host: virtlab208.virt.bos.redhat.com Status: Completed
Status: 1 Completed
Execution time (HH:MM:SS): 05:44:38
User tests executed: 26
User tests passed: 14
User tests failed: 12
User tests success rate: 53.85 %
Failures:
Test Name
Status Reason
kvm.qemu-git.virtio_blk.smp2.virtio_net.Win7.64.sp1.unattended_install.cdrom
FAIL Timeout elapsed while waiting for install to finish [context:
waiting for installation to finish]
^ Here, the windows install timeout happened due to the floppy
regression introduced by 212ec7baa28cc9d819234fed1541fc1423cfe3d8. We
did try Kevin's patches and they did not fix the issue.
kvm.qemu-git.virtio_blk.smp2.virtio_net.RHEL.6.1.x86_64.migrate.tcp
FAIL Unhandled LoginError: Client said 'connection refused'
(output: 'ssh: connect to host 192.168.122.129 port 22: Connection
refused\n') [context: logging into 'vm1']
kvm.qemu-git.virtio_blk.smp2.virtio_net.RHEL.6.1.x86_64.reboot
FAIL Unhandled LoginError: Client said 'connection refused'
(output: 'ssh: connect to host 192.168.122.25 port 22: Connection
refused\n') [context: logging into 'vm1']
kvm.qemu-git.virtio_blk.smp2.virtio_net.RHEL.6.1.x86_64.migrate.unix
FAIL Unhandled LoginError: Client said 'connection refused'
(output: 'ssh: connect to host 192.168.122.3 port 22: Connection
refused\n') [context: logging into 'vm1']
kvm.qemu-git.virtio_blk.smp2.virtio_net.RHEL.6.1.x86_64.migrate.exec
FAIL Unhandled MonitorSocketError: Could not send monitor
command 'info migrate' ([Errno 32] Broken pipe) [context:
migrating 'vm1']
^ All of those failures happened due to qemu segfaults during the
migration process. I believe Luiz had a patch to possibly fix this
migration issue, so copying him.
The segfaults generated core dumps, which we would be happy to scp to a
public box, if someone is interested in them.
Cheers,
Lucas
next parent reply other threads:[~2011-10-31 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201110301350.p9UDowl9028582@int-mx01.intmail.prod.int.phx2.redhat.com>
2011-10-31 2:01 ` Lucas Meneghel Rodrigues [this message]
2011-10-31 11:47 ` [Qemu-devel] [Qemu test report] Autotest | Job ID: 1997 "Upstream qemu.git sanity 10-30-2011 00:05:01" | Status: 1 Completed | Success Rate: 53.85 % Luiz Capitulino
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=4EAE0163.20303@redhat.com \
--to=lmr@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@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 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.