|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] Xen 4.1 Feature Request List
On Wed, Apr 7, 2010 at 7:51 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Wed, Apr 07, 2010 at 04:13:07AM -0700, Grant McWilliams wrote:
>
> These might not be wishes for 4.1 as some may be too big but they're my
> wishlist anyway. Note they also might not be things that belong to the
> Hypervisor but rather to tools associated with.
>
> 1. Make qcow2 actually work and include backing files.
>
Have you checked out blktap2 VHD support? Does it work for you?
I haven't. I thought it was only commercial Xenserver that supported VHD.
See: http://wiki.xensource.com/xenwiki/XenCommonProblems
for links.
> 1. If it can't be made to work then it should be taken out and not
> mentioned in the docs so we don't waste weeks trying to get it to
> work.
>
From which docs?
The internet! :-) I assumed that qcow was in the docs since Xen supports it and it's mentioned all over the forums. It very well might not be mentioned in the docs but it has some support for qcow that no matter which version of xen or Centos I used I ran into some bug that stopped me from using it. As class as I got was to use qcow images as disks but with no backing store which I don't think makes a whole lot of sense.
> 2. Figure out why you can't start a VM with a disk image residing in a
> ramdisk (bug?)
I have never tried this one. Which disk backend did you use?
I was using tap:aio disk images with Xen 3.4. I really wanted to use a qcow2 backing disk in a ram disk so all reads would be super fast then the writes would go to the RAID. I then stepped down from that lofty goal and tried to get any DomU to boot from any image in ramdisk and it would error immediately. It's been a while now so I don't remember the error. I could try it again though.
-- Pasi
Grant McWilliams
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|