On Thu, Mar 24, 2011 at 1:38 PM, Conor Murphy
conor_murphy_v...@hotmail.com wrote:
#4 _int_free (av=value optimized out, p=0x7fa24c0009f0, have_lock=0) at
malloc.c:4795
#5 0x004a18fe in qemu_vfree (ptr=0x7fa24c000a00) at oslib-posix.c:76
#6 0x0045af3d in handle_aiocb_rw
Hi,
The content of aiocb
(gdb) print *aiocb
$1 = {common = {pool = 0x9aced0, bs = 0x1270230, cb = 0x45591f multiwrite_cb,
opaque = 0x7f54b0034f60, next = 0x0}, aio_fildes = 16,
{aio_iov = 0x7f54b006cd48, aio_ioctl_buf = 0x7f54b006cd48},
aio_niov = 17,
aio_nbytes = 65024, ev_signo = 12,
Hi,
I'm trying to write a vioblk driver for Solaris. I've gotten it to the point
where the devices are visible to Solaris and can create and FDISK partition
table and label it.
However, when I try an use newfs to create a filesystem, the VM crashes with the
following in the log
*** glibc
On Thu, Mar 24, 2011 at 11:55:06AM +, Conor Murphy wrote:
Hi,
I'm trying to write a vioblk driver for Solaris. I've gotten it to the point
where the devices are visible to Solaris and can create and FDISK partition
table and label it.
However, when I try an use newfs to create a
Forgot to mention that when I attached gdb to the qemu-kvm process before
running the newfs in the guest, the crash does not happen
Some sort of race condition?
Thanks,
Conor
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
Built with --enable-debug
Running under gdb gives
(gdb) where
#0 0x003d6da330c5 in raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x003d6da34a76 in abort () at abort.c:92
#2 0x003d6da6fcfb in __libc_message (do_abort=2,
fmt=0x3d6db5ea98 ***
glibc detected *** %s:
