Il giorno mar 1 set 2020 alle ore 08:31 Sandro Bonazzola <
sbona...@redhat.com> ha scritto:
> Thanks, can you please open an issue on
> https://github.com/oVirt/ovirt-site/issues if not already done?
>
Or you can push a fix yourself if you have time :-)
>
> Il giorno lun 24 ago 2020 alle ore 21
Thanks, can you please open an issue on
https://github.com/oVirt/ovirt-site/issues if not already done?
Il giorno lun 24 ago 2020 alle ore 21:25 carl langlois <
crl.langl...@gmail.com> ha scritto:
> Hi,
>
> Not sure if this is relevant but in the ovirt doc in the 4.2 to 4.3
> upgrade the repo rpm
+Arik Hadas can you help debugging this?
Il giorno gio 27 ago 2020 alle ore 14:21 ha scritto:
> Hi,
> I'm having problem after I upgraded to 4.4.1 with Windows machines.
>
> The installation sees no disk. Even IDE disk doesn't get detected and
> installation won't move forward no matter what
Hello
I have some blades with 10GE interface that have / need the Emulex be2net
driver, however it is no longer available on Redhat8 / Centos8. Is there
any way to install ovirt to work on these machines?
Here are some links to problems with Redhat.
Emulex NIC using be2net driver
https://access.
I've just tried to verify what you said here.
As a base line I started with the 1nHCI Gluster setup. From four VMs, two
legacy, two Q35 on the single node Gluster, one survived the import, one failed
silently with an empty disk, two failed somewhere in the middle of qemu-img
trying to write the
Thanks for the suggestion, I tried that, but I didn't get very far on a single
node HCI cluster...
And I'm afraid it won't be much better on HCI in general, which is really the
use case I am most interested in.
Silently converting VMs is something rather unexpected from a hypervisor, doing
it t
Not sure it will actually do that, but if you create a new network profile, you
can select a 'port mirroring' option: It is my understanding that is what you
need. You may also want to deselect the filtering rules in the same place.
___
Users mailing li
On Mon, Aug 31, 2020 at 8:41 PM wrote:
> Testing the 4.3 to 4.4 migration... what I describe here is facts is
> mostly observations and conjecture, could be wrong, just makes writing
> easier...
>
> While 4.3 seems to maintain a default emulated machine type
> (pc-i440fx-rhel7.6.0 by default), it
I like playing with shiny new toys and VDO is one :-)
Actually with that it shouldn't matter if whatever is put on top actually has
spare allocation in the file format or just blocks with zeros, which makes for
a reusable HDD in case I am working with imageio images that are raw.
Good to know t
On a machine that survived the import, that worked as expected.
May want to add that to a check list, that the original machine type for legacy
isn't carried over after an import but needs to be set explicitly.
___
Users mailing list -- users@ovirt.org
On Mon, Aug 31, 2020 at 8:17 PM wrote:
>
> After this
> (https://devconfcz2020a.sched.com/event/YOtG/ovirt-4k-teaching-an-old-dog-new-tricks)
Vdsm learned a few tricks but is still old :-)
> I sure do not expect this (log below):
>
> Actually I am trying to evaluate just how portable oVirt stor
I might have found one: You can set the emulated machine to 'legacy' before the
first launch.
No idea yet, if it will actually work, because the boot disk was copied empty...
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to user
Testing the 4.3 to 4.4 migration... what I describe here is facts is mostly
observations and conjecture, could be wrong, just makes writing easier...
While 4.3 seems to maintain a default emulated machine type
(pc-i440fx-rhel7.6.0 by default), it doesn't actually allow setting it in the
cluster
After this
(https://devconfcz2020a.sched.com/event/YOtG/ovirt-4k-teaching-an-old-dog-new-tricks)
I sure do not expect this (log below):
Actually I am trying to evaluate just how portable oVirt storage is and this
case I had prepared a USB3 HDD with VDO, which I could literally move between
f
I'm running oVirt 4.3.10 and I can migrate my Engine from node to node.
I had one similar issue , but powering off and on the HE has fixed it.
You have to check the vdsm log on the source and on destination in order to
figure out what is going on.
Also you might consider checking the libvirt logs
Hi All,
I would like to deploy a VM that will monitor a specific network. I know in
VMware you can set the port group to allow Promiscuous Mode. Is there something
similar I can do in oVirt?
Thanks
Anton Louw
Cloud Engineer: Storage and Virtualization
__
D:
Thanks for letting me know, I suspected that might be the case. I’ll make a
note to fix that in the playbook
On Mon, Aug 31, 2020 at 3:57 AM Stefan Wolf wrote:
> I think, I found the problem.
>
>
>
> It is case sensitive. For the export it is NOT case sensitive but for the
> step "wait for expor
Thanks! The scores of all nodes are not '0'. I find that someone has already
asked a question like this. It seems that this feature has been disabled in
4.3. I am not sure if it is enabled in 4.4.
在 2020-08-29 02:27:03，"Strahil Nikolov" ：
>Have you checked under a shell the output of 'hoste
On Sun, Aug 30, 2020 at 11:46 PM wrote:
>
> BTW: This is the message I get on the import:
> VDSM nucvirt command HSMGetAllTasksStatusesVDS failed: value=low level Image
> copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none',
> '-T', 'none', '-f', 'qcow2',
> '/rhev/data-cen
19 matches
Mail list logo
