search for: danpb

...returns a success code the application can * be sure that all data has been successfully processed. * * Returns 0 on success, -1 upon error */ So maybe in your case you want virStreamAbort instead (which also unconditionally throws an error which is also an issue IMO but can be ignored) CCing danpb for this thoughts on the erroring semantics - Cole

...interface > > though, so I have a workaround, but a hook that triggers on all > > interface events felt cleaner. > > Also keep in mind that the hook scripts aren't an officially supported > part of the API, and are thus liable to change without warning. As an > example, danpb has proposed changing the network hook: > > https://www.redhat.com/archives/libvir-list/2019-March/msg01280.html > > Once this goes in, any network hook script that uses the plugged and > unplugged hooks will no longer work; you would instead need to use the > port-created and p...

...o reuse the > internal chardev abstraction. > > vhost-user-blk could be implemented similarly, but with type='storage' > which is the way we pass through block devices to LXC guests, but it > isn't currently supported in the qemu driver. > > I dunno. Maybe Michal or danpb can provide guidance > @Michal, @danpb, could you give some guidance? > > > Conclusion: > > 1. Add new type(vhostuser) for disk label; > > 2. Add queue sub-label for disk to support multiqueue(<queue > > num='4'/>) or reusing the driver label > > (&...

On Tue, Apr 9, 2019 at 5:10 PM Michal Privoznik <mprivozn@redhat.com> wrote: > > On 4/9/19 4:38 PM, Ruben Kerkhof wrote: > > Hi all, > > > > I have a hook script, /etc/libvirt/hooks/network, that doesn't seem to > > be called when I attach an interface with type 'ethernet' with this > > xml snippet: > > > > <interface

...d, but a hook that triggers on all > > > > interface events felt cleaner. > > > > > > Also keep in mind that the hook scripts aren't an officially supported > > > part of the API, and are thus liable to change without warning. As an > > > example, danpb has proposed changing the network hook: > > > > > > https://www.redhat.com/archives/libvir-list/2019-March/msg01280.html > > > > > > Once this goes in, any network hook script that uses the plugged and > > > unplugged hooks will no longer work; you wou...

...cessfully processed. > > * > > * Returns 0 on success, -1 upon error > > */ > > > > So maybe in your case you want virStreamAbort instead (which also > > unconditionally throws an error which is also an issue IMO but can be ignored) > > > > CCing danpb for this thoughts on the erroring semantics > > > > - Cole

- perform dns lookup on hostname, - randomize local tunnel port - bump rpm spec version updated to include danpb's feedback regarding getaddrinfo --- main.c | 36 ++++++++++++++++++------------------ ovirt-viewer.spec | 9 ++++++++- tunnel.c | 29 ++++++++++++++++++++--------- 3 files changed, 46 insertions(+), 28 deletions(-) diff --git a/main.c b/main.c index 2962f3f..23af6f...

...t; * be sure that all data has been successfully processed. > * > * Returns 0 on success, -1 upon error > */ > > So maybe in your case you want virStreamAbort instead (which also > unconditionally throws an error which is also an issue IMO but can be ignored) > > CCing danpb for this thoughts on the erroring semantics > > - Cole

...e same script that adds the interface > though, so I have a workaround, but a hook that triggers on all > interface events felt cleaner. Also keep in mind that the hook scripts aren't an officially supported part of the API, and are thus liable to change without warning. As an example, danpb has proposed changing the network hook: https://www.redhat.com/archives/libvir-list/2019-March/msg01280.html Once this goes in, any network hook script that uses the plugged and unplugged hooks will no longer work; you would instead need to use the port-created and port-deleted hooks.

Here is an update to the patch posted yesterday. The changes are: (1) Don't use inline (for mdbooth). (2) Added a comment to HACKING (for mdbooth). (3) Check for old-style and new-style glibc functions and use whatever is available (for danpb). (4) Removed the old shell_quote function instead of just commenting it out. Can anyone decode from Uli's message[1] whether these new functions are going to be added to POSIX 2008? It's not very clear to me. Rich. [1] http://udrepper.livejournal.com/20948.html -- Richard Jones, Eme...

