Vmware converter скачать


Подробная инструкция по установке VMware vCenter Converter Standalone

Статья содержит подробную инструкцию по установке и использованию VMware vCenter Converter Standalone

    Для компаний, внедряющих виртуализацию актуален вопрос по переводу своих серверов в виртуальную среду. Официальный метод — это использование VMware converter (можете скачать здесь).

Функционал VMware vCenter Converter Standalone:

  • Конвертация операционной системы установленной на физическом сервере в виртуальную машину для ESXi
  • Конвертация виртуальной машины из ESXi в виртуальную машину для ESXi последней версии
  • Конвертация файла бэкапа Data Protection в виртуальную машину для ESXi
  • Конвертация виртуальных машин из Hyper-V в виртуальную машину для ESXi
  • Конвертация резервной копии Acronis (.tib) в виртуальную машину для ESXi
  • Конвертация из резервной копии Sumantec (.sv2i) в виртуальную машину для ESXi
  • и другие форматы в виртуальную машину для ESXi

Конвертация обычным методом.

Устанавливаем в сеть VMware converter, надежнее всего на ту машину, которую нужно конвертировать:

Соглашаемся с лицензионной политикой:

Папка установки VMware converter:

Два вида работы программы. Локальная установка в операционную систему, которую нужно конвертировать, либо клиент-серверный вариант, когда в ОС удаленно ставится агент VMware converter, а серверная часть находится, например, на компьютере администратора:

Интерфейс выглядит так, здесь же перечислен весь функционал. Нажимаем Convert machine:

Необходимо указать источник (то что нужно конвертировать). Если хотим сконвертировать текущую машину, выбираем Powered-on machine и This local machine. Можно конвертировать удаленную включенную машину (A remote machine). Для этого нужно указать ее IP адрес, логин, пароль и операционную систему (при конвертировании linux машины к ней необходимо подключаться пользователем с root правами, а к Windows машине с правами администратора):

Локальную машину программа определяет сама и довольно точно:

Теперь выбираем, где нужно создать новую виртуальную машину:

Указываем адрес ESXi или vCenter server:

Конвертер подключается к VMware ESXi:

Указываем название виртуальной машины, которая будет создана на VMware ESXi:

Указываем на какой LUN будут помещены файлы виртуальной машины. И версия оборудования (8 версия для ESXi 5+):

На данном шаге мастера можно указать более точно настройки конвертации. Например, выбрать диски которые нужно перенести, виртуальную сеть и другое

Так как конвертация происходит из работающей операционной системы и за время переноса данные могут измениться, можно настроить пост синхронизацию, которая произойдет после основной конвертации

После конвертации можно, включить получившуюся виртуальную машину, установить в нее VMware Tools и другое:

Сама конвертация:

Конвертация через Acronis Boot CD

    Создавать новые виртуальные машины из работающих операционных систем мне кажется не самой лучшей идеей, можно несколько часов ждать окончания переноса и на 99% увидеть FAILED. Поэтому более надежный способ — это сначала сделать резервную копию через загрузочный диск Acronis, а затем из него уже сконвертировать виртуальную машину. Образ Acronis Boot CD можно скачать тут.

     Порядок переноса следующий:

  • Останавливаете сервер, который нужно перенести.
  • Загружаете этот сервер с Acronis Boot CD
  • Делаете актуальную резервную копию, получаете файл .tib
  • Запускаете VMware Converter и скармливаете ему файл .tib
  • В остальном все совпадает с переносом обычным методом

    Можно обойтись вообще без конвертера, а создать в ручном режиме новую виртуальную машину, загрузиться с Acronis Boot CD и восстановить информацию из резервной копии, но вы рискуете увидеть BSOD, т.к. VMware Converter умеет подсовывать нужные драйверы в виртуальную машину, а Acronis нет (может только при использовании функции Universal Resore).

xn--48-6kc0bzbi.xn--p1ai

Как установить VMware vCenter Converter Standalone 5.x.x

Как установить VMware vCenter Converter Standalone 5.x.x

Как установить VMware vCenter Converter Standalone 5.x.x

Больше двух лет назад (ого, давно же!)  вышел VMware vCenter Converter Standalone 5.0, который был заточен под миграцию физических серверов еще на платформу VMware vSphere 5.0.

Новых возможностей за два года у конвертера существенно прибавилось, хотя вряд ли все два года над ним велась напряженная работа. Итак, что нового в vCenter Converter Standalone 5.5:

  • Поддержка VMware vSphere 5.5.
  • Поддержка virtual machine hardware version 10, а значит и таких фич, как диски по 62 ТБ, виртуальные SATA-контроллеры и прочее.
  • Поддержка виртуальных машин RedHat KVM в качестве источника для миграции на платформу vSphere.
  • Новая опция по выбору типа сетевого адаптера для целевой машины на хосте ESXi.
  • Поддержка новых гостевых ОС (см. ниже).
  • Параллельная миграция нескольких дисков одной машины, что существенно ускоряет процесс миграции.
  • Поддержка целевых хранилищ VMware Virtual SAN.

Скачать можно тут.

Запускам exe установщик.

Как установить VMware vCenter Converter Standalone 5.x.x-01

Next.

Как установить VMware vCenter Converter Standalone 5.x.x-02

Next.

Как установить VMware vCenter Converter Standalone 5.x.x-03

Соглашаемся с лицензией

Как установить VMware vCenter Converter Standalone 5.x.x-04

Можем при желании изменить каталог установки, Next

Как установить VMware vCenter Converter Standalone 5.x.x-05

local installation

Как установить VMware vCenter Converter Standalone 5.x.x-06

Установить

Как установить VMware vCenter Converter Standalone 5.x.x-07

Как установить VMware vCenter Converter Standalone 5.x.x-08

Как установить VMware vCenter Converter Standalone 5.x.x-09

Как конвертировать физические сервера описано тут

Ноя 11, 2014 23:23 Иван Семин

pyatilistnik.org

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x

Как поставить VMware vCenter Converter Standalone 5.5 описано подробно тут.

Запускаем VMware vCenter Converter Standalone 5.5

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-01

Выбираем Convert machine

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-02

  • Powered-on machine, работающий компьютер или сервер. Это основной метод работы VMware converter,  «без прерывания работы». Сервер может быть физическим или виртуальным. Находиться в локальной сети или быть локальным (та машина, на которую установлен конвертер). Операционная система Windows или Linux, не Unix. Для Linux сильно ограниченный список операционных систем.
  • VMware Infrastructure virtual machine, в случае, если нужно виртуальную машину со старой платформы(Virtual Center 2.5, ESX(i) 2-4.1),  перевести на новую, пятую. Основное изменение в 5-ой версии VMware vSphere это новая версия виртуального оборудования за номером 8, вместе с ним изменились и VMware tools.
  • VMware Workstation or other Virtual Machine. Workstation очень популярен среди администраторов и часто виртуальная машина из тестовой превращается во временную рабочую. Конвертер перенесет ее на ESXi, в среду vSphere без проблем. Выбираем так же этот пункт, если виртуальные машины работают у вас на VMware Fusion, VMware Player, VMware server 2.x
  • Backup image or third-party virtual machine. Восстановление из имеющегося бэкапа или виртуальной машины другого производителя. Восстановление из резервной копии – это очень полезная функция и я ниже расскажу почему.
  • Hyper-V server. Для перехода с платформы Microsoft на VMware. Отличается от  third-party virtual machine тем, что у вас должен иметься работающий сервер Hyper-V и подключаться конвертер будет к нему. Виртуальные машины должны быть выключены.

Для работы VMware Converter с Windows like операционной системой по схеме  «Powered-on machine» нужны учетные данные администратора системы, чтобы конвертер мог подключиться, установить агента и начать миграцию. Для Linux систем нужно ввести пароль root и иметь возможность подключаться удаленно по SSH. Возможно, понадобиться поправить конфигурационный файл sshd и разрешить root вход. Еще для входа root должен быть в группе wheel.

VMware Converter при корректном подключении определяет, какую операционную систему ему предстоит мигрировать. Сколько и какие у нее диски и разделы, сколько сетевых интерфейсов, оперативной памяти, процессоров. Все эти данные будут использованы для создания новой виртуальной машины на ESXi хосте.

Я вбиваю адрес vCenter и учетные данные.

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-03

Игнорирую предупреждение на сертификат

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-04

Выбираем папку проекта для мигрируемой машины

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-05

Следующий шаг. Указываем хост ESXi на котором будет запущена виртуальная машина. Хранилище, куда будут записаны файлы ВМ и версию виртуального оборудования (10-ая это последняя). Подозреваю, что если бы я указал в качестве Destination system vCenter server, то выбор был бы больше чем из одного варианта. Отобразились бы все доступные хосты и data store

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-06

На следующей странице можно задать какие диски нужно конвертировать какие нет, сколько нужно сетевых интерфейсов и многое другое.

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-07

Смотрим сводку

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-08

Finish. Теперь если посмотреть vCenter там появился таск создания виртуальной машины.

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-09

В самом конверторе будет отображаться время выполнения задания.

Как виртуализовать физический сервер с помощью VMware vCenter Converter Standalone 5.x.x-10

Так же после выполнения задания вы можете столкнуться с ошибкой An error occurred during reconfiguration, и при включении виртуальной машины на гипервизоре esxi вы получите синий экран, решение этой проблемы по ссылке слева.

