On Mon, Nov 2, 2015 at 8:22 AM, Ido Barkan wrote:
> On Sun, Nov 1, 2015 at 8:05 PM, Laine Stump wrote:
>> On 11/01/2015 08:52 AM, Ido Barkan wrote:
>>>
>>> Hi guys,
>>>
>>> We, at oVirt, are considring using the automatic bridge ma
On Sun, Nov 1, 2015 at 8:05 PM, Laine Stump wrote:
> On 11/01/2015 08:52 AM, Ido Barkan wrote:
>>
>> Hi guys,
>>
>> We, at oVirt, are considring using the automatic bridge management
>> feature of libvirt for our hosts
>> (macTableManager='libvirt'
s that have any affect on the
functionality of that feature?
6) are there any plans to support OVS for this feature in the future?
--
Thanks,
Ido Barkan
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
.rpm in order to pass-through
physical
hardware, and it seems that there is a standard way of computing a proper boot
rom for a device.
Since every user of hostdev having this this use case will have to do the same
computation,
I was hoping that libvirt could do it for us.
Thanks,
Ido
- O
Hi,
I am a VDSM developer at Ovirt.
Recently, we opened Bug 1224954 - seabios does not recognize a direct attached
nic [1]
and discovered that in order to leverage the
(as explained in [2]) in the hostdev element, one must compute the correct FILE
path by following something similar to:
$ lsp
Hi,
I am a VDSM developer at Ovirt.
Recently, we opened Bug 1224954 - seabios does not recognize a direct attached
nic [1]
and discovered that in order to leverage the
(as explained in [2]) in the hostdev element, one must compute the correct FILE
path by following something similar to:
$ lspc
