[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Upstream QEMU does not support vhd snapshot

Hi Thanos,
    1.  QEMU can mount normal vhd file which is also created by vhd-util.
    2. using the vhd image with system installed, using:
         vhd-util snapshot -n init.snap -p <parent vhd>
    3. try to use this init.snap in domU config file like this:
    4. After booting,  the SeaBIOS print:   Boot from hard disk, Failed,   not a bootable disk.
    The patch mentioned did not make anything better to this problem.

Best Regards

Date: 2013-07-05 17:33
Subject: RE: [Xen-users] Upstream QEMU does not support vhd snapshot
> -----Original Message-----
> From: kevin.zhang@xxxxxxxxxxx [mailto:kevin.zhang@xxxxxxxxxxx]
> Sent: 05 July 2013 10:24
> To: Thanos Makatos
> Cc: xen-users
> Subject: RE: [Xen-users] Upstream QEMU does not support vhd snapshot
> Hi  Thanos,
>      Thank you for your reply.
>      I applied this patch to xen 4.3.0-rc6, and make tools; make
> install-tools;  and then reboot the system.
>      However, snapshot created by vhd-util still cannot be mounted by
> qemu.
>      I doubt whether there are other problems here.
How do you create the VHD file and how do you snapshot it? What does qemu complain about when you try to mount it?
> ________________________________________
> Best Regards
> From: Thanos Makatos
> Date: 2013-07-05 16:49
> To: kevin.zhang; xen-users
> Subject: RE: [Xen-users] Upstream QEMU does not support vhd snapshot
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxx [mailto:xen-users-
> > bounces@xxxxxxxxxxxxx] On Behalf Of kevin.zhang@xxxxxxxxxxx
> > Sent: 05 July 2013 03:53
> > To: xen-users
> > Subject: [Xen-users] Upstream QEMU does not support vhd snapshot
> >
> > Hi all,
> >
> >         I'm testing 4.3.0-rc6, and found another problem:
> >         The normal vhd snapshot file cannot be mounted by qemu
> > upstream, which is quite upset.
> >         I search from the web, and find somebody said:
> >              This is due to a bug in the blktap2 code which uses loca
> l
> > time instead of UTC
> >        Is there any patch in the main line blktap2 code for this
> > problem?
> AFAIK there isn't any, but you could try applying the fix that exists i
> n blktap2.5: https://github.com/xapi-
> project/blktap/commit/a79ac2c05f97c2384bbf981419f329f184dc646a. It shou
> ldn't be very hard to rebase the patch.
> Cheers
> >
> > ________________________________________
> > Best Regards
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.