similar to: Could you please help with questions about the net failover feature

Hi Laine, For the feature testing before, I only test the linux bridge setting as in 2), it works. Now I tried 1), to use macvtap bridge mode connected to the PF, it can not work as the hostdev interface can not get dhcp ip address on the guest. Check on host, the /var/log/messages and dmesg both says: "Jul 6 04:54:45 dell-per730-xx kernel: ixgbe 0000:82:00.1 enp130s0f1: 1 Spoofed packets

On 2020-07-06 10:01, Laine Stump wrote: > On 7/6/20 5:10 AM, Yalan Zhang wrote: > > > > Hi Laine, > > > > For the feature testing before, I only test the linux bridge setting as > > in 2), it works. > > Now I tried 1), to use macvtap bridge mode connected to the PF, it can > > not work as the hostdev interface can not get dhcp ip address on the >

On 7/8/20 10:02 AM, Ken Cox wrote: > > On 7/8/20 1:30 AM, Stefan Assmann wrote: >> On 2020-07-06 10:01, Laine Stump wrote: >>> On 7/6/20 5:10 AM, Yalan Zhang wrote: >>>> Hi Laine, >>>> >>>> For the feature testing before, I only test the linux bridge setting as >>>> in 2), it works. >>>> Now I tried 1), to use

On 7/6/20 5:10 AM, Yalan Zhang wrote: > > Hi Laine, > > For the feature testing before, I only test the linux bridge setting as > in 2), it works. > Now I tried 1), to use macvtap bridge mode connected to the PF, it can > not work as the hostdev interface can not get dhcp ip address on the guest. > Check on host, the /var/log/messages and dmesg both says: > >

On 7/8/20 1:30 AM, Stefan Assmann wrote: > On 2020-07-06 10:01, Laine Stump wrote: >> On 7/6/20 5:10 AM, Yalan Zhang wrote: >>> Hi Laine, >>> >>> For the feature testing before, I only test the linux bridge setting as >>> in 2), it works. >>> Now I tried 1), to use macvtap bridge mode connected to the PF, it can >>> not work as the

On 3/21/20 1:08 AM, Yalan Zhang wrote: > In my understanding, the standby and primary hostdev interface may be in > different subnet. There is only one hostdev device in the team pair (that will be the one with <teaming type='transient'.../> since it needs to be unplugged during migration). The other device must be a virtio device (the one with <teaming

On Thu, Aug 22, 2019 at 2:24 AM Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Wed, Aug 21, 2019 at 01:37:21PM -0700, Ihar Hrachyshka wrote: > > Hi all, > > > > KubeVirt uses libvirtd to manage qemu VMs represented as Kubernetes > > API resources. In this case, libvirtd is running inside an > > unprivileged pod, with some host mounts / capabilities

On Thu, Aug 22, 2019 at 12:01 PM Laine Stump <laine@redhat.com> wrote: > > On 8/22/19 10:56 AM, Ihar Hrachyshka wrote: > > On Thu, Aug 22, 2019 at 2:24 AM Daniel P. Berrangé <berrange@redhat.com> wrote: > >> > >> On Wed, Aug 21, 2019 at 01:37:21PM -0700, Ihar Hrachyshka wrote: > >>> Hi all, > >>> > >>> KubeVirt uses

Hello, We encountered a problem while testing SRIOV on kubevirt [1]: We are currently using the Device "hostdev" generic options to pass-through the VF to the guest. It is not done through the "interface" (with type hostdev) because that option requires access to the PF which is not available in our case (the VF is moved to the container namespace where libvirt runs, but not

Hi all, I'm testing on debian/unstable SR-IOV feature with Broadcom BCM57810 cards and KVM hypervisor: Compiled against library: libvirt 1.2.1 Using library: libvirt 1.2.1 Using API: QEMU 1.2.1 Running hypervisor: QEMU 1.7.0 bnx2x -> firmware 7.8.17 -> driver from kernel 3.12.7 8 VFs are created on the first PF. For each VF, a specific mac address is set manually using "ip

Hi Laine, Yes we are setting the names as GE0-0 manually. We have turned trust ON for host IGB driver. [root@nfvis libvirt]# ip link show GE0-0 3: GE0-0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 9216<tel:9216> qdisc mq master ovs-system state UP mode DEFAULT qlen 1000<tel:1000> link/ether a0:23:9f:ce:b1:f8 brd ff:ff:ff:ff:ff:ff vf 0 MAC 52:54:00:29:3c:be, spoof checking

Hi Laine, Thanks for taking the time to respond to my question. I think I have not described my problem clearly. Let me explain my issue below with the information that you had requested. My assumption according to the information you gave me is that the admin MAC and VF MAC are the same in my case. I see a PF (GE0-0) interface but I don’t see a vfnetdev interface as you mentioned in your

Dear List , We are using intel 82599EB based SRIOV capable 10GbE cards on the host machine.The VFs are being assigned to the guest in pass through mode and are providing the network connectivity as expected. However when we shutdown the guest the connectivity does not comes back via the VFs on the guest in next boot unless the VFs are detached from the *guest* *before* initiating a shutdown of

On Fri, 23 Aug 2019, 0:27 Laine Stump, <laine@redhat.com> wrote: > (Adding Alex Williamson to Cc so he can correct any mistakes) > > On 8/22/19 4:39 PM, Ihar Hrachyshka wrote: > > On Thu, Aug 22, 2019 at 12:01 PM Laine Stump <laine@redhat.com> wrote: > >> > >> On 8/22/19 10:56 AM, Ihar Hrachyshka wrote: > >>> On Thu, Aug 22, 2019 at 2:24 AM

On 03/10/14 17:15, Laine Stump wrote: > On 10/03/2014 11:38 AM, lejeczek wrote: >> hi everybody >> >> I'd presume virsh makes the best possible choice, right? >> It is that just seems bit... odd having realtek in guest and Intel's >> VF on host, no? > This can safely be ignored - in the case of an SRIOV VF that is assigned > to the guest using PCI

Hi guys, I'm wondering whether libvirt supports live migration for the VM with PCI passthrough devices. or it must be assumed before live migration that all passthrough devices be unplugged? If so, all unplugged devices should be manually hot-plugged to the VM after migration?? Thanks.

I'm planning to set up a libvirt/kvm system using a card with SR-IOV support. I'd like to use the vf pool option rather than statically assigning a vf to each vm. However, I'd also like each vm to have a static MAC address and I have multiple VLANs they will be on. I found in the documentation a syntax for specifying a MAC and a vlan when the vf is statically assigned, but I don't

hi everybody I'd presume virsh makes the best possible choice, right? It is that just seems bit... odd having realtek in guest and Intel's VF on host, no? regards

hi everybody I'm having I pretty regular setup, so I'd like to think. Guest network is to use passthrough and a DNS+DHCP on a neighbour system gets requests and then DHCP updates DNS records but with libvirt host's name instead of guest's. Am I missing something here? How do make a guest claim DNS update and the not host on which that guest is running? many thanks P.

Greetings Laine, > Sent: Monday, April 30, 2018 at 8:31 PM > From: "Laine Stump" <laine@redhat.com> > To: libvirt-users@redhat.com > Cc: daggs <daggs@gmx.com> > Subject: Re: [libvirt-users] connecting host and guest vm using a dummy nic > > On 04/27/2018 06:39 PM, daggs wrote: > > Greetings all, > > > > I have a host machine that runs