RE: [PATCH] block: Don't inactivate bs if it is aleady inactive

ct: Re: [PATCH] block: Don't inactivate bs if it is aleady inactive > > 24.11.2020 13:04, Tuguoyi wrote: > > The following steps will cause qemu assertion failure: > > - pause vm > > - save memory snapshot into local file through fd migration > > - do the above o

Re: [PATCH] block: Don't inactivate bs if it is aleady inactive

24.11.2020 13:04, Tuguoyi wrote: The following steps will cause qemu assertion failure: - pause vm - save memory snapshot into local file through fd migration - do the above operation again will cause qemu assertion failure Hi! Why do you need such scenario? Isn't it more correct and safer to

RE: [PATCH] block: Don't inactivate bs if it is aleady inactive

> The following steps will cause qemu assertion failure: > - pause vm > - save memory snapshot into local file through fd migration > - do the above operation again will cause qemu assertion failure > > The backtrace looks like: > #0 0x7fbf958c5c37 in raise () from /lib/x86_64-linux-gnu/libc.

[PATCH] block: Don't inactivate bs if it is aleady inactive

The following steps will cause qemu assertion failure: - pause vm - save memory snapshot into local file through fd migration - do the above operation again will cause qemu assertion failure The backtrace looks like: #0 0x7fbf958c5c37 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x000