Материал сайта pyatilistnik.org

pyatilistnik.org

Инструкция по миграции физической ИТ-инфраструктуры в виртуальную среду

Миграция физической инфраструктуры в виртуальную среду процедура уникальная по своей сути, двух одинаковых миграций не бывает, потому что не бывает двух одинаковых установок операционных систем на сервер. Есть два пути, по которым можно пойти в случае переезда на виртуальную платформу.

  • Первый, это миграция всего «как есть», с помощью VMware Converter и других подручных средств, о которых пойдет речь далее.
  • Второй способ, мне кажется более профессиональным и рейтинговым, если так можно выразиться, с точки зрения системного администрирования. Я говорю о ручном переносе (переустановке) сервисов, служб, ролей, демонов в чистую виртуальную машину. Если администратор системы может пойти по второму пути, то это доказывает, что он профи в своей области и ему можно смело повышать зарплату, т.к. он знает свою инфраструктуру и может делать с ней все что угодно.

VMware vCenter Converter Standalone 

Сразу нужно сказать, что для его работы vCenter server не нужен и присутствие его в названии скорее дань истории.  На момент написания статьи актуальная версия конвертера 5.0, деления на Windows и Linux версию в ней нет, а есть один установочный файл VMware-converter-all-5.0.0-470252.exe. Его бесплатно, но после регистрации, можно скачать на официальном сайте или с rutracker, это кому как больше нравится, результат не изменится. Установка производится на Windows машину (физическую или виртуальную) с доступом в сеть, в которой находятся готовые для миграции серверы. Саму процедуру установки я описывать не буду, каждый справится и сможет нажать несколько раз «Далее» до полной победы. Установили, запускаем.

 

Сразу приступаем к делу, Convert machine. Мастер просит выбрать, что именно мы будем конвертировать.

  • Powered-on machine, работающий компьютер или сервер. Это основной метод работы VMware converter,  «без прерывания работы». Сервер может быть физическим или виртуальным. Находиться в локальной сети или быть локальным (та машина, на которую установлен конвертер). Операционная система Windows или Linux, не Unix. Для Linux сильно ограниченный список операционных систем.
  • VMware Infrastructure virtual machine, в случае, если нужно виртуальную машину со старой платформы(Virtual Center 2.5, ESX(i) 2-4.1),  перевести на новую, пятую. Основное изменение в 5-ой версии VMware vSphere это новая версия виртуального оборудования за номером 8, вместе с ним изменились и VMware tools.
  • VMware Workstation or other Virtual Machine. Workstation очень популярен среди администраторов и часто виртуальная машина из тестовой превращается во временную рабочую. Конвертер перенесет ее на ESXi, в среду vSphere без проблем. Выбираем так же этот пункт, если виртуальные машины работают у вас на VMware Fusion, VMware Player, VMware server 2.x
  • Backup image or third-party virtual machine. Восстановление из имеющегося бэкапа или виртуальной машины другого производителя. Восстановление из резервной копии – это очень полезная функция и я ниже расскажу почему.
  • Hyper-V server. Для перехода с платформы Microsoft на VMware. Отличается от  third-party virtual machine тем, что у вас должен иметься работающий сервер Hyper-V и подключаться конвертер будет к нему. Виртуальные машины должны быть выключены. 

Что касается поддерживаемых для конвертации операционных систем, список, прямо скажем, не велик, его можно найти в документации к VMware converter на страницах 20-21. Там же список поддерживаемых программ для бэкапов, больше всего мне нравится Acronis, и я его все время использую на практике. И вот почему.

С конвертацией Windows обычно проблем не возникает, система легко опознается конвертером и переносится. Остается только удалить старые устройства в диспетчере оборудования и настроить новое, виртуальное. У Acronis есть программа, которая идет в дополнение к их инструменту резервного копирования Acronis Backup and Recovery 11 (новое название True Image, и новый интерфейс). Acronis Universal Restore помогает решить проблему с драйверами на этапе восстановления из резервной копии, вы не найдете лишних устройств при запуске, а операционная система будет искать все заново.

Linux, вот где проблемы подстерегают. Если даже вы решили мигрировать ОС из списка поддерживаемых VMware converter не факт, что у вас это получится. Бесплатный Linux дает разгуляться в волю фантазии системного администратора. Тут тебе и софтовые RAID и необычные разделы, самописные конфиги, старые не поддерживаемые ядра, необычное оборудование. И скорее всего вы увидите, что VMware converter не может понять, что за систему вы ему подсунули и поэтому мигрировать он ее не будет. И тогда возникает вопрос, а что делать?

1. Для работы VMware Converter с Windows like операционной системой по схеме  «Powered-on machine» нужны учетные данные администратора системы, чтобы конвертер мог подключиться, установить агента и начать миграцию. Для Linux систем нужно ввести пароль root и иметь возможность подключаться удаленно по SSH. Возможно, понадобиться поправить конфигурационный файл sshd и разрешить root вход. Еще для входа root должен быть в группе wheel.

VMware Converter при корректном подключении определяет, какую операционную систему ему предстоит мигрировать. Сколько и какие у нее диски и разделы, сколько сетевых интерфейсов, оперативной памяти, процессоров. Все эти данные будут использованы для создания новой виртуальной машины на ESXi хосте.

2. Затем нужно указать на какой ESXi будет происходить миграция(его адрес или hostname) и пароль для root.

3. Мастер установки попросит задать имя новой виртуальной машины и покажет, какие еще ВМ уже находятся на хосте.

4. Следующий шаг. Указываем хост ESXi на котором будет запущена виртуальная машина. Хранилище, куда будут записаны файлы ВМ и версию виртуального оборудования (8-ая это последняя). Подозреваю, что если бы я указал в качестве Destination system vCenter server, то выбор был бы больше чем из одного варианта. Отобразились бы все доступные хосты и data store. 5. Страница настроек. Сразу вижу ошибку. Все из-за того, что по умолчанию тип диска выставляется, как Thick и если свободного места на datastore не достаточно, то видим критическую ошибку. В моем случае решается сменой типа диска на «тонкий».  Можно задать, какие действия нужно выполнить до и после конвертации компьютера. Я советую отказаться от экспериментов с синхронизацией после миграции, лучше отключить на время базы данных и другие динамические службы. Так вы точно не потеряете свои данные.

После выставления всех настроек можете запускать миграцию и на 90% она окажется успешной.

ФОРМА ЗАКАЗА решений по виртуализации от vmware

Для того, чтобы сделать решений по виртуализации, заполните форму ниже. После отправки формы мы свяжемся с вами в самое ближайшее время!

There is no form with this name or may be the form is unpublished, Please check the form and the url and the form management.

 

   

www.vmstart.ru

VMware Converter: Синхронизация изменений при P2V/ V2V

VMware vCenter Converter Standalone – отличная бесплатная утилита для выполнения конвертации физической системы в виртуальную (P2V) или из одной системы виртуализации в другую (V2V). Начиная с VMware Converter 5.0 система поддерживает возможность синхронизации изменений между исходной системой и виртуальной машиной-копией, расположенной на ESXi хосте. Эта функция позволяет в несколько этапов с минимальным простоем виртуализировать физический сервер с большим объёмом данных на физических дисках. Кроме того, VMware Converter вместе с бесплатным гипервизором VMware vSphere Hyperviso (на базе ESXi), можно превратить в простейшую систему для организации аварийного восстановления (disaster recovery) критических компонентов инфраструктуры, периодически синхронизируя изменения критичных систем с их виртуальными копиями.

При конвертировании включенной Windows системы, VMware Converter копирует данные из машины-источника в целевую ВМ, в то время пока сама машина источник работает и данные на ней меняются. Это первоначальный этап копирования. Во второй раз копируются только изменения, которые были сделаны с момента создания первоначальной копии системы. Этот процесс и называется синхронизацией. Функция синхронизации позволяет уменьшить простой приложения во время P2V / V2V конвертации, так как конечное приложение нужно отключать только на время передачи изменений. При использовании синхронизации можно добиться сокращения времени простоя приложения с нескольких часов до 1-2 часов.

Совет. Синхронизация изменения в VMware Converter  поддерживается только пи использовании vCenter или ESXi серверов версии 4.0 и выше.

