From: Paolo Bonzini <pbonzini@redhat.com>
To: Michal Novotny <minovotn@redhat.com>
Cc: Peter Lieven <pl@dlh.net>, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Win2K8 32-bit Mix of IDE and SCSI assertion
Date: Fri, 06 Aug 2010 13:17:51 +0200 [thread overview]
Message-ID: <4C5BEF5F.90809@redhat.com> (raw)
In-Reply-To: <4C5BED29.2080801@redhat.com>
On 08/06/2010 01:08 PM, Michal Novotny wrote:
>> Aug 5 20:43:06 172.21.59.142 kvm: Aborted
>> Aug 5 20:43:06 172.21.59.142 kvm errno=134
>
> when I tried to seach some information on errno=134 (based on
> assumption it's a standard OS error)
I don't know where exactly the output is coming from, but in this case
134 is not really an errno, but a value returned from waitpid. It
indicates that kvm exited with SIGABRT (SIGABRT = 6, plus bit 7 is set).
> I used perror but it returned some kind of MySQL error code: $ perror
> 134 MySQL error code 134: Record was already deleted (or record file
> crashed) $
You're confusing the C standard function perror with some random
executable you have on your system:
$ yum whatprovides '*/perror'
mysql-server-5.1.45-2.fc13.x86_64 : The MySQL server and related files
Repo : fedora
Matched from:
Filename : /usr/bin/perror
:)
> Is your patch for LSI SCSI controller applied in the upstream ?
Yes, Gerd already pointed to it.
Paolo
next prev parent reply other threads:[~2010-08-06 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 20:58 [Qemu-devel] Win2K8 32-bit Mix of IDE and SCSI assertion Peter Lieven
2010-08-06 8:45 ` [Qemu-devel] " Gerd Hoffmann
2010-08-06 11:08 ` [Qemu-devel] " Michal Novotny
2010-08-06 11:17 ` Paolo Bonzini [this message]
2010-08-06 11:30 ` Michal Novotny
2010-08-06 14:37 ` Peter Lieven
2010-08-06 14:36 ` Michal Novotny
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=4C5BEF5F.90809@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=minovotn@redhat.com \
--cc=pl@dlh.net \
--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).