[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Probs on Windows Host
|
From: |
Ken Moffat |
|
Subject: |
Re: Probs on Windows Host |
|
Date: |
Sat, 2 Nov 2019 22:08:59 +0000 |
|
User-agent: |
Mutt/1.12.2 (2019-09-21) |
On Sat, Nov 02, 2019 at 11:18:34AM -0700, Johny Why wrote:
> hi
>
> getting some issues with qemu running arch-linux guest on a windows 10 host.
> - unexpected ram size
> - no eth0
> - no internet connection
>
For the eth0 question -
> archlabs live iso boots, and says:
> `-> ram: 47mb`
> Why not 600M?
>
> ````
> ip link
> 1: lo <LOOPBACK...
> 2. ens3 <BROADCAST...
> ````
> Why no eth0?
>
For machines with potentially several interfaces, somebody decided
to give predicatable names, see e.g.
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
This is normal on most current distros. On the desktop machine
where I'm typing this the single i/f is enp8s0.
> Attempting to enable wifi with:
> ```
> systemctl enable dhcpcd@ens3.service
> systemctl start dhcpcd@ens3.service
> https://bbs.archlinux.org/viewtopic.php?pid=1182093
> ```
> No errors, but pinging google.com fails with "0 received".
>
That is not the wifi, it is the wired ethernet. If qemu finds a
wireless interface it will have a name starting 'wl'.
> any suggestions?
> thx
ĸen
--
Whilst all mushrooms are edible, the trick is to eat only those which
will prove to be edible more than once. The Celebrated Discworld Almanak
recommends you play safe and eat beans on toast.