On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
When a link change occurs on a backend (like tap), we currently do
not propage such change to the nic. As a result, when someone turns
off a link on a tap device, for instance, then a guest doesn't see
that change and continues to
On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
When a link change occurs on a backend (like tap), we currently do
not propage such change to the nic. As a result, when someone turns
off a link on a tap
On Wed, Apr 02, 2014 at 01:46:14PM +0300, Yan Vugenfirer wrote:
On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
When a link change occurs on a backend (like tap), we currently do
not propage such
On 04/02/2014 04:51 AM, Michael S. Tsirkin wrote:
On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
When a link change occurs on a backend (like tap), we currently do
not propage such change to the nic. As a result, when someone turns
off a link on a tap device, for instance,
On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
When a link change occurs on a backend (like tap), we currently do
not propage such change to the nic. As a
On Wed, Apr 02, 2014 at 10:57:08AM -0400, Vlad Yasevich wrote:
On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
When a link change occurs on a backend
On 04/02/2014 11:03 AM, Michael S. Tsirkin wrote:
On Wed, Apr 02, 2014 at 10:57:08AM -0400, Vlad Yasevich wrote:
On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
On Wed, Apr 02, 2014 at 11:25:32AM -0400, Vlad Yasevich wrote:
On 04/02/2014 11:03 AM, Michael S. Tsirkin wrote:
On Wed, Apr 02, 2014 at 10:57:08AM -0400, Vlad Yasevich wrote:
On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
On Apr 2, 2014, at 11:51 AM, Michael S. Tsirkin m...@redhat.com
On 04/02/2014 11:29 AM, Michael S. Tsirkin wrote:
On Wed, Apr 02, 2014 at 11:25:32AM -0400, Vlad Yasevich wrote:
On 04/02/2014 11:03 AM, Michael S. Tsirkin wrote:
On Wed, Apr 02, 2014 at 10:57:08AM -0400, Vlad Yasevich wrote:
On 04/02/2014 06:46 AM, Yan Vugenfirer wrote:
On Apr 2, 2014, at
On Thu, Nov 21, 2013 at 09:05:51PM -0500, Vlad Yasevich wrote:
When a link change occurs on a backend (like tap), we currently do
not propage such change to the nic. As a result, when someone turns
off a link on a tap device, for instance, then a guest doesn't see
that change and continues to
When a link change occurs on a backend (like tap), we currently do
not propage such change to the nic. As a result, when someone turns
off a link on a tap device, for instance, then a guest doesn't see
that change and continues to try to send traffic or run DHCP even
though the lower-layer is
11 matches
Mail list logo
