similar to: Channel Device virConnectListAllNodeDevices

Hi, virConnectListAllNodeDevices() takes a virNodeDevicePtr **devices. So I need to create an array of virNodeDevicePtr. For that I need to know size / Number of devices. What is the function for that ? Thank You.

This enables the ability to take the ovirt-node-image iso and deploy it to an iscsi disk. It also provides a sample pxe configuration for booting based on the iscsi root device. Includes support for user/password as well as reverse chap user/password. --- Makefile.am | 1 + livecd-iso-to-iscsi | 201 ++++++++++++++++++++++++++++++++++++++++++++++ ovirt-node-image.spec.in |

Hi! I'm oVirt developer responsible for most of 'hostdev' support. While working on SCSI passthrough (that is hostdev type='scsi'), I've encountered few issues I'm not sure how to solve somewhat effectively and nicely. Just a note - oVirt by default disables 'dynamic_ownership', meaning we have to handle endpoint ownership/labeling ourselves. This is not

We now stop queues and drain all the pending requests from all virtqueues. So this is not a TODO anymore. Got rid of incrementing fc->dev_count as well. It did not seem meaningful for virtio_fs. Signed-off-by: Vivek Goyal <vgoyal at redhat.com> --- fs/fuse/virtio_fs.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/fs/fuse/virtio_fs.c b/fs/fuse/virtio_fs.c index

Is possible to get a pointer to «spice» by virNodeDeviceLookupByName API? What «name» I should use for? Thanks a lot!     -- Андрей Фокин

During virtio_kill_sb() we first stop forget queue and drain it and then call fuse_kill_sb_anon(). This will result in sending DESTROY request to fuse server. Once finished, stop all the queues and drain one more time just to be sure and then free up the devices. Given drain queues will call flush_work() on various workers, remove this logic from virtio_free_devs(). Signed-off-by: Vivek Goyal

''btrfsctl -A /path/to/device/file'' would only scan for a valid btrfs on the device using volume recognition helpers. --- btrfsctl.c | 42 ++++++++++++++++++++++++++++++++++++------ 1 files changed, 36 insertions(+), 6 deletions(-) diff --git a/btrfsctl.c b/btrfsctl.c index 66c4e89..61020de 100644 --- a/btrfsctl.c +++ b/btrfsctl.c @@ -34,6 +34,8 @@ #include

On Thu, Sep 05, 2019 at 03:15:15PM -0400, Vivek Goyal wrote: > On Tue, Sep 03, 2019 at 09:55:49AM -0400, Michael S. Tsirkin wrote: > [..] > > What's with all of the TODOs? Some of these are really scary, > > looks like they need to be figured out before this is merged. > > Hi Michael, > > One of the issue I noticed is races w.r.t device removal and super >

http://libvirt.org/formatdomain.html#elementsHostDevSubsys At this description used "drive"-typed address for SCSI. But when i get xml-description of scsi-devices by <code> unsigned int flags = VIR_CONNECT_LIST_NODE_DEVICES_CAP_SCSI_HOST ; int ret = virConnectListAllNodeDevices (currWorkConnect, &nodeDevices, flags); then get by

Hi, ALL, I just look for the class and method to use blockcopy in libvirt-java on this page: http://libvirt.org/sources/java/javadoc/ However, I can not find out. Libvirt-java Support blockcopy ? Thanks. Best Regards, Star Guo

Hi all, I registe node device lifecycle event callback function after connect qemu. In the callback function, I printf the event and detail. When I plug a USB into host, and then pull out, but there is nothing happen. The callback was not called. Could you tell me Why? And what dose node device mean? I want to auto-hotplug usb devices by using libvirt. Bellow the call of libvirt: // node

On Wed, Mar 18, 2020 at 01:10:41PM +0300, Андрей Фокин wrote: > > Is possible to get a pointer to «spice» by virNodeDeviceLookupByName API? > What «name» I should use for? The virNodeDevicePtr APIs are for getting information about physical devices on a host. spice is not a device, it is a remote framebuffer protocol used by QEMU So the question doesn't really make any sense.

Thanks, clear! But may be is a method to get XML description for spice params, like it could be possible for physical devices?   >Среда, 18 марта 2020, 13:21 +03:00 от Daniel P. Berrangé <berrange@redhat.com>: >  >On Wed, Mar 18, 2020 at 01:10:41PM +0300, Андрей Фокин wrote: >> >> Is possible to get a pointer to «spice» by virNodeDeviceLookupByName API? >> What

Hi, Michael Tsirkin pointed out issues w.r.t various locking related TODO items and races w.r.t device removal. In this first round of cleanups, I have taken care of most pressing issues. These patches apply on top of following. git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#virtiofs-v4 I have tested these patches with mount/umount and device removal using qemu monitor. For

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Removed ks files, now in ovirt-node-recipe, which is subpackage of ovirt-node. Removed tools, these are now in ovirt-node-recipe which is subpackage of ovirt-node.

On Tue, Sep 03, 2019 at 01:42:02PM +0200, Miklos Szeredi wrote: > From: Stefan Hajnoczi <stefanha at redhat.com> > > Add a basic file system module for virtio-fs. This does not yet contain > shared data support between host and guest or metadata coherency speedups. > However it is already significantly faster than virtio-9p. > > Design Overview > ===============

On Tue, Sep 03, 2019 at 01:42:02PM +0200, Miklos Szeredi wrote: > From: Stefan Hajnoczi <stefanha at redhat.com> > > Add a basic file system module for virtio-fs. This does not yet contain > shared data support between host and guest or metadata coherency speedups. > However it is already significantly faster than virtio-9p. > > Design Overview > ===============

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Moves tools and kickstart files form ovirt-node-image to subpackage ovirt-node-recipe. Removes old sub packages form ovirt-node, stateless, logos, selinux. Modifies init scripts to meet Fedora packaging guidelines: added status, reload, and lockfile, rhbz: 514221 Added License file.

On Tue, Sep 03, 2019 at 09:55:49AM -0400, Michael S. Tsirkin wrote: [..] > What's with all of the TODOs? Some of these are really scary, > looks like they need to be figured out before this is merged. Hi Michael, One of the issue I noticed is races w.r.t device removal and super block initialization. I am about to post a set of patches which take care of these races and also get rid of