The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state
back to "New" within the next 60 days, otherwise this report will be marked as
"Expired". Or mark it as "Fix Released" if the problem has been solved with a
newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1814381
Title:
qemu can't resolve ::1 when no network is available
Status in QEMU:
Incomplete
Bug description:
I'm not sure if this is a qemu thing or a getaddrinfo/glibc thing, or
even just something about my laptop. However we have a test failure
in nbdkit which only occurs when my laptop is not connected to wifi or
other networking. It boils down to:
$ qemu-img info --image-opts "file.driver=nbd,file.host=::1,file.port=1234"
qemu-img: Could not open 'file.driver=nbd,file.host=::1,file.port=1234':
address resolution failed for ::1:1234: Address family for hostname not
supported
In a successful case it should connect to a local NBD server on port
1234, but if you don't have that you will see:
qemu-img: Could not open
'file.driver=nbd,file.host=::1,file.port=1234': Failed to connect
socket: Connection refused
I can ‘ping6 ::1’ fine.
It also works if I replace ‘::1’ with ‘localhost6’.
My /etc/hosts contains:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1814381/+subscriptions
