Hi,
Am 13.02.2013 12:36, schrieb Paolo Bonzini:
> Il 13/02/2013 10:07, Stefan Priebe - Profihost AG ha scritto:
>>>>>>
>>>>>> commit 47a150a4bbb06e45ef439a8222e9f46a7c4cca3f
>> ...
>>>> You can certainly try reverting it, but this patch is fixing a real bug.
>> Will try that. Yes but even if it fixes a bug and raises another one
>> (kvm segfault) which is the worst one. It should be fixed.
>
> The KVM segfault is exposing a potential consistency problem. What is
> worse is not obvious. Also, it is happening at reset time if this is
> the culprit. Reset usually happens at places where no data loss is caused.
>
> Can you find out what the VM was doing when it segfaulted? (Or even,
> can you place the corefile and kvm executable somewhere where I can
> download it?)
Yes it was doing an fstrim -v / which resulted in:
[45648.453698] end_request: I/O error, dev sda, sector 9066952
> I'll prepare a test program that resets the adapter while doing I/O and
> try to reproduce it myself, in the meanwhile: can you grep the VM's
> /var/log/messages with kernel messages regarding the storage ("aborting
> cmd" and other things after it)?
Sadly not as i don't have acore dump. The kvm processes are started
through variuos Daemons and there seems no way to activate core dumps
for an already running process and i don't know which VM will crash next.
> If not, do your VMs reset themselves
> often for example?
No
> Can you reproduce it on non-rbd storage?
I don't have another storage type. ;-(
Stefan
