** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492621
Title:
Cannot start VMs without routable IPv4 address
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492621
Title:
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492621
Title:
Cannot start VMs without routable IPv4 address
To manage notifications
** Tags removed: qemu-21.10
** Tags added: qemu-22.04 server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492621
Title:
Cannot start VMs without routable IPv4 address
To manage
Launchpad has imported 17 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=12398.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Sourceware.org Bugzilla #12398
https://sourceware.org/bugzilla/show_bug.cgi?id=12398
** Also affects: glibc via
https://sourceware.org/bugzilla/show_bug.cgi?id=12398
Importance: Unknown
It is a pain to see how often other things beat the priority of this ...
But having a config-based (no rebuilds, no custom patches) workaround just
always de-prioritizes it :-/
One day I'll get to it ... (he said and looked at his retirement in 30
years)
** Tags removed: qemu-20.10
** Tags
** Tags added: qemu-20.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492621
Title:
Cannot start VMs without routable IPv4 address
To manage notifications about this bug go to:
Wow a bug from the stone age, so old that I never saw it before :-/
I have to thank you for the bump to it, due to the current freeze for
the coming 20.04 release I'm busy and also unlikely to b able to change
it soon.
But I have taken a todo to revisit this in depth for 20.10
I mean
I agree with @addyp95 - this is a bug in how libvirt works in IPv6-only
environments, and it is still present on focal. For posterity, the
exact details of the workaround are to add the following line to
/etc/libvirt/qemu.conf:
spice_listen = "::1"
** Changed in: qemu (Ubuntu)
Status:
This is still a present bug. In its current defaults, the lack of a
routable ipv4 address will still cause libvirt to fail starting any
guests. While setting ::1 worked for Kevin, this doesn't fix the bug,
just works around it.
--
You received this bug notification because you are a member of
Thanks, Kevin!
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492621
Title:
Cannot start VMs without routable IPv4 address
To
Thanks, Kevin!
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1492621
Title:
Cannot start VMs without routable IPv4
Given that VNC does this as well, I traced the problem all the way back
to getaddrinfo() behavior in libc. I believe this describes it:
https://bugzilla.redhat.com/show_bug.cgi?id=721350
tl;dr: It ignores loopback when enumerating addresses per family.
Workaround is to define the display as ::1,
Given that VNC does this as well, I traced the problem all the way back
to getaddrinfo() behavior in libc. I believe this describes it:
https://bugzilla.redhat.com/show_bug.cgi?id=721350
tl;dr: It ignores loopback when enumerating addresses per family.
Workaround is to define the display as ::1,
Attaching typescript output of requested diagnostic commands.
As OVS rather than Linux bridge is in use, I have included potentially relevant
ovs-* command output.
** Attachment added: "1492621-diag.txt"
Attaching typescript output of requested diagnostic commands.
As OVS rather than Linux bridge is in use, I have included potentially relevant
ovs-* command output.
** Attachment added: "1492621-diag.txt"
Can you show the output of 'sudo ifconfig -a; sudo brctl show; sudo
netstat -nr' ?
Does
nc -l -4 127.0.0.1 & echo ab | nc -4 127.0.0.1
work?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Can you show the output of 'sudo ifconfig -a; sudo brctl show; sudo
netstat -nr' ?
Does
nc -l -4 127.0.0.1 & echo ab | nc -4 127.0.0.1
work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for reporting this bug. I suspect this is actually a libvirt
bug. To make sure, could you check whether
kvm -spice addr=127.0.0.1,port=5900
works for you? At least in an empty network namespace on my host this
seemed to work fine.
** Changed in: qemu (Ubuntu)
Status: New =>
Thanks for reporting this bug. I suspect this is actually a libvirt
bug. To make sure, could you check whether
kvm -spice addr=127.0.0.1,port=5900
works for you? At least in an empty network namespace on my host this
seemed to work fine.
** Changed in: qemu (Ubuntu)
Status: New =>
I don't have the 'kvm' command on this machine, but it definitely
appears to be qemu related:
kjotte@athens:~$ qemu-system-x86_64 -spice addr=127.0.0.1,port=5900
(/usr/bin/qemu-system-x86_64:1785): Spice-Warning **:
reds.c:2330:reds_init_socket: getaddrinfo(127.0.0.1,5900): Address family for
I don't have the 'kvm' command on this machine, but it definitely
appears to be qemu related:
kjotte@athens:~$ qemu-system-x86_64 -spice addr=127.0.0.1,port=5900
(/usr/bin/qemu-system-x86_64:1785): Spice-Warning **:
reds.c:2330:reds_init_socket: getaddrinfo(127.0.0.1,5900): Address family for
23 matches
Mail list logo
