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

[Flavio <fbcyborg@xxxxxxxxx>]

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