Topic: Yum update fails on VirtualBox VM

[dallas]

I decided to try installing beta 1 as server only on Virtual Box 6.1 on my Dell Inspiron 5000, intel Core i7 10th generation.
I'm following the notes in the Testing Environments page on the Wiki and I have fallen at the first hurdle. 

After installing SME and enabling SSH, running yum update in the ssh terminal produces the following error.

[root@sme10 ~]# yum update
Loaded plugins: fastestmirror, post-transaction-actions, priorities, smeserver
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os error was
14: curl#7 - "Failed to connect to 2604:1580:fe02:2::10: Network is unreachable"


I used the text install and disable ipv6 on the way through but this appears to be looking for an ipv6 address.
I can ping mirrorlist.centos.org.
This is my 3rd attempt to build this VM. Have I done something stupid?

Dallas

[brianr]

I think you should check the use of qemu-agent.  I am not sure whether this applies to VB (it does to proxmox).

I found that enabling the qemu-agent caused this sort of yum update failure. 

It is possible that installing the agent on the SME10 might solve, it, but I just disabled it.

Actually, having it enabled on my gateway (also SME10 now!) was the main problem.
 

[TerryF]

Why text installer? Graphic installer has been solid to date..just accept defaults and let it do its thing.

[brianr]

Why text installer? Graphic installer has been solid to date..just accept defaults and let it do its thing.

I don't think the text installer is the problem here, but I do agree that the graphic installer is very much more usable.

[Jean-Philippe Pialasse]

as noted by Brianr,

have you enabled qemu agent without installing it first in the vm?

see https://bugs.contribs.org/show_bug.cgi?id=11395

[dallas]

as noted by Brianr,

have you enabled qemu agent without installing it first in the vm?

see https://bugs.contribs.org/show_bug.cgi?id=11395

I have added the virtio driver as per this section of the Virtual Box User Manual.

  Enable paravirtualized device support. You do this by adding the virtio drivers to the initrd for the VM.

   This procedure works only on machines with a Linux kernel of version 3.4 or later. Check that the VM is running a supported kernel:

    # uname -a

    Use the dracut tool to rebuild initrd. Add the qemu module, as follows:

    # dracut –-logfile /var/log/Dracut.log –-force –-add qemu

    Verify that the virtio drivers are now present in initrd.

     # lsinitrd |grep virtio

systemctl start qemu-guest-agent returns Failed to start qemu-guest-agent.service: Unit not found.

I'm beginning to think I should abandon Virtual Box and use VMWare Player.

[brianr]

I've just done a "standard" graphicall SME10 install on Virtual Box and got the same problem.

Now looking for VB options that might be relevant.

[jameswilson]

I use proxmox and use the virtio drivers for drives and lan no issue. Is this just a virtual box issue?

[brianr]

I've just done a "standard" graphicall SME10 install on Virtual Box and got the same problem.

Now looking for VB options that might be relevant.

Looks like a false alarm (although the original poster should check this as well)

VB default for the network interface is "NAT" I changed it to "Bridged" and yum springs into action.

Note the qemu-agent is different I think to the Virtio drivers. The agent is used to communicate between the VM and the host (in our case proxmox), I was unable to find an equivalent for VB.

[TerryF]

I think I recall way way back something similar with Esxi, was using version 5.# back then

[dallas]

Looks like a false alarm (although the original poster should check this as well)

VB default for the network interface is "NAT" I changed it to "Bridged" and yum springs into action.

Note the qemu-agent is different I think to the Virtio drivers. The agent is used to communicate between the VM and the host (in our case proxmox), I was unable to find an equivalent for VB.

Hmm... A new install today fails again.
I have 2 configured NICs, both set as bridged.
Note there is only physical NIC on the laptop.
Laptop OS is Windows10

Config in screen shots.
Can you please share you VB settings.

Dallas

[brianr]

Why do you have 2 network ports and why are they connected to a controller? I would expect them to be connected to two unique ports. Unless you are planning for a Server/Gateway with two ports, I would delete one of the them.
What are the options on the "Name" dropdown?

Here are my details attached

I am on Fedora 33, VB version 6.1.18

[dallas]

Why do you have 2 network ports and why are they connected to a controller? I would expect them to be connected to two unique ports. Unless you are planning for a Server/Gateway with two ports, I would delete one of the them.
What are the options on the "Name" dropdown?

Here are my details attached

I am on Fedora 33, VB version 6.1.18

I have 2 ports for Server/Gateway. There is only one physical Ethernet port (via USB-C adapter).
Names options are Realtek USB GbE Family Controller and Intel(R) Wi-Fi 6 AX201 160Mhz

