[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [virt-tools-list] what does virt-v2v check for in a multiboot os?



I ran this from my Fedora 14 desktop:

[root fedora14 ~]# virt-filesystems -a
/nfs/sr-adc01.BOTETOURTVA.US-flat.vmdk --all --long --uuid
Name      Type       VFS  Label Size        Parent   UUID
/dev/sda1 filesystem ntfs -     10733958144 -        E2C82D8CC82D5FD1
/dev/sda1 partition  -    -     10733958144 /dev/sda -
/dev/sda  device     -    -     32226647040 -        -

Going back to the very original problem, I wasn't able to use virt-v2v
until I deleted my second partition from my vmdk file (which was
empty).

I had a single vmdk file, with the OS on one partition, and useless
data on the second.  I couldn't get virt-v2v to do anything with the
vm because it thought (I assume) that the second partition was another
OS, so I deleted that partition, and then virt-v2v worked fine.

-Kenny

On Wed, Jan 26, 2011 at 10:54 PM, Kenneth Armstrong <digimars gmail com> wrote:
> This is with the Recovery Console installed:
>
> [root rhel6 testing]# virt-inspector --perl sr-adc01.BOTETOURTVA.US-flat.vmdk
> open /dev/kvm: No such file or directory
> Could not initialize KVM, will disable KVM support
> $VAR1 = '/dev/sda1';
> $VAR2 = {
>          'arch' => 'i386',
>          'apps' => [],
>          'os' => 'windows',
>          'major_version' => '5',
>          'root_device' => '/dev/sda1',
>          'filesystems' => {
>                             '/dev/sda1' => {
>                                              'arch' => 'i386',
>
> 'windows_registered_owner' => 'MIS',
>                                              'content' => 'windows-root',
>                                              'is_root' => 1,
>                                              'windows_current_type'
> => 'Multiprocessor Free',
>                                              'windows_system_hive' =>
> '/WINDOWS/system32/config/system',
>                                              'os_minor_version' => '2',
>                                              'fsos' => 'windows',
>                                              'systemroot' => '/WINDOWS',
>                                              'windows_software_hive'
> => '/WINDOWS/system32/config/software',
>                                              'windows_software_type'
> => 'SYSTEM',
>
> 'windows_registered_organization' => 'BOTETOURT MIS',
>                                              'windows_current_build'
> => '1.511.1 () (Obsolete data - do not use)',
>                                              'is_mountable' => 1,
>                                              'os_major_version' => '5',
>                                              'boot_ini' => '/boot.ini',
>                                              'fstype' => 'ntfs',
>                                              'product_name' =>
> 'Microsoft Windows Server 2003'
>                                            }
>                           },
>          'root' => $VAR2->{'filesystems'}{'/dev/sda1'},
>          'minor_version' => '2',
>          'mounts' => {
>                        '/' => '/dev/sda1'
>                      },
>          'product_name' => 'Microsoft Windows Server 2003'
>        };
>
>
> [root rhel6 testing]# virt-inspector sr-adc01.BOTETOURTVA.US-flat.vmdk
> open /dev/kvm: No such file or directory
> Could not initialize KVM, will disable KVM support
> windows i386 5.2 (Microsoft Windows Server 2003) on /dev/sda1:
>  Mountpoints:
>    /dev/sda1                      /
>  Filesystems:
>    /dev/sda1:
>      type: ntfs
>      content: windows-root
>  Applications:
>
>
> [root rhel6 testing]# guestfish --ro -a sr-adc01.BOTETOURTVA.US-flat.vmdk
>
> Welcome to guestfish, the libguestfs filesystem interactive shell for
> editing virtual machine filesystems.
>
> Type: 'help' for help with commands
>      'quit' to quit the shell
>
>><fs> list-partitions
> libguestfs: error: guestfs_list_partitions: call launch before using
> this function
> (in guestfish, don't forget to use the 'run' command)
>><fs> run
> open /dev/kvm: No such file or directory
> Could not initialize KVM, will disable KVM support
>><fs> list-partitions
> /dev/vda1
>><fs> list-devices
> /dev/vda
>><fs> mount-ro /dev/vda1 /
>><fs> ll /
> total 2097425
> drwxrwxrwx  1 root root       8192 Jan 26 18:32 .
> dr-xr-xr-x 20 root root          0 Jan 27 03:42 ..
> -rwxrwxrwx  2 root root       1024 Aug 25  2009 .rnd
> -rwxrwxrwx  1 root root          0 Mar 31  2009 AUTOEXEC.BAT
> -rwxrwxrwx  1 root root        255 Jan 25 20:22 BOOT.BAK
> drwxrwxrwx  1 root root          0 Jan 13 01:01 Backup Exec AOFO Store
> -rwxrwxrwx  1 root root          0 Mar 31  2009 CONFIG.SYS
> drwxrwxrwx  1 root root       4096 Jan 25 20:12 Config.Msi
> drwxrwxrwx  1 root root       4096 Jan 13 16:26 Documents and Settings
> drwxrwxrwx  1 root root    1232896 Jan 24 21:44 I386
> -rwxrwxrwx  1 root root          0 Mar 31  2009 IO.SYS
> -rwxrwxrwx  1 root root          0 Mar 31  2009 MSDOS.SYS
> -rwxrwxrwx  1 root root      47772 Feb 18  2007 NTDETECT.COM
> drwxrwxrwx  1 root root       4096 Jan 13 15:40 Program Files
> drwxrwxrwx  1 root root          0 Jun 29  2010 RECYCLER
> drwxrwxrwx  1 root root          0 Mar 31  2009 System Volume Information
> -rwxrwxrwx  1 root root      22870 Mar 11  2007 TZupdate.reg
> -rwxrwxrwx  2 root root         65 May  5  2010 TrackitAudit.id
> drwxrwxrwx  1 root root     131072 Jan 26 18:31 WINDOWS
> -rwxrwxrwx  1 root root      69751 Jul 20  2009 avremove.log
> -rwxrwxrwx  1 root root        326 Jan 26 18:32 boot.ini
> -rwxrwxrwx  2 root root        297 Jan 24 18:12 boot.old.txt
> drwxrwxrwx  1 root root      40960 Jan 26 18:32 cmdcons
> -rwxrwxrwx  1 root root     300144 Feb 18  2007 cmldr
> -rwxrwxrwx  1 root root      94720 Feb 18  2007 msizap.exe
> -rwxrwxrwx  1 root root      47956 Jun 23  2010 netstat.txt
> -rwxrwxrwx  1 root root      39163 Jun 23  2010 netstat2.txt
> -rwxrwxrwx  1 root root     297072 Feb 18  2007 ntldr
> -rwxrwxrwx  1 root root 2145386496 Jan 26 18:30 pagefile.sys
> drwxrwxrwx  1 root root          0 Mar 31  2009 wmpub
>
>><fs> umount /
>><fs>
>
>
> It doesn't look that much different except for the additions of the
> cmdcons directory and the cmldr file on the root of C:\
>
> -Kenny
>
> On Wed, Jan 26, 2011 at 1:22 PM, Kenneth Armstrong <digimars gmail com> wrote:
>> Yeah, this is without Recovery Console installed:
>>
>> [root rhel6 e95548d0-2ee2-4ffb-b960-6f74b17966f2]# virt-inspector
>> --perl 5b5503fa-954f-42c8-b9a4-05a9a7b6ee9e
>> open /dev/kvm: No such file or directory
>> Could not initialize KVM, will disable KVM support
>> $VAR1 = '/dev/sda1';
>> $VAR2 = {
>>          'arch' => 'i386',
>>          'apps' => [],
>>          'os' => 'windows',
>>          'major_version' => '5',
>>          'root_device' => '/dev/sda1',
>>          'filesystems' => {
>>                             '/dev/sda1' => {
>>                                              'arch' => 'i386',
>>
>> 'windows_registered_owner' => 'MIS',
>>                                              'content' => 'windows-root',
>>                                              'is_root' => 1,
>>                                              'windows_current_type'
>> => 'Multiprocessor Free',
>>                                              'windows_system_hive' =>
>> '/WINDOWS/system32/config/system',
>>                                              'os_minor_version' => '2',
>>                                              'fsos' => 'windows',
>>                                              'systemroot' => '/WINDOWS',
>>                                              'windows_software_hive'
>> => '/WINDOWS/system32/config/software',
>>                                              'windows_software_type'
>> => 'SYSTEM',
>>
>> 'windows_registered_organization' => 'BOTETOURT MIS',
>>                                              'windows_current_build'
>> => '1.511.1 () (Obsolete data - do not use)',
>>                                              'is_mountable' => 1,
>>                                              'os_major_version' => '5',
>>                                              'boot_ini' => '/boot.ini',
>>                                              'fstype' => 'ntfs',
>>                                              'product_name' =>
>> 'Microsoft Windows Server 2003'
>>                                            }
>>                           },
>>          'root' => $VAR2->{'filesystems'}{'/dev/sda1'},
>>          'minor_version' => '2',
>>          'mounts' => {
>>                        '/' => '/dev/sda1'
>>                      },
>>          'product_name' => 'Microsoft Windows Server 2003'
>>        };
>>
>>
>> I'll re-install it, and try again.
>>
>> -Kenny
>>
>> On Wed, Jan 26, 2011 at 1:18 PM, Richard W.M. Jones <rjones redhat com> wrote:
>>> On Wed, Jan 26, 2011 at 01:07:37PM -0500, Kenneth Armstrong wrote:
>>>> [root rhel6 e95548d0-2ee2-4ffb-b960-6f74b17966f2]# virt-inspector
>>>> 5b5503fa-954f-42c8-b9a4-05a9a7b6ee9e
>>>
>>> I forgot to ask to you add the --perl flag, ie:
>>>
>>>  virt-inspector --perl 5b5503fa-954f-42c8-b9a4-05a9a7b6ee9e
>>>
>>> However ...
>>>
>>>> windows i386 5.2 (Microsoft Windows Server 2003) on /dev/sda1:
>>>>   Mountpoints:
>>>>     /dev/sda1                      /
>>>>   Filesystems:
>>>>     /dev/sda1:
>>>>       type: ntfs
>>>>       content: windows-root
>>>>   Applications:
>>>
>>> This presumably is the Windows guest after removing the Recovery
>>> Console?  I would expect to have seen two operating systems being
>>> displayed here if the Recovery Console was still installed.  It's
>>> really the case where the Recovery Console is installed (and virt-v2v
>>> fails) which is the interesting one.
>>>
>>>                - - - -
>>>
>>> By the way you might want to try out:
>>>
>>>  http://people.redhat.com/~rjones/rhel6.1-libguestfs-preview/
>>>
>>> Although these are not supported and might break RHEL 6.0 virt-v2v
>>> (they shouldn't -- it's just I haven't tested this combination
>>> together).
>>>
>>> Rich.
>>>
>>> --
>>> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
>>> virt-df lists disk usage of guests without needing to install any
>>> software inside the virtual machine.  Supports Linux and Windows.
>>> http://et.redhat.com/~rjones/virt-df/
>>>
>>
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]