Re: [Qemu-devel] Win2K8 32-bit Mix of IDE and SCSI assertion

[Michal Novotny]

On 08/06/2010 01:17 PM, Paolo Bonzini wrote:
> 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).

Well then, this could be the thing.

> > 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
>
> :)

Yeah, you're right. It's accessing this file nevertheless the reason I 
confused it was that when I put the argument of some known error code 
for OS, it's returning the OS error but when it's not known it's 
returning the MySQL error.

I wrote a small program to confirm it. It has this line: printf("err 
134: %s\n", strerror(134)); and when I run this program it's returning:

$./ax
err 134: Unknown error 134
$

so that's why I got confused, sorry.
> > Is your patch for LSI SCSI controller applied in the upstream ?
>
> Yes, Gerd already pointed to it.
>
> Paolo

Well then, then if the patch is applied I don't know what else could 
caused it since those registers were really closely connected to the 
invalid phase jumps.

Michal

--
Michal Novotny<address@hidden>, RHCE
Virtualization Team (xen userspace), Red Hat