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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
