From: RW <kvm@tauceti.net>
To: Liang Guo <bluestonechina@gmail.com>
Cc: KVM mailing list <kvm@vger.kernel.org>
Subject: Re: Segfault
Date: Fri, 22 Jan 2010 15:45:30 +0100 [thread overview]
Message-ID: <4B59BA0A.3070008@tauceti.net> (raw)
In-Reply-To: <229432dd1001220635t5ba74dah982d5e5862035a0@mail.gmail.com>
Thanks for the hint but unfortunately every qemu command quits with
a segfault with this image:
scotty images # qemu-nbd nweb.img
Segmentation fault
[192749.840652] qemu-nbd[16052]: segfault at 7f88b1382000 ip
0000000000419492 sp 00007fff1e94f710 error 7 in qemu-nbd[400000+31000]
It's sad that a segfault of Qemu/KVM can corrupt a whole image
while the host itself was running without any problems as the
segfault happened. Seems that the data is lost. But thanks again
anyway!
Robert
On 01/22/10 15:35, Liang Guo wrote:
>
> 2010/1/20 RW <kvm@tauceti.net <mailto:kvm@tauceti.net>>
>
>
> > Is there any chance to get (some) data in the image back? Backup
> is a few weeks old :-(
> >
>
>
> you may use kvm-nbd or qemu-nbd to present kvm image as a NBD device, so
> that you can use nbd-client to access them. eg:
>
> kvm-nbd /vm/sid1.img
> modprobe nbd
> nbd-client localhost 1024 /dev/nbd0
> fdisk -l /dev/nbd0
>
> --
> Liang Guo
> http://bluestone.cublog.cn
next prev parent reply other threads:[~2010-01-22 14:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 21:40 Segfault Robert Wimmer
2010-01-20 10:34 ` Segfault RW
[not found] ` <229432dd1001220635t5ba74dah982d5e5862035a0@mail.gmail.com>
2010-01-22 14:45 ` RW [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-29 9:04 Segfault Andrew Tsykhonya
2017-12-31 8:59 ` Segfault Eric Sunshine
2018-01-02 10:11 ` Segfault Andrew Tsykhonya
2010-01-19 21:22 Segfault Robert Wimmer
2003-08-20 19:21 SEGFAULT Sandro Dangui
2003-08-15 18:05 Parsing multipart MIME Darío Mariani
2003-08-20 18:56 ` SEGFAULT John T. Williams
2003-08-20 19:35 ` SEGFAULT Glynn Clements
2002-06-26 1:56 SegFault Stas Sergeev
2002-06-26 3:11 ` SegFault Dan Egli
2002-06-26 3:14 ` SegFault Dan Egli
2002-06-25 20:13 SegFault Dan Egli
[not found] ` <3D18E115.9B5981C1@microsoft.com>
2002-06-26 0:56 ` SegFault Dan Egli
2002-06-26 1:02 ` SegFault Dan Egli
2001-09-05 21:53 segfault Jim Paris
2001-09-05 3:54 segfault Jim Paris
2001-09-05 17:15 ` segfault Florian Lohoff
2001-09-05 18:05 ` segfault Maciej W. Rozycki
2001-09-05 21:51 ` segfault Jim Paris
2001-09-13 18:59 ` segfault Jim Paris
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=4B59BA0A.3070008@tauceti.net \
--to=kvm@tauceti.net \
--cc=bluestonechina@gmail.com \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.