...gt; > > * Returns 0 on success, -1 upon error > > > */ > > > > > > So maybe in your case you want virStreamAbort instead (which also > > > unconditionally throws an error which is also an issue IMO but can be ignored) > > > > > > CCing danpb for this thoughts on the erroring semantics > > > > > > - Cole

...gh, so I have a workaround, but a hook that triggers on all > > > interface events felt cleaner. > > > > Also keep in mind that the hook scripts aren't an officially supported > > part of the API, and are thus liable to change without warning. As an > > example, danpb has proposed changing the network hook: > > > > https://www.redhat.com/archives/libvir-list/2019-March/msg01280.html > > > > Once this goes in, any network hook script that uses the plugged and > > unplugged hooks will no longer work; you would instead need to use th...

Compared to v3 this suggests: +Suggests: qemu-block-curl +Suggests: qemu-block-gluster +Suggests: qemu-block-iscsi +Suggests: qemu-block-rbd +Suggests: qemu-block-ssh which I missed in an earlier email from danpb.

hi, I am currently investigating a bug with libvirt lxc. Whenever I do a systemctl daemon-reload on the host, my container loses his memory limit and then reports having access to 8 exabyte of memory. I have tracked the issue down to two parts: memory.limit_in_bytes jumps from the correct value to 9223372036854771712. libvirt lxc appears to set the memory limit in transient way without writing

Hi Cole & Michal, I'm sorry for my late response, I just end my journey today. Thank your response, your suggestion is very helpful to me. I have added Michal in this mail, Michal helps me review my initial patchset. (https://www.spinics.net/linux/fedora/libvir/msg191339.html) All concern about this feature is the XML design. My original XML design exposes more details of Qemu.

Hi, The following snippet works fine e.g. receiving the data but when calling stream.finish() we get the following error: stream = con.newStream() vol.download(stream, 0, 0, 0) buf = stream.recv(1024) stream.finish() libvirt: I/O Stream Utils error : internal error: I/O helper exited abnormally Traceback (most recent call last): File "./helpers/kvm2ovirt", line 149, in <module>

This is only lightly tested. In particularly I only tested that the non-secure-boot path still works. I didn't test it on RHEL 7.3 yet because I haven't got enough free disk space for these giant source *.ova files :-( Will try to give that a go later. Rich.

Hi everyone, If a VM is configured to have a console attached to it, like using http://libvirt.org/formatdomain.html#elementCharConsole Libvirt offers access to VM serial console's using the virDomainOpenConsole API[1] However, I didn't find a way to 1. list the existing connections to the console 2. kill an existing connection - without reconnecting using VIR_DOMAIN_CONSOLE_FORCE[2]

...l=> field, and we would want to reuse the internal chardev abstraction. vhost-user-blk could be implemented similarly, but with type='storage' which is the way we pass through block devices to LXC guests, but it isn't currently supported in the qemu driver. I dunno. Maybe Michal or danpb can provide guidance > Conclusion: > 1. Add new type(vhostuser) for disk label; > 2. Add queue sub-label for disk to support multiqueue(<queue > num='4'/>) or reusing the driver label > (<driver name='vhostuser' queues='4'), which one is better? &gt...

...were refactoring the other bits of libvirt to make the xl plugin easier [14:18] <DV> We really try to not break libvirt upstream, ideally having the git version run for regtests on libxl would be a good idea <gwd> DV: Upstream Xen Project already does that. <DV> * DV agrees with danpb , even in RHEL we rebase to try to avoid backporting <gwd> Having a new libvirt shouldn't *interfere* with oVirt, virt-install, &c&c. [14:19] <DV> gwd: ah, good, are the result available publicly, if yes then maybe breakages should be reported on libvirt-list! <DV>...