l for snapshots.
Opened https://bugzilla.redhat.com/show_bug.cgi?id=1584682.
On Thu, May 31, 2018 at 1:19 PM, Nir Soffer wrote:
On Thu, May 31, 2018 at 1:05 PM Martin Polednik
wrote:
On 31/05/18 12:47 +0300, Elad Ben Aharon wrote:
>Execution is done, 59/65 cases passed. Latest 4.2.4 executi
rt.org/#/c/90906/ <https://gerrit.ovirt.org/#/c/90906/>*
vdsm-4.20.28-6.gitc23aef6.el7.x86_64
On Tue, May 29, 2018 at 4:26 PM, Martin Polednik
wrote:
On 29/05/18 15:30 +0300, Elad Ben Aharon wrote:
Hi Martin,
Can you please create a cerry pick patch that is based on 4.2?
See https://
0.el7.centos.x86_64
>> >>> (/vdsm-4.20.27-3.gitfee7810.el7.centos.x86_64)
>> >>> Requires: glusterfs-fuse >= 3.12
>> >>> Installed: glusterfs-fuse-3.8.4-54.8.el7.x86_64
(@rhv-4.2.3)
>> >>>
>> >>> There
On 24/04/18 00:37 +0300, Elad Ben Aharon wrote:
I will update with the results of the next tier1 execution on latest 4.2.3
That isn't master but old branch though. Could you run it against
*current* VDSM master?
On Mon, Apr 23, 2018 at 3:56 PM, Martin Polednik
wrote:
On 23/04/18
sing [2], which covers all the
requested areas, on iSCSI, NFS and Gluster.
I'll update with the results.
[1]
https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/4.2
_dev/job/rhv-4.2-ge-flow-storage/1161/
[2]
https://gerrit.ovirt.org/#/c/89830/
vdsm-4.30.0-291.git77aef9a.el7.x86_64
On
table enough at the moment.
That is still pretty good.
[1] https://gerrit.ovirt.org/#/c/89830/
Thanks
On Wed, Apr 18, 2018 at 2:17 PM, Martin Polednik
wrote:
On 18/04/18 11:37 +0300, Elad Ben Aharon wrote:
Hi, sorry if I misunderstood, I waited for more input regarding what areas
have
that covers basic operations (start & stop VM, migrate it), snapshots
and merging them, and whatever else would be important for storage
sanity.
mpolednik
On Wed, Apr 18, 2018 at 11:16 AM, Martin Polednik
wrote:
On 11/04/18 16:52 +0300, Elad Ben Aharon wrote:
We can test this on iSCSI
wrote:
Please make sure to run as much OST suites on this patch as possible
before merging ( using 'ci please build' )
But note that OST is not a way to verify the patch.
Such changes require testing with all storage types we support.
Nir
On Tue, Apr 10, 2018 at 4:09 PM, Martin Polednik
T is not a way to verify the patch.
Such changes require testing with all storage types we support.
Nir
On Tue, Apr 10, 2018 at 4:09 PM, Martin Polednik
wrote:
Hey,
I've created a patch[0] that is finally able to activate libvirt's
dynamic_ownership for VDSM while not
e QA that
could assist with this?
Nir
Nir
On Tue, Apr 10, 2018 at 4:09 PM, Martin Polednik
wrote:
Hey,
I've created a patch[0] that is finally able to activate libvirt's
dynamic_ownership for VDSM while not negatively affecting
functionality of our storage code.
That of course
Hey,
I've created a patch[0] that is finally able to activate libvirt's
dynamic_ownership for VDSM while not negatively affecting
functionality of our storage code.
That of course comes with quite a bit of code removal, mostly in the
area of host devices, hwrng and anything that touches devices;
Hey list,
As a part of High Performance VMs feature [1], the oVirt virt team is
planning to introduce a fine grained CPU pinning control for various
VM threads (vcpu, io, emulator).
Current idea for the pinning is to allow per-host configuration of the
number of CPUs per numa node to be reserved
On 24/05/17 12:57 +0200, Michal Skrivanek wrote:
Hi all,
we plan to work on an improvement in VM definition for high performance
workloads which do not require desktop-class devices and generally favor
highest possible performance in expense of less flexibility.
We’re thinking of adding a new V
t would be
beneficial to make it difficult to use to discourage using
metadata as a generic junkyard
>> It is verbose because it is generic - indeed perhaps too generic.
>> I can try something else based on a concept from Martin
Polednik. Will
>> follow u
On 04/01/17 09:57 +0200, Roy Golan wrote:
I'm getting the feeling I'm not alone in this, authoring and publishing a
wiki page isn't as used to be for long time.
I want to suggest a bit lighter workflow:
1. Everyone can merge their page - (it's a wiki)
Same as with (public and open) code, no o
On 08/12/16 11:26 +0200, Edward Haas wrote:
On Thu, Dec 8, 2016 at 10:12 AM, Martin Polednik
wrote:
On 08/12/16 09:28 +0200, Edward Haas wrote:
On Wed, Dec 7, 2016 at 11:54 PM, Nir Soffer wrote:
broken_on_ci is uses default name="OVIRT_CI", to mark it also for
travis, we ne
On 08/12/16 09:28 +0200, Edward Haas wrote:
On Wed, Dec 7, 2016 at 11:54 PM, Nir Soffer wrote:
broken_on_ci is uses default name="OVIRT_CI", to mark it also for
travis, we need another broken_on_ci with name="TRAVIS_CI".
Maybe this test should run only if nm is active on the machine?
We ne
Hello developers,
this e-mail is mostly aimed at VDSM contributors (current and
potential) and should serve as continuation of the idea started at our
weekly meeting.
We've had a proposal of moving the project to github[1] and using
reviewable[2] as a code review due to github's code review inte
On 02/12/16 10:55 +0100, Anton Marchukov wrote:
Hello All.
Engine log can be viewed here:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3838/artifact/exported-artifacts/basic_suite_master.sh-el7/exported-artifacts/test_logs/basic-suite-master/post-004_basic_sanity.py/lago-bas
On 28/10/16 09:06 +0200, Sandro Bonazzola wrote:
Hi,
some time ago we've been asked to provide aarch64 build of qemu-kvm-ev for
CentOS Cloud SIG consumption.
We did it, and while at it we also built oVirt 4.0 VDSM dependencies for
aarch64 in CentOS Virt SIG.
Testing repositories have been create
On 30/11/16 13:10 +0100, Sven Kieske wrote:
On 30/11/16 08:48, Martin Polednik wrote:
It's not really irrelevant, the host still uses disk cache. Anyway,
there is BZ[1] with a presentation[2] that (imho reasonably) states:
"Reduce dirty page limits in KVM host to allow
direct I/O wri
On 30/11/16 13:11 +0100, Sven Kieske wrote:
On 30/11/16 09:13, Yaniv Kaul wrote:
Thanks, but it really makes no sense to me. The direct IO by the VMs is
going to a different storage than what the host is writing to, in most
cases.
The host would write to the local disk, the VMs - to a shared sto
On 29/11/16 22:01 +0200, Yaniv Kaul wrote:
It appears that VDSM changes the following params:
vm.dirty_ratio = 5
vm.dirty_background_ratio = 2
Any idea why? Because we use cache=none it's irrelevant anyway?
It's not really irrelevant, the host still uses disk cache. Anyway,
there is BZ[1] with
On 14/09/16 10:42 +0200, Sandro Bonazzola wrote:
On Mon, Aug 29, 2016 at 11:01 AM, Sandro Bonazzola
wrote:
Hi,
within CentOS Virt SIG interest in having ppc64le and aarch64 as supported
architecture in oVirt has raised.
Packages from oVirt 4.0.2 has been built for both architectures for
hyperv
Hey devels,
last week, I've been working on patch series that moves most of
configuration and "static" files away from our source code to a dir
called "static"[1]. (based on the previous' week VDSM weekly)
Current version has static dir's layout as flat - keeping all files in
the directory with
On 29/03/16 20:36 +0300, Nir Soffer wrote:
On Tue, Mar 29, 2016 at 7:44 PM, Martin Polednik wrote:
On 29/03/16 11:12 -0400, Francesco Romani wrote:
Hi,
in the last Vdsm developer call we agreed to promote a few modules in the
common repository.
The common repository provides the additional
On 29/03/16 11:12 -0400, Francesco Romani wrote:
Hi,
in the last Vdsm developer call we agreed to promote a few modules in the
common repository.
The common repository provides the additional guarantees over regular modules
in lib/vdsm/
- stable API
- (thus) safe to use across verticals
the
On 03/03/16 16:46 +0200, Nir Soffer wrote:
On Thu, Mar 3, 2016 at 4:28 PM, Martin Polednik
wrote:
Hello developers!
I've been chasing a bug that lead me to an idea of improving our XML
logging. Now, to see a VMs generated libvirt XML, we have to rely on
vdsm.log. The issue is that the l
Hello developers!
I've been chasing a bug that lead me to an idea of improving our XML
logging. Now, to see a VMs generated libvirt XML, we have to rely on
vdsm.log. The issue is that the log is rotating and therefore, it is
easy to miss the correct XML when dealing with busy hypervisor.
Since w
On 04/02/16 12:13 +0200, Nir Soffer wrote:
On Thu, Feb 4, 2016 at 10:54 AM, Martin Polednik wrote:
- Original Message -
From: "Dan Kenigsberg"
To: "devel"
Sent: Tuesday, February 2, 2016 5:19:12 PM
Subject: [ovirt-devel] sync meeting - Vdsm 2.2
(nir, piotr,
- Original Message -
> From: "Dan Kenigsberg"
> To: "devel"
> Sent: Tuesday, February 2, 2016 5:19:12 PM
> Subject: [ovirt-devel] sync meeting - Vdsm 2.2
>
> (nir, piotr, danken)
>
> - splitting supervdsmServer:
> I think that its a good idea, and that https://gerrit.ovirt.org/#/c/5
On 27/01/16 09:53 +0200, Nir Soffer wrote:
On Wed, Jan 27, 2016 at 9:29 AM, Yedidyah Bar David wrote:
On Tue, Jan 26, 2016 at 7:26 PM, Nir Soffer wrote:
On Tue, Jan 26, 2016 at 5:29 PM, Yaniv Dary wrote:
I suggest for ease of use and tracking we change the versioning to align to
the engine
On 11/12/15 12:31 +0100, Michal Skrivanek wrote:
On 10 Dec 2015, at 16:36, Yaniv Kaul wrote:
On Thu, Dec 10, 2015 at 5:07 PM, Martin Polednik mailto:mpoled...@redhat.com>> wrote:
Hello developers,
tl;dr version:
* deprecate report_host_threads_as_cores
* remove cpuSockets, u
Hello developers,
tl;dr version:
* deprecate report_host_threads_as_cores
* remove cpuSockets, use sum(numaNodes.keys())
* report threadsPerCore for ppc64le / report total number of threads
for ppc64le
* work on our naming issues
I've been going over our capabilities reporting code in VDSM due
On 26/10/15 15:24 +0200, Dan Kenigsberg wrote:
On Mon, Oct 26, 2015 at 11:17:10AM +0100, Michal Skrivanek wrote:
> On 26 Oct 2015, at 09:41, Dan Kenigsberg wrote:
>
> On Mon, Oct 05, 2015 at 02:53:00PM +0200, Martin Polednik wrote:
>> On 05/10/15 11:31 +0200, Michal
On 05/10/15 11:31 +0200, Michal Skrivanek wrote:
On Oct 3, 2015, at 20:48 , Martin Polednik wrote:
Hello everyone,
I've been reworking the fake_kvm and faqemu VDSM hook to make them
somewhat more usable and mostly to allow testing of ppc64le on x86_64
based hosts.
TL;DR version: che
Hello everyone,
I've been reworking the fake_kvm and faqemu VDSM hook to make them
somewhat more usable and mostly to allow testing of ppc64le on x86_64
based hosts.
TL;DR version: checkout [1], enable fake_kvm and happy ppc64le hacking :)
Current fake_kvm isn't really a hook and is contained w
- Original Message -
> From: "Dan Kenigsberg"
> To: "Martin Polednik"
> Cc: devel@ovirt.org
> Sent: Friday, May 1, 2015 5:06:04 PM
> Subject: Re: [ovirt-devel] [vdsm] VmDevices rework
>
> On Tue, Apr 28, 2015 at 04:28:12AM -0400, Martin Poled
Hello everyone,
I have started working on line of patches that deal with current state of VM
devices
in VDSM. There is a wiki page at [1] describing the issues, phases and final
goals
for this work. Additionally, there is formal naming system for code related to
devices. I would love to hear you
Hello,
Since dealing with SR-IOV, we've discovered the need to persist
number of virtual functions for given virtual functions. The need
is actually split into 2 parts: setting the number and persisting it.
Our talks have pointed to 5 choices in persistence mechanisms:
* let engine set the number
address)
As hostdev passthrough feature is progressing, I would like you
to look at updated http://www.ovirt.org/Features/hostdev_passthrough.
Any questions/comments are more then welcome!
Martin Polednik
___
Devel mailing list
Devel@ovirt.org
http://
e set on the vf
> > > whether it
> > > is connected to the vm via macvtap or directly.
> >
> > Are you sure about this? I think that when a host device is attached to
> > a VM, it disappears from the host, and the the guest can send arbitrary
> > unmodifi
- Original Message -
> From: "Dan Kenigsberg"
> To: "Martin Polednik" , dc...@redhat.com
> Cc: devel@ovirt.org
> Sent: Wednesday, July 23, 2014 12:19:42 PM
> Subject: Re: [ovirt-devel] VDSM mom dependancy on RHEL7
>
> On Tue, Jul 22, 2014 a
Hi,
I've gone through installing VDSM on RHEL7 host
(Red Hat Enterprise Linux Server release 7.0 (Maipo)) and encountered
issue with mom:
Error: Package: mom-0.4.1-2.el6.noarch (ovirt-3.5-epel)
Requires: python(abi) = 2.6
Installed: python-2.7.5-16.el7.x86_64 (@rhel7)
Hello,
I'm actively working on getting host device passthrough (pci, usb and scsi)
exposed in VDSM, but I've encountered growing complexity of this feature.
The devices are currently created in the same manner as virtual devices and
their reporting is done via hostDevices list in getCaps. As I im
Hello
I'm writing in order to propose a change to faqemu hook as indicated in [1],
modifying the hook's default behavior:
There are currently hardcoded x86_64 and PPC memory limits (20480 and 262144),
this change would remove these implicit constraints and keep the memory
unchanged.
A new variab
- Original Message -
> From: "Francesco Romani"
> To: "Adam Litke"
> Cc: "Martin Polednik" , devel@ovirt.org
> Sent: Friday, May 23, 2014 9:26:49 AM
> Subject: Re: [ovirt-devel] [vdsm] Unifying VM device representations
>
> - Or
47 matches
Mail list logo
