I'm seeing this issue. Unable to start the VM.
My setup:
Ubuntu 22.04
Two RTX 6000 Ada
CPU AMD EPYC 7742 64-Core Processor
Is there a recommended fix? Comment #8 suggests this has been solved in
>= Bionic, but why am I still seeing it then?
--
You received this bug notification because you are
I've dupped another case onto this, it stays an issue that from the libvirt
side has been handled by
https://gitlab.com/libvirt/libvirt/-/commit/8c70d04bab7278c96390a913fa949a17cd3124f9
which is in >=Bionic.
AFAIU remaining issues as outlined in comment #2 are still considered
more an libnl/driv
We have not seen this bug in the recent time. So, this bug can be
closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794997
Title:
virNetlinkEventCallback:700 : nl_recv returned with error: No b
Govinda,
Is this still an issue? If yes, can you reopen the bug ..
If not, advise next steps ...
thanks,
Anish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794997
Title:
virNetlinkEventCallback
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/179499
[Expired for libnl3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libnl3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794997
As per QA, these messages were found in syslog while creating a 16GPU VM
but there is no functionality loss or issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794997
Title:
virNetlinkEventCall
Also the error doesn't indicate that libvirt is doing anything wrong here.
It runs nl_recv [1] in virNetlinkEventCallback which eventually will do recvmsg
[2] and gets reported that it didn't fit - so it correctly relay that up the
stack.
Now that is a somewhat known issue [3], but it should be
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
Specifically, please provide full steps to reprod
