From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-15?Q?Martin_Tr=F6ster?= Subject: FW: Xen 3.3.0 - QEMU COW disk image with sparse backing file - VM fails to start Date: Mon, 02 Feb 2009 20:07:59 +0100 Message-ID: <441688901@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable Return-path: 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,=20 I posted my problem to start QCOW based disk images on Xen 3.3 below at xe= n-users already, but as I did not get any responses yet, I directly contac= ted K. Wolf (as a frequent contributor in the QEMU Xen code). He suggested= to post my problem here at xen-devel. Please see the quoted mail below fo= r a detailled description on how my problem occurs. Furthermore, Kevin poi= nted me to this patch on Xen-changelog, which probably introduced the prob= lem I am seeing: http://lists.xensource.com/archives/html/xen-changelog/2008-10/msg00132.ht= ml WIth help of this information, I probably might have a try to undo the cha= nges in a private Xen build, but this does not sound like a good long-term= option, especially for somebody not too deep into Xen/Qemu development...= Therefore, let me kindly ask why it is considered to "handle QCOW backing = files correctly" now=3F The patch, in my eyes, allows to use a raw file as b= acking file, but breaks the use of a QCOW file (sparse file, in my setup) = as a backing file. In my setup, this breaks the use of all current QCOW-fi= les I am running when migrating from Xen-3.2 to Xen-3.3. Although I cannot easily provide a fix by myself, I'd really like to have = an approach both allowing to use QCOW- =5Fand=5F raw images as backing builds.= Any help here is appreciated. Thanks! Cheers, Martin > -----Urspr=FCngliche Nachricht----- > Von: "Martin Tr=F6ster" > Gesendet: 20.01.09 16:22:12 > An: xen-users@lists.xensource.com > Betreff: Xen 3.3.0 - QEMU COW disk image with sparse backing file - VM f= ails to start > Hi, >=20 > I upgraded my Xen 3.2-based test system to Xen 3.3. With this installati= on, I am no longer able to start images with COW disk images based on qcow= sparse files. Starting the DomU via xm create gives success status (with = "Startig Domain test" message printed to console), but xm list directly af= terwards shows no entry for the VM. >=20 > The image structure is: > Base File A.img (sparse QCOW2 file) > COW File B.img (QCOW2 file with A.img as backing file) used as disk in X= en config file (see VM config file below) >=20 > I am running a CentOS 5.2 server with the pre-build packages at http://w= ww.gitco.de/repro and can repro this behaviour on both 3.3.0 and 3.3.1RC1=5F= pre (no 3.3.1 final version available, no time yet to do a build on my own= ). >=20 > In detail, I see the following behaviour: > -> RAW image with disk using file:/ - works > -> QCOW sparse image using tap:qcow - works > -> QCOW image based on RAW image using tap:qcow - works > -> QCOW image based on QCOW sparse image using tap:qcow - fails. >=20 > Logs of failing case: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > /var/log/xen/xend.log shows that the domain immediately terminates, but = no ERROR indication: > [2009-01-20 09:13:55 20596] DEBUG (XendDomainInfo:1443) XendDomainInfo.h= andleShutdownWatch > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s vif. > [2009-01-20 09:13:55 20596] DEBUG (DevController:160) Waiting for 0. > [2009-01-20 09:13:55 20596] DEBUG (DevController:645) hotplugStatusCallb= ack /local/domain/0/backend/vif/8/0/hotplug-status. > [2009-01-20 09:13:55 20596] DEBUG (DevController:645) hotplugStatusCallb= ack /local/domain/0/backend/vif/8/0/hotplug-status. > [2009-01-20 09:13:55 20596] DEBUG (DevController:659) hotplugStatusCallb= ack 1. > [2009-01-20 09:13:55 20596] DEBUG (DevController:160) Waiting for 1. > [2009-01-20 09:13:55 20596] DEBUG (DevController:645) hotplugStatusCallb= ack /local/domain/0/backend/vif/8/1/hotplug-status. > [2009-01-20 09:13:55 20596] DEBUG (DevController:659) hotplugStatusCallb= ack 1. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s vscsi. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s vbd. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s irq. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s vkbd. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s vfb. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s console. > [2009-01-20 09:13:55 20596] DEBUG (DevController:160) Waiting for 0. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s pci. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s ioports. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s tap. > [2009-01-20 09:13:55 20596] DEBUG (DevController:160) Waiting for 51712.= > [2009-01-20 09:13:55 20596] DEBUG (DevController:645) hotplugStatusCallb= ack /local/domain/0/backend/tap/8/51712/hotplug-status. > [2009-01-20 09:13:55 20596] DEBUG (DevController:659) hotplugStatusCallb= ack 1. > [2009-01-20 09:13:55 20596] DEBUG (DevController:155) Waiting for device= s vtpm. > [2009-01-20 09:13:55 20596] INFO (XendDomain:1172) Domain test (8) unpau= sed. > [2009-01-20 09:13:57 20596] INFO (XendDomainInfo:1634) Domain has shutdo= wn: name=3Dtest id=3D8 reason=3Dpoweroff. > [2009-01-20 09:13:57 20596] DEBUG (XendDomainInfo:2389) XendDomainInfo.d= estroy: domid=3D8 > [2009-01-20 09:13:57 20596] DEBUG (XendDomainInfo:2406) XendDomainInfo.d= estroyDomain(8) > [2009-01-20 09:13:57 20596] DEBUG (XendDomainInfo:1939) Destroying devic= e model > [2009-01-20 09:13:57 20596] DEBUG (XendDomainInfo:1946) Releasing device= s > [2009-01-20 09:13:57 20596] WARNING (image:472) domain test: device mode= l failure: no longer running; see /var/log/xen/qemu-dm-test.log=20 >=20 > /var/log/xen/qemu-dm-test.log shows nothing spectacular at all (at least= for me): > domid: 8 > qemu: the number of cpus is 1 > config qemu network with xen bridge for tap8.0 xenbr0 > config qemu network with xen bridge for tap8.1 eth0 > Using xvda for guest's hda > Strip off blktap sub-type prefix to /path/to/test.img (drv 'qcow') > Watching /local/domain/0/device-model/8/logdirty/next-active > Watching /local/domain/0/device-model/8/command > qemu=5Fmap=5Fcache=5Finit nr=5Fbuckets =3D 10000 size 3145728 > shared page at pfn 3fffe > buffered io page at pfn 3fffc > Time offset set 0 > Register xen platform. > Done register platform. >=20 > /var/log/messages also shows nothing remarkable. Interesting entries nev= er seen before are: > Jan 19 17:50:02 test kernel: tapdisk[21929] general protection rip:40b31= 5 rsp:42900108 error:0 > but they occur all the time on Xen 3.3 and Xen 3.3.1 using qcow images (= but seem to be recovered) >=20 > VM config file: > ------------------------------------------------------------------------= ------------------ > name =3D "test" > device=5Fmodel =3D '/usr/lib64/xen/bin/qemu-dm' > builder =3D "hvm" > kernel =3D "/usr/lib/xen/boot/hvmloader" >=20 > # hardware > memory =3D "1024" > disk =3D [ 'tap:qcow:/path/to/B.img,ioemu:xvda,w' ] > vcpus=3D1 >=20 > # network > vif =3D [ 'type=3Dioemu,mac=3D02:00:00:00:00:01','type=3Dioemu,bridge=3Deth0,mac=3D0= 2:00:00:00:01:98' ] > dhcp =3D "dhcp" >=20 > # visualization > sdl =3D 0 > vnc =3D 1 > vncviewer =3D 0 > ------------------------------------------------------------------------= ------------------ >=20 > Any help is appreciated. Thanks! >=20 > Cheers, > Martin =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Deutschlands gr=F6=DFte Online-Videothek schenkt Ihnen 12.000 Videos!* http://entertainment.web.de/de/entertainment/maxdome/index.html