Truth be told I dont really know. What I am going to be doing with it is
pretty much mostly some lab stuff and get working with VRF's a bit
There is a known limitation with virtio backend driver uses interrupt mode
to receive packets and vSRX uses DPDK -
https://dpdk.readthedocs.io/en/stable/nics/virtio.html which in turn
creates a bottleneck in to the guest VM. It is more ideal to use something
like SR-IOV instead and remove as many buffer layers as possible with PCI
passthrough
One easier way too is to use DPDK OVS. I know ovirt supports OVS in later
versions more natively so I just didnt go after it and I dont know if there
is any difference between just regular OVS and DPDK OVS. I dont have a huge
requirement of insane throughput, just need to get packets from amazon back
to my lab and support overlapping subnets
This exercise was somewhat of a POC for me to see if it can be done. A lot
of Junipers documentation does not take in to account such things as ovirt
or proxmox or any linux overlay to hypervisors like it does for vmware /
vcenter which is no fault of their own. They assume flat KVM host (or 2 if
clustered) whereas stuff like ovirt can introduce variables (eg: no MAC
spoofing)
On Fri, Mar 23, 2018 at 3:27 PM, FERNANDO FREDIANI <
fernando.frediani(a)upx.com> wrote:
Out of curiosity how much traffic can it handle running in these
Virtual
Machines on the top of reasonable hardware ?
Fernando
2018-03-23 4:58 GMT-03:00 Joop <jvdwege(a)xs4all.nl>:
> On 22-3-2018 10:17, Yaniv Kaul wrote:
>
>
>
> On Wed, Mar 21, 2018 at 10:37 PM, Charles Kozler < <ckozleriii(a)gmail.com>
> ckozleriii(a)gmail.com> wrote:
>
>> Hi All -
>>
>> Recently did this and thought it would be worth documenting. I couldnt
>> find any solid information on vsrx with kvm outside of flat KVM. This
>> outlines some of the things I hit along the way and how to fix. This is my
>> one small way of giving back to such an incredible open source tool
>>
>>
https://ckozler.net/vsrx-cluster-on-ovirtrhev/
>>
>
> Thanks for sharing!
> Why didn't you just upload the qcow2 disk via the UI/API though?
> There's quite a bit of manual work that I hope is not needed?
>
> @Work we're using Juniper too and oud of curiosity I downloaded the qcow2
> image and used the UI to upload it and add it to a VM. It just works :-)
> oVirt++
>
> Joop
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users