similar to: Hyper-V v2v

Le 08/01/2016 09:17, Richard W.M. Jones a écrit : > On Thu, Jan 07, 2016 at 12:08:13PM +0100, Kevin C wrote: >> Hi list, >> >> What is the best method to migrate Hyper-V 2012 VM to oVirt/RHEV ? I >> made a v2v livecd, but it never load consoles and never launch p2v >> service (works well with BIOS VM or hardware, but G2 HyperV VM needs >> EFI to boot).

Hello I have error virt-v2v: error: unable to rebuild initrd (/boot/initramfs-4.2.3-300.fc23.x86_64.img) because mkinitrd or dracut was not found in the guest My physical machine run on fedora23 Boot on usb made from virt-p2v-livecd-1.32.0.fc23.iso <http://oirase.annexia.org/virt-p2v/virt-p2v-livecd-1.32.0.fc23.iso> Log joined to this mail Do you have this problem ?

Greetings, I am suffering of several weird errors which show randomly and make me suspect some concurrency issue. Libguestfs version is 1.28.1, linux kernel 3.16, libvirt 1.2.9 and qemu 2.1. What I'm trying to do is comparing the disk state at two different point of a guest execution. Disk snapshots are taken through libvirt in different moments (I am aware of caching issue), from such

2015-05-27 15:21 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > On Wed, May 27, 2015 at 09:38:38AM +0300, NoxDaFox wrote: > > * RuntimeError: file receive cancelled by daemon - On r = > > libguestfsmod.checksums_out (self._o, csumtype, directory, sumsfile) > > * RuntimeError: hivex_close: do_hivex_close: you must call 'hivex-open' > > first to

On Sun, Mar 23, 2014 at 12:26:28PM +0000, Richard W.M. Jones wrote: > Secondly, we should be able to inspect all Linux guests, including > Tiny Core Linux, but it looks like in this case it is failing. This > is a bug. I had a look at how the Tiny Core Linux ISO is arranged. It loads the main operating system root partition as a single large initramfs, with optional modules loaded

Hello, We have a nodejs app which is injecting first boot scripts using virt-customize however the exact same commands are working when triggered manually. Here is the debug output of the commands Regards, Peter [ 0.0] Examining the guest ... libguestfs: trace: set_network true libguestfs: trace: set_network = 0 libguestfs: trace: add_drive

Hi, On Wed, November 16, 2016 11:10 am, Richard W.M. Jones wrote: > >> It eventually did complete, after several hours. But I don't understand >> why this particular VM took so long when others (with similar disk >> sizes/usages/configurations) completed in only 1-2 minutes. Each VM is >> effectively exactly the same (it's a build slave), so it's just the

Continuation/rework of: https://www.redhat.com/archives/libguestfs/2020-May/msg00020.html This is my approach, as I explained here: https://bugzilla.redhat.com/show_bug.cgi?id=1828952#c4 https://www.redhat.com/archives/libguestfs/2020-May/msg00035.html IOW: do not attempt to relabel if the guest is not enforcing, as it is either useless or may fail; few words more are in the comments of patch #3.

Hi Rich, On Wed, November 16, 2016 1:34 pm, Richard W.M. Jones wrote: > On Wed, Nov 16, 2016 at 11:31:40AM -0500, Derek Atkins wrote: >> > Running `virt-v2v -v -x ...' and observing the output will give you a >> > good idea of what precisely it was doing for those hours. >> >> Well, as I said in my original email, it was hanging at running >> setfiles:

> On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote: > > Hi, > > My last VM imported in 2 minutes. This one has been sitting for three > hours. I think this is a bug. well, some time it does take a long time. Are you sure it was hung? No I/O going on? adding libguestfs list Thanks, michal > > Just in case it helps, here's a larger piece of

Hello, I launched guestfsd in my guest with this command : guestfsd* -rv*. When i close the handle the deamon crashes. This is the output i got (Deamon side) : guestfsd: main_loop : new request, len 0x28 fsync /dev/sda /dev/sr0 : No medium found guestfsd : main_loop : proc 282

I have been able to get a litle further with converting a windows VM. After getting the updated virt-v2v code and rhsrvany, I now get this error: libguestfs: trace: hivex_node_set_value = 0 libguestfs: trace: upload "/usr/share/virtio-win/drivers/amd64/Win2012R2/netkvm.cat" "/Windows/Drivers/VirtIO" guestfsd: main_loop: proc 365 (hivex_node_set_value) took 0.01 seconds

The options -x -v gave me an error that no such option so I ruined it with —debug option. root@ny2proxd03:/var/lib/vz/images/100# virt-resize --expand /dev/sda3 vm-100-disk-1.qcow2 vm-100-disk-1.qcow2.resized --debug command line: virt-resize --expand /dev/sda3 vm-100-disk-1.qcow2 vm-100-disk-1.qcow2.resized --debug Examining vm-100-disk-1.qcow2 ... libguestfs: trace: add_drive

Hi Rich, This is v3 series to add support for resizing MBR logical partitions. changes to v3: 1. merge patch 1 and patch 3 in v3 2. let mbr_part_type return 'primary' for GPT partitions 3. add test for resizing logical partitions 4. fix extending the extended partition (yet). see patch 7. changes to v2: 1. remove p_part_num 2. remove filter_parts 3. name the function

Hello everyone! After I ran virt-resize (v1.31.28) on my disk with win2012R2 (partition table [GPT]: VFAT (100M), unknown (128M), NTFS (64G)) My VM fails to boot: black screen informing that Windows failed to start... Status: 0xc000000e Info: an unexpected error has occured. After some investigations, I realized that Windows remembers the GUID of disk it is installed to. If I execute

If you spend your time looking at libguestfs debugging output you'll see many messages from the daemon main loop like this: guestfsd: main_loop: new request, len 0x54 guestfsd: main_loop: proc 278 (mkfs) took 0.02 seconds I don't think these messages really bring much value. This commit removes them entirely. An alternative might be to change them to make them shorter and/or less

On 12/10/2015 02:55 PM, Pino Toscano wrote: > On Thursday 10 December 2015 13:55:26 Maxim Perevedentsev wrote: >> Hello everyone! >> >> After I ran virt-resize (v1.31.28) on my disk with win2012R2 >> (partition table [GPT]: VFAT (100M), unknown (128M), NTFS (64G)) >> My VM fails to boot: black screen informing that >> >> Windows failed to start...

Hi I`ve been trying this guestfs_mount_local api for quite a few days, but still can`t get over it. Now it seems to have enter the fuse loop but have some problems with 'mount'? and stops at guestfs_mount_local_run(g). Here`s corresponding code in the test program: ?? if(guestfs_mount_local(g,"/mnt/libg")==-1) exit(EXIT_FAILURE); else guestfs_mount_local_run(g); ?? Below is a

Here is a preliminary fix for this bug. I'm running the test suite on this now. Rich.

Windows server 2012 sets partition names with spaces. ><fs> part-get-name /dev/sda 3 libguestfs: trace: part_get_name "/dev/sda" 3 guestfsd: main_loop: new request, len 0x38 parted -s -m /dev/null Error: The device /dev/null is so small that it cannot possibly store a file system or partition table. Perhaps you selected the wrong device? Warning: Error fsyncing/closing