Re: [arch-general] vagrant/virtualbox archlinux guest private_network
On Wed, Jun 22, 2016 at 5:38 PM, Jonathan Steel
On Wed 22 Jun 2016 at 16:37, Andre "Osku" Schmidt via arch-general wrote:
[...] I did not setup netctl on the client yet, cause it fails with the same error (and wanted to keep things simple as possible).
- Is this a vagrant bug? - Did i forget something important in the client? - Would it be possible to use systemd-networkd instead?
You have to install netctl on the box; Vagrant expects it to be there to configure NICs.
- Does your archlinux guest work with private_network?
Yes, and I don't do anything special so install netctl on the box and share further errors.
netctl is installed https://github.com/oskude/vagrant-archmini/blob/private_network/install.sh#L... care to share your box setup scripts?
On Wed 22 Jun 2016 at 18:06, Andre "Osku" Schmidt wrote:
[...] I don't do anything special so install netctl on the box and share
further errors.
netctl is installed https://github.com/oskude/vagrant-archmini/blob/private_network/install.sh#L...
care to share your box setup scripts?
Does that solve your issue or are you having further errors? I don't have a script, only notes: pacstrap /mnt base vim syslinux virtualbox-guest-utils \ virtualbox-guest-modules-arch openssh /etc/ssh/sshd_config: PermitRootLogin yes systemctl enable vboxservice sshd dhcpcd vagrant package --base *vmname* --output *name*.box -- Jonathan Steel
On Wed, Jun 22, 2016 at 7:18 PM, Jonathan Steel
On Wed 22 Jun 2016 at 18:06, Andre "Osku" Schmidt wrote:
[...] I don't do anything special so install netctl on the box and share
further errors.
netctl is installed
https://github.com/oskude/vagrant-archmini/blob/private_network/install.sh#L...
care to share your box setup scripts?
Does that solve your issue or are you having further errors? I don't have a script, only notes:
pacstrap /mnt base vim syslinux virtualbox-guest-utils \ virtualbox-guest-modules-arch openssh
/etc/ssh/sshd_config: PermitRootLogin yes
systemctl enable vboxservice sshd dhcpcd
vagrant package --base *vmname* --output *name*.box
the errors are for the "private_network" branch[0], that has netctl installed. i now also updated that branch[0] with following: - install dhcpcd and `systemctl enable dhcpcd` - generates same error - add "PermitRootLogin yes" in sshd_config - generates same error - (i thought vagrant does everything through vagrant user and sudo) - install vboxservice and `systemctl enable vboxservice` - generates same error - (i gathered from vbox wiki page[1] that we dont need to enable vboxservice anymore) - disable systemd-networkd and systemd-resolved and setup netctl - generates same error - (would still love to use systemd-networkd instead;P) - disable dhcpcd service - generates same error - (i assumed from netctl wiki page[2] that we dont need to manually enable/start dhcpcd, cause it does not mention it) i would be curious to see what the output of `ip a` looks like on a working client with private_network. cause somehow vagrant here is not finding the one it wants, and tries to start netctl without device/profile name?: "Failed to restart netctl@.service: Unit name netctl@.service is missing the instance name." i guess i'll try to findout what exactly vagrant is trying to find/do. darn .andre [0] https://github.com/oskude/vagrant-archmini/tree/private_network [1] "Since version 5.0.16, virtualbox-guest-modules-arch and virtualbox-guest-dkms use systemd-modules-load service to load their modules at boot time." https://wiki.archlinux.org/index.php/Virtualbox#Load_the_Virtualbox_kernel_m... [2] https://wiki.archlinux.org/index.php/Netctl
If it can help you
vagrant@archlinux:~$ ip a
1: lo:
On Wed, Jun 22, 2016 at 7:18 PM, Jonathan Steel
wrote: On Wed 22 Jun 2016 at 18:06, Andre "Osku" Schmidt wrote:
[...] I don't do anything special so install netctl on the box and share
further errors.
netctl is installed
https://github.com/oskude/vagrant-archmini/blob/private_network/install.sh#L...
care to share your box setup scripts?
Does that solve your issue or are you having further errors? I don't have a script, only notes:
pacstrap /mnt base vim syslinux virtualbox-guest-utils \ virtualbox-guest-modules-arch openssh
/etc/ssh/sshd_config: PermitRootLogin yes
systemctl enable vboxservice sshd dhcpcd
vagrant package --base *vmname* --output *name*.box
the errors are for the "private_network" branch[0], that has netctl installed.
i now also updated that branch[0] with following:
- install dhcpcd and `systemctl enable dhcpcd` - generates same error
- add "PermitRootLogin yes" in sshd_config - generates same error - (i thought vagrant does everything through vagrant user and sudo)
- install vboxservice and `systemctl enable vboxservice` - generates same error - (i gathered from vbox wiki page[1] that we dont need to enable vboxservice anymore)
- disable systemd-networkd and systemd-resolved and setup netctl - generates same error - (would still love to use systemd-networkd instead;P)
- disable dhcpcd service - generates same error - (i assumed from netctl wiki page[2] that we dont need to manually enable/start dhcpcd, cause it does not mention it)
i would be curious to see what the output of `ip a` looks like on a working client with private_network. cause somehow vagrant here is not finding the one it wants, and tries to start netctl without device/profile name?:
"Failed to restart netctl@.service: Unit name netctl@.service is missing the instance name."
i guess i'll try to findout what exactly vagrant is trying to find/do.
darn .andre
[0] https://github.com/oskude/vagrant-archmini/tree/private_network [1] "Since version 5.0.16, virtualbox-guest-modules-arch and virtualbox-guest-dkms use systemd-modules-load service to load their modules at boot time." https://wiki.archlinux.org/index.php/Virtualbox#Load_the_Virtualbox_kernel_m... [2] https://wiki.archlinux.org/index.php/Netctl
On Wed, Jun 22, 2016 at 8:40 PM, Ilya Boka via arch-general < arch-general@archlinux.org> wrote:
If it can help you vagrant@archlinux:~$ ip a 1: lo:
mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 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: eth0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 08:00:27:1a:b1:01 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::784:a34a:587c:970/64 scope link valid_lft forever preferred_lft forever 3: enp0s8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 08:00:27:33:fa:78 brd ff:ff:ff:ff:ff:ff inet 192.168.33.10/24 brd 192.168.33.255 scope global enp0s8 valid_lft forever preferred_lft forever inet 192.168.56.101/24 brd 192.168.56.255 scope global enp0s8 valid_lft forever preferred_lft forever inet6 fe80::afdf:f5bc:334f:c4f2/64 scope link valid_lft forever preferred_lft forever
Cool, i should have thought it before, it was a missing kernel driver... thanks for the tip for 3 net devices, i always had only 2! the missing kernel module was: /usr/lib/modules/*/kernel/drivers/net/ethernet/intel/e1000/e1000.ko.gz i thought i tried without my "minifications" already, dammit. sorry for the noise! .andre ps. i guess i should include all possible modules vbox could use...
Hi! If you need a base machine for Vagrant you can use mine: https://vagrantcloud.com/ogarcia/boxes/archlinux-x32 https://vagrantcloud.com/ogarcia/boxes/archlinux-x64 I update it once a month. Greetings. 2016-06-22 21:53 GMT+02:00 Andre "Osku" Schmidt via arch-general < arch-general@archlinux.org>:
On Wed, Jun 22, 2016 at 8:40 PM, Ilya Boka via arch-general < arch-general@archlinux.org> wrote:
If it can help you vagrant@archlinux:~$ ip a 1: lo:
mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 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: eth0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 08:00:27:1a:b1:01 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 brd 10.0.2.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::784:a34a:587c:970/64 scope link valid_lft forever preferred_lft forever 3: enp0s8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 08:00:27:33:fa:78 brd ff:ff:ff:ff:ff:ff inet 192.168.33.10/24 brd 192.168.33.255 scope global enp0s8 valid_lft forever preferred_lft forever inet 192.168.56.101/24 brd 192.168.56.255 scope global enp0s8 valid_lft forever preferred_lft forever inet6 fe80::afdf:f5bc:334f:c4f2/64 scope link valid_lft forever preferred_lft forever Cool,
i should have thought it before, it was a missing kernel driver... thanks for the tip for 3 net devices, i always had only 2!
the missing kernel module was: /usr/lib/modules/*/kernel/drivers/net/ethernet/intel/e1000/e1000.ko.gz
i thought i tried without my "minifications" already, dammit.
sorry for the noise! .andre
ps. i guess i should include all possible modules vbox could use...
-- Óscar García Amor | ogarcia at moire.org | http://ogarcia.me
participants (4)
-
Andre "Osku" Schmidt
-
Ilya Boka
-
Jonathan Steel
-
Óscar García Amor