I ran QEMU on Valgrind for several hours last night, including a couple
of boot-shutdown cycles of RedHat8, and lots of file copying/deletion
in the guest to get the qcow2 image up to 8GB and generally cause a lot
of disk IO. I got no memory errors whatsoever from Valgrind and got no
filesystem
J M Cerqueira Esteves <[EMAIL PROTECTED]> wrote:
> herbie hancock wrote:
> > Hello, i had also a reproducible disk crash:
> > info of the last good image, size is about 3,5GB
> >
> > I never experienced such a bad problem with qemu before, maybe it is a
> > problem with qcow2 format ?
>
>
herbie hancock wrote:
> Hello, i had also a reproducible disk crash:
> info of the last good image, size is about 3,5GB
>
> I never experienced such a bad problem with qemu before, maybe it is a
> problem with qcow2 format ?
After the problems with qcow2 images which I reported here a few weeks
Julian Seward wrote:
>
> Something similar happened to me. At first I thought it was a hardware
> (host) problem and so do not have good details - this is from memory.
I had trouble (disk access errors when installing Debian/mipsel) with a
5 GB qcow2 image with only some hundred MB of payload. I
Something similar happened to me. At first I thought it was a hardware
(host) problem and so do not have good details - this is from memory.
- 0.9.0, binary build from qemu.org
- i386 openSUSE 10.2 host
- RedHat 8 guest
- .qcow2 image, max size 8GB
- using the Accelerator but not -kernel-kqemu
