Sorry about the spam...
You were right, I worked with old libvirt, Thanks!
I have another question about QEMU memory allocation,
There is a possibility to put in libvirt :
This is suppose to lock all the memory that has been allocated for the
guest into host's ram,
Is there any way to ju
You were right, I worked with old libvirt, Thanks!
I have another question about QEMU memory allocation,
There is a possibility to put in libvirt :
On Thu, Jan 28, 2016 at 10:53 AM, Daniel P. Berrange
wrote:
> On Thu, Jan 28, 2016 at 09:46:26AM +0100, Paolo Bonzini wrote:
> >
> >
> > On 28/
On Thu, Jan 28, 2016 at 09:46:26AM +0100, Paolo Bonzini wrote:
>
>
> On 28/01/2016 08:28, Roy Shterman wrote:
> >
> > Important to understand that after modifying and saving configuration of
> > xml with virsh edit $name_of_guest
> >
> > when i reenter the xml i can't see the iothread configura
On 28/01/2016 08:28, Roy Shterman wrote:
>
> Important to understand that after modifying and saving configuration of
> xml with virsh edit $name_of_guest
>
> when i reenter the xml i can't see the iothread configuration in there.
> don't understand why.
>
I suspect that your libvirt is too o
On Thu, 01/28 09:28, Roy Shterman wrote:
> Tried it again,
>
> Important to understand that after modifying and saving configuration of
> xml with virsh edit $name_of_guest
>
> when i reenter the xml i can't see the iothread configuration in there.
> don't understand why.
>
> Also, after add wha
Tried it again,
Important to understand that after modifying and saving configuration of
xml with virsh edit $name_of_guest
when i reenter the xml i can't see the iothread configuration in there.
don't understand why.
Also, after add what you suggested I checked with "info qtree" command on
the
On Wed, 01/27 21:03, Roy Shterman wrote:
> Hi,
>
> First of all thank very much for your help,
>
> Second, unfortunately data-plane didn't worked well, I tried to add threads
> from the instructions you gave me.
>
> Here is my full xml file, maybe you can help me to understand why it didn't
> wo
Hi,
First of all thank very much for your help,
Second, unfortunately data-plane didn't worked well, I tried to add threads
from the instructions you gave me.
Here is my full xml file, maybe you can help me to understand why it didn't
worked :
gen-r-vrt-105-007-RH7.0x64
8f79e97e-d452-4577-
On 20/01/2016 21:12, Roy Shterman wrote:
> Hi,
>
> I have two questions,
>
> First, I'm developing for Libiscsi and trying to work with virtio-scsi
> dataplane or even virtio-blk dataplane and it doesn't works well.
>
> I'm working with latest qemu and latest Libiscsi in RedHat 7 libvirt
> pac
On Wed, 01/20 22:12, Roy Shterman wrote:
> and nothing happened, can you think of something i'm missing?
The "x-data-plane=on" option used to be the temporary flag and has been removed
since last release of QEMU. In the command line, the syntax to use dataplane
for virtio-blk/scsi is:
-object
Hi,
I have two questions,
First, I'm developing for Libiscsi and trying to work with virtio-scsi
dataplane or even virtio-blk dataplane and it doesn't works well.
I'm working with latest qemu and latest Libiscsi in RedHat 7 libvirt
package.
my iscsi xml part is :
virtio-blk -
11 matches
Mail list logo
