search for: blockiowritebandwidth

...t User-Agent: Mutt/1.5.21 (2010-09-15) Turns out this is fairly easy, although quite obscure. Just use ‘systemd-run --pipe’ to run the virt-v2v command in a cgroup. The ‘--pipe’ option ensures it is still connected to stdin/stdout/ stderr (but see below). $ systemd-run --user --pipe \ -p BlockIOWriteBandwidth="/dev/sda2 1K" \ virt-v2v -i disk /var/tmp/fedora-27.img -o local -os /var/tmp Running as unit: run-u4429.service [ 0.0] Opening the source -i disk /var/tmp/fedora-27.img [ 0.0] Creating an overlay to protect the source from being modified etc. See systemd.resource-con...

[Adding Tomas Golembiovsky] On Wed, Sep 26, 2018 at 12:11 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > Rather than jumping to a solution, can you explain what the problem > is that you're trying to solve? > > You need to do <X>, you tried virt-v2v, it doesn't do <X>, etc. > Well, that's mainly IMS related challenges. We're working on

...n > Turns out this is fairly easy, although quite obscure. > > Just use ‘systemd-run --pipe’ to run the virt-v2v command in a cgroup. > The ‘--pipe’ option ensures it is still connected to stdin/stdout/ > stderr (but see below). > > $ systemd-run --user --pipe \ > -p BlockIOWriteBandwidth="/dev/sda2 1K" \ > virt-v2v -i disk /var/tmp/fedora-27.img -o local -os /var/tmp > > Running as unit: run-u4429.service > [ 0.0] Opening the source -i disk /var/tmp/fedora-27.img > [ 0.0] Creating an overlay to protect the source from being modified > e...