diff options
author | zhanghailiang <zhang.zhanghailiang@huawei.com> | 2014-08-26 16:06:17 +0800 |
---|---|---|
committer | Stefan Hajnoczi <stefanha@redhat.com> | 2014-09-04 14:31:54 +0100 |
commit | e1d64c084b2cc7e907b4e64026d8c8dba59116f8 (patch) | |
tree | 6e26e084d20ad717c68ccb3ac72f0218e2cc3d6d /aio-posix.c | |
parent | 30eaca3acdf17d7bcbd1213eb149c02037edfb0b (diff) | |
download | hqemu-e1d64c084b2cc7e907b4e64026d8c8dba59116f8.zip hqemu-e1d64c084b2cc7e907b4e64026d8c8dba59116f8.tar.gz |
net: Forbid dealing with packets when VM is not running
For all NICs(except virtio-net) emulated by qemu,
Such as e1000, rtl8139, pcnet and ne2k_pci,
Qemu can still receive packets when VM is not running.
If this happened in *migration's* last PAUSE VM stage, but
before the end of the migration, the new receiving packets will possibly dirty
parts of RAM which has been cached in *iovec*(will be sent asynchronously) and
dirty parts of new RAM which will be missed.
This will lead serious network fault in VM.
To avoid this, we forbid receiving packets in generic net code when
VM is not running.
Bug reproduction steps:
(1) Start a VM which configured at least one NIC
(2) In VM, open several Terminal and do *Ping IP -i 0.1*
(3) Migrate the VM repeatedly between two Hosts
And the *PING* command in VM will very likely fail with message:
'Destination HOST Unreachable', the NIC in VM will stay unavailable unless you
run 'service network restart'
Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
Reviewed-by: Jason Wang <jasowang@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'aio-posix.c')
0 files changed, 0 insertions, 0 deletions