search for: vf1

...a VarIdent structure to my gam model which is fitting smoothing functions to the time variables year and month for a particular species. When I try to add the varIdent weights to variable Month I get this error returned. Error in model.frame.default(formula = Chel ~ 1 + M + YM + M + YM, weights = Vf1, : variable lengths differ (found for '(weights)') Here is the simple code I am using. library(mgcv); library(lattice) library(nlme) Vf1=varIdent(form=~M) Chel2=gam(Chel~s(M, fx=F, bs="tp")+ s(YM, fx=F, bs="tp")+s(M,YM, fx=F, bs="tp"), family=poisson(link=...

...aid that I should write xml like below: ============================ <network> <name>macvtap_passthrough’</name> <forward mode=’passthrough> <interface dev=’vf0’ /> <interface dev=’vf1’ /> .. .. </forward> </network> ============================ I guess here the vf0 & vf1 should be the VFs of Intel 82599. What make me confused is that we know we can not see the vf 0 & vf 1 directly from the ho...

Hi, I am trying to add multiple variance structures such as the first example below: vf1 <- varComb(varIdent(form = ~1|Sex), varPower()) However my code below will not work can anybody please advise me? VFcomb<-varComb(varExp(form=~depcptwithextybf),varFixed(form=~FebNAO)) also if you have two variables with the same weights function would you write that as: VFcomb<-varCom...

...e only have >a single bit so the goal for now is trying to keep this as simple as >possible. I have another usecase that would require the solution to be different then what you suggest. Consider following scenario: - baremetal has 2 sr-iov nics - there is a vm, has 1 VF from each nics: vf0, vf1. No virtio_net - baremetal would like to somehow tell the VM to bond vf0 and vf1 together and how this bonding should be configured, according to how the VF representors are configured on the baremetal (LACP for example) The baremetal could decide to remove any VF during the VM runtime, it can...

...so the goal for now is trying to keep this as simple as >>possible. > > I have another usecase that would require the solution to be different > then what you suggest. Consider following scenario: > - baremetal has 2 sr-iov nics > - there is a vm, has 1 VF from each nics: vf0, vf1. No virtio_net > - baremetal would like to somehow tell the VM to bond vf0 and vf1 > together and how this bonding should be configured, according to how > the VF representors are configured on the baremetal (LACP for example) > > The baremetal could decide to remove any VF durin...

...so the goal for now is trying to keep this as simple as >>possible. > > I have another usecase that would require the solution to be different > then what you suggest. Consider following scenario: > - baremetal has 2 sr-iov nics > - there is a vm, has 1 VF from each nics: vf0, vf1. No virtio_net > - baremetal would like to somehow tell the VM to bond vf0 and vf1 > together and how this bonding should be configured, according to how > the VF representors are configured on the baremetal (LACP for example) > > The baremetal could decide to remove any VF durin...

...> + > >> + # Enable vDPA VF auxiliary device(s) in the PF > >> + devlink dev param set pci/$PF_BDF name enable_vnet value true cmode runtime > >> + > > > > Does this mean we can't do per VF configuration for vDPA enablement > > (e.g VF0 for vdpa VF1 to other type)? > > For now, yes, a PF only supports one VF type at a time. We've thought > about possibilities for some heterogeneous configurations, and tried to > do some planning for future flexibility, but our current needs don't go > that far. If and when we get there...

On Tue, Feb 20, 2018 at 2:42 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Fri, Feb 16, 2018 at 07:11:19PM CET, sridhar.samudrala at intel.com wrote: >>Patch 1 introduces a new feature bit VIRTIO_NET_F_BACKUP that can be >>used by hypervisor to indicate that virtio_net interface should act as >>a backup for another device with the same MAC address. >>

On Tue, Feb 20, 2018 at 2:42 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Fri, Feb 16, 2018 at 07:11:19PM CET, sridhar.samudrala at intel.com wrote: >>Patch 1 introduces a new feature bit VIRTIO_NET_F_BACKUP that can be >>used by hypervisor to indicate that virtio_net interface should act as >>a backup for another device with the same MAC address. >>

...\ | L2 driver | . \ +-------------+ . \ | . \ | . \ +------------------------+ +------------+ | PF VF1 VF2 ... VFn | | | | | | regular | | SR-IOV NIC | | nic | | +--------------+ | | +--------+ | | embedded | | +---+ | |...

...\ | L2 driver | . \ +-------------+ . \ | . \ | . \ +------------------------+ +------------+ | PF VF1 VF2 ... VFn | | | | | | regular | | SR-IOV NIC | | nic | | +--------------+ | | +--------+ | | embedded | | +---+ | |...

This is something I've been working on: Reworking inspection so it's not a big mess of ad hoc C code, but instead uses a well-defined domain-specific language to describe how we inspect guests. The best introduction to this is the manual page, which I include below (it's also included in patch 2/3). Rich. ---------------------------------------------------------------------- NAME

Previously posted: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html Inspection now really succeeds on a small number of simple guests. To test it out: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" Rich.

This is a more working version. Inspection (partially) succeeds on a real guest this time :-) You can test it out on a real guest (in this case, a CentOS disk image located at /tmp/centos-6.img) by doing: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" which will print lots of debugging, and at the end the

For background on this change, see: https://rwmj.wordpress.com/2015/12/06/inspection-now-with-added-prolog/ v2 was previously posted here: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html To test this patch series on a real guest, you can do: $ ./run guestfish -v -x -a /var/tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection