Hey everybody, Any news about the topic? I could not find anything relevant yet.
Thanks, Rom On Tue, Jan 21, 2014 at 3:34 PM, Rom Freiman <[email protected]> wrote: > Hi, > > We all agree that it's not specific to virt-v2v. > > I managed to reproduce the same double fault on "normal" L2 boot - without > libguestfs interference. > And as Paolo wrote already, he will take a look at it. > > Thanks, > Rom > > > On Tue, Jan 21, 2014 at 3:05 PM, Richard W.M. Jones <[email protected]>wrote: > >> On Tue, Jan 21, 2014 at 04:38:30PM +0100, Kashyap Chamarthy wrote: >> > On 01/17/2014 04:06 PM, Rom Freiman wrote: >> > > Kashyap, just to be sure - it happens to you during the v2v >> > > conversion? on L2? >> > >> > I haven't done any v2v conversions in L2 (or at any other level). >> >> I'm highly doubtful this problem is specific to virt-v2v. virt-v2v >> might trigger it in some circumstances, but it seems to be a broader >> problem that could affect any libguestfs instance running in L2, or >> indeed any *VM*. >> >> Rich. >> >> -- >> Richard Jones, Virtualization Group, Red Hat >> http://people.redhat.com/~rjones >> virt-top is 'top' for virtual machines. Tiny program with many >> powerful monitoring features, net stats, disk stats, logging, etc. >> http://people.redhat.com/~rjones/virt-top >> > >
_______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