В этой статье мы покажем, как настраивается и работает синхронизация изменений между исходным сервером (файловый сервер с 700 Гб данных на внутренних дисках) и его виртуальной копией с помощью VMware vCenter Converter Standalone 6.0.

  1. Нужно скачать и установить VMware Converter Standalone (предпочтительно установить его на отдельный сервер).
  2. Создадим новое задание конвертации: File-> New-> Convert machine.
  3. Выберем, что нужно сконвертировать включенную систему (Powered-on machine), указать ее имя/адрес, тип ОС и учетную запись и пароль пользователя с правами администратора.
  4. VMware Converter подключается к указанному серверу и установит на нем службу VMware vCenter Converter Standalone Agent (vmware-converter-agent)
  5. Затем будет предложено указать имя сервера ESXi (или сервера vCenter) , на котором будет создаваться виртуальная машина, и учетные данные для доступа к нему
  6. Нам будет предложено выбрать имя создаваемой ВМ, ее местоположение, имя фермы, хоста, дисковое хранилище и версию виртуальной машины (virtual hardware)
  7. Затем нужно выбрать диски целевой системы, которые нужно скопировать, настройки памяти и CPU и т.д. Нас больше всего интересует настройки в секции Advanced.
  8. Мы планируем сконвертировать систему в ВМ в два этапа: первоначальный, когда выполняется инициирующая конвертация и финальный, когда выполняется синхронизация изменений, произошедших с момента первоначального копирования данных.
  9. Ставим галку Synchronize change. Выбираем когда выполнить следующую синхронизацию. Обязательно(!!) снимает галку Perform final synchronization.
  10. На вкладке Post-Conversion выберите действия, которые нужно будет выполнить после финальной синхронизации. Мы хотим автоматически включить созданную ВМ (Power on destination machine), отключить исходный сервер (Power off source machine), установить VMTools и т.д.
  11. Осталось запустить первоначальную фазу конвертации P2V и дождаться ее окончания.

    Примечание. В нашем случае, для физического файлового сервера с 700 Гб данных конвертация заняла порядка 15 часов.

  12. После окончания первоначальной конвертации мы можем вручную выполнить повторную синхронизацию. Для этого выбираем задание в консоли VMware Converter и в контекстном меню выберем Synchronize.

    Примечание. VMware Converter устанавливает на исходной системе специальный “bitmap driver” (служба bmdrvr), который отслеживает изменения, произошедшие в системе с момента последней синхронизации.

  13. В открывшемся окне мастера укажем, что синхронизацию нужно запустить немедленно, а по окончании ее выполнить финальную синхронизацию. Чтобы пользователи не могли править файлы на сервере в момент финальной синхронизации, можно временно остановить файловый сервис. 
  14. Финальная синхронизация заняла около часа, в течении которых изменения на исходной машине были реплицированы на ВМ. После чего старый сервер автоматически отключился, а новая ВМ – включилась.
  15. Осталось выполнить окончательную донастройку ВМ (удалить скрытые сетевые карты, старые драйвера устройств, назначить ip адреса новым сетевым интрефейсам и т.д.) – и виртуальная машина готова к работе.

В процессе выполнения синхронизации изменений сервер vSphere создаст на целевой машине отдельные снапшоты (снимки), позволяющие в случае чего откатиться к любому этапу синхронизации (логика работы VMware Converter будет при этом нарушена).

winitpro.ru

VMware vCenter Converter Standalone 4.0.1 Release Notes

VMware vCenter Converter Standalone 4.0.1 | 5/21/2009 | Build 161434

Last Document Update: 9/17/2010

Check periodically for additions and updates to these release notes.

These release notes cover the following topics:

Introduction to VMware vCenter Converter Standalone 4.0.1

VMware vCenter Converter Standalone provides an easy-to-use solution to automate the process of creating VMware virtual machines from physical machines (running Windows and Linux), other virtual machine formats, and third-party image formats. Through an intuitive wizard-driven interface and a centralized management console, Converter Standalone can quickly and reliably convert multiple local and remote physical machines without any disruptions or downtime.

Benefits

  • Convert physical machines running Windows and Linux operating systems to VMware virtual machines quickly, reliably, and without any disruption or downtime.
  • Convert third-party formats such as Parallels Desktop, Symantec Backup Exec System Recovery, Norton Ghost, Acronis, StorageCraft, and Microsoft Virtual Server or Virtual PC to VMware virtual machines.
  • Enable centralized management of remote conversions of multiple physical servers or virtual machines simultaneously.
  • Populate new virtual machine environments from a large directory of virtual machine appliances.
  • Ensure conversion reliability through quiesced snapshots of the guest operating system on the source machine before data migration.
  • Enable non-disruptive conversions through hot cloning, with no source server downtime or reboot.

What's New

The VMware vCenter Converter Standalone 4.0.1 release is an update to Converter Standalone 4.0, and includes the following new features:

  • Support for vSphere 4.0 as source and destination targets:
    • Support for configuring target disks as thin provisioned disks
    • Support creation of IDE disks on vSphere 4.0
    • Support for backup products to restore vSphere 4.0 virtual machines backed up using VCB
    • Support for creation of virtual hardware version 7.0 virtual machines on vSphere 4.0. targets as well as migration of hardware version 7.0 virtual machines from Workstation and Server platforms to vSphere 4.0
  • Support for importing OVF 1.0 single virtual machine images.
  • Support for customization of Windows Server 2008 guests.

Top of Page

Installation Notes

Users with limited rights cannot install Converter Standalone 4.0.1 on Windows

Top of Page

Platforms

You can install all components of VMware vCenter Converter Standalone 4.0.1 (Converter Standalone client, Converter Standalone server, and Converter Standalone agent) on the following platforms:

  • Windows 2000 SP4
  • Windows XP Professional (32 bit and 64 bit)
  • Windows Server 2003 (32 bit and 64 bit)
  • Windows Vista (32 and 64 bit)
  • Windows Server 2008 (32 bit and 64 bit)*
  • Red Hat Enterprise Linux 4.0 (32 bit and 64 bit)
  • Red Hat Enterprise Linux 5.0 (32 bit and 64 bit)
  • SUSE Linux Enterprise Server 10 (32 bit and 64 bit)
  • Ubuntu 6.x
  • Ubuntu 7.x (32 bit and 64 bit)
  • Ubuntu 8.x (32 bit and 64 bit)

* vCenter Converter Standalone 4.0.1 supports only Windows Server 2008 and does not support Windows Server 2008 R2.

You can install Converter Standalone 4.0.1 server and agent (no GUI client supported) on the following platforms:
  • Red Hat Enterprise Linux 3.0
  • SUSE Linux Enterprise Server 8
  • SUSE Linux Enterprise Server 9 (32 bit)
  • Ubuntu 5.x

Top of Page

Interoperability

Converter Standalone 4.0.1 supports the following sources and destinations:

Source Destination
Local or remote physical machine running an operating system noted in Supported Guest Operating Systems

Workstation 6.5.x, Workstation 6.0.x, Workstation 5.x, and Workstation 4.x 1VMware Fusion 1.x, 2.x

vSphere 4.0 ESX Server 3.x ESX Server 3i version 3.5 Installable and ESX Server 3i version 3.5 Embedded ESX Server 2.5.x (if VirtualCenter 2.x manages ESX Server) VMware Server 1.x, 2.x VirtualCenter 2.x

Microsoft Virtual PC 2004 (for Windows only), Microsoft Virtual PC 2007 (for windows only) Microsoft Virtual Server 2005, and 2005 R2 VMware Consolidated Backup Acronis True Image Echo 9.1, 9.5, and Acronis True Image 10.0, 11.0 (Home product) 1, 2Symantec Backup Exec System Recovery (formerly LiveState Recovery) 6.5, 7.0, 8.0 and 8.5, LiveState Recovery 3.0 and 6.0 2Norton Ghost version 10.0, 11.0, 12.0, 13.0, and 14.0 (.sv2i files) 2Parallels Desktop for Microsoft Windows and Mac OS x 2.5, 3.0, and 4.0 3StorageCraft ShadowProtect 2.0, 2.5, 3.0, 3.1, and 3.2 2, 4

OVF spec version 0.9 and 1.0 5Local OVF or OVA file 5URL to and OVF or OVA file 5

VMware Workstation 6.5.x, 6.0.x, and 5.x 4VMware Player 1.x, 2.0.x, and 2.5.x VMware Server 1.x and 2.x VMware Fusion 1.x and 2.x ESX Server 3.x and 4.0 ESXi 3.5 and 4.0 Installable and ESXi 3.5 and 4.0 Embedded vCenter Server 2.x and 4.0

OVF and OVA virtual appliances, OVF spec version 1.0 5

1 Only Workstation 5.5 and 6.x can power on linked imports of .sv2i images. Workstation 6 is required to power on linked clones of Acronis True Image and StorageCraft ShadowProtect images. 2 Supported only in Converter Standalone server and agent for Windows. 3 Parallels Virtuozzo Containers are not supported in Converter Standalone. 4 For conditions and limitations about importing Backup Exec System Recovery, ShadowProtect, and Consolidated Backup images, see chapter 2, "System Requirements," of the VMware vCenter Converter Standalone User's Guide. 5 OVF supports import and creation of .vmdk images only.

Windows virtual machines running on Hyper-V Server, Citrix XenServer 4 Enterprise Edition, and Virtual Iron version 4.2 can be imported as live sources (using local or remote hot cloning) with Converter Standalone 4.0.1.

Prior releases of Converter Standalone (versions 3.x and 4.0.0) might not be compatible with VMware vSphere 4.0.

Top of Page

Supported Guest Operating Systems

Converter Standalone 4.0.1 supports the following guest operating systems:

  • Windows NT SP6 and later
  • Windows 2000 SP4
  • Windows XP Professional (32 bit and 64 bit)
  • Windows Server 2003 (32 bit and 64 bit)
  • Windows Vista (32 bit and 64 bit)
  • Windows Server 2008 (32 bit and 64 bit)*
  • Red Hat Enterprise Linux 2.1 (32 bit)
  • Red Hat Enterprise Linux 3.0 (32 bit and 64 bit)
  • Red Hat Enterprise Linux 4.0 (32 bit and 64 bit)
  • Red Hat Enterprise Linux 5.0 (32 bit and 64 bit)
  • Red Hat Linux Advanced Server 2.1 (32 bit)
  • SUSE Linux Enterprise Server 8.0
  • SUSE Linux Enterprise Server 9.0 (32 bit and 64 bit)
  • SUSE Linux Enterprise Server 10.0 (32 bit and 64 bit)
  • Ubuntu 5.x
  • Ubuntu 6.x
  • Ubuntu 7.x (32 bit and 64 bit)
  • Ubuntu 8.x (32 bit and 64 bit)

