It is reasonable flow that you inherit the configuration from the template, but
you can change most of the settings during the creation of the VM, I just don't
understand why not to be able to change the disk size and name.
Why disk size? You can say the same thing with any other settings, so
Hi Gianluca,
this looks like an issue in the module.
I have created PR which should fix the problem [1].
Please check it out. You can manually create an ansible library to which
you would copy the module and add the fix there or wait till it is added to
ansible 2.9.
Further issues/requests
On Mon, Jun 15, 2020 at 10:20 PM Dominik Holler wrote:
> Hello,
> CentOS 8.2 was released before oVirt was prepared for CentOS 8.2 .
> Currently oVirt-4.4 fails to install on CentOS 8.2 .
> This will be fixed soon.
>
An updated version of ovn and ovs is available already on some mirrors.
Please
On Tue, Jun 16, 2020 at 12:51 PM Dominik Holler wrote:
>
>
>
> On Mon, Jun 15, 2020 at 10:20 PM Dominik Holler wrote:
>>
>> Hello,
>> CentOS 8.2 was released before oVirt was prepared for CentOS 8.2 .
>> Currently oVirt-4.4 fails to install on CentOS 8.2 .
>> This will be fixed soon.
>
>
> An
Hi All
I think I have come across this bug:
https://access.redhat.com/solutions/5075561
Updating Ovirt to 4.3.10 shows that the kernel installed on the hosts is the
version that has the issue:
3.10.0-1127.8.2.el7.x86_64
The RedHat article suggests updating to kernel-3.10.0-1127.10.1.el7 but
Hi,
"Chaz Vidal" writes:
> Hi All
> I think I have come across this bug:
>
> https://access.redhat.com/solutions/5075561
>
> Updating Ovirt to 4.3.10 shows that the kernel installed on the hosts
> is the version that has the issue:
>
> 3.10.0-1127.8.2.el7.x86_64
>
> The RedHat article suggests
Thanks, so during an upgrade from 4.3.10 to 4.4 there should not be any issues
as I have already established a Cluster and a CPU type?
On 15/06/2020, 23:01, "Anton Gonzalez" wrote:
Hey. Yup, this is a known issue. You can reference the following threads:
Hey,
I have created a template that the disk is a thick (raw) with a size of 15GB.
I am trying to create a VM from that template but having the disk with a much
larger size, both template and the VM are set to use thick and I create the
new VM with the clone option, so there’s no link between
On Wed, Jun 10, 2020 at 6:32 PM Joop wrote:
>
> On 8-6-2020 19:55, Joop wrote:
> > On 8-6-2020 17:52, Strahil Nikolov wrote:
> >> Are you using ECC ram ?
> > No, but what are the chances that starting a VM by using Run directly vs
> > using the Boot wait menu and it hitting that bad bit each and
On 3-6-2020 14:58, Joop wrote:
> Hi All,
>
> Just had a rather new experience in that starting a VM worked but the
> kernel entered grub2 rescue console due to the fact that something was
> wrong with its virtio-scsi disk.
> The message is Booting from Hard Disk
> error:
Hey Joop,
are you using fully allocated qcow2 images ?
Best Regards,
Strahil Nikolov
На 16 юни 2020 г. 20:23:17 GMT+03:00, Joop написа:
>On 3-6-2020 14:58, Joop wrote:
>> Hi All,
>>
>> Just had a rather new experience in that starting a VM worked but the
>> kernel entered grub2 rescue
On Tue, Jun 16, 2020 at 8:31 PM Philip Brown wrote:
>
> nevermind.. found the answer myself thank goodness.
>
> had to rename the volume back to the value of the msdUUID. not the spUUID,
> which I already tried.
>
> If its fatal to rename that volume...
> would be nice to have it lockedout or
nevermind.. found the answer myself thank goodness.
had to rename the volume back to the value of the msdUUID. not the spUUID,
which I already tried.
If its fatal to rename that volume...
would be nice to have it lockedout or something?
- Original Message -
From: "Philip Brown"
To:
Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3
on the way, I browsed into the Storage area, in one of the nodes.
Noticed under the "Volume groups", area that the volumes were named after some
loong ID string.
Saw there was a "rename" button.
figured it would be just
On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum wrote:
>
> Hey,
>
> I have created a template that the disk is a thick (raw) with a size of 15GB.
>
> I am trying to create a VM from that template but having the disk with a much
> larger size, both template and the VM are set to use thick and I create
On Tue, Jun 16, 2020 at 11:01 PM Joop wrote:
>
> On 16-6-2020 19:44, Strahil Nikolov wrote:
> > Hey Joop,
> >
> > are you using fully allocated qcow2 images ?
> >
> > Best Regards,
> > Strahil Nikolov
> >
> I noticed that when I use import VM from an Export domain I see that it
> sometimes uses
On Tue, Jun 16, 2020 at 10:18 PM Philip Brown wrote:
>
>
> Okay, since you asked:
>
> (note: this is in node 4.3.10. but hosted-engine is 4.2
> I'd LIKE to upgrade it. but the upgrade process is broken.
> thats a whole nuther story, aobut how postgresql10 doesnt show up even
> though its
On 16-6-2020 19:44, Strahil Nikolov wrote:
> Hey Joop,
>
> are you using fully allocated qcow2 images ?
>
> Best Regards,
> Strahil Nikolov
>
I noticed that when I use import VM from an Export domain I see that it
sometimes uses preallocated and sometimes thin-provisioned for the disk(s).
Don't
I need to change everything.
the server name
the mount path
(and eventually, the contents ;)
- Original Message -
From: "Strahil Nikolov"
To: "users" , "Philip Brown"
Sent: Tuesday, June 16, 2020 4:37:30 PM
Subject: Re: [ovirt-users] cant edit ISO domain in any way
What do you want
Thank you for the response!
I tried to do another upgrade again on the ovirt manager and can confirm that
it is now in the supposedly fixed version of the kernel.
However, when I try to update the hosts using the prescribed gui style method
they do report back as no updates available.
Should
Hey Nir,
in ovirt 4.3.something the default behaviour for Gluster changed from thin
to fully allocated.
My guess is that the shard xlator cannot catch up with the I/O.
Do you think that I should file a RFE to change the shard size ?
As far as I know RedHat support only 512MB shard size,
What do you want to change ?
На 17 юни 2020 г. 0:36:49 GMT+03:00, Philip Brown написа:
>oVirt 4.3: Okay, I found documentation that I cant have more than one
>"ISO" type storage domain.
>I can kinda understand that.
>
>But, I cant even edit or delete the existing one?
>Even when logged in to
I am hoping to try out adding RDO to oVirt after things with CentOS 8.2 settle
down. I've done deployments of RDO on KVM before without any issues (TripleO
Quickstart), but this would be my first time trying it on oVirt.
Since oVirt recently updated to the openstack-java 3.2.9 packages, is
Okay, since you asked:
(note: this is in node 4.3.10. but hosted-engine is 4.2
I'd LIKE to upgrade it. but the upgrade process is broken.
thats a whole nuther story, aobut how postgresql10 doesnt show up even though
its required for
yum update 'ovirt*setup'
:-/)
1. go to individual
On Mon, Jun 8, 2020 at 3:10 PM Joop wrote:
>
> On 3-6-2020 14:58, Joop wrote:
> > Hi All,
> >
> > Just had a rather new experience in that starting a VM worked but the
> > kernel entered grub2 rescue console due to the fact that something was
> > wrong with its virtio-scsi disk.
> > The message
oVirt 4.3: Okay, I found documentation that I cant have more than one "ISO"
type storage domain.
I can kinda understand that.
But, I cant even edit or delete the existing one?
Even when logged in to the oVirt GUI as admin@internal?
Is this some kind of bug or something?
26 matches
Mail list logo
