On Fri, Oct 10, 2014 at 4:07 PM, Richard W.M. Jones <rjones(a)redhat.com> wrote:
On Fri, Oct 10, 2014 at 04:03:26PM +0800, Zhi Yong Wu wrote:
> On Fri, Oct 10, 2014 at 3:39 PM, Richard W.M. Jones <rjones(a)redhat.com> wrote:
> > On Fri, Oct 10, 2014 at 11:40:03AM +0800, Zhi Yong Wu wrote:
> >> HI, Richard
> >>
> >> Is there any plan to make daemon to directly run on the hypervisor,
> >> not starting a guest? e.g. directly export a guest image to be a block
> >> device on the hypervisor?
> >
> > Not in 1.28, but adding lxc:// support to the libvirt backend
> > (src/launch-libvirt.c) would be fairly easy.
> >
> > It's an idea that has been kicked around before on the list, eg:
> >
> >
https://www.redhat.com/archives/libguestfs/2014-January/msg00296.html
> It's not what i said, i mean that when you run virt-resize, it doesn't
> start a appliance guest. You know, it will bring up a lot of troubles
> or risks if a guest is started.
There are no risks as far as I'm aware. What kind of troubles/risks?
You
can't make sure that guest never fail or panic forever, right?
That is, you will have to maintain that guest, not customers' guests.
This risk is beyond thought. The maintainance cost will be very
expensive in our super large scale cloud environment.
We are trying not to start a appliance guest when issuing a libguestfs
command, such as virt-resize.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages.
http://libguestfs.org
--
Regards,
Zhi Yong Wu