WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Help with the migration to XEN-4.1 please

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] Help with the migration to XEN-4.1 please
From: Flavio <fbcyborg@xxxxxxxxx>
Date: Wed, 14 Sep 2011 16:05:27 +0200
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 14 Sep 2011 07:06:48 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=zaXxx8u2cgh4btjKWhLn5wwhmUKFO0Yze/12XTLQwBk=; b=WQQN01HEqtiHXB9snBL6VSMjTCsKiv1rQkXBGj4qhvN6t0BdI5tw0DhPLK4QLp9l0d xtBwmmbNFymRfT9r8mFq5KziIz9PSe1XecLsbL2A9MDFfX7gXmQA5HKmg7Lg7jYV8xLa P1H7CQWNF/IenTWTUxHmJzHSwH0VWRFo9slsw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1316007936.2892.35.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CAP8Jb=rKu5RFW0tuvHtD819Dz6Jy2HB5OT-d86T1tEk2OP=dtA@xxxxxxxxxxxxxx> <CAP8Jb=pX3mq7vebZ+CKGyh-YM+QH0Vr+Fphaqug_bEgNGLafBg@xxxxxxxxxxxxxx> <1315907178.2892.7.camel@xxxxxxxxxxxxxxxxxxxxxx> <CAP8Jb=qfMa1c8w10inO_gt6-RCscaAsdQ_SyjTxfjSuTAfDMOw@xxxxxxxxxxxxxx> <1316001435.2892.24.camel@xxxxxxxxxxxxxxxxxxxxxx> <CAP8Jb=qrdraJ0c7CLEYEug2nQjxCTvokfGQB4CjNgaacON_DPg@xxxxxxxxxxxxxx> <1316007936.2892.35.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 14 September 2011 15:45, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> From the above it looks like Gentoo has gone for separate xenconsoled
> and xenstored initscripts so you are probably ok.
OK.

> Are you seeing anything under /var/log/xen?
Yes, of course.

> Sepcifically the xl-* and
For instance, if I look for the file related to my gentoo guest I see
xl-gentoo-10.0-x86_64.log and the content is:
Waiting for domain gentoo-10.0-x86_64 (domid 1) to die [pid 6250]
Domain 1 is dead
Unable to get domain death info, quitting

It says it is dead because I issued the command xl destroy <domain_id>
xl shutdown doesn't work, as for the xl reboot.

> qemu-* logs with the name of your VM in.
qemu-dm-gentoo-10.0-x86_64.log and this is the content:

domid: 1
Warning: vlan 0 is not connected to host network
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
/var/tmp/portage/app-emulation/xen-tools-4.1.1-r4/work/xen-4.1.1/tools/ioemu-qemu-xen/hw/xen_blktap.c:628:
Init blktap pipes
Could not open /var/run/tap/qemu-read-1
xen be core: xen be core: can't open gnttab device
can't open gnttab device
xen be core: xen be core: can't open gnttab device
can't open gnttab device
xen be core: xen be core: can't open gnttab device
can't open gnttab device
xs_read(): target get error. /local/domain/1/target.
(qemu) (qemu)


> Do you see any evidence of
> qemu-dm actually getting started? (does it appear in "ps" output etc)
If no virtual machines are running no. But when the VM starts yes:
root      6412  0.1  0.7 118280 16512 ?        Ssl  15:53   0:00
qemu-dm -d 1 -domain-name gentoo-10.0-x86_64 -nographic -M xenpv

>
> Running "xl -vvv create ..." might also print extra debugging which
> might be useful. Please can you post all the logs.
Here it is: http://pastebin.com/t6ekJWJ7

>
> The file:/mnt/data/xen/vmstore/gentoo-10.0/gentoo-10.0.x86-64.img (and
> the other one) is interesting.
As you see I use loop files for the root filesystems. In what sense do you say
it is interesting? I have only these files in that directory:
gentoo-10.0.x86-64.cfg
gentoo-10.0.x86-64.img
swap.img

> A modern kernel does not have the blktap
> driver (for various reasons this cannot go upstream) and so xl falls
> back to a qemu provided block backend if this is not present and block
> back. This is different to how xm/xend worked, it would setup a loop
> device for file:// devices and use blkback.
>
> Can you try manually setting up a loop device (losetup) and passing
> phy:/dev/loopN instead of the file://....*.img? This isn't a real
> solution but it will be a useful datapoint.
I've tried to do that but it seems to be the same thing of using the file:/
syntax.

Thank you so much for your support.

-- 
Flavio

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel