Re: UI - cannot remove disk whiel system is running
by Strahil
Everything ended well - despite the warning 'do not shutdown' I powered off and powered on the VM.
This action allowed me to trigger a snapshot deletion (again) and it completed successfully.
Removing the disk of interest also completed successfully.
So, I got a happy ending.
Best Regards,
Strahil NikolovOn Jul 7, 2019 17:41, Strahil <hunter86_bg(a)yahoo.com> wrote:
>
> I think I'm getting closer.
>
> It seems the snapshot of the VM did not get deleted and that might be the problem.
>
> Can someone give me a hint how to remove the snapshot as I get an error:
>
> Cannot remove Snapshot. The following disks are in ILLEGAL status: uyuni-OS-Disk1 - please remove them and try again.
>
> Yet, removal of the disk cannot happen as I got:
> Cannot detach Virtual Disk. The disk is already configured in a snapshot. In order to detach it, remove the disk's snapshot.
>
> This seems like 'Catch 22' .
>
> Best Regards,
> Strahil Nikolov
>
> On Jul 7, 2019 17:30, Strahil <hunter86_bg(a)yahoo.com> wrote:
>>
>> Hello All,
>>
>> I have changed my system layout and the old disk is removed (echo 1 > /sys/block/sdX/device/delete) from OS, but UI complains when I try to remove with the following error:
>>
>> Error while executing action: Cannot remove Virtual Disk. At least one of the VMs is not down.
>>
>> Is it a limitation of oVirt ? If so, I will open an enhancement entry in bugzilla.
>>
>> As far as I remember KVM allowed me to make such stuff without any issues so far.
>>
>> Best Regards,
>> Strahil Nikolov
1 month, 2 weeks
Re: UI - cannot remove disk whiel system is running
by Strahil
I think I'm getting closer.
It seems the snapshot of the VM did not get deleted and that might be the problem.
Can someone give me a hint how to remove the snapshot as I get an error:
Cannot remove Snapshot. The following disks are in ILLEGAL status: uyuni-OS-Disk1 - please remove them and try again.
Yet, removal of the disk cannot happen as I got:
Cannot detach Virtual Disk. The disk is already configured in a snapshot. In order to detach it, remove the disk's snapshot.
This seems like 'Catch 22' .
Best Regards,
Strahil NikolovOn Jul 7, 2019 17:30, Strahil <hunter86_bg(a)yahoo.com> wrote:
>
> Hello All,
>
> I have changed my system layout and the old disk is removed (echo 1 > /sys/block/sdX/device/delete) from OS, but UI complains when I try to remove with the following error:
>
> Error while executing action: Cannot remove Virtual Disk. At least one of the VMs is not down.
>
> Is it a limitation of oVirt ? If so, I will open an enhancement entry in bugzilla.
>
> As far as I remember KVM allowed me to make such stuff without any issues so far.
>
> Best Regards,
> Strahil Nikolov
1 month, 2 weeks
UI - cannot remove disk whiel system is running
by Strahil
Hello All,
I have changed my system layout and the old disk is removed (echo 1 > /sys/block/sdX/device/delete) from OS, but UI complains when I try to remove with the following error:
Error while executing action: Cannot remove Virtual Disk. At least one of the VMs is not down.
Is it a limitation of oVirt ? If so, I will open an enhancement entry in bugzilla.
As far as I remember KVM allowed me to make such stuff without any issues so far.
Best Regards,
Strahil Nikolov
1 month, 2 weeks
VM snapshot - some info needed
by Strahil Nikolov
Hello Community,
I have noticed that if I want a VM snapshot with memory - I get a warning "The VM will be paused while saving the memory" .Is there a way to make snapshot without pausing the VM for the whole duration ?
I have noticed that it doesn't matter if VM has qemu-guest-agent or ovirt-guest-agent.
Thanks in advance for sharing your thoughts.
Best Regards,Strahil Nikolov
1 month, 2 weeks
Experience 4.1.x -> 4.2.8 -> 4.3.4 upgrade lessons
by Richard Chan
Hi oVirters,
Did a 4.1 - > 4.2.8 -> 4.3.4 upgrade in two hops. Here is my experience,
hope it can save you some pain.
Gotchas
1. For shutdown VMs, their disks were deactivated (though still attached)
2. For shutdown VMs, their NICs were "Up" but "Unplugged"
3. VM Custom Compatibility Version is hard to find. (If it is too old say
3.6, 4.1) they won't start up. The location is: VM -> Edit -> System ->
Advanced Parameters (click this)
"Advanced Parameters" is an expandable widget that is quite small when
collapsed. When it is expanded then you will see "Custom Compatibility
Version"
4. Storage Domain migration to V5: I use a NFS storoage domain. This is
migrated to the "V5" format and a lot of cleanup is done. If you have stray
files or images not owned by 36:36 (vdsm:kvm on my NFS server), the V5
upgrade will fail, there will be no SPM, and the Data Center will oscillate
between Non-responsive and Contending.
Why would there be non 36:36 uid/gid files? This is a long story, but from
the older 3.x days when there was less functionality, we would sometimes
directly manipulate the filesystem and/or qcow2 images using guestfish or
equivalent tools which would change the owner to qemu:qemu. Forgetting to
chown back to vdsm:kvm is a recipe for pain.
Cheers!
--
Richard Chan
1 month, 2 weeks
Re: Upgraded to 4.3: getting SpmStart failure
by Strahil
Can you run the engine manually on another server ?
hosted-engine --vm-start
Best Regards,
Strahil NikolovOn Jul 5, 2019 18:05, Richard Chan <richard(a)treeboxsolutions.com> wrote:
>
> My engine is getting SpmStart failure.
>
> What is the best way to troubleshoot this?
>
>
> --
> Richard Chan
>
1 month, 2 weeks
Ovirt 4.3.5.3-1.el7 manual migration fails
by Strahil
Hey Community,
Can someone tell me which log should be checked - as one of my VMs cannot be live migrated.
In this case it get's stuck at 99% for several minutes and then fails.
Best Regards,
Strahil Nikolov
1 month, 2 weeks
importing a vm is always very slow
by Crazy Ayansh
Hi Users,
Why importing the vm from export domain is very slow and how can we do it
fast ? How to cancel a import process ?
[image: image.png]
Thanks
1 month, 2 weeks
Anaconda crashing on start while trying to Install oVirt Node on bare metal
by rubentrindade＠live.com
Hello there!
I'm trying to install an oVirt node(the most stable recent one) on a machine(just in case you didn't figure from the title :P) and anaconda just crashes \o/
I've tried to start anaconda in text mode, but the error is the exact same.
Here's a screenshot of the event(text mode, although it shouldn't matter):
https://i.imgur.com/ihO1xWP.jpg
The only "disk" attached to the machine has no partitions, it's absolutely clean. The machine in question is a PowerEdge M520, if that matters, and I'm trying to install on top of a pair of 32GB mirrored SD cards.
I installed CentOS7 on a machine that's virtually the same(they're the exact same, but aren't the same machine) and didn't have any problem.
I just have no idea. Never encountered such problem. So any help would be very appreciated. Thanks ^^
1 month, 2 weeks
