qemu-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Han Han
Subject: Re: [Qemu-discuss] e1000 / pc ~ e1000e / q35
Date: Fri, 1 Jun 2018 14:45:17 +0800

>From the description, I think you are very likely hit this kernel bug:
https://bugzilla.kernel.org/show_bug.cgi?id=198047

It seems unfixed in 4.14.4 . Please use other kernel version for workaround
:)

On Thu, May 31, 2018 at 4:04 PM, Pascal <address@hidden> wrote:

> hi,
>
> here is the requested informations.
> I hope it will help you.
> I am available if you need more informations.
>
> regards.
>
> 2018-05-30 12:18 GMT+02:00 Han Han <address@hidden>:
>
>> I didn't face the problem in rhel. But I suggest you to provide the dmesg
>> and modinfo of e1000e in your VM.
>>
>> On Mon, May 28, 2018 at 9:53 PM, Pascal <address@hidden> wrote:
>>
>>> the guests are started as follows :
>>>
>>> /usr/bin/qemu-system-x86_64 -enable-kvm -m 2048 -machine {q35|pc} -usb
>>> -hda
>>> {arch1|arch2}.img
>>>
>>> regards.
>>>
>>> 2018-05-28 15:32 GMT+02:00 Pascal <address@hidden>:
>>>
>>> > 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.
>>> >>
>>> >
>>> >
>>>
>>
>>
>>
>> --
>> Best regards,
>> -----------------------------------
>> Han Han
>> Quality Engineer
>> Redhat.
>>
>> Email: address@hidden
>> Phone: +861065339333
>>
>
>


-- 
Best regards,
-----------------------------------
Han Han
Quality Engineer
Redhat.

Email: address@hidden
Phone: +861065339333


reply via email to

[Prev in Thread] Current Thread [Next in Thread]