* vCenter Converter Standalone 4.0.1 supports only Windows Server 2008 and does not support Windows Server 2008 R2.

CAUTION: During cloning of powered-on Linux machines, Converter Standalone 4.0.1 preserves the following source file systems on the target: ext2, ext3, reiserfs, and vfat. All other source file systems are converted into ext3 file systems on the target virtual machine.

Top of Page

Experimental Support

The support for the following features is experimental in Converter Standalone 4.0.1:

  • Conversion of virtual machine sources and third-party images that run Windows by using Converter Standalone server for Linux

Top of Page

Prior Releases of Converter Standalone

Features from prior releases of Converter Standalone are described in the release notes for each release. To view release notes for prior releases of Converter Standalone, click one of the following links:

Top of Page

Known Issues

The Converter Standalone 4.0.1 release contains the following known issues:

Top of Page

Installation

Users with limited rights cannot install Converter Standalone 4.0.1 on Windows If you are logged in to Windows as a non-administrator user, the following error message is displayed while the InstallShield is extracting files for Converter Standalone installation: Unable to save file: C:\WINDOWS\Installer\ The system cannot find the path specified. The error is displayed because limited users do not have the required write permissions. Workaround: Select the %TEMP% directory to extract the installation files:

  1. Click OK in the error message. A Save As dialog box appears.
  2. Browse to the Temp folder of the current user (for example, C:\Documents and Settings\"username"\Local Settings\Temp) and click OK.
NOTE: You still need to log in as an administrator to install Converter Standalone.

Connecting to Converter Standalone Server fails after successful installation on a non-English Windows system Converter Standalone stores configuration and data files under default application data directory in Windows. On Windows XP and Windows Server 2003, this is typically at: C:\Documents and Settings\All Users\Application Data. On Windows Vista and Windows Server 2008, this is C:\ProgramData\. If the equivalent directory on your non-English Windows system contains non-ASCII characters, Converter Standalone does not load properly. If Converter Standalone is installed to a directory whose name contains non-ASCII characters, Converter Standalone fails to start.

You must restart 64-bit Windows Server 2008 and Vista machines before re-installing Converter Standalone 4.0.1 If you uninstall Converter Standalone from a Windows Server 2008 or Vista 64-bit machine and do not restart it, a subsequent Converter Standalone installation might fail with the following error message: Error 29142 unable to start vstor 2 mntapi 1.0 driver. Workaround: Restart the Windows Server 2008 or Vista machine and try installing Converter Standalone again.

No warning message is displayed when installing Converter 3.0.3 on top of Converter Standalone 4.0.1 If you start the Converter 3.0.3 installer on a system that already has Converter Standalone 4.0.1 installed, no warning message is displayed to notify you that Converter Standalone 4.0.1 will be uninstalled.

User Account Control (UAC) prevents uninstalling Converter Standalone 4.0.1 from Windows Vista or later You cannot uninstall Converter Standalone 4.0.1 from Windows > Control Panel > Add or Remove programs if UAC is enabled. Workaround: Uninstall Converter Standalone using its installer:

  1. Run the VMware-converter-4.0.1-xxxxxxx.exe.
  2. On the Program maintenance page, select Remove.
  3. Click Next followed by Remove to complete uninstalling Converter Standalone.

Converter Standalone installer removes Workstation 6.5.x remote agents without notification When you use Workstation 6.5.x to hot-clone a Windows source machine, Workstation deploys a remote Workstation agent on the source. If you choose to leave the remote agent on that source and then install Converter Standalone 4.0.1 on the same machine, the Converter Standalone installer uninstalls that agent without any warning messages.

Deploying Converter Standalone agent on the remote source machine fails If Converter Standalone is already installed on a remote source machine, but remote access was not enabled during Converter Standalone installation, you cannot perform remote hot cloning of this source as Converter Standalone agent cannot be deployed. Workarounds:

  • Run Converter Standalone installer on the remote source machine and install Remote Access by using the Modify option.
  • Log in to the remote source machine, run Converter Standalone, and perform a local hot cloning task.

Converter Standalone 4.0.1 fails to install Converter Standalone remote agent during remote hot cloning During hot cloning of a remote source machine that has VMware Converter 3.x agent installed, Converter Standalone 4.0.1 fails to install its agent. The following error appears in the log file: vm.fault.AgentInstallFailed. Workaround: Remove the Converter 3.x agent manually from the remote machine and try remote hot cloning again. To remove VMware Converter 3.x agent manually, use Add or Remove Programs.

Remote agent installation is unsuccessful when you specify a computer or DNS name with non-ASCII characters in the Conversion wizard If you use non-ASCII characters to populate the computer or DNS name field when selecting a source in the Conversion wizard, the installation of Converter Standalone agent fails. Workaround: Use the IP address instead of the non-ASCII name.

Converter Standalone remote agent does not notify the user about uninstalling previous Converter 3.0.x installation on the same machine during remote hot cloning process If Converter Standalone 4.0.1 is converting a remote machine source that already has Converter 3.0.x installed on it, Converter Standalone 4.0.1 uninstalls the old installation without notifying or warning the user.

When installing Converter Standalone server, the converter-client.xml file is automatically updated This results in changing the default communication port of any Converter Standalone client previously installed on the system to match the value specified for Converter Standalone server installation. Please keep this in mind when using Converter Standalone client to connect to a remote Converter Standalone server as the communication port might differ. Workaround: You can specify the communication port explicitly in the connection dialog box by using the hostname:port convention.

Subsequent P2V conversions of remote source machines that run 64-bit Windows Server 2008 or Vista might fail after a successful conversion If you convert successfully a remote source machine that runs 64-bit Windows Server 2008 or Vista operating system and then try converting it again, the conversion fails with the following error message Converter Standalone Agent installation failed on x.x.x.x Error code: 1603, where x.x.x.x is the IP address of the source machine. This error message might occur if automatic uninstall of remote Converter Standalone agent was enabled during the first successful conversion. Workaround: Restart the remote source machine and try running the conversion task again.

Top of Page

General

The target virtual machine might not start up after conversion with a customized disk-volume layout Changing the disk-volume layout by re-ordering volumes or adding disks on the Data to Copy pane of the View/Edit Options page, might prevent the target virtual machine from starting up. This is because the boot-code of some systems cannot handle moving of the boot volume or moving the boot volume beyond the 8GB mark.

Converter Standalone fails to connect to a powered-on Linux source if the .bashrc file contains an echo statement Converter Standalone might fail to connect to a powered-on Linux source machine if the given login account has a .bashrc file that contains an echo statement. Converter Standalone uses the SFTP protocol to copy files on the source Linux system, and SFTP fails at receiving the echo statement in the .bashrc file. As a result, Converter Standalone might stop responding for 10 minutes while retrieving source machine information or might display the following error message: Unable to query the live Linux source machine. See Connection to a Linux source fails despite correct SSH configuration (KB 1009153) for troubleshooting tips. Workaround: Remove the echo statement from the .bashrc file. You can safely place this echo statement in the .bash_profile file. This does not affect conversion tasks.

The conversion task fails at 99% progress while powering on the target virtual machine If the Power on target machine option is selected on the Advanced options pane of the View/Edit Options page, the conversion task might fail after target reconfiguration with the following error message: Failed to acquire lock on the file. This is because Converter Standalone acquires a lock on the target machine during reconfiguration and might not release the lock after reconfiguration is completed. Workaround: Use vSphere Client to power on the target virtual machine manually. Do not select the Power on target machine option on the Advanced options pane of the View/Edit Options page.

Converter Standalone does not change PIC HAL to APIC HAL during conversion of Windows source machines If the source to convert is running a Programmable Interrupt Controller (PIC) HAL, Converter Standalone does not change the PIC HAL to an Advanced Programmable Interrupt Controller (APIC) HAL in the target virtual machine. As a result, the target virtual machine might not boot or might fail to perform properly. To find out which HAL is running, go to Windows Device Manager and select Computer in the list of devices. If it displays Standard PC or Advanced Configuration and Power Interface (ACPI) PC, you are running a PIC HAL. Workaround: VMware virtual machines are APIC computers. If your source computer is a PIC computer that runs a PIC HAL, you must update the HAL in the target virtual machine to APIC HAL after the conversion. For more information on configuring the correct HAL, see HAL options after Windows XP or Windows Server 2003 Setup. Note: Microsoft does not support running a PIC HAL on an APIC computer. If your source is an APIC computer running a PIC HAL, you must configure the right HAL on the source machine before starting the conversion.

