From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roger Pau Monne Subject: Re: [PATCH v6 10/13] libxl: set nic type to VIF by default Date: Thu, 28 Jun 2012 10:28:17 +0100 Message-ID: <4FEC23B1.8030904@citrix.com> References: <1339676475-33265-1-git-send-email-roger.pau@citrix.com> <1339676475-33265-11-git-send-email-roger.pau@citrix.com> <20452.22966.110320.601890@mariner.uk.xensource.com> <4FE9E153.1050309@citrix.com> <20120626165808.GC2058@reaktio.net> <1340787043.29172.10.camel@zakaz.uk.xensource.com> <4FEC2248.4080005@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FEC2248.4080005@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Ian Jackson , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org Roger Pau Monne wrote: > In the past this was not a problem, since when the guest is PV, we > didn't launch Qemu, and thus the tap device was never created and the > hotplug scripts were not launched. Now that we launch hotplug scripts > from libxl this is a problem, because when we call libxl_device_nic_add, > libxl has no idea if the domain is a PV or HVM guest, and only sees the > network type, which is set to IOEMU by default. > > This is the main problem, I think it should be ok to leave the default > type as IOEMU in libxl__device_nic_setdefault and set the type manually > to VIF for PV guests in > libxl_create.c:libxl__domain_build_info_setdefault, does this sound ok? My bad, libxl__domain_build_info_setdefault doesn't have access to libxl_domain_config, I will search for another place...