[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
Can you check for any differences betwewn the newly created VM and the old one. Set an alias as follows: alias virsh='virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf' Then: virsh dumpxml oldVM virsh dumpxml newVM Maybe somethhing can give a clue what is going on. Best Regards, Strahil NikolovOn Jan 12, 2020 20:03, Latchezar Filtchev wrote: > > Dear Strahil, > > > > Last strange discovery. Newly installed VM – same OS, same NIC’s – connected > to the same VLAN’s. Both machines are running on the same virtualization host. > > Newly installed VM – no network issues at all. It works flawlessly. > > > > It is really very strange. > > > > Best, > > Latcho > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UIJTEVABP5HYENJGH63JHZCPPHAVHCKT/
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
Maybe it's related to the CentOS 5.2 e1000 kernel module . Can you install another CentOS 5.2 and verify that the issue exists? Any chance to upgrade the VM to 5.11 or just update the kernel so it is at least 2.6.25 , so you can try the virtio NIC ? Best Regards, Strahil NikolovOn Jan 12, 2020 20:03, Latchezar Filtchev wrote: > > Dear Strahil, > > > > Last strange discovery. Newly installed VM – same OS, same NIC’s – connected > to the same VLAN’s. Both machines are running on the same virtualization host. > > Newly installed VM – no network issues at all. It works flawlessly. > > > > It is really very strange. > > > > Best, > > Latcho > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HV7U7GPKLUZFOGVDVTU27W72LZO7XBSF/
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
Dear Strahil, Last strange discovery. Newly installed VM – same OS, same NIC’s – connected to the same VLAN’s. Both machines are running on the same virtualization host. Newly installed VM – no network issues at all. It works flawlessly. It is really very strange. Best, Latcho From: Strahil Sent: Sunday, January 12, 2020 5:58 PM To: Latchezar Filtchev ; users Subject: RE: [ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7 I guess I didn't clarify myself. I asked if you can shutdown the VM and then set only this VM's 'Custom compatibility mode' to 4.2 and power up to test. Yet, if the cluster was at 4.2 when you imported , then I am afraid that the 'Custom Compatibility mode' won't make a difference. I'd recommend you to open a bug on bugzilla.redhat.com<http://bugzilla.redhat.com> and share the link with the mailing list. Many of the dev take a look here. But st Regards, Strahil Nikolov On Jan 12, 2020 15:02, Latchezar Filtchev mailto:lat...@aubg.bg>> wrote: Yes! It is. After upgrade 4.2 to 4.3 datacenter and cluster compatibility mode was 4.2 when I discovered the issue. Then I set Cluster mode to 4.3 – no luck. It is not so easy to return it to 4.2. Thank you! Best, Latcho From: ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/DU6WYXHWAGPW7MLPPYOWUGAKGBBQKLGC/
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
You were OK. I misunderstood. Checked and changed VM compatibility mode. It is the same. Bug – I will continue to troubleshoot. At least to convince myself that this is not caused by hardware used. Then I will file a bug. Thank you! Best, Latcho From: Strahil Sent: Sunday, January 12, 2020 5:58 PM To: Latchezar Filtchev ; users Subject: RE: [ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7 I guess I didn't clarify myself. I asked if you can shutdown the VM and then set only this VM's 'Custom compatibility mode' to 4.2 and power up to test. Yet, if the cluster was at 4.2 when you imported , then I am afraid that the 'Custom Compatibility mode' won't make a difference. I'd recommend you to open a bug on bugzilla.redhat.com<http://bugzilla.redhat.com> and share the link with the mailing list. Many of the dev take a look here. But st Regards, Strahil Nikolov On Jan 12, 2020 15:02, Latchezar Filtchev mailto:lat...@aubg.bg>> wrote: Yes! It is. After upgrade 4.2 to 4.3 datacenter and cluster compatibility mode was 4.2 when I discovered the issue. Then I set Cluster mode to 4.3 – no luck. It is not so easy to return it to 4.2. Thank you! Best, Latcho From: ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/HWQFGGLPZO4H2LTFWUVVJIIFNF3CM6HQ/
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
I guess I didn't clarify myself. I asked if you can shutdown the VM and then set only this VM's 'Custom compatibility mode' to 4.2 and power up to test. Yet, if the cluster was at 4.2 when you imported , then I am afraid that the 'Custom Compatibility mode' won't make a difference. I'd recommend you to open a bug on bugzilla.redhat.com and share the link with the mailing list. Many of the dev take a look here. But st Regards, Strahil NikolovOn Jan 12, 2020 15:02, Latchezar Filtchev wrote: > > Yes! It is. > > > > After upgrade 4.2 to 4.3 datacenter and cluster compatibility mode was 4.2 > when I discovered the issue. Then I set Cluster mode to 4.3 – no luck. It is > not so easy to return it to 4.2. > > > > Thank you! > > Best, > > Latcho > > > > > > From:___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Y54FJBWQ7MT4KZH4CS4CZXVIRZNJAKN3/
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
Yes! It is. After upgrade 4.2 to 4.3 datacenter and cluster compatibility mode was 4.2 when I discovered the issue. Then I set Cluster mode to 4.3 – no luck. It is not so easy to return it to 4.2. Thank you! Best, Latcho From: Strahil Sent: Sunday, January 12, 2020 2:20 PM To: Latchezar Filtchev ; users Subject: RE: [ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7 This seems quite odd. What happens when you set custom compatibility mode to 4.2 ? I think it was in Edit -> system -> Advanced options -> Custom compatibility mode -> 4.2 Best Regards, Strahil Nikolov On Jan 12, 2020 13:24, Latchezar Filtchev mailto:lat...@aubg.bg>> wrote: Hi Strahil, Unfortunately virtio drives cannot be used. Guest OS is CentOS 5.2, kernel 2.6.18-92.1.17.el5.centos.plusPAE The network connectivity of the VM is very short (please see below). Till I connect the VM (via spice) network connectivity is already gone. tcpdump –I eth0 –v tcpdump: listening on eth0, link-type EN10MB ( Ethernet ), capture 96 bytes 0 packets captured 0 packets received by filer 0 packets dropped by kernel From 172.17.17.7<http://172.17.17.7> icmp_seq=60 Destination Host Unreachable From 172.17.17.7<http://172.17.17.7> icmp_seq=61 Destination Host Unreachable From 172.17.17.7<http://172.17.17.7> icmp_seq=62 Destination Host Unreachable From 172.17.17.7<http://172.17.17.7> icmp_seq=63 Destination Host Unreachable From 172.17.17.7<http://172.17.17.7> icmp_seq=64 Destination Host Unreachable From 172.17.17.7<http://172.17.17.7> icmp_seq=65 Destination Host Unreachable 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=66 ttl=64 time=2.19 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=67 ttl=64 time=0.567 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=68 ttl=64 time=0.339 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=69 ttl=64 time=0.337 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=70 ttl=64 time=0.288 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=71 ttl=64 time=0.305 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=72 ttl=64 time=0.293 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=73 ttl=64 time=0.346 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=74 ttl=64 time=0.359 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=75 ttl=64 time=0.479 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=76 ttl=64 time=0.391 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=77 ttl=64 time=0.302 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=78 ttl=64 time=0.327 ms 64 bytes from 172.17.16.16<http://172.17.16.16>: icmp_seq=79 ttl=64 time=0.321 ms From 172.17.17.7<http://172.17.17.7> icmp_seq=125 Destination Host Unreachable From 172.17.17.7<http://172.17.17.7> icmp_seq=126 Destination Host Unreachable From 172.17.17.7<http://172.17.17.7> icmp_seq=127 Destination Host Unreachable From 172.17.17.7<http://172.17.17.7> icmp_seq=128 Destination Host Unreachable Thank you! Best, Latcho From: Strahil Nikolov mailto:hunter86...@yahoo.com>> Sent: Sunday, January 12, 2020 12:52 PM To: users mailto:users@ovirt.org>>; Latchezar Filtchev mailto:lat...@aubg.bg>> Subject: Re: [ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7 Hi Lacho, Can you run the virtio drivers ? They are the most tested in KVM . Also, can you run a tcpdump (with e1000) and check what is going on when the network disapperead? Best Regards, Strahil Nikolov В неделя, 12 януари 2020 г., 09:22:52 ч. Гринуич+2, Latchezar Filtchev mailto:lat...@aubg.bg>> написа: Dear Strahi, I tried rtl8139. The behavior is the same. Best, Latcho From: Strahil mailto:hunter86...@yahoo.com>> Sent: Sunday, January 12, 2020 1:19 AM To: Latchezar Filtchev mailto:lat...@aubg.bg>>; users mailto:users@ovirt.org>> Subject: Re: [ovirt-users] Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7 Hi Latcho, Most probably it's a bug. Have you tried virtio and/or rtl-based NIC ? As far as I know, CentOS 5 supports Virtio after Kernel >= 2.6.25 . Best Regards, Strahil Nikolov On Jan 11, 2020 19:54, Latchezar Filtchev mailto:lat...@aubg.bg>> wrote: Hello Everyone, I am aware my guest OS is out of support but I experienced the following: oVirt – 4.2.8 (self-hosted engine) VM – CentOS 5.2; two VNIC’s ( driver used e1000) connected to different VLAN’s; - no issues with network connectivity After upgrade to oVirt 4.3.7 The same VM starts normally. Network is available for several seconds (10 – 20 pings) and then it disappears. The machine works but no ping t
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
This seems quite odd. What happens when you set custom compatibility mode to 4.2 ? I think it was in Edit -> system -> Advanced options -> Custom compatibility mode -> 4.2 Best Regards, Strahil NikolovOn Jan 12, 2020 13:24, Latchezar Filtchev wrote: > > Hi Strahil, > > > > Unfortunately virtio drives cannot be used. Guest OS is CentOS 5.2, kernel > 2.6.18-92.1.17.el5.centos.plusPAE > > > > The network connectivity of the VM is very short (please see below). Till I > connect the VM (via spice) network connectivity is already gone. > > tcpdump –I eth0 –v > > tcpdump: listening on eth0, link-type EN10MB ( Ethernet ), capture 96 bytes > > > > 0 packets captured > > 0 packets received by filer > > 0 packets dropped by kernel > > > > From 172.17.17.7 icmp_seq=60 Destination Host Unreachable > > From 172.17.17.7 icmp_seq=61 Destination Host Unreachable > > From 172.17.17.7 icmp_seq=62 Destination Host Unreachable > > From 172.17.17.7 icmp_seq=63 Destination Host Unreachable > > From 172.17.17.7 icmp_seq=64 Destination Host Unreachable > > From 172.17.17.7 icmp_seq=65 Destination Host Unreachable > > 64 bytes from 172.17.16.16: icmp_seq=66 ttl=64 time=2.19 ms > > 64 bytes from 172.17.16.16: icmp_seq=67 ttl=64 time=0.567 ms > > 64 bytes from 172.17.16.16: icmp_seq=68 ttl=64 time=0.339 ms > > 64 bytes from 172.17.16.16: icmp_seq=69 ttl=64 time=0.337 ms > > 64 bytes from 172.17.16.16: icmp_seq=70 ttl=64 time=0.288 ms > > 64 bytes from 172.17.16.16: icmp_seq=71 ttl=64 time=0.305 ms > > 64 bytes from 172.17.16.16: icmp_seq=72 ttl=64 time=0.293 ms > > 64 bytes from 172.17.16.16: icmp_seq=73 ttl=64 time=0.346 ms > > 64 bytes from 172.17.16.16: icmp_seq=74 ttl=64 time=0.359 ms > > 64 bytes from 172.17.16.16: icmp_seq=75 ttl=64 time=0.479 ms > > 64 bytes from 172.17.16.16: icmp_seq=76 ttl=64 time=0.391 ms > > 64 bytes from 172.17.16.16: icmp_seq=77 ttl=64 time=0.302 ms > > 64 bytes from 172.17.16.16: icmp_seq=78 ttl=64 time=0.327 ms > > 64 bytes from 172.17.16.16: icmp_seq=79 ttl=64 time=0.321 ms > > From 172.17.17.7 icmp_seq=125 Destination Host Unreachable > > From 172.17.17.7 icmp_seq=126 Destination Host Unreachable > > From 172.17.17.7 icmp_seq=127 Destination Host Unreachable > > From 172.17.17.7 icmp_seq=128 Destination Host Unreachable > > > > Thank you! > > Best, > > Latcho > > > > > > From: Strahil Nikolov > Sent: Sunday, January 12, 2020 12:52 PM > To: users ; Latchezar Filtchev > Subject: Re: [ovirt-users] Re: Unstable VM network connectivity after upgrade > 4.2.8 to 4.3.7 > > > > Hi Lacho, > > > > Can you run the virtio drivers ? > > > > They are the most tested in KVM . > > > > Also, can you run a tcpdump (with e1000) and check what is going on when the > network disapperead? > > > > Best Regards, > > Strahil Nikolov > > > > В неделя, 12 януари 2020 г., 09:22:52 ч. Гринуич+2, Latchezar Filtchev > написа: > > > > > > Dear Strahi, > > > > I tried rtl8139. The behavior is the same. > > > > Best, > > Latcho > > > > > > From: Strahil > Sent: Sunday, January 12, 2020 1:19 AM > To: Latchezar Filtchev ; users > Subject: Re: [ovirt-users] Unstable VM network connectivity after upgrade > 4.2.8 to 4.3.7 > > > > Hi Latcho, > > Most probably it's a bug. > Have you tried virtio and/or rtl-based NIC ? > > As far as I know, CentOS 5 supports Virtio after Kernel >= 2.6.25 . > > Best Regards, > Strahil Nikolov > > On Jan 11, 2020 19:54, Latchezar Filtchev wrote: >> >> Hello Everyone, >> >> >> >> I am aware my guest OS is out of support but I experienced the following: >> >> >> >> oVirt – 4.2.8 (self-hosted engine) >> >> VM – CentOS 5.2; two VNIC’s ( driver used e1000) connected to different >> VLAN’s; - no issues with network connectivity >> >> >> >> After upgrade to oVirt 4.3.7 >> >> >> >> The same VM starts normally. Network is available for several seconds (10 – >> 20 pings) and then it disappears. The machine works but no ping to/from VM. >> When I am returning the same machine (via export domain) to oVirt 4.2.8 >> environment – it works as expected. >> >> >> >> Can someone advise on this? Any help will be greatly appreciated. >> >> >> >> Thank you. >> >> Best, >> >> Latcho >> >> >> >> >> >> &g
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
Hi Strahil, Unfortunately virtio drives cannot be used. Guest OS is CentOS 5.2, kernel 2.6.18-92.1.17.el5.centos.plusPAE The network connectivity of the VM is very short (please see below). Till I connect the VM (via spice) network connectivity is already gone. tcpdump –I eth0 –v tcpdump: listening on eth0, link-type EN10MB ( Ethernet ), capture 96 bytes 0 packets captured 0 packets received by filer 0 packets dropped by kernel From 172.17.17.7 icmp_seq=60 Destination Host Unreachable From 172.17.17.7 icmp_seq=61 Destination Host Unreachable From 172.17.17.7 icmp_seq=62 Destination Host Unreachable From 172.17.17.7 icmp_seq=63 Destination Host Unreachable From 172.17.17.7 icmp_seq=64 Destination Host Unreachable From 172.17.17.7 icmp_seq=65 Destination Host Unreachable 64 bytes from 172.17.16.16: icmp_seq=66 ttl=64 time=2.19 ms 64 bytes from 172.17.16.16: icmp_seq=67 ttl=64 time=0.567 ms 64 bytes from 172.17.16.16: icmp_seq=68 ttl=64 time=0.339 ms 64 bytes from 172.17.16.16: icmp_seq=69 ttl=64 time=0.337 ms 64 bytes from 172.17.16.16: icmp_seq=70 ttl=64 time=0.288 ms 64 bytes from 172.17.16.16: icmp_seq=71 ttl=64 time=0.305 ms 64 bytes from 172.17.16.16: icmp_seq=72 ttl=64 time=0.293 ms 64 bytes from 172.17.16.16: icmp_seq=73 ttl=64 time=0.346 ms 64 bytes from 172.17.16.16: icmp_seq=74 ttl=64 time=0.359 ms 64 bytes from 172.17.16.16: icmp_seq=75 ttl=64 time=0.479 ms 64 bytes from 172.17.16.16: icmp_seq=76 ttl=64 time=0.391 ms 64 bytes from 172.17.16.16: icmp_seq=77 ttl=64 time=0.302 ms 64 bytes from 172.17.16.16: icmp_seq=78 ttl=64 time=0.327 ms 64 bytes from 172.17.16.16: icmp_seq=79 ttl=64 time=0.321 ms From 172.17.17.7 icmp_seq=125 Destination Host Unreachable From 172.17.17.7 icmp_seq=126 Destination Host Unreachable From 172.17.17.7 icmp_seq=127 Destination Host Unreachable From 172.17.17.7 icmp_seq=128 Destination Host Unreachable Thank you! Best, Latcho From: Strahil Nikolov Sent: Sunday, January 12, 2020 12:52 PM To: users ; Latchezar Filtchev Subject: Re: [ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7 Hi Lacho, Can you run the virtio drivers ? They are the most tested in KVM . Also, can you run a tcpdump (with e1000) and check what is going on when the network disapperead? Best Regards, Strahil Nikolov В неделя, 12 януари 2020 г., 09:22:52 ч. Гринуич+2, Latchezar Filtchev mailto:lat...@aubg.bg>> написа: Dear Strahi, I tried rtl8139. The behavior is the same. Best, Latcho From: Strahil mailto:hunter86...@yahoo.com>> Sent: Sunday, January 12, 2020 1:19 AM To: Latchezar Filtchev mailto:lat...@aubg.bg>>; users mailto:users@ovirt.org>> Subject: Re: [ovirt-users] Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7 Hi Latcho, Most probably it's a bug. Have you tried virtio and/or rtl-based NIC ? As far as I know, CentOS 5 supports Virtio after Kernel >= 2.6.25 . Best Regards, Strahil Nikolov On Jan 11, 2020 19:54, Latchezar Filtchev mailto:lat...@aubg.bg>> wrote: Hello Everyone, I am aware my guest OS is out of support but I experienced the following: oVirt – 4.2.8 (self-hosted engine) VM – CentOS 5.2; two VNIC’s ( driver used e1000) connected to different VLAN’s; - no issues with network connectivity After upgrade to oVirt 4.3.7 The same VM starts normally. Network is available for several seconds (10 – 20 pings) and then it disappears. The machine works but no ping to/from VM. When I am returning the same machine (via export domain) to oVirt 4.2.8 environment – it works as expected. Can someone advise on this? Any help will be greatly appreciated. Thank you. Best, Latcho ___ Users mailing list -- users@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-le...@ovirt.org<mailto:users-le...@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/DAPMFAA3XZOUJ2K4PAMOS7O6BULEBRFF/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VA45WAX4EFEW7FE6J2UKGBOC52R4JW5A/
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
Hi Lacho, Can you run the virtio drivers ? They are the most tested in KVM . Also, can you run a tcpdump (with e1000) and check what is going on when the network disapperead? Best Regards,Strahil Nikolov В неделя, 12 януари 2020 г., 09:22:52 ч. Гринуич+2, Latchezar Filtchev написа: Dear Strahi, I tried rtl8139. The behavior is the same. Best, Latcho From: Strahil Sent: Sunday, January 12, 2020 1:19 AM To: Latchezar Filtchev ; users Subject: Re: [ovirt-users] Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7 Hi Latcho, Most probably it's a bug. Have you tried virtio and/or rtl-based NIC ? As far as I know, CentOS 5 supports Virtio after Kernel >= 2.6.25 . Best Regards, Strahil Nikolov On Jan 11, 2020 19:54, Latchezar Filtchev wrote: Hello Everyone, I am aware my guest OS is out of support but I experienced the following: oVirt – 4.2.8 (self-hosted engine) VM – CentOS 5.2; two VNIC’s ( driver used e1000) connected to different VLAN’s; - no issues with network connectivity After upgrade to oVirt 4.3.7 The same VM starts normally. Network is available for several seconds (10 – 20 pings) and then it disappears. The machine works but no ping to/from VM. When I am returning the same machine (via export domain) to oVirt 4.2.8 environment – it works as expected. Can someone advise on this? Any help will be greatly appreciated. Thank you. Best, Latcho ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/DAPMFAA3XZOUJ2K4PAMOS7O6BULEBRFF/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/BE6B3JVAQBVA2RCB6LT72H6FZSCY4Y5X/
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
Dear Strahi, I tried rtl8139. The behavior is the same. Best, Latcho From: Strahil Sent: Sunday, January 12, 2020 1:19 AM To: Latchezar Filtchev ; users Subject: Re: [ovirt-users] Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7 Hi Latcho, Most probably it's a bug. Have you tried virtio and/or rtl-based NIC ? As far as I know, CentOS 5 supports Virtio after Kernel >= 2.6.25 . Best Regards, Strahil Nikolov On Jan 11, 2020 19:54, Latchezar Filtchev mailto:lat...@aubg.bg>> wrote: Hello Everyone, I am aware my guest OS is out of support but I experienced the following: oVirt – 4.2.8 (self-hosted engine) VM – CentOS 5.2; two VNIC’s ( driver used e1000) connected to different VLAN’s; - no issues with network connectivity After upgrade to oVirt 4.3.7 The same VM starts normally. Network is available for several seconds (10 – 20 pings) and then it disappears. The machine works but no ping to/from VM. When I am returning the same machine (via export domain) to oVirt 4.2.8 environment – it works as expected. Can someone advise on this? Any help will be greatly appreciated. Thank you. Best, Latcho ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/DAPMFAA3XZOUJ2K4PAMOS7O6BULEBRFF/
[ovirt-users] Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
Hi Latcho, Most probably it's a bug. Have you tried virtio and/or rtl-based NIC ? As far as I know, CentOS 5 supports Virtio after Kernel >= 2.6.25 . Best Regards, Strahil NikolovOn Jan 11, 2020 19:54, Latchezar Filtchev wrote: > > Hello Everyone, > > > > I am aware my guest OS is out of support but I experienced the following: > > > > oVirt – 4.2.8 (self-hosted engine) > > VM – CentOS 5.2; two VNIC’s ( driver used e1000) connected to different > VLAN’s; - no issues with network connectivity > > > > After upgrade to oVirt 4.3.7 > > > > The same VM starts normally. Network is available for several seconds (10 – > 20 pings) and then it disappears. The machine works but no ping to/from VM. > When I am returning the same machine (via export domain) to oVirt 4.2.8 > environment – it works as expected. > > > > Can someone advise on this? Any help will be greatly appreciated. > > > > Thank you. > > Best, > > Latcho > > > > > > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/Q6ZSFPI72NO5DNGTNM5XM2GFKIC6FAYY/
