[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

[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

[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

[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

[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

[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