ip output when the network is not connected:
$ ip a show scope host
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state
DOWN group default qlen 1000
link/ether e8:6a:64:5d:2c:66 brd ff:ff:ff:ff:ff:ff
3: wlp61s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
group default qlen 1000
link/ether 1e:2b:b1:0c:99:ef brd ff:ff:ff:ff:ff:ff
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0
state DOWN group default qlen 1000
link/ether 52:54:00:72:04:db brd ff:ff:ff:ff:ff:ff
** Description changed:
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':
addre
- ss resolution failed for ::1:1234: Address family for hostname not supported
+ $ 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':
Faile
- d to connect socket: Connection refused
+ 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
--
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:
New
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
