Re: [Qemu-discuss] e1000 / pc ~ e1000e / q35

[Pascal]

hello,

I come back to you with this subject that I opened to bring some
clarifications, because my problem remains and also because nobody seems
confronted with it.

my physical host is an ArchLinux with 4.14.40-1-lts kernel and Qemu 2.12.0.

in my first virtualisation case, my virtual host - my guest - is an
ArchLinux with 4.9.36-1-lts kernel (e1000e ver. 3.2.6-k) : everything works
normally when I request the assignment of a network address with dhcpcd
(after a few seconds, my guest gets the 10.0.2.15 intended address).

in my second virtualisation case, my guest is an ArchLinux with
4.14.40-1-lts kernel (e1000e ver. 3.2.6-k) : no carrier is detected and
therefore no address is assigned to the enp0s2 network card.

this problem does not appear if I add in both cases the parameter *"-machine
pc"* (which forces the use of the module e1000/ens3 instead of the module
e1000e/enp0s2).

I think the problem would rather come from the virtualized 4.14.40-1-lts
kernel side because I do not meet it on my physical host which also uses
the e1000e module...

does anyone have an idea or a lead ?

regards, lacsaP.

2018-05-11 15:39 GMT+02:00 Pascal <address@hidden>:

> hi,
>
> when I run qemu with machine pc, my virtual network card "runs", but not
> when I run it with machine q35.
>
> in the first case (pc), module e1000 is loaded and dhcpcd on ens3 is ok (
> 10.0.2.15/24).
>
> in the second case (q35), module e1000e is loaded and dhcpcd on enp0s2 is
> ko (waiting for carrier/timed out).
>
> does anyone have a lead ?
>
> my host is ArchLinux 4.14.40-1-lts and my guest is ArchLinux 4.14.32-1-lts.
>
> regards.
>