On 5/2/20 02:20, Ed Greshko wrote:
On 2020-02-04 17:45, Stephen Morris wrote:
> I tried Virtualbox with vm's for every version of Fedora from F29 to F31 and
internet access fails in every version. The network gets an IP Address from DHCP and
Firefox can access
http://www.google.com.au and return results for google searches, but it
cannot access the default home page of
https://start.fedoraproject.org, nor can dnf
refresh any of its repositories. It also doesn't matter what network setting I specify
in the VM settings the same thing happens on every one of them. I'm not
sure at the moment what the issue is.
Well, you are running VMware Player and VirtualBox as host on Windows 10. And the guest
systems
are Fedora.
This is opposite of what I, and I suspect others here, are familiar with.
My bare metal systems are all Fedora. I run both VirtualBox and QEMU virtualization
without difficulty.
Yes, there are some quirks. But those quirks are most likely different if your bare
metal system is Windows.
IMO, you probably should seek help from those running virtualization with Windows as the
host system.
Thanks Ed, I'll see if I can find someone who is running the same
setup
as me.
As a side issue, I had to reinstall vmware and virtualbox as a result of
having to reinstall windows because the SSD that is windows drive c died
on the weekend. After the reinstall of virtualbox the network issues I
had with the original install have disappeared, but the X11 virtualbox
video driver supplied by fedora does not support the 4k resolution of my
monitor whereas the X11 vmware driver supplied by fedora does. Is this
something that can be raised as a bugzilla?
regards,
Steve