If it test this in Server Only mode, can I change it to Server/Gateway when I install it on a physical server?

[brianr]

If it test this in Server Only mode, can I change it to Server/Gateway when I install it on a physical server?

yes just run the console setup again. "su admin" from the command line or login directly as admin.

Ps I suspect you should choose " Intel(R) Wi-Fi 6 AX201 160Mhz" as the port.

PPS oh - that is the Wifi - no sorry, don't choose that one!!

What is the make of the laptop?

[dallas]

What is the make of the laptop?

It's a Dell Inspiron 15 5000.

I changed the install to Server Only and still no go.
I can ping mirrorlist.centos.org but I still get the same error.
I'm going to delete the VM from virtual box and start a completely fresh VM.

[dallas]

It's a Dell Inspiron 15 5000.

I've installed VMware Workstation 16 Player and have the same problem.
It may be the Laptop... or Windows 10?

[brianr]

I can ping mirrorlist.centos.org but I still get the same error.

That does sound like my problem with the qemu-agent or the VB equivalent...

Let us know how you get on.

[TerryF]

Windows 10 Home 20H2
Dell p6-2300a Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz   3.41 GHz

VirtualBox Version 6.1.18 r142142 (Qt5.6.2)

Set machine Bios to Virtualization On
Set windows 10 Fetaures on/off Virtual Machine Platform - On
VM - used RedHat 64bit
Set network to Bridged Adapter

Began install of SME10beta1 - all defaults except as above

at graphical install summary screen made sure Network was turned on (ensures network is working during setup later) I do same in all my installs regardless of platform

Install completed - yum update all OK

Added: sorry, server only mode, DHCP off, ip local 192.168.2.123 my gateway is 192.168.2.19

[brianr]

Can you try pinging centos.mirrorlist.org from the SME10 VM?

and also try pinging the SME10 VM from the Windows 10 host?

[TerryF]

Be handy to see what you have if you do this and post results here

PS C:\WINDOWS\system32> ipconfig

[dallas]

Be handy to see what you have if you do this and post results here

PS C:\WINDOWS\system32> ipconfig

Windows ipconfig output.

[dallas]

Can you try pinging centos.mirrorlist.org from the SME10 VM?

and also try pinging the SME10 VM from the Windows 10 host?

Both successful.

[dallas]

Windows 10 Home 20H2
Dell p6-2300a Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz   3.41 GHz

VirtualBox Version 6.1.18 r142142 (Qt5.6.2)

Set machine Bios to Virtualization On
Set windows 10 Fetaures on/off Virtual Machine Platform - On
VM - used RedHat 64bit
Set network to Bridged Adapter

Began install of SME10beta1 - all defaults except as above

at graphical install summary screen made sure Network was turned on (ensures network is working during setup later) I do same in all my installs regardless of platform

Install completed - yum update all OK

Added: sorry, server only mode, DHCP off, ip local 192.168.2.123 my gateway is 192.168.2.19

I'll try your config and report back.

[TerryF]

I am not familiar with VMware so am just guessing what the "Eth Adapter Vmware Network VMnet1" is the sme10 VM under VMware ??.

However .. here are the IPs you listed and mine for comparison,

I believe your issue is you have not setup your SME10 VM  to be on the same lan as your gateway.

Ensure VB network is set to bridged, VMware may have something similar

Yours

Gateway - 192.168.40.1

Win10 IP - 192.168.40.73

VB virtual adapter - 192.168.56.1

Eth Adapter Vmware Network VMnet1 - 192.168.10.1

VMware virt adapter - 192.168.31.1

SME10VM - ?? should be in range  - 192.168.40.#


Mine - server only setup

Gateway - 192.168.2.19

Win10 IP - 192.168.2.153

VB virtual adapter - 192.168.56.1

SME10 VM - 192.168.2.123

In my setup the gateway is providing the DHCP functionality, all others are turned off..

Good Luck

[TerryF]

So above is basics, just to add a little red herring for the future once you get it all working you can manipulate how your SME10 plays with networks and can do lots of interesting things wiki is a trove of gems...

[dallas]

I believe your issue is you have not setup your SME10 VM  to be on the same lan as your gateway.

SME10 VM IP is on the local lan, 192.168.40.150. I can run an ssh from the host (192.168.40.73) to the SME10. VB network is set to bridged.

[TerryF]

No worries, sweet

If still no yum update, then its something between your gateway and the mirrors

