>> Can you look the original value up somehow and us the resize callback >> only as a notification that something changed? (that value would have to >> be stored somewhere and migrated I assume - maybe that's already being >> done) > > Ok. I will take a look at that. But can we instead pass the > block->used_length to > fw_cfg_add_file_callback(). That way we don’t have to change the > qemu_ram_resize() > as well. I think Igor has suggested this before[1] and I had a go at it > before coming up > with the "req_length" proposal here.
You mean, passing the old size as well? I don't see how that will solve the issue, but yeah, nothing speaks against simply sending the old and the new size. -- Thanks, David / dhildenb
