| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Help with the migration to XEN-4.1 please
On Wed, 2011-09-14 at 08:30 -0400, Flavio wrote:
> On 14 September 2011 13:57, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
[...]
> /etc/init.d/xenconsoled
> /etc/init.d/xendomains
> /etc/init.d/xenstored
[...]
> > You should have /etc/init.d/xencommons or Gentoo must provide you with
> > some equivalent (I don't know enough about Gentoo to know)
> I don't think there is something equivalent; maybe it's the case to
> open a bug report
> on bugs.gentoo.org.
>From the above it looks like Gentoo has gone for separate xenconsoled
and xenstored initscripts so you are probably ok.
> On 14 September 2011 13:57, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> >
> > What is the content of your vm_config_file.cfg?
> For instance, this is the config file I use to start the Gentoo VM
> (which was working
> very well with the XM toolstack:
>
> kernel = "/mnt/data/xen/kernel/vmlinuz-xen-3.0.4-domU"
> memory = "512"
> name = "gentoo-10.0-x86_64"
> vif = ['bridge=xenbr0']
> dhcp = "dhcp"
> disk =
> ['file:/mnt/data/xen/vmstore/gentoo-10.0/gentoo-10.0.x86-64.img,xvda1,w',
> 'file:/mnt/data/xen/vmstore/gentoo-10.0/swap.img,xvda2,w']
> root = "/dev/xvda1 ro"
> vcpus = 2
> extra = 'console=hvc0 xencons=tty'
> ip = "off"
>
> >
> > In particular I am thinking that if you have "file:" or "tap:" style
> > disks you will need qemu-xen installed and if this was missing you might
> > get errors like the above.
> I have
> /usr/bin/qemu-img-xen
> /usr/bin/qemu-nbd-xen
> /usr/lib64/xen/bin/qemu-dm
> /usr/share/xen/qemu
>
> but not qemu-xen (I don't know what package to install for that)
I think it is the thing you have as /usr/lib64/xen/bin/qemu-dm is
qemu-xen.
Are you seeing anything under /var/log/xen? Sepcifically the xl-* and
qemu-* logs with the name of your VM in. Do you see any evidence of
qemu-dm actually getting started? (does it appear in "ps" output etc)
Running "xl -vvv create ..." might also print extra debugging which
might be useful. Please can you post all the logs.
The file:/mnt/data/xen/vmstore/gentoo-10.0/gentoo-10.0.x86-64.img (and
the other one) is interesting. 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.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home