Hi Strahil and Gianluca,

Thank you guys so much for getting back to me.

I was using e1000 for VMs, not physical servers. Much appreciated for your
suggestions and I've turned to virtio and would redo the stress testing.
Hope everything works fine. 😀

Happy new year.

Regards,
Joey


On Thu, Dec 31, 2020 at 9:32 PM Gianluca Cecchi <gianluca.cec...@gmail.com>
wrote:

> On Thu, Dec 31, 2020 at 8:04 AM Strahil Nikolov via Users <users@ovirt.org>
> wrote:
>
>> Are you using E1000 on the VMs or on the Host ?
>> If it's the second , you should change the hardware .
>>
>> I have never used e1000 for VMs as it is an old tech. Better to install
>> the virtio drivers and then use the virtio type of NIC.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> [snip]
>
>>
>> Hi folks,
>>
>> Happy holidays.
>>
>> I'm having an urgent problem :smile: .
>>
>> I've installed oVirt 4.4.2 on CentOS 8.2 and then created several Windows
>> 7 vms for stress testing. I found that the heavy network load would lead to
>> the e1000 net card NOT able to receive packets, it seemed totally blocked.
>> In the meantime, packet sending was fine.
>>
>> Only re-enabling the net card can restore the network. Has anyone also
>> had this problem? Looking forward to your insights. Much appreciated.
>>
>>
>> Best regards,
>> Joey
>>
>>
>>
> You should follow what described here that seems somehow updated because
> the previously "oVirt Guest Tools" iso is no longer referred there.
>
>
> https://www.ovirt.org/documentation/virtual_machine_management_guide/#chap-Installing_Windows_Virtual_Machines
>
> In practice you have to install the virtio-win rpm package on your engine
> (now at 1.9.14.4 version) and then upload the file
> /usr/share/virtio-win/virtio-win.iso (actually a link to the exact release
> version file) as a disk to a storage domain
>
> Then you can attach the iso to the VM and inside the iso you will find
> under the NetKVM directory some subdirs for the different os versions and
> w7 (with both x86 and amd64 subdirs) is still there.
> To use drivers for paravirtualized network devices you have to choose
> VirtIO as the type of the network interface in web admin gui for the VM and
> probably reconfigure it inside the OS because it will be detected as a new
> one and will lose previous configuration.
> You can also use (at install time or later) paravirtualized drivers for
> disks.
>
> HIH,
> Gianluca
>
>
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LLCCNS6ZNRHYP6UWX2PO77JV6AJURY32/

Reply via email to