Target virtual machine might not boot if you change the disk controller type while importing a Linux virtual machine In Linux virtual machines, the root device may be defined using the block device name (such as /dev/sda1) in /boot/grub/grub.conf, /boot/grub/menu.lst, or /etc/fstab. If you change the disk controller type while importing the virtual machine, the target virtual machine might not boot. This is because the root device now has a different name (for example, it might have been changed to /dev/hda1). Workaround: Reconfigure the target virtual machine manually. At the minimum, change the root device name to reflect its new name in the target virtual machine. To make your system more robust, use the volume label or UUID instead of the block device name.

During conversion of powered-on Linux machines, Converter Standalone does not recognize Linux source volumes if they are mapped directly on a hard disk Workaround: Linux source volumes that are not managed by LVM must be located in a partition so Converter Standalone can recognize them during cloning of powered-on Linux sources.

Converter Standalone does not preserve disabled network adapters during conversion of physical machine sources that run on Windows During P2V conversion of Windows source machines, Converter Standalone does not detect disabled network adapters on the source and does not preserve them on the destination virtual machine. Workaround: On the View/Edit Options page, click Networks to add network adapters to the destination virtual machine.

Import of standalone VMware sources with a VMDK file greater than 2GB to a hosted destination that resides on a network share that does not support large files, fails If you select a standalone virtual machine source with VMDK file greater than 2GB and try to convert it to hosted destination residing on a remote network location that does not support large files (for example, Linux SMB or NFS share), the conversion task might fail with one of following error messages:

  • Unable to connect to the virtual disk
  • Remote server closed connection after 0 response bytes read
  • An error occurred during an operation on a virtual disk
  • .
If conversion is successful, the following error message related to the VMDK file might appear when you power on the target virtual machine: Internal Inconsistency errors Workaround:
  1. In the main application window of Converter Standalone, right-click the failed task and select Copy As New...
  2. Go to the View/Edit Options page and select Data to Copy.
  3. In the Data to Copy pane, select the volumes to copy and click Advanced.
  4. On the Target Layout tab, select 2GB Split not pre-allocated or 2GB Split pre-allocated as the target disk type.
  5. Click Next to view a summary of the conversion task.
  6. On the Ready to Complete page, click Finish to resubmit the task.

Operating system error recovery screen displays on powering on virtual machines restored from VCB images of Vista and Windows Server 2008 When you power on a virtual machine restored from a VCB image that contains Vista or Windows Server 2008 operating system for the first time, a system recovery error appears on the screen. The issue is observed with VCB images that are created either from running virtual machines or from powered-off virtual machines when their guest operating system was not properly shut down before taking the VCB image. Workaround:

  1. In the vSphere Client Inventory, select the target virtual machine and click the Console tab to open the virtual machine console.
  2. On the Console tab, select to boot as normal in the system recovery screen.

Converter Standalone displays wrong task summary information when using Copy as New to create tasks If you copy an existing task within Converter Standalone and change the destination to Virtual appliance, the Ready To Complete step in the Conversion wizard might contain residual destination information (physical memory, number of CPUs, configuration files datastore, and destination customization) inherited from the original task.

Target virtual machines converted from third-party virtual images running Windows NT with SMP run with 100% CPU usage after the conversion Source third-party images that run Windows NT with multi-processor kernels are not reconfigured properly during conversion. After the conversion, they continue to run with multi-CPU kernel and consume 100% of the virtual CPU capacity.

Linked Cloning of source images greater than 2GB to a network share that does not support large files fails Creating linked clones from source images that are larger than 2GB to a network share that does not support large files (for example, to a Linux SMB share) fails. Converter Standalone does not split the source files into smaller chunks. If the source is larger than the supported file size on the destination, the conversion tasks fails.

Consecutive conversions of powered-on machines running Windows Server 2000 fail every other time If you try to convert a powered-on machine running Windows Server 2000 several consecutive times, every second conversion task fails with the following error in Converter Standalone logs: agent.internal.fault.PlatformError.summary. Workaround: If the conversion task fails, right-click the task in the task list, select Copy As New to create a new conversion task, and run it again.

Conversion of powered-on Linux machines fails during volume cloning if the password for the source machine contains a backslash character Workaround: Change the password on the source machine so that it does not contain a backslash character.

Creating a conversion task to import a standalone VMware source with a VMDK file greater than 2GB from a network share that does not support large files, fails If you select a standalone virtual machine source with VMDK file greater than 2GB residing on a remote network location that does not support large files (for example, Linux SMB share), the following error message appears in the Converter wizard on clicking Next or View source details: agent.internal.fault.FileOpenError.summary. Workaround: Map the network shared folder to the machine where Converter Standalone runs, and select the source from there.

Linked cloning of standalone VMware sources to Linux SMB shared destination fails Linked cloning tasks of VMware standalone sources to SMB shared destinations that run on Linux fail with the following error: converter.fault.FileIOFault.

Converter Standalone client is unable to start Converter Standalone services on Windows Vista if UAC is enabled When the User Account Control (UAC) is enabled on Windows Vista, Converter Standalone might fail to start the VMware vCenter Converter Agent service and VMware vCenter Converter Server service. The following error message is displayed: VMware vCenter Converter Server is installed but not running. When VMware vCenter Converter Server is not running you will not be able to connect to local server. Please go to Control Panel - Administrative Tools - Services to start it manually. Click here to open the Services control panel now. Workaround: Follow the link to start the Converter Standalone services manually.

The number of LVM logical volumes per volume group is limited to 12 for powered-on Linux sources During the conversion of powered-on Linux machines, Converter Standalone converts LVM volume groups into new disks on the target virtual machine. The number of LVM logical volumes on a source LVM volume group cannot exceed 12. Workaround: Move volumes out of the new disk to other target disks:

  1. On the View/Edit Options page of the Conversion wizard, click Data to copy.
  2. From the Data copy type drop-down menu, select Select Volumes to copy and click Advanced.
  3. On the Target Layout tab, select a volume to move and click Move Up or Move Down until it is moved to the destination target disk. You can move volumes between disks as long as they are not Active (/boot) or System (/) volumes.
  4. (Optional) To create a new target disk, click Add Disk.

By default, the Linux P2V helper virtual machine is powered off when the conversion task finishes Workaround: Manually disable this option in the converter-agent.xml file. See Disabling Automatic Shutdown of Helper Virtual Machines After Converting Powered-On Linux Sources (KB 1008210).

By default, you cannot log in to the helper virtual machine during conversion of powered-on Linux sources Workaround: Manually enable this option in the converter-agent.xml file. See Enabling Logging in to Helper Virtual Machine During Conversion of Powered-On Linux Sources (KB 1008209).

By default, Linux core dump is disabled but you can enable it on the system where Converter Standalone server for Linux runs If an issue occurs during conversion with Converter Standalone server and agent for Linux, you can check the Linux core dump file or send it to support for error analysis. As Linux core dump is disabled by default, you must enable it on the system where Converter Standalone server for Linux runs. See Enabling and Configuring Linux Core Dump (KB 1009887).

An error message appears when powering on a target virtual machine cloned from a live Windows Server 2003 source When you power on a target virtual machine that is converted from a live Windows Server 2003 source, the following dialog box appears: "Why did the computer shutdown unexpectedly?". This dialog box does not represent an issue with the target machine. It only requires information for the reason why the source was shut down. You can safely dismiss the dialog and proceed to work with the target virtual machine as usual.

Source volumes on top of volume managers other than LVM are not recognized during conversion of powered-on Linux machines Converter Standalone recognizes only managed source volumes that run on the LVM volume manager. Other volume managers, including but not limited to Veritas Volume Manager (VxVM), are not recognized.

Converter Standalone 4.0.1 does not recognize source volumes that reside on Linux Software RAID configurations During cloning of powered-on Linux machines, Converter Standalone does not recognize source volumes that are part of a Software RAID configuration (also referred to as multiple disk, or md, configurations).

LILO boot loader is not supported for Linux sources You can convert powered-on machines that run Linux only if GRUB is installed as the boot loader on the source.

Microsoft Windows Vista reboots repeatedly after customization Providing wrong customization information might cause the target virtual machine to reboot repeatedly if the source operating system is Microsoft Windows Vista. During conversion or configuration, if you choose to customize Microsoft Windows Vista and provide wrong customization information, for example invalid serial key, the customized target reboots repeatedly. This is a known issue with Microsoft Windows Vista. Workaround: Make sure that the provided customization information is valid.

Converting source machines to Windows Vista or Windows Server 2008 local or network share drive and selecting the Pre-allocated target disk option might result in failure to clone the disk In Converter Standalone agent log you will find the following error: [NFC ERROR] File error -- Failed to write to the target file: An error was detected. This might be due to a known file system issue on Windows Vista and Windows Server 2008. Workarounds:

By default, Converter Standalone has a 20 minute timeout when waiting for the helper virtual machine to start up during Linux P2V conversion This might cause a Linux P2V conversion task to fail due to connection timeout. Workaround: Extend the timeout period (in milliseconds) by modifying the linuxP2VBootTimeout flag in the converter-agent.xml file. See Extending the Timeout Period for Helper Virtual Machine Startup (KB 1008301) for details.

Sparse files are not preserved during conversion of powered-on source machines that run Linux By default, Converter Standalone does not preserve sparse files on the source machine during Linux P2V conversion. If you have large sparse files on the source, they are created as non-sparse on the target virtual machine. This renders the used space on the target file system larger than that on the source machine. This might also cause the conversion task to fail with a timeout error. Workaround: Manually enable keeping sparse files during Linux conversions by modifying the keepSparseFile flag in the converter-agent.xml file. See Enable Retention of Sparse Files During Linux Conversions (KB 1008303) for detailed instructions.

