Closed iproute-net closed 2 years ago
Hello.
Are you sure about it? I just tried it and it is working fine for me:
~ ❯ mkdir ubuntu-20.04-server-amd64
~ ❯ cd ubuntu-20.04-server-amd64
~/ubuntu-20.04-server-amd64 ❯ vagrant init peru/ubuntu-20.04-server-amd64
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
~/ubuntu-20.04-server-amd64 ❯ VAGRANT_DEFAULT_PROVIDER=virtualbox vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'peru/ubuntu-20.04-server-amd64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'peru/ubuntu-20.04-server-amd64'
default: URL: https://vagrantcloud.com/peru/ubuntu-20.04-server-amd64
==> default: Adding box 'peru/ubuntu-20.04-server-amd64' (v20220102.01) for provider: virtualbox
default: Downloading: https://vagrantcloud.com/peru/boxes/ubuntu-20.04-server-amd64/versions/20220102.01/providers/virtualbox.box
default: Calculating and comparing box checksum...
==> default: Successfully added box 'peru/ubuntu-20.04-server-amd64' (v20220102.01) for 'virtualbox'!
==> default: Importing base box 'peru/ubuntu-20.04-server-amd64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'peru/ubuntu-20.04-server-amd64' version '20220102.01' is up to date...
==> default: Setting the name of the VM: ubuntu-2004-server-amd64_default_1641396216977_99320
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
~/ubuntu-20.04-server-amd64 ❯ vagrant ssh Welcome to Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-91-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
Last login: Wed Jan 5 15:24:02 2022
vagrant@localhost:~$ ip a s
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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:c1:4d:e0 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic eth0
valid_lft 86374sec preferred_lft 86374sec
inet6 fe80::a00:27ff:fec1:4de0/64 scope link
valid_lft forever preferred_lft forever
vagrant@localhost:~$
Hi Petr,
I have attached the Vagrantfile Vagrantfile.txt
and these screenshots which shows the error:
Best Regards, Keyvan
Thank you Keyvan
May I ask you to run the same commands as I did and past here their output please?
Here they are:
mkdir ubuntu-20.04-server-amd64
cd ubuntu-20.04-server-amd64
vagrant init peru/ubuntu-20.04-server-amd64
VAGRANT_DEFAULT_PROVIDER=virtualbox vagrant up
vagrant ssh
# then run "ip a s"
Thank you...
Thanks Petr it is working, let me find the issue because I need more customized NICs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Dears,
I used peru/ubuntu-20.04-server-amd64 in MAC with vagrant and virtual box. The VM got stuck into ssh auth method: private key, I start to investigate the issue, and then I saw that there is no IP address on VM and I have this error in dmesg logs:
fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
the systemd-networkd.service was up and running, but the network was not working properly.