>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 wrote:
> hi,
>
> here is the requested informations.
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 :
> 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 a
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 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
>
>
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 :
> hello,
>
> I come back to you with this subject that I opened to bring some
> clarifications, because my problem remai
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 g
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/
