[Bug 1653499] Re: libvirt display error after restart driver

2021-09-30 Thread Christian Ehrhardt 
*** This bug is a duplicate of bug 1794997 ***
https://bugs.launchpad.net/bugs/1794997

Clearing out old unresolved issues, this is really actually a problem
within libnl more than anything else. The default should be ok (as Josh
posted). I marked this a dup as there was another bug with better link
references already.

But the TL;DR stays as I said in comment 3 - it is non fatal and should
be addressed in libnl.

** This bug has been marked a duplicate of bug 1794997
   virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space 
available

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653499

Title:
  libvirt display error after restart driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1653499/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1653499] Re: libvirt display error after restart driver

2017-01-09 Thread Joshua Powers
@paelzer per the description and syslog this looks to be with Mellanox
cards:

HCA 1: CX354A - ConnectX-3 Pro QSFP
HCA 3: CX456A - ConnectX-4 QSFP
HCA 4: CB192A - Connect-IB QSFP
HCA 5: CX4121A - ConnectX-4 LX SFP28

Which will apparently use the mlx4 and mlx5 drivers.

** Changed in: libvirt (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653499

Title:
  libvirt display error after restart driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1653499/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1653499] Re: libvirt display error after restart driver

2017-01-08 Thread Chen Ben Enosh
which details do you need from my cards and drivers?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653499

Title:
  libvirt display error after restart driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1653499/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1653499] Re: libvirt display error after restart driver

2017-01-06 Thread ChristianEhrhardt
I'd quote something from that thread that I agree to for us I think:
"Up to now our position has been that this problem should be fixed in
libnl, so we have preferred to not patch libvirt for it, but instead get
libnl fixed."

Therefore adding libnl task.

Also in the past this was very driver specific to ixgbe.
>From the log snippet I only see mlx4 warnings.

Could you elaborate on the cards/drivers available and used in your
system?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653499

Title:
  libvirt display error after restart driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1653499/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1653499] Re: libvirt display error after restart driver

2017-01-04 Thread Chen Ben Enosh
syslog after restart driver:
Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Reached target Host and Network Name 
Lookups.

Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Starting NFS status monitor for 
NFSv2/3 locking 
 
Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Starting Notify NFS peers of a 
restart...  
  
Jan  5 09:29:24 qa-h-vrt-044 rpc.statd[7847]: Version 1.2.8 starting

  
Jan  5 09:29:24 qa-h-vrt-044 rpc.statd[7847]: Flags: TI-RPC 

  
Jan  5 09:29:24 qa-h-vrt-044 sm-notify[7846]: Version 1.2.8 starting

  
Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Started Notify NFS peers of a restart. 

  
Jan  5 09:29:24 qa-h-vrt-044 systemd[1]: Started NFS status monitor for NFSv2/3 
locking..   
  
Jan  5 09:29:24 qa-h-vrt-044 kernel: [57029.219054] FS-Cache: Loaded

  
Jan  5 09:29:24 qa-h-vrt-044 kernel: [57029.236040] FS-Cache: Netfs 'nfs' 
registered for caching  

Jan  5 09:29:28 qa-h-vrt-044 kernel: [57033.623710] mlx4_en: enp65s0: Close 
port called 
  
Jan  5 09:29:28 qa-h-vrt-044 kernel: [57033.884115] mlx4_en :41:00.0: 
removed PHC 

Jan  5 09:29:28 qa-h-vrt-044 kernel: [57033.885654] mlx4_en: enp65s0d1: Close 
port called 

Jan  5 09:29:28 qa-h-vrt-044 systemd[1]: Stopping ifup for enp65s0...   

  
Jan  5 09:29:28 qa-h-vrt-044 ifdown[7896]: Cannot find device "enp65s0" 

  
Jan  5 09:29:29 qa-h-vrt-044 ifdown[7896]: Cannot find device "enp65s0" 

  
Jan  5 09:29:29 qa-h-vrt-044 systemd[1]: Stopped ifup for enp65s0.  

  
Jan  5 09:29:29 qa-h-vrt-044 systemd[1]: Stopping ifup for enp65s0d1... 

  
Jan  5 09:29:29 qa-h-vrt-044 ifdown[7961]: Cannot find device "enp65s0d1"   

  
Jan  5 09:29:29 qa-h-vrt-044 ifdown[7961]: Cannot find device "enp65s0d1"   

  
Jan  5 09:29:29 qa-h-vrt-044 systemd[1]: Stopped ifup for enp65s0d1.

  
Jan  5 09:29:30 qa-h-vrt-044 ntpd[3243]: Deleting interface #430 enp65s0, 
58.96.65.1#123, interface stats: received=0, sent=0, dropped=0, 
active_time=51866 secs  
Jan  5 09:29:30 qa-h-vrt-044 ntpd[3243]: Deleting interface #431 enp65s0d1, 
59.96.65.1#123, interface stats: received=0, sent=0, dropped=0, 
active_time=51866 secs
Jan  5 09:29:30 qa-h-vrt-044 ntpd[3243]: Deleting interface #434 enp65s0, 
fe80::f652:14ff:fe7a:5aa1%237#123, interface stats: received=0, sent=0, 
dropped=0, active_time=51864 secs   
Jan  5 09:29:30 qa-h-vrt-044 ntpd[3243]: Deleting interface #435 enp65s0d1, 
fe80::f652:14ff:fe7a:5aa2%238#123, interface stats: received=0, sent=0, 
dropped=0, active_time=51864 secs 
Jan  5 09:29:30 qa-h-vrt-044 kernel: [57035.6

[Bug 1653499] Re: libvirt display error after restart driver

2017-01-03 Thread Joshua Powers
Thanks for reporting this issue.

nl_recv is from libnl3. Can you provide the full libvirt and syslog to
see if there is any additional data that might help? Also do you have
identically configured systems that are also working as expected?

This message can happen when you have a number of I/O cards, especially
newer ones with SRIOV capabilities that require more buffer space, but
not sure if that is the case here.  In Xenial the page size is set by:

 682 if (page_size == 0)
 683 page_size = getpagesize() * 4;


** Changed in: libvirt (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653499

Title:
  libvirt display error after restart driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1653499/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs