Topic: Yum update fails on VirtualBox 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