- Users - oVirt List Archives

How can I link the cloned disks from a snapshot to the original disks?
by FMGarcia 13 Jan '20

13 Jan '20

Hello, Sorry, I posted in bugzilla, and you advise me than my question isn't error. https://bugzilla.redhat.com/show_bug.cgi?id=1789534 I will attach the same archives and the same text. Description of problem: This problem is bizarre/unusual/convoluted, such that I think that it won't affect to anybody. But the system allows it. In a backup from snapshot with several disks, we can know the original disks from each disk through their names and their sizes. But, and if several disks had the same name and same size? How could we do it without inspect the content of each disk? With the java Sdk, the order of the discs from the original machine to the cloned machine changes, making this path not possible either. In attached files, I show the disks[with different name and order of java Sdk] of the original vm[vm1] and the cloned vm[vm1Clone]. And others[vm2] and [vm2Clone] with the same process, but all disks have the same name. The disks have two sizes: 1Gb and 2Gb. Steps to Reproduce: 1. Create a vm, and attach several disks with same name and same size. 2. Create a backup from snapshot. 3. Now, try to differentiate the disks cloned from original, without looking at their contents. Actual results: I think that it is impossible without I look at their contents. Expected results: Knowing which disk of the cloned machine links to which disk of the original machine. Additional info: If you need more info, request me it Vm.log -> Vm original with different disk name VmClone.log -> Vm clone with different disk name Vm2.log -> Vm original with same disk name Vm2Clone.log -> Cloned vm with same disk name Thanks for your time, Fran

1 0

Re: Please Help, Ovirt Node Hosted Engine Deployment Problems 4.3.2
by William Smyth 13 Jan '20

13 Jan '20

I'm running into the exact same issue as described in this thread. The HostedEngine VM (HE) loses connectivity during the deployment while on the NAT'd network and the deployment fails. My HE VM is never migrated to shared storage because that part of the process hasn't been reached, nor have I been asked for the shared storage details, which are simple NFS shares. I've tried the deployment from the CLI and through Cockpit, both times using the Ansible deployment, and both times reaching the same conclusion. I did manage to connect to the Centos 7 host that is running the HE guest with virt-manager and moved the NIC to the 'ovirtmgmt' vswitch using macvtap, which allowed me to access HE from the outside world. One of the big issues though is that the HE isn't on shared storage and I'm not sure how to move it there. I'm running 2 Centos 7 hosts with different CPU makes, AMD and Intel. So i have two separate single-host clusters but I'm trying to at least have the HA setup for the HE, which I think is still possible. I know that I won't be able to do a live migration, but that's not a big deal. I'm afraid my failed deployment of HE is preventing this and I'm at an impasse. I don't want to give up on oVirt but it's becoming difficult to get my lab environment operational and I'm wasting a lot of time troubleshooting. Any help or suggestions would be greatly appreciated. William Smyth

1 0

Can we please migrate to 2020 and get a user friendly issues/support tool?
by m.skrzetuski＠gmail.com 13 Jan '20

13 Jan '20

Hello everyone, I can speak only for myself but I find mailing lists so 1990. Could we migrate this list to something (user friendly) Jira like? I have to admit it's rather difficult to search an read the archive for old issues in the e-mail format. Kind regards Skrzetuski

3 3

Setting up cockpit?
by m.skrzetuski＠gmail.com 13 Jan '20

13 Jan '20

Hello everyone, I'd like to get cockpit to work because currently when I click "Host Console" on a host I just get "connection refused". I checked and after the engine installation the cockpit service was not running. When I start it, it runs and answers on port 9090, however the SSL certificate is broken. - How do I auto enable cockpit on installation? - How do I supply my own SSL certification to cockpit? Kind regards Skrzetuski

2 8

Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
by Strahil 12 Jan '20

12 Jan '20

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 <Latcho(a)aubg.bg> 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 > >

1 0

Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
by Strahil 12 Jan '20

12 Jan '20

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 <Latcho(a)aubg.bg> 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 > >

1 0

Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
by Strahil 12 Jan '20

12 Jan '20

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 <Latcho(a)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:

2 2

Low disk space on Storage
by suporte＠logicworks.pt 12 Jan '20

12 Jan '20

Hi, I'm running ovirt Version:4.3.4.3-1.el7 My filesystem disk has 30 GB free space. Cannot start a VM due to an I/O error storage. When tryng to move the disk to another storage domain get this error: Error while executing action: Cannot move Virtual Disk. Low disk space on Storage Domain DATA4. The sum of pre-allocated disk is the total of the storage domain disk. Any idea what can I do to move a disk to other storage domain? Many thanks -- Jose Ferradeira http://www.logicworks.pt

5 5

Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
by Strahil 12 Jan '20

12 Jan '20

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 <Latcho(a)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 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 <hunter86_bg(a)yahoo.com> > Sent: Sunday, January 12, 2020 12:52 PM > To: users <users(a)ovirt.org>; Latchezar Filtchev <Latcho(a)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 <latcho(a)aubg.bg> написа: > > > > > > Dear Strahi, > > > > I tried rtl8139. The behavior is the same. > > > > Best, > > Latcho > > > > > > From: Strahil <hunter86_bg(a)yahoo.com> > Sent: Sunday, January 12, 2020 1:19 AM > To: Latchezar Filtchev <Latcho(a)aubg.bg>; users <users(a)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 <Latcho(a)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(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/DAPMFAA3XZOUJ…

2 1

Re: Unstable VM network connectivity after upgrade 4.2.8 to 4.3.7
by Strahil 12 Jan '20

12 Jan '20

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 <Latcho(a)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 > > > > > >

3 3