Can you say do a
# wget http://mirror.canada.pialasse.com/releases/testing/10/smeupdates-testing/x86_64/RPMS/smeserver-yum-2.6.0-46.el7.sme.noarch.rpm

Thats the latest smeserver-yum update in smeupdates-testing..

[TerryF]

maybe even try this, it is a valid update from smeupdates

# yum update http://mirror.canada.pialasse.com/releases/testing/10/smeupdates/x86_64/RPMS/smeserver-release-10.0-2.beta1.el7.sme.noarch.rpm

Added: if using the same VM to switch things about, worthwhile doing a # yum clean all just to clear its head

[dallas]

I think this is a hardware issue related to my new laptop. It may be specific the the laptops CPU.

I've installed VB on an old 2008 MacBook Pro and while the VM is extremely slow, I'm able to run yum update.
Further testing reveals that I can ssh into the MBP SME VM from any machine on my network. This is NOT true of the VM on the Dell laptop. While I can ssh from the Dell laptop that is hosting the VM I can't ssh from any other machine on the network.

Mystery solved. Happy to provide more details if anyone is interested.

Thank you everyone for your help and suggestions.

[TerryF]

Bloody PITA good to get to bottom of it... have to go and have a look at hardware specs to see what eth hardware details are .. even if just for hardware compat details etc, pity s that is a good bit of hardware you have

[dallas]

Here is the info about the hardware in both the old MBP & the Dell laptop.
I'm giving up on trying to get the Dell VM working. I'm suspicious of the USB-C Ethernet Adapter.

15in MacBook Pro Late 2008
Model 5,1
8GB 1067MHz DDR3 Memory
2.4 GHz Core 2 Duo P8600
Intel PRO/1000 EB 80003ES2LAN 10/100/1000BASE-T Gigabit Ethernet
OS Mojave - rEFInd boot manager

Dell Inspiron 15 ICL 5000 Series 5501
16GB 3200Mhz DDR4 Memory
10th Generation Intel Core i7-1065G7
Dell USB-C(M) to Gigabit Ethernet Adapter
OS Windows 10 Professional

[brianr]

I've just looked at the spec for this machine. There is no integral ethernet adaptor, just an addon USB-C to HDMI and Ethernet external adaptor. I suspect that VB is not connecting to the ehternet part of it sucessfully.

https://forums.virtualbox.org/viewtopic.php?t=74826

Post not quite aligned, but maybe indicative of a problem?

[dallas]

I installed Oracle_VM_VirtualBox_Extension_Pack-6.1.18.vbox-extpack and enabled USB 3. When I booted the VM it took over the USB-C port and I lost all network connection on the host. yum update in the VM still failed.
So my suspicion of the USB Ethernet adapter was correct.

BTW the Laptop has 1xHDMI, 2xUSB3, 1xUSB-C and a micro SD card reader.

[brianr]

I installed Oracle_VM_VirtualBox_Extension_Pack-6.1.18.vbox-extpack and enabled USB 3. When I booted the VM it took over the USB-C port and I lost all network connection on the host. yum update in the VM still failed.
So my suspicion of the USB Ethernet adapter was correct.

BTW the Laptop has 1xHDMI, 2xUSB3, 1xUSB-C and a micro SD card reader.

So that confirms our suspicions that the Dell Laptop arrangement for an ethernet connection are not compatible  with Virtual Box, or probably any of the other VM management tools!

[dallas]

So that confirms our suspicions that the Dell Laptop arrangement for an ethernet connection are not compatible  with Virtual Box, or probably any of the other VM management tools!

Yes that's my conclusion also. In fact any modern laptop is probably not suitable for running VMs as most are WiFi only.

[TerryF]

If I had the hardware would make an interesting investigation

As far as Wifi goes see this interesting bit of info - https://askubuntu.com/questions/363003/no-internet-connection-on-virtualbox-windows-7-as-guest-ubuntu-13-04-as-host

[dallas]

and also this https://forums.virtualbox.org/viewtopic.php?f=6&t=98133

I tried the WiFi and it didn't work either.

[TerryF]

You keep spoiling the party

[dallas]

You keep spoiling the party

Just happy to help out others. 

[Jean-Philippe Pialasse]

my two cents here. 
Not using vb but but virtmanager with libvirt on fedora. The default offered connexions did not work for me.  I had to manually create a bridge on my host and select this one to be able to have my vm to access the internet. 

[dallas]

my two cents here. 
Not using vb but but virtmanager with libvirt on fedora. The default offered connexions did not work for me.  I had to manually create a bridge on my host and select this one to be able to have my vm to access the internet.

We have determined that this is a hardware issue. Both VB and VMware Player have the same issue.