Hi,
as advised, I've changed the guest OS to SmartOS. I was able to migrate
the OS to the second qemu. Before the migration, I've started debugger
using "mdb -K". Now I have two VMs:
1. The source VM running mdb.
2. The destination VM also running mdb without a problem.
When I resume the OS by exiting mdb in the source VM, everything is
running fine.
When I do the same in the second VM, the processes start to crash with SEGV.
The contents of the two VMs are expected to be absolutely identical..
but apparently they are not. Anyway, with running mdb on both VMs, it
seems as an ideal debug setup to me - just compare and find the
difference. I believe it should be easy to look on the memory.
Unfortunately, even after 2 days spent reading various mdb manuals and
handbooks, I don't know how to actually do it.
Can you please help me with that?
Thank you.
Jan
On 13. 7. 2017 2:40, Robert Mustacchi wrote:
Hi Ján,
Unfortunately, I'm not very familiar with the internals of Linux. What I
might suggest trying to do is to maybe test with migrating SmartOS, only
because it'll hopefully be easier for us to look at dumps, get a crash
dump, and debug.
I suspect that likely what's going on here is that some part of the
migrated state has not been correctly saved and/or restored, especially
given that we never really focused on bring up at the time.
Sorry I don't have a more actionable next step for you.
Robert
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
