[Xen-users] Crashes on image file backed VMs

[Andre Fucs <afucs2001@xxxxxxxxx>]

Hi

I am running Xen 4.5.1 (arch built from AUR) and noticed that none of my Linux or Windows VMs backed by image files (qcow2, raw, you name it) will crash after a few seconds to minutes:

sudo coredumpctl info 2756

           PID: 2756 (qemu-system-i38)

           UID: 0 (root)

           GID: 0 (root)

        Signal: 7 (BUS)

     Timestamp: Fri 2015-12-18 21:44:25 AEDT (12min ago)

  Command Line: /usr/lib/xen/bin/qemu-system-i386 -xen-domid 6 -chardev socket,id=libxl-cmd,path=/run/xen/qmp-libxl-6,server,nowait -mon chardev=libxl-cmd,mode=control -nodefaults -name test.hvm -vnc 127.0.0.1:0,to=99 -display none -serial pty -device cirrus-vga,vgamem_mb=8 -boot order=cd -smp 2,maxcpus=2 -device rtl8139,id=nic0,netdev=net0,mac=00:aa:aa:aa:aa:aa -netdev type=tap,id=net0,ifname=vif6.0-emu,script=no,downscript=no -machine xenfv -m 760 -drive file=/mnt/test.raw,if=ide,index=0,media=disk,format=raw,cache=writeback

    Executable: /usr/lib/xen/bin/qemu-system-i386

 Control Group: /user.slice/user-1000.slice/session-c2.scope

          Unit: session-c2.scope

         Slice: user-1000.slice

       Session: c2

     Owner UID: 1000 (xafucs)

       Boot ID: 923836bc18c248a084ed286a6c9c7d5d

    Machine ID: 0812fdb213c0401e8e53e442256a04e0

      Hostname: xdemo

       Message: Process 2756 (qemu-system-i38) of user 0 dumped core.

                Stack trace of thread 2756:

                #0  0x000055b2a1e155d3 blk_handle_requests (qemu-system-i386)

                #1  0x000055b2a1d99fb3 aio_bh_poll (qemu-system-i386)

                #2  0x000055b2a1d99bdc aio_poll (qemu-system-i386)

                #3  0x000055b2a1d99de3 aio_ctx_dispatch (qemu-system-i386)

                #4  0x00007fef67d30dc7 g_main_context_dispatch (libglib-2.0.so.0)

                #5  0x000055b2a1eba35e glib_pollfds_poll (qemu-system-i386)

                #6  0x000055b2a1f2bab2 main_loop (qemu-system-i386)

                #7  0x00007fef6420f610 __libc_start_main (libc.so.6)

                #8  0x000055b2a1d997b9 _start (qemu-system-i386)

                Stack trace of thread 2761:

                #0  0x00007fef6607faf7 do_sigwait (libpthread.so.0)

                #1  0x00007fef6607fb6d sigwait (libpthread.so.0)

                #2  0x000055b2a1f30fcc qemu_dummy_cpu_thread_fn (qemu-system-i386)

                #3  0x00007fef660764a4 start_thread (libpthread.so.0)

                #4  0x00007fef642d813d __clone (libc.so.6)

                Stack trace of thread 2762:

                #0  0x00007fef6607faf7 do_sigwait (libpthread.so.0)

                #1  0x00007fef6607fb6d sigwait (libpthread.so.0)

                #2  0x000055b2a1f30fcc qemu_dummy_cpu_thread_fn (qemu-system-i386)

                #3  0x00007fef660764a4 start_thread (libpthread.so.0)

                #4  0x00007fef642d813d __clone (libc.so.6)

                Stack trace of thread 2964:

                #0  0x00007fef6607e4a5 do_futex_wait (libpthread.so.0)

                #1  0x00007fef6607e56f __new_sem_wait_slow (libpthread.so.0)

                #2  0x00007fef6607e622 sem_timedwait (libpthread.so.0)

                #3  0x000055b2a200341e qemu_sem_timedwait (qemu-system-i386)

                #4  0x000055b2a1f02a8c worker_thread (qemu-system-i386)

                #5  0x00007fef660764a4 start_thread (libpthread.so.0)

                #6  0x00007fef642d813d __clone (libc.so.6)

                Stack trace of thread 2963:

                #0  0x00007fef6607e4a5 do_futex_wait (libpthread.so.0)

                #1  0x00007fef6607e56f __new_sem_wait_slow (libpthread.so.0)

                #2  0x00007fef6607e622 sem_timedwait (libpthread.so.0)

                #3  0x000055b2a200341e qemu_sem_timedwait (qemu-system-i386)

                #4  0x000055b2a1f02a8c worker_thread (qemu-system-i386)

                #5  0x00007fef660764a4 start_thread (libpthread.so.0)

                #6  0x00007fef642d813d __clone (libc.so.6)

                Stack trace of thread 2758:

                #0  0x00007fef6607efad read (libpthread.so.0)

                #1  0x00007fef65b2655a read_all (libxenstore.so.3.0)

                #2  0x00007fef65b26676 read_message (libxenstore.so.3.0)

                #3  0x00007fef65b26f86 read_thread (libxenstore.so.3.0)

                #4  0x00007fef660764a4 start_thread (libpthread.so.0)

                #5  0x00007fef642d813d __clone (libc.so.6)

                Stack trace of thread 2961:

                #0  0x00007fef6607e4a5 do_futex_wait (libpthread.so.0)

                #1  0x00007fef6607e56f __new_sem_wait_slow (libpthread.so.0)

                #2  0x00007fef6607e622 sem_timedwait (libpthread.so.0)

                #3  0x000055b2a200341e qemu_sem_timedwait (qemu-system-i386)

                #4  0x000055b2a1f02a8c worker_thread (qemu-system-i386)

                #5  0x00007fef660764a4 start_thread (libpthread.so.0)

                #6  0x00007fef642d813d __clone (libc.so.6)

                Stack trace of thread 2769:

                #0  0x00007fef6607c07f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)

                #1  0x000055b2a20032d4 qemu_cond_wait (qemu-system-i386)

                #2  0x000055b2a1f1c587 vnc_worker_thread_loop (qemu-system-i386)

                #3  0x000055b2a1f1c967 vnc_worker_thread (qemu-system-i386)

                #4  0x00007fef660764a4 start_thread (libpthread.so.0)

                #5  0x00007fef642d813d __clone (libc.so.6)

                Stack trace of thread 2958:

                #0  0x00007fef6607e4a5 do_futex_wait (libpthread.so.0)

                #1  0x00007fef6607e56f __new_sem_wait_slow (libpthread.so.0)

                #2  0x00007fef6607e622 sem_timedwait (libpthread.so.0)

                #3  0x000055b2a200341e qemu_sem_timedwait (qemu-system-i386)

                #4  0x000055b2a1f02a8c worker_thread (qemu-system-i386)

                #5  0x00007fef660764a4 start_thread (libpthread.so.0)

                #6  0x00007fef642d813d __clone (libc.so.6)

has anyone seem something like that?

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users