I found the mainline linux 3.0-rc6 xen-blkfront driver doesn't implement suspend func. In my opinion, the blkfront should wait till responses of all the pending requests come back, then domu can be suspended, otherwise, after the migration, vm of target host will request from target host, meanwhile, the blkback of source host maybe do the pending requests until they's done.
if migrate the vm with high io pressure, the requests of this vm may disorder.
And i saw the gpl windows pv driver, blkfront will change its state and wait for blkback closing, after blkback closing, the pending requests definitely are done.
More, i did some test with migration, while vm was running dd task, xm migrate -l . before it suspend, gdb tapdisk2. after migration, new vm started. then quit gdb, the pending request were written back to disk after new requests.
if migrate the vm with high io pressure, the requests of this vm may disorder.
And i saw the gpl windows pv driver, blkfront will change its state and wait for blkback closing, after blkback closing, the pending requests definitely are done.
More, i did some test with migration, while vm was running dd task, xm migrate -l . before it suspend, gdb tapdisk2. after migration, new vm started. then quit gdb, the pending request were written back to disk after new requests.
4925
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
