10:10 a.m.
Heyho guys,
is there any reason why mixed storage migration is restriced. I am unable to serve
parameter
"migrate_disks" through #migrate_to_uri3. It looks like there is a missing macro
here.
http://libvirt.org/git/?p=ruby-libvirt.git;a=blob;f=ext/libvirt/domain.c#.... Could you
please
verify this?
regrads,
tim
8:52 a.m.
Hi there,
On Thu, Mar 3, 2016 at 11:10 AM, Tim Förster - Hetzner Online AG <
tim.foerster(a)hetzner.de> wrote:
Heyho guys,
is there any reason why mixed storage migration is restriced. I am unable
to serve parameter
"migrate_disks" through #migrate_to_uri3. It looks like there is a missing
macro here.
http://libvirt.org/git/?p=ruby-libvirt.git;a=blob;f=ext/libvirt/domain.c#....
Could you please
verify this?
This is probably one of those enums I just haven't gotten to yet. I can
look at implementing it for the next release. Note, though, that all of
these fields are integers, so as a temporary workaround you should be able
to just use the correct number.
Chris
9:48 a.m.
Hi,
rebuilding the gem is not quite easy. I am not able to find the actual gemspec. There are
also some
missing features, which are available though virsh. Such as 'virsh domblklist' to
find out the
actual registered block targets or rate limiting with iotune the burst iops.
tim
Am 07.03.2016 um 15:52 schrieb Chris Lalancette:
Hi there,
On Thu, Mar 3, 2016 at 11:10 AM, Tim Förster - Hetzner Online AG
<tim.foerster(a)hetzner.de
<mailto:tim.foerster@hetzner.de>> wrote:
Heyho guys,
is there any reason why mixed storage migration is restriced. I am unable to serve
parameter
"migrate_disks" through #migrate_to_uri3. It looks like there is a missing
macro here.
http://libvirt.org/git/?p=ruby-libvirt.git;a=blob;f=ext/libvirt/domain.c#.... Could
you please
verify this?
This is probably one of those enums I just haven't gotten to yet. I can look at
implementing it for
the next release. Note, though, that all of these fields are integers, so as a temporary
workaround
you should be able to just use the correct number.
Chris
3:17 p.m.
On Mon, Mar 7, 2016 at 10:48 AM, Tim Förster - Hetzner Online AG <
tim.foerster(a)hetzner.de> wrote:
Hi,
rebuilding the gem is not quite easy. I am not able to find the actual
gemspec. There are also some
The gemspec is in the git repository. You should be able to clone git://
libvirt.org/ruby-libvirt.git, then run "rake gem" to get a new gem.
missing features, which are available though virsh. Such as
'virsh
domblklist' to find out the
actual registered block targets or rate limiting with iotune the burst
iops.
ruby-libvirt aims to expose the libvirt API through ruby, not the virsh
API. Sometimes virsh provides additional functionality on top of the
libvirt API, which will not necessarily be implemented in ruby-libvirt. In
this particular case, virsh domblklist parses virDomainGetXMLDesc() to
output a list of block devices. virDomainGetXMLDesc() is supported by
ruby-libvirt, but domblklist itself would not be. That being said, it
should be fairly straightforward to implement it in ruby by first calling
dom.xml_desc(), and then parsing the output with your favorite ruby XML
parsing library.
Chris
3182
days inactive
3186
days old
3 comments
2 participants
participants (2)
-
Chris Lalancette -
Tim Förster - Hetzner Online AG