Re: [Xen-devel] [PATCH 3/4] Allow vif= to specify PCI address for each nic

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Jun 16, 2015 at 11:23:46AM -0400, Don Slutz wrote:
[...]
> >>>> which enables usage of xen-netback.
> >>>>
> >>>
> >>> In any case, exposing HVM-only options to top-level vif configuration
> >>> space doesn't look right.
> >>
> >>
> >> There are already HVM-only options in vifs:
> >>
> >> ### type
> >>
> >> This keyword is valid for HVM guests only.
> >> ...
> >> ### model
> >>
> >> This keyword is valid for HVM guest devices with `type=ioemu` only.
> >> ...
> >>
> >>> Why do you want to set bus and addr? The
> >>> rationale should be stated in commit message.
> >>
> >>
> >> That is why I said:
> >>
> >>>> This can help with Windows finding nics at boot time.
> >>
> >> Windows boot code is not as flexible as Linux.  Most versions of Windows
> >> like to blue screen if the hardware changes enough.
> >>
> > 
> > Looks like you're trying to migrate a guest from VMWare to Xen. If
> > device_model_args_new is sufficient please just use that.
> > 
> 
> It works, but slowly because you are prevented from using the faster PV
> nics.
> 

I'm a bit lost here. Aren't you trying to preserve the same nic
configuration for Windows for compatibility reason (even if it's
slower)? Why is PV network involved? How does this work?

Wei.

>    -Don Slutz
> 
> > Wei.
> > 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel