Yikes - wrong list! Fingers and brain not in sync, sorry for the noise.
John
Meeting date/time: Jul 01, 13:00 UTC
Previous meetings: http://etherpad.corp.redhat.com/PlatformVirtStorageMeetings
Prior meeting:
http://etherpad.corp.redhat.com/PlatformVirtStorageMeetings-2020-Jun-10
Join the meeting:
Bluejeans: https://redhat.bluejeans.com/1471327918/
(phone numbers are
On 03/02/2017 07:37 AM, Daniel P. Berrange wrote:
> Currently the query-migrate-parameters command will omit reporting
> of the tls-creds & tls-hostname parameters if their value is NULL.
> This makes it impossible for an app to detect if these parameters
> are supported by QEMU, without trying
On 12/21/2016 12:11 PM, Weiwei Jia wrote:
> Hi,
>
> I cannot add iothreads
> (https://libvirt.org/formatdomain.html#elementsIOThreadsAllocation) in
> the libvirt xml configuration file. Once I add
> "4" and other related config for IOthreads into
> the libvirt xml configuration file with virsh
>>> After creating the vGPU, if required by the host driver, all the other
>>> type ids would disappear from "virsh nodedev-dumpxml pci__86_00_0" too.
>>
>> Not wanting to make assumptions, but this reads as if I create one type
>> 11 vGPU, then I can create no others on the host. Maybe I'm
On 09/02/2016 05:48 PM, Paolo Bonzini wrote:
>
>
> On 02/09/2016 20:33, Kirti Wankhede wrote:
>> We could even do:
echo $UUID1:$GROUPA > create
where $GROUPA is the group ID of a previously created mdev device into
which $UUID1 is to be created and added to the same
On 09/02/2016 02:33 PM, Kirti Wankhede wrote:
>
> On 9/2/2016 10:55 PM, Paolo Bonzini wrote:
>>
>>
>> On 02/09/2016 19:15, Kirti Wankhede wrote:
>>> On 9/2/2016 3:35 PM, Paolo Bonzini wrote:
my-vgpu
pci__86_00_0
On 09/02/2016 06:05 AM, Paolo Bonzini wrote:
>
>
> On 02/09/2016 07:21, Kirti Wankhede wrote:
>> On 9/2/2016 10:18 AM, Michal Privoznik wrote:
>>> Okay, maybe I'm misunderstanding something. I just thought that users
>>> will consult libvirt's nodedev driver (e.g. virsh nodedev-list && virsh
[...]
>>
>> Figured I'd chime in since I tripped across this today...
>>
>> I think the one thing that concerns me about this '_' approach is we'd
>> be "stuck" with it. Eventually if 'initiator-name' is added to the
>> -drive command (as well as being able to parse the 'user=' and
>>
On 04/13/2016 12:17 PM, Daniel P. Berrange wrote:
> The iSCSI block driver has a very strange approach whereby it
> does not accept options directly as part of the -drive arg,
> but instead takes them indirectly from a -iscsi arg. To make
> up -driver and -iscsi args, it takes the iSCSI target
On 04/08/2014 12:45 PM, Eric Blake wrote:
On 04/08/2014 10:26 AM, John Ferlan wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1002813
If qemuDomainBlockResize() is passed a size not on a KiB boundary - that
is passed a size based in bytes (VIR_DOMAIN_BLOCK_RESIZE_BYTES), then
depending
11 matches
Mail list logo
