qemu and xl semantics

[Christoph Egger <Christoph.Egger@amd.com>]

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