[Users] trouble with imported windows VM

[Jonathan Horne]

I did try to create a new VM and add the 2 disks that were originally imported, but still no go.  The vm refuses to boot.

I was also unable to import just the D drive attached to a VM, it gave me the error " virt-v2v: No root device found in this operating system image".  Right now I am trying to consolidate the KVM virtual machine down to 1 disk partitioned to the necessary C and D drives, and ill try an import like that (since it was previously successful coming from KVM with just the one disk).

-----Original Message-----
From: Vered Volansky [mailto:vered at redhat.com]
Sent: Tuesday, April 30, 2013 6:45 AM
To: Jonathan Horne
Cc: Richard W.M. Jones; users at ovirt.org
Subject: Re: [Users] trouble with imported windows VM

Jonathan,

I've asked around (with people not that familiar with v2v) and we're thinking of two options - 1. Assuming that the disks weren't imported with the vm at all use v2v to import each disk separately, then create a new VM and configure it from the top.
2. If the disks were indeed imported, create a new VM with those disks, configure it and remove the old one.

Good luck with that,
Vered

----- Original Message -----
> From: "Jonathan Horne" <jhorne at skopos.us>
> To: "Richard W.M. Jones" <rjones at redhat.com>
> Cc: users at ovirt.org
> Sent: Monday, April 29, 2013 3:55:12 PM
> Subject: Re: [Users] trouble with imported windows VM
>
> I did a conversion with all disks connected on the KVM at once (which,
> the KVM version of the VM works fine, all SQL services start and DBs
> come up fine).
>
> When I import the VM with virt-v2v, the new VM will not boot until I
> remove the D drive.
>
> Rich, copying the disk over manually sounds like a viable plan, but im
> not sure what target directory to put it in.  is there some specific
> place it should go when copying in by hand?
>
> Thanks,
> jonathan
>
> -----Original Message-----
> From: Richard W.M. Jones [mailto:rjones at redhat.com]
> Sent: Wednesday, April 24, 2013 3:58 PM
> To: Jonathan Horne
> Cc: Itamar Heim; Laszlo Hornyak; users at ovirt.org; Allon Mureinik
> Subject: Re: [Users] trouble with imported windows VM
>
>
> On Wed, Apr 24, 2013 at 05:14:50PM +0000, Jonathan Horne wrote:
> > This is my current gotcha.  If I import it with a single disk from
> > KVM (C drive only), its successful.  If I add the 2nd disk to KVM
> > and import it, it will import both disks, but I get the error at the
> > beginning of this thread.  If I detach the 2nd imported disk, it boots again.
> >
> > Now, I made another VM on kvm that contained only my D drive, and
> > imported that.  After the import, I got this:
> >
> > [root at d0lppc021 ~]# virt-v2v -i libvirt -ic
> > qemu+ssh://root@rnd8/system -o rhev -os d0lppc021.skopos.me:/opt/nfs
> > -of qcow2 -oa sparse -n ovirtmgmt ws08-svr-3Donly
> > ws08-svr-03-0_copy.raw: 100%
> > [===================================================================
> > == ====================================================]D 4h09m19s
> > virt-v2v: No root device found in this operating system image.
> >
> >
> > The D drive contains only things like SQL db files and other related data.
> > Am I using virt-v2v incorrectly for this 2nd disk (in either
> > scenario, a single VM with 2 disks, or even on a standalone (and
> > albeit unbootable) VM with just the D drive)?
>
> The bad news is that virt-v2v won't work on a data disk.  It has to be
> presented with either just the operating system disk, or all disks at once.
>
> The good news is that you don't need to convert data disks!  virt-v2v
> knows nothing about them, and would do nothing to them.  Simply copy
> the data disk over to the export domain using 'scp' or 'dd' or whatever.
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones Fedora Windows cross-compiler.
> Compile Windows programs, test, and build Windows installers. Over 100 libraries supported.
> http://fedoraproject.org/wiki/MinGW
>
> ________________________________
> This is a PRIVATE message. If you are not the intended recipient,
> please delete without copying and kindly advise us by e-mail of the
> mistake in delivery. NOTE: Regardless of content, this e-mail shall
> not operate to bind SKOPOS to any order or other contract unless
> pursuant to explicit written agreement or government initiative
> expressly permitting the use of e-mail for such purpose.
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>

________________________________
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.