On Thu, Sep 04, 2014 at 12:55:38PM +0800, Jason Wang wrote:
> On 09/02/2014 10:23 PM, Stefan Hajnoczi wrote:
> > Do not modify guest memory or devices when the guest is stopped.
> > Currently the netdevs still send packets while the guest is stopped if
> > their file descriptor was being monitored
On Tue, Sep 02, 2014 at 05:25:53PM +0300, Michael S. Tsirkin wrote:
> On Tue, Sep 02, 2014 at 03:23:10PM +0100, Stefan Hajnoczi wrote:
> > Do not modify guest memory or devices when the guest is stopped.
> > Currently the netdevs still send packets while the guest is stopped if
> > their file descr
On 09/02/2014 10:23 PM, Stefan Hajnoczi wrote:
> Do not modify guest memory or devices when the guest is stopped.
> Currently the netdevs still send packets while the guest is stopped if
> their file descriptor was being monitored for write (e.g. the socket
> write buffer filled before the guest wa
On Tue, Sep 02, 2014 at 03:23:10PM +0100, Stefan Hajnoczi wrote:
> Do not modify guest memory or devices when the guest is stopped.
> Currently the netdevs still send packets while the guest is stopped if
> their file descriptor was being monitored for write (e.g. the socket
> write buffer filled b
Do not modify guest memory or devices when the guest is stopped.
Currently the netdevs still send packets while the guest is stopped if
their file descriptor was being monitored for write (e.g. the socket
write buffer filled before the guest was stopped).
Netdevs call qemu_flush_queued_packets() w
