Re: [Xen-devel] Qemu-dm crash with 4.9-unstable

[Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>]

On 02/17/2017 12:43 PM, Jan Beulich wrote:
>>>> On 17.02.17 at 11:27, <rcojocaru@xxxxxxxxxxxxxxx> wrote:
>> I've installed Xen 4.9-unstable (master branch, commit
>> 1e88db4701d6e2d00c04795e6aacaea942b617e6) on an old Ubuntu workhorse
>> machine, and when using quemu-xen-traditional, quemu-dm crashes with
>> this backtrace:
>>
>> # gdb /usr/lib/xen/bin/qemu-dm core
>> Reading symbols from /usr/lib/xen/bin/qemu-dm...done.
>> [New LWP 16753]
>> [New LWP 16758]
>> [New LWP 16759]
>> [New LWP 16834]
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> Core was generated by `/usr/lib/xen/bin/qemu-dm -d 19 -domain-name
>> win7_32 -vnc 0.0.0.0:0 -vncunused -'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0  __memcpy_sse2_unaligned () at
>> ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
>> 36      ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such
>> file or directory.
>> (gdb) bt
>> #0  __memcpy_sse2_unaligned () at
>> ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
>> #1  0x00007f6ed1857e0d in do_dm_op (xch=0x23bb160, domid=19, nr_bufs=2)
>> at xc_private.c:808
>> #2  0x00007f6ed1851f85 in xc_hvm_track_dirty_vram (xch=0x23bb160,
>> dom=19, first_pfn=983040, nr=576, dirty_bitmap=0x7ffcd33ad730) at
>> xc_misc.c:562
> 
> Considering this, it would seem quite possible that this is another
> manifestation of the bug fixed by
> https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg01985.html

I've applied your patch and it has indeed solved the problem.


Thanks,
Razvan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel