On 04/30/2014 06:02 PM, Michal Privoznik wrote:
My ACK was premature ..
On 24.04.2014 15:19, Ján Tomko wrote:
Instead of guessing it from the interface name, look into
/proc/net/vlan/interface.
This works for devices not named real_device.vlan ID,
avoiding an error flood when virt-manager
On 24.04.2014 15:19, Ján Tomko wrote:
Instead of guessing it from the interface name, look into
/proc/net/vlan/interface.
This works for devices not named real_device.vlan ID,
avoiding an error flood when virt-manager keeps asking about
them every second:
My ACK was premature ..
On 24.04.2014 15:19, Ján Tomko wrote:
Instead of guessing it from the interface name, look into
/proc/net/vlan/interface.
This works for devices not named real_device.vlan ID,
avoiding an error flood when virt-manager keeps asking about
them every second:
On Thu, Apr 24, 2014 at 03:19:45PM +0200, Ján Tomko wrote:
Instead of guessing it from the interface name, look into
/proc/net/vlan/interface.
This works for devices not named real_device.vlan ID,
avoiding an error flood when virt-manager keeps asking about
them every second:
On 04/25/2014 06:21 PM, Dave Allan wrote:
On Thu, Apr 24, 2014 at 03:19:45PM +0200, Ján Tomko wrote:
Instead of guessing it from the interface name, look into
/proc/net/vlan/interface.
This works for devices not named real_device.vlan ID,
avoiding an error flood when virt-manager keeps
On Fri, Apr 25, 2014 at 08:28:32PM +0300, Laine Stump wrote:
On 04/25/2014 06:21 PM, Dave Allan wrote:
On Thu, Apr 24, 2014 at 03:19:45PM +0200, Ján Tomko wrote:
Instead of guessing it from the interface name, look into
/proc/net/vlan/interface.
This works for devices not named
Instead of guessing it from the interface name, look into
/proc/net/vlan/interface.
This works for devices not named real_device.vlan ID,
avoiding an error flood when virt-manager keeps asking about
them every second:
https://bugzilla.redhat.com/show_bug.cgi?id=966329
---
