search for: l392

...n fact both things: we create a bi-directional pipe, and we optionally enable full IP networking. I suggest TBH you just look at the code, as that's simpler than me explaining it: http://git.annexia.org/?p=libguestfs.git;a=blob;f=src/launch.c;h=0b15ce98d79fac55032a7e93788f62d0011e8c34;hb=HEAD#l392 The key words are "virtio serial" and "user networking". Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen...

On 2018-12-16 8:04 a.m., Charles Lepple wrote: > On Dec 15, 2018, at 10:32 PM, James <bjlockie at lockie.ca> wrote: >> >> My UPS has an LCD that says the battery is 100% and the estimated run time is 12min. >> The uspc has similar results. >> The problem is when line power is lost the UPS batter goes to 0% very quickly (seconds). >> >> It charged to 85%

>Thank you for taking a look. I think that the answer depends on how much slower GNU linkers are with separate .eh_frame sections. If it is not too slow, it may make >sense to generate split .eh_frame sections unconditionally. Otherwise, we might want to add a new option so that clang doesn't produce split .eh_frame sections by >default. I'll start investigating the

.../gold/object.cc#L1372 Did not investigate it, but it looks it is place (https://sourceware.org/ml/binutils/2009-06/msg00097.html) mentioned in comment for https://marc.info/?l=llvm-commits&m=144683596826489. LLD ~head fails here https://github.com/llvm-mirror/lld/blob/master/ELF/InputFiles.cpp#L392 as we are trying to do cast to InputSection, though .eh_frame is not regular InputSection but EhInputSection. Basing on all above I supposed it should be fine to not emit SHF_LINK_ORDER flags for start. I changed implementation so that it emits multiple .eh_frames and sets sh_link field for SHT_X8...

...nal garbage collector. To this end, disks which have not been finalized are given a special description so it should be possible to find them after a full migration has completed: https://github.com/libguestfs/libguestfs/blob/e2bafffce24cd8c0436bf887ee166a3ae2257bbb/v2v/output_openstack.ml#L386-L392 IIRC virt-v2v-wrapper is sending kill -9 to virt-v2v, which it should not do. > The fourth challenge is to limit the resources allocated to virt-v2v > during conversion, because concurrent conversions may have a huge > impact on conversion host performance. In the case of an oVirt host,...

[Adding Tomas Golembiovsky] On Wed, Sep 26, 2018 at 12:11 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > Rather than jumping to a solution, can you explain what the problem > is that you're trying to solve? > > You need to do <X>, you tried virt-v2v, it doesn't do <X>, etc. > Well, that's mainly IMS related challenges. We're working on

...> this end, disks which have not been finalized are given a special > description so it should be possible to find them after a full > migration has completed: > > > https://github.com/libguestfs/libguestfs/blob/e2bafffce24cd8c0436bf887ee166a3ae2257bbb/v2v/output_openstack.ml#L386-L392 > > IIRC virt-v2v-wrapper is sending kill -9 to virt-v2v, which it should > not do. > It's not virt-v2v-wrapper that kills virt-v2v, it's ManageIQ. We have the PID from virt-v2v-wrapper state file. What would be the preferred way to interrupt it ? > > The fourth challen...