FYI there's some more recent discussion over here:
https://www.redhat.com/archives/libvir-list/2019-December/msg00817.html
There isn't any objections to using for
vhost-user-blk, so maybe that's a good place to start.
Thanks,
Cole
On 10/15/19 7:34 AM, Li Feng wrote:
> Cole Robinson 于2019年10月1
On 10/14/19 3:12 AM, Li Feng wrote:
> 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
Sorry for the late reply, and thanks Jano for pointing out elsewhere
that this didn't receive a response.
On 8/12/19 5:56 AM, Li Feng wrote:
Hi Guys,
And I want to add the vhost-user-scsi-pci/vhost-user-blk-pci support
for libvirt.
The usage in qemu like this:
Vhost-SCSI
-chardev socket,id=c
Hi Guys,
And I want to add the vhost-user-scsi-pci/vhost-user-blk-pci support
for libvirt.
The usage in qemu like this:
Vhost-SCSI
-chardev socket,id=char0,path=/var/tmp/vhost.0
-device vhost-user-scsi-pci,id=scsi0,chardev=char0
Vhost-BLK
-chardev socket,id=char1,path=/var/tmp/vhost.1
-device vh
On 01/29/2013 03:23 AM, Daniel P. Berrange wrote:
> On Mon, Jan 28, 2013 at 02:54:28PM -0700, Eric Blake wrote:
>> On 01/26/2013 09:17 PM, Stefan Berger wrote:
In a subsequent patch we now test inside that function whether the new
command line parameter is available using the capability (
On Mon, Jan 28, 2013 at 02:54:28PM -0700, Eric Blake wrote:
> On 01/26/2013 09:17 PM, Stefan Berger wrote:
> >> In a subsequent patch we now test inside that function whether the new
> >> command line parameter is available using the capability (from another
> >> patch) and create fd=/dev/set/10 an
On 01/26/2013 09:17 PM, Stefan Berger wrote:
>> In a subsequent patch we now test inside that function whether the new
>> command line parameter is available using the capability (from another
>> patch) and create fd=/dev/set/10 and vhostfd=/dev/set/20 respectively
>> *and* already add "-add-fd set
On 01/26/2013 08:44 PM, Stefan Berger wrote:
On 01/25/2013 06:35 PM, Eric Blake wrote:
On 01/22/2013 12:07 PM, Stefan Berger wrote:
On 01/22/2013 01:29 PM, Daniel P. Berrange wrote:
On Tue, Jan 22, 2013 at 01:09:50PM -0500, Stefan Berger wrote:
Thanks for starting on this; it is something I ha
On 01/25/2013 06:35 PM, Eric Blake wrote:
On 01/22/2013 12:07 PM, Stefan Berger wrote:
On 01/22/2013 01:29 PM, Daniel P. Berrange wrote:
On Tue, Jan 22, 2013 at 01:09:50PM -0500, Stefan Berger wrote:
Thanks for starting on this; it is something I have also been
planning to work on.
Glad to b
On 01/22/2013 12:07 PM, Stefan Berger wrote:
> On 01/22/2013 01:29 PM, Daniel P. Berrange wrote:
>> On Tue, Jan 22, 2013 at 01:09:50PM -0500, Stefan Berger wrote:
>>> Add two API calls to virCommand for generating the parameters necessary
>>> for passing to the QEMU -add-fd option, for example "set
On 01/22/2013 01:29 PM, Daniel P. Berrange wrote:
On Tue, Jan 22, 2013 at 01:09:50PM -0500, Stefan Berger wrote:
Add two API calls to virCommand for generating the parameters necessary
for passing to the QEMU -add-fd option, for example "set=10,fd=20",
and the file descriptor set for the path= o
On Tue, Jan 22, 2013 at 01:09:50PM -0500, Stefan Berger wrote:
> Add two API calls to virCommand for generating the parameters necessary
> for passing to the QEMU -add-fd option, for example "set=10,fd=20",
> and the file descriptor set for the path= option, such as for example
> "/dev/fdset/10"
>
Add two API calls to virCommand for generating the parameters necessary
for passing to the QEMU -add-fd option, for example "set=10,fd=20",
and the file descriptor set for the path= option, such as for example
"/dev/fdset/10"
Regards,
Stefan
---
src/libvirt_private.syms |2 +
src/util/vi
On Mon, Dec 05, 2011 at 05:13:54PM +0100, Christophe Fergeau wrote:
> On Mon, Dec 05, 2011 at 01:35:52PM +, Daniel P. Berrange wrote:
> > On Fri, Dec 02, 2011 at 02:40:03PM +0100, Christophe Fergeau wrote:
> > > Hi,
> > >
> > > This patch series adds support for setting nodes as has been
> >
On Mon, Dec 05, 2011 at 01:35:52PM +, Daniel P. Berrange wrote:
> On Fri, Dec 02, 2011 at 02:40:03PM +0100, Christophe Fergeau wrote:
> > Hi,
> >
> > This patch series adds support for setting nodes as has been
> > discussed in the "[PATCH libvirt-glib 02/15] Add objects for dealing with
> >
On Fri, Dec 02, 2011 at 02:40:03PM +0100, Christophe Fergeau wrote:
> Hi,
>
> This patch series adds support for setting nodes as has been
> discussed in the "[PATCH libvirt-glib 02/15] Add objects for dealing with
> devices" thread.
>
> It introduces a GVirConfigDomainChardev which derives fro
Hi,
This patch series adds support for setting nodes as has been
discussed in the "[PATCH libvirt-glib 02/15] Add objects for dealing with
devices" thread.
It introduces a GVirConfigDomainChardev which derives from
GVirConfigDomainDevice. The actual classes to create , ,
nodes will inherit fro
Hi everyone,
We currently using libvirt for PYTI GSOC Project (it works very well!)
and we encounter a problem. We use VM with two disk images, one which
must to be snapshoted/rollbacked and the other one which must be not.
We use VirtualBox as hypervisor and to do so, VirtualBox define
"Special i
These patches add support for the legacy qemu -vmchannel option. The following
domain xml:
becomes:
-vmchannel di:0200,unix:/tmp/vmchannel,server,nowait
I don't expect these to be merged, but I would appreciate a review.
Thanks,
Matt
--
Libvir-list mailing list
Libvir-list@redhat.com
This is an update of the patchset I posted yesterday. There have been a few
changes in the 4th patch, which actually adds guestfwd support:
Firstly, after discussion on IRC, it was agreed that 'vmchannel' is a poor name
for the collection of implementations of private host<->guest channels, becaus
This series adds support for a vmchannel using qemu's guestfwd. I'll be
following up with support for virtio-serial and RHEL5's vmchannel.
A vmchannel is specified as:
There are a couple of minor complications. Firstly, the existing chrdev
structure assumes that all front-ends take only
Hello,
the following patches add full support for qcow/qcow2 volume encryption,
assuming a client that supports it.
(Main changes since the previous version:
* Add "flags" argument to virSecretDefineXML(), virSecretGetXMLDesc(),
virSecretSetValue(), virSecretGetValue()
* Various clean-ups and
Hello,
the following patches add full support for qcow/qcow2 volume encryption,
assuming a client that supports it.
(Main changes since the previous version:
* Significantly change the internal API, basing it on virSecretPtr instead of
(virConnectPtr, secret_id); details in patch 1
* Make vir
23 matches
Mail list logo
