search for: l215

As a follow up to https://reviews.llvm.org/D20217 I would like to use lto/thinlto to refine when a symbol is marked as local/preemptable. I'm not very familiar with lto though so would appreciate some guidance about how best to go about this. Regards Sean Fertile

...limitation is by design? - If yes, then how should I get the network type disk's physical, allocation and capacity info? - If not, is there any plan to implement it? Thanks! [1] https://github.com/openstack/ceilometer/blob/stable/mitaka/ceilometer/compute/virt/libvirt/inspector.py#L215 [2] https://bugs.launchpad.net/ceilometer/+bug/1457440 [3] https://github.com/libvirt/libvirt/blob/d6c25c34ef682a69f73f6ec200129e61b2932088/src/qemu/qemu_driver.c#L11727 [4] https://github.com/libvirt/libvirt/blob/d6c25c34ef682a69f73f6ec200129e61b2932088/src/storage/storage_backend.c#L142

...<&3' > > Both fail... So what's happening is that /etc/resolv.conf in the appliance never gets created. *If* /etc/resolv.conf had been created then we should see evidence that this code had been run: https://github.com/libguestfs/libguestfs/blob/master/daemon/command.c#L148-L215 (eg. the "renaming ... to ..." messages should appear). Question is why does /etc/resolv.conf not get created? On Fedora, it is created by dhclient running from appliance/init: https://github.com/libguestfs/libguestfs/blob/master/appliance/init#L88-L94 On Debian/Ubuntu that is suppos...

On 03/13/2015 11:13 AM, Richard W.M. Jones wrote: > > Yes, the log indicates name resolution not working. Please try the > diagnosis steps that I outlined in: > > https://www.redhat.com/archives/libguestfs/2015-March/msg00075.html Sorry, I somehow missed the above message. $ ./run guestfish get-backend direct Here are the outputs of the /dev/tcp test, first doing: $ ./run