On 1/13/20 12:14 AM, m.skrzetu...@gmail.com wrote:
I just saw the list of modules at
Does this mean you (oVirt devs) did not update ovirt Ansible modules
I just saw the list of modules at
Does this mean you (oVirt devs) did not update ovirt Ansible modules since 2
Anyhow, the following tasks create a VM with
Well if *you* don't see any issues then we can finally sleep at night.
Users mailing list -- email@example.com
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
Can you check for any differences betwewn the newly created VM and the old one.
Set an alias as follows:
alias virsh='virsh -c
virsh dumpxml oldVM
virsh dumpxml newVM
Maybe somethhing can give a clue what is going on.
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 ?
Strahil NikolovOn Jan 12,
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.
You were OK. I misunderstood. Checked and changed VM compatibility mode. It is
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.
Sent: Sunday, January 12, 2020
my guess is that you have a linux system running there.Usually even in a
SAN-based environement , we keep our Bare-Metal Hosts with LUNs no bigger than
Picking 16TB as a single disk is a poor choice and I would recommend you to do
a "pvmove" on the OS to smaller disks .
Can you please provide more details?
1) Origin domain type.
2) Destination domain type & size.
3) Was VM up or not? Live Migration?
4) Engine logs if you have.
On Thu, Jan 9, 2020 at 12:29 PM Demeter Tibor wrote:
> Dear Users,
> I have exactly same problem.
> When I
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.
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.
Sent: Sunday, January 12, 2020 2:20 PM
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
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
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
I'm currently migrating all my ISOs from the ISO domain to the DATA domain but
it seems that the checksum (on brick level) mismatches.The problem is that I
have managed to upload several ISOs (one of them 4.9GB) without issues.
Restarting the ovirt-imageio-proxy.service and
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
Best Regards,Strahil Nikolov
В неделя, 12 януари 2020 г., 09:22:52 ч. Гринуич+2, Latchezar Filtchev
Mail list logo