hello,
since some days ovirt-ha-agent is not running anymore
i ve 4 ovirt hosts and only on one host the agent is running.
maybe it was from an update, because i lost one agent after an other.
i ve done a complete fresh install for the host with the latest ovirt node.
I ve got on tree hosts
and here is the broker.log
MainThread::INFO::2019-12-07
15:20:03,563::broker::47::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
ovirt-hosted-engine-ha broker 2.3.6 started
MainThread::INFO::2019-12-07
What is the content of
'/rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/'
?
Usually when you restart the broker & agent, they will check if the links exist
and are recreated again.
You can try to set the host into maintenance
Anyone ?
On Sun, 8 Dec 2019 at 2:00 AM, Vijay Sachdeva
wrote:
> What step I did was:
>
>
>
>1. Used qemu-img to convert the vhdx to raw img
>2. Created a blank disk and copied my converted disk to same location.
>3. Renamed the converted drive with the name of blank disk.
>4.
Hi Vijay
Based on your initial post about using virt-v2v I don't know how
intelligent virt-v2v is in knowing and converting the VM machine type.
However the boot issue could be related to Hyper-V defaulting to "Gen 2"
VMs which are all UEFI based. Hence your current VMs
should have a FAT32
Hi.
Although if I add this converted disk as second disk..I could see the data
there.
But not booting as single disk..as windows 2016 OS data is kept and have to
deliver to one of my client. Bit of stuck here.
Thanks
On Sun, 8 Dec 2019 at 11:46 AM, Mathieu Simon
wrote:
> Hi Vijay
>
> Based
On Fri, Dec 6, 2019 at 3:35 PM Robert Webb wrote:
>
> Hi all,
>
> I am trying to deploy the self hosted engine via cockpit and it is failing at
> the very end of deployment when it is checking the VM Health. I have done
> multiple clean installs and run this and it fails every time.
>
> I have
you are right, thank you
now it is up and running again
[root@kvm380 ~]# ls
/rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern\:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/
-lha
insgesamt 0
drwxr-xr-x. 2 vdsm kvm 67 1. Jan 1970 .
drwxr-xr-x. 6 vdsm kvm 64 7. Dez 12:08 ..
One question, once disk is converted to KVM format.
What is the way to use that drive and run a VM from it within Ovirt environment.
Vijay Sachdeva
From: Strahil
Date: Friday, 6 December 2019 at 8:57 PM
To: users , Vijay
Subject: Re: [ovirt-users] Hyper-V to KVM | v2v
Have
Hi Stefan,
it seems that there is some conflict on brick level (that's why it is
?).Just move the files in the brick to another location and then
restart the broker and agent:
[root@kvm380 ~]# mkdir /root/broken_stuff; mv
What step I did was:
Used qemu-img to convert the vhdx to raw img
Created a blank disk and copied my converted disk to same location.
Renamed the converted drive with the name of blank disk.
Created a VM and attached my converted disk to VM.
Error: No bootable disk found
But when I
the contet is
[root@kvm380 ~]# ls
/rhev/data-center/mnt/glusterSD/kvm380.durchhalten.intern:_engine/36663740-576a-4498-b28e-0a402628c6a7/ha_agent/
-lha
ls: Zugriff auf
12 matches
Mail list logo
