search for: l72

Hi there, I was wondering if you could help me with a problem I'm having with virt-sysprep. It's a recurrent problem running virt-sysprep: Examining the guest ... Fatal error: exception Guestfs.Error("guestfs_launch failed. See http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs and/or run 'libguestfs-test-tool'.") So I ran virt-sysprep and

...if the rate is substantially less than 1 megabit? We either ought to scale this according to the size of the number being printed, or else let the user select it. For scaling, here's some code from fio: https://github.com/axboe/fio/blob/bef74db41fb5a1607fd55cb86544165fc08acac1/lib/num2str.c#L72 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http:/...

...nection, although only 2 of them are being used on Ubuntu. (1) If you don't supply a list of domain names on the command line, then virt-df will call libvirt to get them. That happens in df/domains.c:get_all_libvirt_domains: https://github.com/libguestfs/libguestfs/blob/master/df/domains.c#L72 If you supply a domain name, then this is not used. (2) Secondly, virt-df calls into libguestfs (the C library) call guestfs_add_domain() with a domain name parameter as a literal string, either one fetched from (1) or one you passed on the command line. Libguestfs then looks that up with libvirt...

Hello, I'm running into an issue using the 'virt-df' command when SASL is enabled in libvirt. I'm running version 1.26.5 of libguestfs on an Ubuntu 14.04 OS. I'm running 'virt-df' for all guests at one time, not specifying a domain or image to use. I was expecting a SASL authentication prompt but to no avail. Below is a sample run: root@all-in-one:~# virt-df -P 15

...nection, although only 2 of them are being used on Ubuntu. (1) If you don't supply a list of domain names on the command line, then virt-df will call libvirt to get them. That happens in df/domains.c:get_all_libvirt_domains: https://github.com/libguestfs/libguestfs/blob/master/df/domains.c#L72 If you supply a domain name, then this is not used. (2) Secondly, virt-df calls into libguestfs (the C library) call guestfs_add_domain() with a domain name parameter as a literal string, either one fetched from (1) or one you passed on the command line. Libguestfs then looks that up with libvirt...

Not getting any love (tender or otherwise) on my pull request<https://github.com/rails/rails/pull/7035>so I thought you folks might like to chip in. What do you think? #cast and #cast! allow you to declare a mapping from generated column names to simplified database column types (i.e. those used in migrations). This way scopes with columns generated in their select lists can also include

...of them are being used on Ubuntu. > > (1) If you don't supply a list of domain names on the command line, then virt-df will call libvirt to get them. That happens in > df/domains.c:get_all_libvirt_domains: > > https://github.com/libguestfs/libguestfs/blob/master/df/domains.c#L72 > > If you supply a domain name, then this is not used. > > (2) Secondly, virt-df calls into libguestfs (the C library) call > guestfs_add_domain() with a domain name parameter as a literal string, either one fetched from (1) or one you passed on the command line. > Libguestfs t...

- Use more friendly output with GiB and MiB/s. - Measure time per operation, providing finer grain stats - Add missing stats for flush I hope that these changes will help to understand and imporve virt-v2v performance. Nir Soffer (3): filters: stats: Show size in GiB, rate in MiB/s filters: stats: Measure time per operation filters: stats: Add flush stats filters/stats/stats.c | 117

The method is here: https://github.com/rails/rails/blob/master/activerecord/lib/active_record/persistence.rb#L288. The method takes the in-memory attribute value and increments it by the specified amount. A safer approach (from an isolation standpoint) would be to let the database determine the value. Instead of telling the database what value to persist in the database, the SQL can written