[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 11/13] libxl: set nic type to VIF by default
Roger Pau Monne writes ("Re: [Xen-devel] [PATCH 11/13] libxl: set nic type to VIF by default"): > If this is right, I have to change my hotplug patches, but this will be > a mess, because I have no way to tell if a domain is PV or HVM when > plugging in the devices, so if VIF is passed for both PV or PV+TAP I > will have no way of knowing that. Hmmm. > Should we create three different nic types? VIF (PV), IOEMU (TAP), > HYBRID (PV+TAP)? I think this might be better. Or alternatively, always provide PV, and have a flag which says `do provide ioemu'. I think it's very confusing if setting the `type' to `ioemu' rather than `pv' means `do provide pv but provide ioemu as well'. Another way of looking at it is: if we wanted to provide some other interfaces (besides Xen PV and emulated PCI) in the future, would it be an alternative to PV or to PCI or something additional ? Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |