The networking is ok, but the /etc/resolv.conf is deleted before every
command execution. As a workaround, you can rewrite it and chain a
series of commands:
virt-sysprep -v -x -a CentOS-7-x86_64-GenericCloud.qcow2 --network
--run-command 'echo "nameserver 169.254.2.3" > /etc/resolv.conf; yum
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libguestfs (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/1768085
Title:
The difference with and without --network is in the qemu command line,
basically whether
we set up a user network or not:
https://github.com/libguestfs/libguestfs/blob/bd4e99cc134dd20cb1f16ac11e44810de30b973a/lib
/launch-direct.c#L674
I'm guessing that ‘dhclient eth0’ only "works" without the
Setting 'export LIBGUESTFS_BACKEND=direct' does not help. I will try to find a
way to build 1.38 for Ubuntu and re-try.
Thank you, Richard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768085
Hangs on dhclient on Ubuntu 18.04, and works on 17.10:
$ virt-rescue --scratch --network -v -x
Runs perfectly on both 17.10 and 18.04, but there is no network set up:
$ virt-rescue --scratch -v -x
17.10:
...
+ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
I'm not sure, but can you try a few simple tests:
$ virt-rescue --scratch --network -v -x
$ virt-rescue --scratch -v -x
Do those commands fail in the same way? Does it make a difference if the
--network option is present?
Also it might be worth using the latest version 1.38.
--
You received
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768085
Title:
virt-customize: dhclient can't get IP address
To manage notifications about this bug go to: