search for: msg00065

...e` job timing to compile everything: real 31m9.792s user 17m18.359s sys 13m17.868s - `make -k check` is still running as I write this, albeit a bit slow. [1] https://bugzilla.redhat.com/show_bug.cgi?id=966807 [2] https://www.redhat.com/archives/linux-audit/2013-May/msg00065.html -- /kashyap

Hi, I am following the below link to install a Fedora19 guest on Fedora19 Host. http://kashyapc.com/2011/08/18/unattended-guest-install-with-a-local-kickstart/ Version : libvirtd (libvirt) 1.0.5.1, QEMU emulator version 1.4.2, Copyright (c) 2003-2008 Fabrice Bellard I have the iso which I loop mounted and created a http repo using python module "python -m SimpleHTTPServer". This

...s to be examined what the result would be if I repeat this on ext4 (and SSD). [*] http://www.freedesktop.org/wiki/Software/systemd/VirtualizedTesting/ > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=966807 > [2] https://www.redhat.com/archives/linux-audit/2013-May/msg00065.html > > -- /kashyap

...TURI, "qemu:///system", -1); } ---------------------------------------------------------------------- By the way, some of the virt tools can open multiple connections to libvirt, and it is architecturally hard to change this: https://www.redhat.com/archives/libguestfs/2012-October/msg00065.html Does libvirt (or policy kit?) provide any mechanism for caching these credentials within the same process, so that we don't have to provide the same creds back to libvirt for multiple connections? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones vi...

...virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html https://www.redhat.com/archives/libguestfs/2015-November/msg00065.html Currently the product variant (eg. client or server) is ignored (see email I sent earlier today). There's actually a fourth patch which I didn't include, which just adds the content of all of the *.inf files from the virtio-win 1.7.4 ISO and directory, to test-data/fake-virtio-win....

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub

...virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html https://www.redhat.com/archives/libguestfs/2015-November/msg00065.html Currently the product variant (eg. client or server) is ignored. --- v2v/v2v_unit_tests.ml | 623 ++++++++------------------------------------------ v2v/windows.ml | 289 +++++++++++++---------- v2v/windows.mli | 2 +- 3 files changed, 265 insertions(+), 649 deletions(-) diff...

v5: https://www.redhat.com/archives/libguestfs/2017-June/msg00065.html Since v5, this now implements inspection almost completely for Linux and Windows guests. Rich.