Hi,

Config:
Os: Windows Server 2022
VM server: Hyper-V
VM Guest: scratch Linux, from linuxfromscratch.org, so(4 me) moslty unix, versus Linux: network command available(afk) ifconfig, ip - no netstat, lshw
Operating mode: console, so no GUI like in uBuntu, Debian.
Network Card: Virtual, i have try with Legacy, but still not working.

I have problem to get to work the virtual network card in the guess vm, im not sure how network hardware or hardware work in Unix - Linux, like i undestand and do with Windows:

Did i have to install driver?

It doesn't seem's normal that i don't have any valid MAC address when i do ifconfig, did i have to start from there?

here is my ifconfig output(sorry 4 images, no networking, no copy-paste):



Remark: i dont have any mention about eth0 there.

Just to let you know that i have other guess vm(centOS, console mode) work with the same hardware, virtual switch, etc.

I'm really not sure that the guess vm see the hardware network card at all...

Help Please !!!

tx

Welcome 2LQ.org!!! I'm surprised the wise experts didn't jump in to help you
(I rate my Linux expertise about 0.2 on a scale of 0 to 10: I know about 2% of Linux)

It looks like your Linux guest did not see an ethernet card (virtual) Hardware presented by the hyper-v host. (I love virtualbox and have never tried hyper-v [nor VMware], but I am not suggesting it, because you would have to totally get rid of hyper-v [only one hypervisor allowed I guess], which you probably use for other things.)

You might try another distro (just as a 'sanity check'): my favorite is MLL (the .iso is only 10 MB)

I think you also have to do something with hyper-v, which I public_Library-researched here: https://www.linuxquestions.org/quest...1/#post6375283 (I had dozens of hours of enjoyable learning, but the Original Poster [OP] never came back to LQ after their last post)

I've only created VM's on Hyper-V on the free server version. It was a very complex command line process. The full version has access to a easier way. So, I'd ask the question, did you create a nic and exactly how if you did?

i'm surprise too, over 100 views, just your two replies probably that it is not much common

thank for trying to help me !!

yes it look like many users use VB and look that their less problem(i'm really not sure), but i really wan't trying to continue using hyper-v

yes it look a long reading, i will check your link

@jefro: i'm just create a default external virtual switch in hyper-v and select it when i create the VM, i have try Legacy network card too, without success. If you use hyper-v with GUI, the option is available on the right side(Virtual Switch Manager), like you i have already create vm(with virtual switch) with command line on an hyper-v core server, yes it is more complex(hope i've been exact

i have check your idea of MLL, it look very nice and tiny(that's what i want), but it look like another os that i have to compile and that's what i do woth LFS. I think i will stay with LFS because i already do it(just have to fix my network problem) and i'm not sure i want to go under another long reading and try with another thing that is look similar to LFS. Wanna add that i like the way to build all the source to create a Linux or Unix distro, i think it is better for know how Linux work, anyway we will see

i think i have advance a bit(hopefully):

i finally compile the lshw utility and got some other and i think helpful information that i will share here with you

lshw show me that i have a network card, but 'UNCLAIMED' and habitually this mean that no driver are claimed for this devices, here is the output(sorry again 4 imaging):



you see there, product and vendor?

if you google this, you gonna see that Intel doesn't seem's want to share the source for their driver:

https://community.intel.com/t5/Ether...ler/m-p/717084

i have found this page and i think i'm gonna try to go over with this suggested compilation open source:

https://github.com/torvalds/linux/bl...p/tulip_core.c

but i'm not sure where to find inclusion like Linux/??

any advise will be appreciated, thanks in advance !!!

(I'm guessing) you need the appropriate driver for that insane device, listed in your picture, which M$EvilOS presents to you. (Look into the few common=sane devices which virtualbox present and the pre-built MLL.iso is happy with!!!)

Web research the device name shown in your picture plus some keywords like Linux driver. You will find something like:
https://bugs.launchpad.net/ubuntu/+s...x/+bug/1440072
Try running ubuntu, even it's mini ISO.

This reminds me of the conspiracy theory that: Microsoft will only allow its version of Linux (Ubuntu, once it buys Canonical for a MuskPenny) to exist

Maybe #3 will give us_n00bs some hits on how to add the "DECchip 21140" driver to LFS (/ANYlinux &post this .config for my mll), for M$HypErVil

P. S. IDK (yet!!!) How to add drivers, like for my Wi-Fi or the OP's "DECchip 21140" to mll (just in case someone wants to spend the time doing this, to make an mll .iso that will work for the OP). (I have managed to install static binaries, even from a .deb, but I haven't gotten myself motivated to figure out how to add drivers and rebuild an MLL ISO)