Target virtual machines cloned from OVF sources fail to power on after conversion If you convert an OVF source, the option to reconfigure the target virtual machine is off by default. This might prevent the target virtual machine from starting up properly. Workaround: If the destination machine does not boot after conversion, try reconfiguring the destination image using the Configuration wizard.

Converter Standalone cannot detect the power state of VMware Workstation or other VMware hosted source virtual machines if they are located on a read-only network share If the source machine is a Workstation or other VMware hosted source and is located on a network share with read-only permissions, Converter Standalone cannot detect if the source is powered on or suspended. This might lead to data inconsistency on the target machine if changes are made to the powered-on source virtual machine during conversion. Workarounds:

  • Verify that the source virtual machine is powered off prior to conversion.
  • Provide write privileges to the network share where the source virtual machine resides.

Owner name and organization are not displayed properly after customizing the guest operating system After customizing the guest operating system, Unicode characters used for owner name and organization on the Computer Information page do not appear the way they were set in the Conversion or the Configuration wizard. For all Windows operating systems except Windows Vista, customization parameters such as user name and organization must use characters only from the local encoding of the default user profile of the guest. For example, you can use Japanese characters for the user name only on a guest whose default user profile's local encoding is set to Japanese. These restrictions do not apply to Windows Vista guests because Windows Vista uses a UTF-8 encoded XML file to store the Microsoft sysprep parameters. Earlier versions of Windows use the sysprep.inf file, and the Microsoft Windows mini-setup process reads that file in the local encoding only. Workaround: Either do not use Unicode characters when assigning owner name and organization name for the target virtual machine, or use the workaround described at: http://support.microsoft.com/kb/310441/.

Destination machines converted from physical machine sources running Windows 2000 display blue screen on startup If the source physical machine has IDE disks and is running a version of Windows 2000 earlier than Service Pack 4, the resulting destination virtual machine fails on startup and displays the following error message on a blue screen: inaccessible_boot_device. The issue pertains to Windows and was fixed by Microsoft in Service Pack 4. For more information on this issue, see http://support.microsoft.com/kb/249694/. Workarounds:

  • Select destination disk controller type as SCSI on the View/Edit Options page in Converter wizard.
  • Upgrade the source machine to Service Pack 4 before conversion.
  • Upgrade the destination virtual machine to Service Pack 4 using the Windows installation CD. For more information on in-place upgrade of Windows 2000, see http://support.microsoft.com/kb/292175/.

Target virtual machines that were converted to ESX 4.0 or ESXi 4.0 hosts using volume-based cloning fail to start up if they contain IDE disks You cannot use volume-based cloning to create IDE disks on ESX 4.0 or ESXi 4.0 destinations because the target virtual machine fails to start up. A disk error message or a blank screen is displayed. The target virtual machine fails to start up in the following scenario:

  • When a source machine (physical or virtual) that contains IDE disks is converted to an ESX 4.0/ESXi 4.0 virtual machine by using volume-based cloning, and Preserve source is selected for the disk controller type on View/Edit Options page > Devices pane of the Conversion wizard.
  • When the source machine does not contain IDE disks but IDE is selected as the target disk controller type on View/Edit Options page > Devices pane of the Conversion wizard.

Workaround: For all cloning and conversion operations to ESX 4.0/ESXi 4.0 destinations, select SCSI controller type for the target virtual machine. If an IDE controller must be created in the ESX 4.0/ESXi 4.0 destination virtual machine, use disk-based cloning to create it.

By default, Converter Standalone requires a root login to the source machine for powered-on Linux conversion tasks Workaround: Enable the use of sudo in the converter-agent.xml file to use non-root credentials during Linux P2V. See Enabling the Use of Non-root User for Hot Cloning of Linux Source Machines (KB 1008164) for details.

Converter Standalone 4.0.1 client can connect only to Converter Standalone server of the same version The following error message is displayed when you try to connect to a remote Converter Standalone server that is not the same version as Converter Standalone client: The version of the server we connect to is not supported. Converter Standalone server must be version 4.0.1 so that Converter Standalone client can connect to it. Workaround: Run Converter Standalone 4.0.1 installer on the Converter Standalone server machine to install the Converter Standalone 4.0.1 server.

