Another hint: I've never seens this using qemu 1.3.1
Stefan
Am 13.02.2013 08:49, schrieb Stefan Priebe - Profihost AG:
Hi Paolo,
sadly no luck. A VM crashed again.
[ ~]# addr2line -e /usr/lib/debug/usr/bin/kvm -f 24040c
virtio_scsi_command_complete
hw/virtio-scsi.c:429
Same point
Hi,
could this be this one?
commit 47a150a4bbb06e45ef439a8222e9f46a7c4cca3f
Author: Paolo Bonzini pbonz...@redhat.com
Date: Thu Jan 10 15:49:08 2013 +0100
virtio-scsi: abort in-flight I/O when the device is reset
When the device is reset, the SCSI bus should also be reset so
that
Il 13/02/2013 09:19, Stefan Priebe - Profihost AG ha scritto:
Hi,
could this be this one?
commit 47a150a4bbb06e45ef439a8222e9f46a7c4cca3f
Author: Paolo Bonzini pbonz...@redhat.com
Date: Thu Jan 10 15:49:08 2013 +0100
virtio-scsi: abort in-flight I/O when the device is reset
Hi,
Am 13.02.2013 09:57, schrieb Paolo Bonzini:
Il 13/02/2013 09:19, Stefan Priebe - Profihost AG ha scritto:
Hi,
could this be this one?
commit 47a150a4bbb06e45ef439a8222e9f46a7c4cca3f
...
You can certainly try reverting it, but this patch is fixing a real bug.
Will try that. Yes but even
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
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
Il 13/02/2013 13:55, Stefan Priebe - Profihost AG ha scritto:
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
Hi paolo,
thanks for your work. Should i still apply your old patch to scsi-disk
or should i remove it?
Stefan
Am 13.02.2013 14:39, schrieb Paolo Bonzini:
Il 13/02/2013 13:55, Stefan Priebe - Profihost AG ha scritto:
Hi,
Am 13.02.2013 12:36, schrieb Paolo Bonzini:
Il 13/02/2013 10:07, Stefan
Output of cat:
[: ~]# cat /sys/block/*/device/scsi_disk/*/provisioning_mode
writesame_16
Stefan
Am 13.02.2013 14:39, schrieb Paolo Bonzini:
Il 13/02/2013 13:55, Stefan Priebe - Profihost AG ha scritto:
Hi,
Am 13.02.2013 12:36, schrieb Paolo Bonzini:
Il 13/02/2013 10:07, Stefan Priebe -
Hi,
I added this:
-trace events=/tmp/events,file=/root/qemu.123.trace
and put the events in the events file as i couldn't handle \n in my app
starting the kvm process. But even when doing an fstrim the trace file
stays at 24 bytes - is this correct?
Stefan
Am 13.02.2013 14:39, schrieb Paolo
Il 13/02/2013 15:30, Stefan Priebe - Profihost AG ha scritto:
I added this:
-trace events=/tmp/events,file=/root/qemu.123.trace
and put the events in the events file as i couldn't handle \n in my app
starting the kvm process. But even when doing an fstrim the trace file
stays at 24 bytes -
Hi,
Am 13.02.2013 16:24, schrieb Paolo Bonzini:
Il 13/02/2013 15:30, Stefan Priebe - Profihost AG ha scritto:
I added this:
-trace events=/tmp/events,file=/root/qemu.123.trace
and put the events in the events file as i couldn't handle \n in my app
starting the kvm process. But even when doing
Hi,
no VM crashed this morning.
Stefan
Am 13.02.2013 16:24, schrieb Paolo Bonzini:
Il 13/02/2013 15:30, Stefan Priebe - Profihost AG ha scritto:
I added this:
-trace events=/tmp/events,file=/root/qemu.123.trace
and put the events in the events file as i couldn't handle \n in my app
Hi,
thanks - i applied the patch to the latest master. I hope that this will
solve my issue. Will this one get integrated in 1.4 final?
Greets,
Stefan
Am 11.02.2013 15:42, schrieb Paolo Bonzini:
Il 11/02/2013 15:18, Stefan Priebe - Profihost AG ha scritto:
Some trace that a request was
Il 12/02/2013 14:46, Stefan Priebe - Profihost AG ha scritto:
Hi,
thanks - i applied the patch to the latest master. I hope that this will
solve my issue. Will this one get integrated in 1.4 final?
No, only 1.4.1 and 1.5 unfortunately. Let's give it a week for you to
test it.
Paolo
Hi Paolo,
sadly no luck. A VM crashed again.
[ ~]# addr2line -e /usr/lib/debug/usr/bin/kvm -f 24040c
virtio_scsi_command_complete
hw/virtio-scsi.c:429
Same point like last time:
static void virtio_scsi_command_complete(SCSIRequest *r, uint32_t status,
Hello list,
i've seen segfaults of the kvm process. Sadly i've no core dumps just
the line from dmesg:
kvm[26268]: segfault at c050 ip 7fcfc3465eac sp 7fffe85a0d00
error 4 in kvm[7fcfc3223000+3ba000]
Is it possible to get the function and some more details out of this
line? I've symbol
Il 11/02/2013 08:46, Stefan Priebe - Profihost AG ha scritto:
i've seen segfaults of the kvm process. Sadly i've no core dumps just
the line from dmesg:
kvm[26268]: segfault at c050 ip 7fcfc3465eac sp 7fffe85a0d00
error 4 in kvm[7fcfc3223000+3ba000]
Is it possible to get the
11.02.2013 11:46, Stefan Priebe - Profihost AG пишет:
Hello list,
i've seen segfaults of the kvm process. Sadly i've no core dumps just
the line from dmesg:
kvm[26268]: segfault at c050 ip 7fcfc3465eac sp 7fffe85a0d00
error 4 in kvm[7fcfc3223000+3ba000]
Is it possible to get the
On Mon, Feb 11, 2013 at 08:46:03AM +0100, Stefan Priebe - Profihost AG wrote:
i've seen segfaults of the kvm process. Sadly i've no core dumps just
the line from dmesg:
kvm[26268]: segfault at c050 ip 7fcfc3465eac sp 7fffe85a0d00
error 4 in kvm[7fcfc3223000+3ba000]
Is it possible to
Hi Stefan,
Am 11.02.2013 10:40, schrieb Stefan Hajnoczi:
On Mon, Feb 11, 2013 at 08:46:03AM +0100, Stefan Priebe - Profihost AG wrote:
i've seen segfaults of the kvm process. Sadly i've no core dumps just
the line from dmesg:
kvm[26268]: segfault at c050 ip 7fcfc3465eac sp 7fffe85a0d00
So it looks a bit like a race condition in the virtio-scsi driver.
Command got canceled and the completed or something like this.
Stefan
Am 11.02.2013 10:40, schrieb Stefan Hajnoczi:
On Mon, Feb 11, 2013 at 08:46:03AM +0100, Stefan Priebe - Profihost AG wrote:
i've seen segfaults of the kvm
Il 11/02/2013 10:48, Stefan Priebe - Profihost AG ha scritto:
Great thing! This is current git master.
[: ~]# addr2line -e /usr/lib/debug/usr/bin/kvm -f 242eac
virtio_scsi_command_complete
/opt/debianpackages/pve-squeeze.sources/pve-qemu-kvm/qemu-kvm/hw/virtio-scsi.c:429
static void
Hi,
Am 11.02.2013 13:48, schrieb Paolo Bonzini:
Il 11/02/2013 10:48, Stefan Priebe - Profihost AG ha scritto:
req-resp.cmd-status = status;
if (req-resp.cmd-status == GOOD) {
req-resp.cmd-resid = tswap32(resid);
} else {
req-resp.cmd-resid = 0;
sense_len
On Mon, Feb 11, 2013 at 2:08 PM, Stefan Priebe - Profihost AG
s.pri...@profihost.ag wrote:
Hi,
Am 11.02.2013 13:48, schrieb Paolo Bonzini:
Il 11/02/2013 10:48, Stefan Priebe - Profihost AG ha scritto:
req-resp.cmd-status = status;
if (req-resp.cmd-status == GOOD) {
Hi Stefan,
yes i use virtio-scsi-pci in all my guests. As it is the only one where
i can use fstrim from guest to storage with rbd ;-)
Stefan
Am 11.02.2013 14:21, schrieb Stefan Hajnoczi:
On Mon, Feb 11, 2013 at 2:08 PM, Stefan Priebe - Profihost AG
s.pri...@profihost.ag wrote:
Hi,
Am
Il 11/02/2013 14:35, Stefan Priebe - Profihost AG ha scritto:
Hi Stefan,
yes i use virtio-scsi-pci in all my guests. As it is the only one where
i can use fstrim from guest to storage with rbd ;-)
Can you check for anything suspicious in the kernel console output?
Paolo
Stefan
Am
Hi Paolo,
as the guest crashes i can't check the guest. On the host i just have
the segmentation fault line. Anything else is from the bootprocess or
enabling the tap device. So nothing suspicious.
Greets,
Stefan
Am 11.02.2013 14:56, schrieb Paolo Bonzini:
Il 11/02/2013 14:35, Stefan Priebe -
Il 11/02/2013 14:58, Stefan Priebe - Profihost AG ha scritto:
Hi Paolo,
as the guest crashes i can't check the guest. On the host i just have
the segmentation fault line. Anything else is from the bootprocess or
enabling the tap device. So nothing suspicious.
What about log from the serial
Hi,
nothing. What are you searching for?
Stefan
Am 11.02.2013 14:59, schrieb Paolo Bonzini:
Il 11/02/2013 14:58, Stefan Priebe - Profihost AG ha scritto:
Hi Paolo,
as the guest crashes i can't check the guest. On the host i just have
the segmentation fault line. Anything else is from the
Il 11/02/2013 15:02, Stefan Priebe - Profihost AG ha scritto:
Hi,
nothing. What are you searching for?
Some trace that a request was actually cancelled, but I think I believe
that. This seems to be the same issue as commits
1bd075f29ea6d11853475c7c42734595720c3ac6 (iSCSI) and
Hi,
Some trace that a request was actually cancelled, but I think I
believe
Ah but that must be in guest not on host right? How to grab that from
client when it is crashing?
that. This seems to be the same issue as commits
1bd075f29ea6d11853475c7c42734595720c3ac6 (iSCSI) and
Il 11/02/2013 15:18, Stefan Priebe - Profihost AG ha scritto:
Some trace that a request was actually cancelled, but I think I
believe
Ah but that must be in guest not on host right? How to grab that from
client when it is crashing?
Serial console could have something like sda: aborting
33 matches
Mail list logo
