On Mon, Nov 30, 2015 at 11:10:52AM -0500, Ken D'Ambrosio wrote:
This means there was an error (some function returned -1), but the
error message was not set. Could you capture the backtrace when this
happens? It's hard to find the exact point, but going function and
checking what returns -1 sh
Hello all,
I find this curious behavior that libvirt will automatically insert a USB
controller and a memballoon virtio driver into the domain's XML, when defineXML
is called. IOW, the original XML did not have these 2 devices but they are
present right after defineXML is called. Why should
On 11/30/2015 07:06 AM, Vasiliy Tolstov wrote:
> 2015-11-30 14:32 GMT+03:00 John Ferlan :
>> As long as the qemu you're using supports the "-object iothread", then
>> this works. I forget the exact version it went into qemu.
>
>
> Nice! Thanks! (i'm use latest qemu) how can i check that data-p
> This means there was an error (some function returned -1), but the
> error message was not set. Could you capture the backtrace when this
> happens? It's hard to find the exact point, but going function and
> checking what returns -1 should do.
Assuming by "backtrace" you mean the strace outp
>>
>> I've read, that disabling 'kvm_steal_time' feature should workarund
>> this bug, but i can't find a way to disable it in libvirt's domain
xmlfile.
>
>There is no support for that in libvirt. Either we must addit ad a
>feature (patches welcome), but if that's there just for a workaround,
>
On Mon, Nov 30, 2015 at 01:57:24AM +0100, Lentes, Bernd wrote:
> Hi,
>
> i read that virsh uses internally qemu-img
> (http://serverfault.com/questions/692435/qemu-img-snapshot-on-live-vm).
> Is that true ? so snapshotting a running vm with virsh or qemu-img is
> the same ?
Functionally, it is th
2015-11-30 14:32 GMT+03:00 John Ferlan :
> As long as the qemu you're using supports the "-object iothread", then
> this works. I forget the exact version it went into qemu.
Nice! Thanks! (i'm use latest qemu) how can i check that data-plane
used by virtio-scsi ?
--
Vasiliy Tolstov,
e-mail: v.
On 11/30/2015 06:23 AM, Vasiliy Tolstov wrote:
> 2015-11-30 14:17 GMT+03:00 John Ferlan :
>> Such as?
>>
>> http://libvirt.org/formatdomain.html#elementsIOThreadsAllocation
>>
>> and usage within as or
>
>
> So you mean that if i define iothread in domain xml and create
> virtio-scsi it auto
2015-11-30 14:17 GMT+03:00 John Ferlan :
> Such as?
>
> http://libvirt.org/formatdomain.html#elementsIOThreadsAllocation
>
> and usage within as or
So you mean that if i define iothread in domain xml and create
virtio-scsi it automatic enables virtio-scsi-data-plane?
--
Vasiliy Tolstov,
e-ma
On 11/30/2015 02:58 AM, Vasiliy Tolstov wrote:
> 2015-11-19 16:09 GMT+03:00 John Ferlan :
>> Check out virsh iothread{info|pin|add|del} and of course the
>> corresponding virDomain{Add|Pin|Del}IOThread and virDomainGetIOThreadInfo.
>
>
> Yes, thanks! Does in near feature libvirt devs integrate
2015-11-30 13:30 GMT+03:00 Adolf Augustin :
> Is it possible to modify the path-variable manually ?
As i know path value is not used for sheepdog... may be i miss something?
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
___
libvirt-users mailing li
Hi,
I tried two different approaches.
1.) Convert an existing Image with qemu-img
qemu-img convert -t directsync lubuntu-14.04.3-desktop-i386.iso
sheepdog:lubuntu1404.iso
=
results in
=
2015-11-19 16:09 GMT+03:00 John Ferlan :
> Check out virsh iothread{info|pin|add|del} and of course the
> corresponding virDomain{Add|Pin|Del}IOThread and virDomainGetIOThreadInfo.
Yes, thanks! Does in near feature libvirt devs integrate this ability
to domain format? As i understand all qemu sta
2015-11-24 15:33 GMT+03:00 Adolf Augustin :
> t should have been solved in libvirt 1.2.17
>
> See here: https://libvirt.org/news.html
>
> =
>
> update sheepdog client] update sheepdog client path (Vasiliy Tolstov),
> .
> =
14 matches
Mail list logo