Conversion task fails if the name of the destination virtual machine contains special characters If the name of the destination virtual machine contains special characters (such as slash (/), backslash (\), colon (:), asterisk (*), question marks (?), quotation marks ("), or angle brackets ()) conversion fails with the following error message: agent.internal.fault.ImageProcessingTaskFault.summary. Workaround: Do not use slash (/), backslash (\), colon (:), asterisk (*), question marks (?), quotation marks ("), or angle brackets () in the destination virtual machine name.

Task progress is not shown when importing a virtual machine that is larger than 1TB Converter Standalone does not display the progress of conversion tasks if the source virtual machine is larger than 1TB. Conversion tasks are completed successfully, but the user cannot monitor their progress. Workaround: You can monitor the disk performance of the destination ESX host to check if tasks are running properly.

Conversion of a powered-on Windows Server 2008 source with non-formatted volume fails You cannot convert powered-on source machines running Windows Server 2008 if their volumes haven't been formatted. The VSS version in Windows Server 2008 does not support unformatted volumes. The following error appears in the log file: Failed to create VSS snapshot of source volume. Error code :2147754764 (0x8004230C) Workaround:

  • Format the non-formatted volume and try the conversion again.
  • Deselect all non-formatted volumes while setting up the conversion task in the Data to copy pane of the View/Edit Options page.

Converter Standalone does not support cloning powered-on Windows Server 2008 sources with FAT/FAT32 volume file system VSS under Windows Server 2008 does not support FAT/FAT32. Trying to convert a FAT/FAT32 volume causes the conversion task to fail. Workaround: Deselect all FAT/FAT32 volumes on the View/Edit Options page of the Conversion wizard.

Converter can convert FAT/FAT32 volumes during hot cloning only if the source machine has at least one NTFS volume For source machines running under Windows versions earlier than Windows Server 2008, VSS can take snapshots of FAT/FAT32 volumes only if the source machine has at least one NTFS volume. For all operating systems that support volume-based cloning, you need at least one NTFS volume for VSS to work.

Conversion fails if there is not enough space on the source to take a VSS snapshot If the space on the source volume is not enough for the VSS to create a snapshot, conversion fails with the following error: Failed to create VSS snapshot of source volume. Error code: 2147754783(0x8004231F). Workaround: Try cleaning up the source volumes (especially the system volume and all NTFS volumes) and try to convert the source again.

When running on Linux, Converter Standalone can reconfigure Windows virtual machine sources only if they have NTFS-formatted boot and system volumes This limitation does not apply when converting powered-on sources.

Converter Standalone remote agent does not notify the user about Converter 3.0.x remote agents that have been installed on the source system during remote hot cloning process If Converter Standalone 4.0.1 is converting a remote machine source that already has a remote agent from Converter 3.0.x version, it uninstalls the old remote agent without issuing a notification or warning message. This prevents older Converter versions from converting this source machine later.

Previous Converter versions cannot convert source machines that have Converter Standalone 4.0.1 agent installed on them. Converter Standalone 4.0.1 agent is deployed on the source machine during conversion. If Converter Standalone 4.0.1 agent is not uninstalled after the conversion, older Converter versions cannot deploy their agents on top of the newer Converter Standalone agent version. Therefore, you cannot use previous Converter versions to convert sources that have already been converted with Converter Standalone 4.0.1. Workaround: Uninstall Converter Standalone 4.0.1 agent before trying to convert the source with an older Converter version.

Task validation fails if the volumes to be cloned requires volume-based file-level cloning and if synchronize changes is active After clicking Finish on the Ready to Complete page, an error message appears in the information bar, and the conversion task cannot be submitted to the task list. Synchronization cannot be enabled if at least one of the source volumes requires file-level cloning. File-level cloning is required when reducing or increasing the size of FAT/FAT32 volumes and when reducing the size of NTFS volumes.

The target virtual machine does not start up after conversion if the active partition is not on the first disk of the source machine Converter Standalone detects the active partition and runs conversion and reconfiguration successfully even if the active partition is not on the first disk of the source machine. However, the BIOS of the target virtual machine might not be able to locate the disk that contains the active partition. Hence, the target virtual machine might fail to start up. Workaround: Rearrange disks order on the target virtual machine BIOS after the conversion.

Converter Standalone fails to configure the target virtual machine if users modify the disks order in the source machine BIOS If a user modifies the boot order in the BIOS of the source machine, Converter might fail to recognize the source boot disk properly, which might cause the target configuration to fail. Workaround: Rearrange disks order in the source machine BIOS before the conversion.

Converter Standalone is unable to detect the system volume if it resides on a SCSI disk and if IDE disks are present in the source machine On source machines with SCSI and IDE disks, Converter is unable to detect the system volume if the system volume resides on a SCSI disk. Converter only checks the first IDE disk in such configurations.

Converter does not report all disks and volumes present on the system while converting a powered-on source machine running Windows operating system This issue is caused by a bug in Microsoft APIs that Converter uses to query devices. The issue is observed with Windows XP Professional 64-bit, without any service pack, and might be present in other versions of Windows XP or Windows Server 2003 as well. Workaround: Update to the latest service pack where the issue is resolved. This issue is not observed in Service Pack 1 for Windows XP Professional 64-bit.

Converter Standalone agent does not start automatically after reboot If the source machine starts up too slowly, Converter Standalone agent might not start automatically after the source machine is restarted. Workaround: Start the Converter Standalone agent manually:

  1. Right-click My Computer and select Manage.
  2. In the Computer Management window, select Services and Applications > Services on the left.
  3. In the list on the right, double-click VMware vCenter Converter Agent.
  4. Click Start to start the process.
  5. Click Apply followed by OK.

Task progress and estimated time to completion are unreliable under certain conditions The task progress displayed in Converter task list as well as the estimated time left to task completion might be miscalculated if the source system has a large amount of free space or very large files on its disks, as well as in case of unexpected network degradation.

If the hardware configuration of the source machine is modified while the Conversion wizard is open, you need to restart the conversion wizard in order to view correct source details Source machine details are retrieved per wizard session, as this is a time-consuming process. If some changes occur on the source machine (such as adding memory or hard drives) after this information is retrieved, the Conversion wizard does not show information about the changes. Workaround: Restart the conversion wizard.

Conversion of remote powered-on sources running under Windows 2000 fails randomly with Error code: 2 For Windows 2000 sources, you need to restart the remote source machine after deploying the Converter Standalone agent and before starting the conversion. Sometimes, the conversion task is submitted to Converter server before the source system restart is complete. The following error is displayed: Failed to create snapshot of source volume. Error code: 2. Workaround: Make sure the source is rebooted, and then resubmit the task.

Volume-based cloning fails with the following error in the logs: Failed to get unallocated clusters, error 87 If the source volume size is not equal to the file system size on the volume, block-based volume-level cloning fails. Although this is not so common on physical machines, it is very common with third-party backup images of Windows Vista and Windows Server 2008 because for these operating systems, the partitions are not cylinder aligned. Workarounds:

  • For non-physical sources, use disk-based cloning.
  • For other sources, use file-level cloning (by resizing the volumes).

Cloning a source that contains file system errors might result in a damaged virtual machine See Cloning a Source That Contains File System Errors May Result in a Damaged Copy (KB 1006689).

The target virtual machine is not created when performing an OVF export larger than 2GB Virtual appliances can be very large and might exceed 2GB in size. When choosing a destination for your virtual appliance (OVF or OVA), ensure that you use a file system, such as NTFS, which can support large files. FAT file systems do not support files greater than 2GB. If a conversion process fails, an Error code=12 in the log file indicates that you have reached this limitation.

The source virtual machine does not have the appropriate drivers The following error message appears in the log file when reconfiguration fails because the appropriate drivers are missing from the source operating system: Unable to find symmpi.sys in the specified CAB files This is usually observed in Windows Server 2003 SP1. Workaround:

  1. Save the virtual machine created during the failed import to a backup location.
  2. Attach the VMDK file containing the system folder to another Windows Server 2003 virtual machine.
  3. Replace the WINDOWS\Driver Cache\i386\driver.cab file in the target virtual machine with a version of the driver.cab file that includes the missing driver from the helper virtual machine.
  4. Detach the VMDK file from the helper virtual machine and run the Configure Machine wizard on the target virtual Machine.

Sysprep deletes drive letter mappings if your task includes customization If you choose customization options and the destination virtual machine fails at a Please Wait screen after the second sysprep reboot, you need to rerun the import without customization. This issue occurs because of a problem with Microsoft sysprep, which deletes the drive letter mappings, preventing access to certain files.

After customizing a virtual machine, rebooting it produces an error message stating that msgina.dll failed to load See the VMware Knowledge Base article, Error: "Logon User Interface DLL msgina.dll failed to load" and the Microsoft Knowledge Base article, "Error Message: User Interface Failure: The Logon User Interface DLL Msgina.dll Failed to Load" .

Customization is not applied if a virtual machine is manually restarted after running the configuration task The process for customization occurs as follows:

  1. User customizes the virtual machine image with Converter and wait for 100 percent completion.
  2. Converter Standalone agent powers on the virtual machine and waits for it to reboot automatically.
  3. Sysprep processes the customizations.
  4. Sysprep reboots the virtual machine.
  5. The Windows operating system loads, and the network configurations occur.
If you manually reboot the virtual machine at step 2, without waiting for it to automatically reboot, the customization process breaks. When Windows discovers new hardware and asks you to reboot, if you select Yes, the customization process breaks. In both scenarios, customization settings are not applied to the virtual machine. Workaround: Wait for the machine to automatically reboot twice before the customization settings are applied and you can safely log in.

Top of Page

Managed Products

Incorrect settings of vNetwork Distributed Switch after conversion to a managed destination In Conversion wizard, if you select a managed destination, and on the Networks pane of the View/Edit Options page you select a distributed virtual port group of a vNetwork Distributed Switch, the vNetwork Distributed Switch settings are not applied correctly on the destination virtual machine, even though the conversion completes successfully. Workaround: Use vSphere Client to edit manually the vNetwork Distributed Switch settings on the destination virtual machine:

  1. Locate the target virtual machine in the vSphere Inventory list.
  2. Right-click the target virtual machine and select Edit Settings...
  3. On the Hardware tab, select the network adapter to set.

Conversion of powered-on Linux machines might fail when VMware HA is enabled in ESX 3.5 Update 3 When Virtual Machine Monitoring is enabled on VMware HA (High Availability), a known issue in ESX 3.5 Update 3 causes the helper virtual machine to reboot unexpectedly. This results in premature termination of powered-on Linux source conversions. See Virtual Machine may unexpectedly reboot when using VMware HA with Virtual Machine Monitoring on ESX 3.5 Update 3 (KB 1007899). Workaround: Upgrade to ESX 3.5 Update 4 or higher and VMware vCenter Server 2.5 Update 4 or higher.

Virtual machines cloned from powered-on sources running SLES 10 operating systems to ESX 4.0 or ESXi 4.0 managed destinations with virtual hardware version 7.0 start up very slowly If you clone a powered-on source machine that runs on SLES 10 operating system to ESX 4.0 or ESXi 4.0 destination with virtual hardware version 7.0, the target virtual machine starts up very slowly. This is because the /sbin/hwup shell script tries to start devices that no longer exist. This issue is observed with source machines running SLES 10 without any service pack. Workarounds:

  • Update the source machine with SLES 10 Service Pack 1 or 2.
  • Remove all files that have filenames starting with hwcfg-bus-pci- from the /etc/sysconfig/hardware directory. To do this, run the following command from root shell: rm -rf /etc/sysconfig/hardware/hwcfg-bus-pci-*.

Conversions of VMware Infrastructure virtual machine sources with 15 or more disks to any ESX destination managed by VirtualCenter 2.5 fail If you import a virtual machine source that resides on an ESX 3.5 host to an ESX 3.5 destination managed by VirtualCenter 2.5, and the source machine has 15 or more VMDK files, the conversion task fails with the following error message in Converter Standalone logs: FAILED: agent.internal.fault.NfcConnectionFault.summary Workaround:

  1. Convert the source machine to a hosted virtual machine destination, such as Workstation.
  2. Convert the resulting virtual machine to the ESX managed by vCenter where you want it to reside.

While exporting a virtual machine from an ESX 3.5 host to OVF "folder of files" format by using Converter Standalone, the vNICs are forcibly changed from their native type While exporting a virtual machine source from an ESX 3.5 host to the OVF "folder of files" format, Converter Standalone changes the source vNICs from their native type (vmxnet, vlance, or e1000) to either PCNet32 (vlance) or E1000 (e1000). This might result in an unexpected lack of network connectivity when the OVF file is imported. Workaround: Edit the .vmx file to manually modify the vNIC type after importing the virtual appliance.

Conversion from and to ESX hosts fails if the number of disks on the source machine is more than nine When converting a source machine that has more than nine disks, conversion fails with the following error in the log file: Error on logout (ignored): Operation timed out SSLStreamImpl::BIORead ( 3BBA4E8) timed out. The error is due to the limited number of NFC connections that can be established to ESX hosts. Workaround: Connect to the target ESX host through a vCenter Server. In this case, the number of source disks is limited to 27 for ESX and to 23 for ESXi hosts.

Virtual machines cloned from SLES 9 SP4 sources to ESX 3.0 destinations fail to boot after conversion If you convert a SLES 9 source with SP4 to an ESX 3.0 managed destination and select LSI Logic disk controller type for the destination machine, the resulting virtual machine fails to boot and displays the following error message: No root device found; exiting to /bin/sh sh: can't access tty; job control turned off. The issue is observed due to LSI Logic driver incompatibility. Workarounds:

Top of Page

Third-Party Formats

NEW You cannot create a valid OVA image if any of the source disks is larger than 8GB If you convert a virtual machine source that has one or more disks larger than 8GB to an OVA image, the conversion task completes successfully, but the resulting OVA image is not valid. Workaround: If any of the source .vmdk files is larger than 8GB, convert the source virtual machine to OVF files instead of OVA image.

NEW You cannot convert OVA image sources if they contain virtual disk files larger than 8GB If you try to convert an OVA image source that is larger than 8GB, the OVA extraction fails and Converter Standalone does not deploy the target virtual machine to the destination. This issue occurs if any of the source .vmdk files of the OVA image is larger than 8GB. The issue is not observed if you deploy virtual machines from OVF source files. Workaround: If any of the source .vmdk files is larger than 8GB, deploy virtual machines from the OVF files instead of the OVA image.

Limitations when converting third-party images You can use Converter Standalone 4.0.1 to convert third-party virtual machines, system images, and backup images with the following limitations:

  • Backups of systems with dynamic disks are not supported (ShadowProtect and Backup Exec System Recovery).
  • All images for the backup of a machine must be in a single folder that contains no other images (ShadowProtect and Backup Exec System Recovery).
  • For incremental images, up to 16 incremental backups are supported (ShadowProtect and Backup Exec System Recovery).
  • Images of systems with logical drives are not supported if the logical drive is also a system or active volume (only for ShadowProtect sources).
  • For volume-based cloning of Acronis and StorageCraft, all volumes in the disk before the active and system volumes must be backed up. For example, if a disk has 4 partitions, 1-4, with partition 2 as the active volume and partition 3 as the system volume, the backup must include volumes 1 through 3 (ShadowProtect and Backup Exec System Recovery).
  • Virtual machines from Macintosh versions of Virtual PC are not supported.
  • The operating system on the source Virtual PC or Virtual Server virtual machine must be a Windows guest operating system supported by the intended VMware platform (for example, Workstation 5.x or 6.0.x). For a list of supported systems, see the Guest Operating System Installation Guide.

Separate backup images should be stored in different folders Storing more than one third-party backup in a single folder results in a failed migration. Workaround: Place each backup in its own folder before using Converter Standalone to import an image.

Target virtual machine might not boot up because an incorrect disk number is reported from Symantec backups In some circumstances, the disk number reported in the Symantec library is incorrect, which causes the resulting image to be unbootable because the virtual machine searches for the Master Boot Record (MBR) in the incorrect device. Workaround: In the main Workstation menu, choose VM > Settings > Hard Disk > Advanced and switch the virtual device node so that the target virtual machine boots from the same disk as the source machine.

Virtual machines converted from Parallels 4.0 images with guest operating systems running Linux, might appear to not start up after conversion Converter Standalone supports only Windows guest operating systems for Parallels sources. With some Linux guests running under Parallels, the target virtual machine might appear to boot unsuccessfully even though it runs. This is due to incompatibility issues between the display driver used in the Linux guest and the display adapter of the target VMware virtual machine.

Conversion of powered-on Hyper-V local machines might fail If the source machine is a powered-on local Hyper-V machine, the conversion task fails, and the following error message appears: Failed to create VSS snapshot of source volume. error code: 2147754758 (0x80042306). The following error appears in the Converter agent log file: VSS Snapshot creation failed for the volume \\?\Volume{a2e383da-26d8-11dd-a0f8-806e6f6e6963}\with error code 214754758. The issue is observed if two VSS services (Microsoft Software Shadow Copy Provider Service and Volume Shadow Copy Service) are not started or are not operating properly on the source machine. Workarounds:

  • Restart the source machine and try cloning it again.
  • Set the starting mode for Microsoft Software Shadow Copy Provider Service and Volume Shadow Copy Service to Automatic.

Top of Page

User's Guide and Help

Missing limitation in Table 1, Supported Sources, of the Converter Standalone Online Help The Third-party virtual machines or system images row contains a list of supported versions for Parallels products, but does not mention explicitly that Parallels Virtuozzo Containers are not supported in Converter Standalone.

Typographical error in Table 1, Supported Sources, of the Converter Standalone Online Help The Third-party virtual machines or system images row contains a list of supported versions for Symantec Backup Exec System Recovery. The list reads ...7.0, 8.0, and 8.0. The text should read ...7.0, 8.0, and 8.5.

Converter Standalone displays an empty help page when installed on Microsoft Windows Server 2008 When VMware vCenter Converter Standalone is installed on Microsoft Windows Server 2008 and the system default browser is Microsoft Internet Explorer 7, if a user invokes help either from the Help menu or by pressing F1, Internet Explorer is started but displays an empty page. The reason for this is that the default settings in Internet Explorer 7 do not allow execution of JavaScript code in the browser. Workaround: Enable the Active scripting option in Internet Explorer 7.

Help page is displayed with errors in Firefox browsers when Converter Standalone is running on Linux systems The following error appears in the error console of Firefox when opening Converter Standalone help page on Linux Systems: Expected end of value for property but found "border". Error In parsing value for property "background". Declaration dropped. You can ignore this error as it does not affect the content of help files.

You cannot customize the guest operating system of Linux sources VMware vCenter Converter Standalone 4.0.1 online help does not state this explicitly.

Silent command line commands for Converter Standalone agent are not listed in VMware vCenter Converter Standalone 4.0.1 User's Guide The commands for silent installation of Converter Standalone agent can be found in the VMware Knowledge Base. For a list of silent mode commands, see Using the Command-Line to Install VMware vCenter Converter Standalone Agent (KB 1008207).

F1 does not work when a combo box is selected in the Conversion wizard window When the focus is on a combo box in the Conversion wizard, the F1 shortcut for help does not work. Workaround: Press Alt+H keys on your keyboard to invoke Converter Standalone help.

Top of Page

Resolved Issues

The following issues have been resolved in Converter Standalone 4.0.1 release:

General

Virtual machines created from OVF sources with SCSI LSI Logic disk controller might not start up after conversion to an ESX destination. Converter Standalone 4.0.1 preserves the disk controller type.

Converter Standalone Linux installer fails when the icon or desktop directory is missing. This issue is no longer present in Converter Standalone 4.0.1

You cannot install Converter Standalone 4.0. on a Linux machine running with a Xen kernel. This issue is fixed in Converter Standalone 4.0.1 Linux installer.

Not all disks are detected while trying to import VPC and VS images. This issue is no longer present in Converter Standalone 4.0.1.

OVA file is overwritten if a .ova file with a specified virtual appliance name already exists. If you are exporting to a virtual appliance with the OVA file option specified, and if a .ova file with a name identical to the destination virtual appliance name is specified, no error message is issued and the existing OVA file is overwritten. If, however, the existing .ova file is read-only, the OVA creation task fails. This issue is fixed in Converter Standalone 4.0.1 and now an error message prompts you to change the .ova filename.

When you resize disks to Min size on the Data to Copy pane of the View/Edit Options page, the resulting new disk size is approximately 10 percent larger. If you hot clone a physical source machine and specify Min size for the source data, the actual disk size created is approximately 10 percent larger than the displayed minimum size.

Top of Page

User's Guide and Help

You cannot customize the guest operating system of Linux sources VMware vCenter Converter Standalone 4.0.1 User's Guide states this explicitly.

Typographical error on page 64 of Converter Standalone User's Guide The Sysprep files locations for Linux begin with /var/lib/..., and not with /usr/lib/... as was stated in the guide.

Typographical error on page 60 of Converter Standalone User's Guide Customize a Virtual Appliance procedure, step 3 read ...contains a SHAI digest of each of the files.... The text now reads ...contains a SHA1 digest of each of the files...

Web server port cannot be selected during Client-Server installations on Linux Step 12c on page 32 of the Converter Standalone User's Guide described the way to specify the Web server port to use during conversions. This setting is unavailable in Converter Standalone 4.0.1, therefore it was removed from the procedure.

Typographical error on page 30 of Converter Standalone User's Guide The filename in step 1 and current directory in step 3 read VMware-converter-e.x.p-.tar.gz, now it reads VMware-converter-4.x.x-.tar.gz as is should.

Error in Table 2-1, Supported Operating Systems, on page 18 of Converter Standalone User's Guide Table 2-1, Supported Operating systems, contains SUSE Linux Enterprise Server 7.0. SUSE Linux Enterprise Server version 7.0 is not supported in Converter Standalone 4.0.1.

Typographical error in Table 2-3, Supported Sources, on page 19 of Converter Standalone User's Guide The Third-party virtual machines or system images row contains a list of supported versions for Symantec Backup Exec System Recovery. The list read ...7.0, 8.0, and 8.0. The text now reads ...7.0, 8.0, and 8.5.

Missing limitation in Table 2-3, Supported Sources, on page 19 of Converter Standalone User's Guide The Third-party virtual machines or system images row contained a list of supported versions for Parallels products, but did not mention explicitly that Parallels Virtuozzo Containers were not supported in Converter Standalone.

Error in Table 2-5, Virtual Machine Conversion Limitations, on page 20 of Converter Standalone User's Guide For Linux host operating systems, VMware Tools installation is not supported. Table 2.5 of Converter Standalone User's Guide erroneously stated that it was supported for Windows guests.

Converter Standalone 4.0.1 converts VCB image sources only if Converter Standalone is installed on a Windows platform The VMware vCenter Converter Standalone 4.0.1 User's Guide states this explicitly.

Typographycal error in Table 2-7 on page 23 of VMware vCenter Converter Standalone 4.0 User's Guide Table 2-7 stated that the default device type for Floppy and CD-ROM is changed to host device. The default device type for Floppy and CD-ROM is changed to client device.

Top of Page

www.vmware.com


Смотрите также