From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Egger Subject: qemu and xl semantics Date: Fri, 17 Dec 2010 10:00:37 +0100 Message-ID: <201012171000.38220.Christoph.Egger@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi! When I start a guest with xm the disk startup script assigns a loopback device for qemu to open it. Now it seems that qemu opens the disk image directly. Then when the loopback device wants to open the disk image then that fails with EBUSY. How is the disk startup script supposed to work with the new semantic for a) HVM guests b) PV guests ? The network startup script adds the tap device to the bridge or assigns an ip address. With xl neither the disk nor the network script runs. So when I start the guest with xl then I have the tap device assigned to the guest but the tap device is not configured in the dom0. How does the 'xl' way work in respect to the network script used with 'xm' ? Christoph -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632