Hello, all,
I was experiencing this problem and was able to get around it by
additionally passing `--no-systemd-networkd --enable-dhcp` to vmdebootstrap.
regards
Afif
--
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name
On Wed, 30 Nov 2016 at 09:16:09 +0100, Johannes Schauer wrote:
> Quoting Martin Pitt (2016-11-30 08:52:51)
> > The expected state is that it is a symlink to
> > /run/systemd/resolve/resolv.conf, and that's the bit that apparently doesn't
> > exist -- i. e. systemd-resolved.service is not running in
Hi,
Quoting Martin Pitt (2016-11-30 09:51:10)
> Johannes Schauer [2016-11-30 9:39 +0100]:
> > sorry I didn't mention that before. Without the autopkgtest setup script,
> > vmdebootstrap finishes successfully.
>
> Finish yes, that's the easy part. The interesting part is whether you can
> boot th
Johannes Schauer [2016-11-30 9:39 +0100]:
> sorry I didn't mention that before. Without the autopkgtest setup script,
> vmdebootstrap finishes successfully.
Finish yes, that's the easy part. The interesting part is whether you
can boot that VM and resolve names in it? Is resolved running?
Martin
Hi,
Quoting Martin Pitt (2016-11-30 09:32:05)
> Hence I would like to see if vmdebootstrap is also broken without the setup
> script. It might very well be possible that the autopkgtest setup script
> changes some configuration which breaks resolved or whatnot.
sorry I didn't mention that before.
Johannes Schauer [2016-11-30 9:16 +0100]:
> > The expected state is that it is a symlink to
> > /run/systemd/resolve/resolv.conf, and that's the bit that apparently doesn't
> > exist -- i. e. systemd-resolved.service is not running in your case. So
> > using
> > the second method and vmdebootstra
Hi Martin,
Quoting Martin Pitt (2016-11-30 08:52:51)
> The expected state is that it is a symlink to
> /run/systemd/resolve/resolv.conf, and that's the bit that apparently doesn't
> exist -- i. e. systemd-resolved.service is not running in your case. So using
> the second method and vmdebootstrapp
Hello,
Johannes Schauer [2016-11-29 8:04 +0100]:
> + cat /tmp/tmpSxHjE2/etc/resolv.conf
> cat: /tmp/tmpSxHjE2/etc/resolv.conf: No such file or directory
> EEEK! Something bad happened...
> Command failed: /usr/share/autopkgtest/setup-commands/setup-testbed
> /tmp/tmpSxHjE2 autopkgtest-sid.raw
>
Hi Martin,
Quoting Martin Pitt (2016-11-28 22:31:52)
> Johannes Schauer [2016-11-28 12:15 +]:
> > Can you tell me a way to diagnose the problem as apparently it works fine
> > for
> > you?
So I put this into the file:
echo $root
cat $root/etc/resolv.conf
And added a -x. With that I got on
Hi,
Quoting Martin Pitt (2016-11-27 22:43:21)
> I ran exactly the same command successfully on my box, with the same
> vmdebootstrap version, and http://httpredir.debian.org/debian works fine
> inside the VM. Was that perhaps a temporary network glitch? (Deutsche
> Telekom has failed DNS resoluti
Control: tag -1 unreproducible
Johannes Schauer [2016-11-27 1:28 +0100]:
> $ AUTOPKGTEST_APT_PROXY=http://127.0.0.1:3142 sudo vmdebootstrap --verbose
> --serial-console --distribution=sid
> --customize=/usr/share/autopkgtest/setup-commands/setup-testbed
> --user=test/test --size=10 --g
Package: autopkgtest
Version: 4.2.1
Severity: normal
Hi,
as the man page suggests, I'm running:
$ AUTOPKGTEST_APT_PROXY=http://127.0.0.1:3142 sudo vmdebootstrap --verbose
--serial-console --distribution=sid
--customize=/usr/share/autopkgtest/setup-commands/setup-testbed
--user=test/test --siz
12 matches
Mail list logo
