Re: [ovirt-users] how to build oVirt engine on eclipse?
by Nir Soffer
On Thu, Jan 7, 2021 at 8:20 PM Henry lol <pub.virtualization(a)gmail.com> wrote:
...
> I've just only imported existing maven projects from engine's git, but there were so many errors and failed to build.
>
> Should I do some configurations before importing?
There are some dependencies mentioned in README.adoc.
I think most developers are using IntelliJ IDEA
https://www.jetbrains.com/idea/
But I don't think anyone is building from the IDE. You can build using:
make clean install-dev PREFIX="$HOME/ovirt-engine"
See README.adoc for more info on building engine.
Adding devel(a)ovirt.org since this question is not about using ovirt.
Nir
3 years, 11 months
Issue: Device path changed after adding disks to guest VM
by Joy Li
Hi All,
I'm facing the problem that after adding disks to guest VM, the device
target path changed (My ovirt version is 4.3). For example:
Before adding a disk:
virsh # domblklist <vmname>
Target Source
---------------------------------------------------------
hdc -
vda /dev/mapper/3600a09803830386546244a546d494f53
vdb /dev/mapper/3600a09803830386546244a546d494f54
* vdc /dev/mapper/3600a09803830386546244a546d494f55*
vdd /dev/mapper/3600a09803830386546244a546d494f56
vde /dev/mapper/3600a09803830386546244a546d494f57
vdf /dev/mapper/3600a09803830386546244a546d494f58
After adding a disk, and then shutdown and start the VM:
virsh # domblklist <vmname>
Target Source
---------------------------------------------------------
hdc -
vda /dev/mapper/3600a09803830386546244a546d494f53
vdb /dev/mapper/3600a09803830386546244a546d494f54
*vdc /dev/mapper/3600a09803830386546244a546d494f6c*
* vdd /dev/mapper/3600a09803830386546244a546d494f55*
vde /dev/mapper/3600a09803830386546244a546d494f56
vdf /dev/mapper/3600a09803830386546244a546d494f57
vdg /dev/mapper/3600a09803830386546244a546d494f58
The devices' multipath doesn't map to the same target path as before, so in
my VM the /dev/vdc doesn't point to the old
/dev/mapper/3600a09803830386546244a546d494f55 anymore.
Anybody knows how can I make the device path mapping fixed without being
changed after adding or removing disks.
Many thanks in advance.
Joy
3 years, 11 months
Vdsm: Small version numbering change?
by Milan Zamazal
Hi,
we have a nice coincidence now that Vdsm 4.40.40 corresponds to
ovirt-4.4.4 branch. Would we like to use this opportunity to make Vdsm
versions aligned with oVirt 4.4.* versions?
We can tag the next master build, which will be no longer part of
ovirt-4.4.4 branch, as v4.40.50. Or we could tag it as v4.40.500 to be
on the safe side, but both 4.4.3 and 4.4.4 had less than 10 tags on
master, so it's probably not needed and there is always v4.40.591-like
workaround available.
What do you think?
Regards,
Milan
3 years, 11 months
