RedHat P2V failed 99% - Grub problem

Similar Questions

• opatch 10.1.2 Oracle Home - ERROR: OPatch failed due to problems in the area of patch.

  Hi all

  DB: 11.2.0.3.0

  EBS:12.1.3

  Operating systems: Solaris SPARC 64-bit

  I get the following error message on the command below:

  opatch $ apply - invPtrLoc $ORACLE_HOME/oraInst.loc

  Setup Oracle interim Patch version 1.0.0.0.64
  Copyright (c) 2011 Oracle Corporation. All rights reserved...

  Oracle recommends using the latest version of OPatch
  and read the OPatch documentation in the docs/OPatch
  Directory for its use. For more information on the last OPatch and
  other support issues, please refer to document ID 293369.1
  available on My Oracle Support (https://myoraclesupport.oracle.com)

  Oracle home: /d001/test1/apps/tech_st/10.1.2
  The Oracle Home Inventory: /d001/test1/apps/tech_st/10.1.2/inventory
  Inventory Center: / export/home/applmgr/oraInventory
  from: /var/opt/oracle/oraInst.loc
  YES location: /d001/test1/apps/tech_st/10.1.2/oui
  YES shared library: /d001/test1/apps/tech_st/10.1.2/oui/lib/solaris/liboraInstaller.so
  Location of Java: /d001/test1/apps/tech_st/10.1.2/jdk/jre/bin/java
  Location of the log file: /d001/test1/apps/tech_st/10.1.2/.patch_storage/ < patch ID > / *.log

  The patch directory field must be a number.

  ERROR: OPatch failed due to problems in the area of patch.

  $ opatch version

  Setup Oracle interim Patch version 1.0.0.0.64
  Copyright (c) 2011 Oracle Corporation. All rights reserved...

  Oracle recommends using the latest version of OPatch
  and read the OPatch documentation in the docs/OPatch
  Directory for its use. For more information on the last OPatch and
  other support issues, please refer to document ID 293369.1
  available on My Oracle Support (https://myoraclesupport.oracle.com)

  OPatch Version: 1.0.0.0.64

  Tried the underside of the notes but the error persists. Even tried several times 'p6880880_101000_SOLARIS64.zip' to download and unzip on the server, but of no use. This question took place now for a few days.

  (Error: OPatch failed due to problems in the area of the Patch [ID 1281504.1]).

  Opatch error: The Patch Directory area must be a number [258650.1 ID]

  O patch 1.0 . 0.0.55 fails with the error 'the Patch directory field must be a number' [ID 394601.1]

  Patch Directory area must be a number: Opatch returns with the Code error = 170 [369555.1 ID]

  Please let me know any other suggestion is appreciated as the runinstaller from Patch 5983622 -Upgrade to Forms 10 g OracleAS and statement 10.1.2.3 (437878,1) fails after running root.sh Run specific tasks.

  I'm upgrading to 10.1.2.3.0 forms using - reclassification OracleAS g 10 forms and States to 10.1.2.3 (437878.1)

  Thank you for your time

  Kind regards

  user10088255

  Hi user10088255,

  Please follow the procedure under the section 'How to check the contents of the inventory Central' (Doc ID 742477.1) to check whether or not 10.1.2 ORACLE_HOME is registered in the central inventory. If it is not registered then follow one of the methods in the same doc to add.

  Thank you

  Hussein

• ERROR: OPatch failed due to problems in the area of patch.

  HIII...,
  
  IM upgrading Forms 10 g OracleAS and reports in Oracle E-Business Suite Release 12.
  
  IM one of the additional fixes 9357237 such application mentioned in the metalink document
  
  Upgrade OracleAS 10 g forms and reports Oracle E-Business Suite Release 12 [437878.1 ID].
  
  Im getting the following error in the application of the patch
  
  
  Oracle home: /u02/oracle/PROD/apps/tech_st/10.1.2
  The Oracle Home Inventory: /u02/oracle/PROD/apps/tech_st/10.1.2/inventory
  Inventory Center: / u02/app/oraInventory
  from: /etc/oraInst.loc
  YES location: /u02/oracle/PROD/apps/tech_st/10.1.2/oui
  YES shared library: /u02/oracle/PROD/apps/tech_st/10.1.2/oui/lib/linux/liboraInstaller.so
  Location of Java: /u02/oracle/PROD/apps/tech_st/10.1.2/jre/1.4.2/bin/java
  Location of the log file: /u02/oracle/PROD/apps/tech_st/10.1.2/.patch_storage/ < patch ID > / *.log
  
  The patch directory field must be a number.
  
  ERROR: OPatch failed due to problems in the area of patch.
  
  
  IM using OPatch version: 1.0.0.0.64.
  
  When I downloaded nd unzipped the patch just like that
  
  [oracle@msftrac2 patches] $ cd 9357237 /
  [oracle@msftrac2 9357237] $ ls-l
  Total 132
  drwxr-xr-x 4 oracle oinstall 4096 13 April 2010 8447875
  drwxr-xr-x 5 oracle oinstall 4096 13 April 2010 9352208
  drwxr-xr-x 4 oracle oinstall 4096 13 April 2010 9357234
  -rw - r - r - 1 oracle oinstall 84630 13 April 2010 README.html
  -rw - r - r - 1 oracle oinstall 67 13 April 2010 README.txt
  -rwxr-xr-x 1 oracle oinstall 2258 remove_demo.sh April 13, 2010
  
  
  Can someone help me solve the problem. ?... waiitng for your suggestions...
  
  
  Thanks and greetings...

  Hello
  This shows that you do not have the README file in patches

  8447875
  9352208
  9357234

  Try to create a README.txt file in each of these directories and then apply the patch.

  Furthermore, what is the command that you use to apply this hotfix. (opatch apply or opatch napply)

  Thank you

• P2V on Redhat 8 failing miserably

  Hello

  I was responsible for the conversion of a v8 box antique intact Red Hat in a virtual machine.  I had no problem of conversion of a series of boxes of SUSA before but it continues to refer to me.  The question I wonder is am I flogging a dead horse?  I know that this version is not supported, but is it because this will only work with success as a virtual machine or because nobody really wants to support older versions of LINUX?

  Thanks in advance for any help

  /StuZ

  Welcome to the forum.

  8 HR is not supported the cause is an old distro.

  But it can work in an environment virtual (there are only a few problems with clock... screw).

  But to convert it, do it manually (creating a VM, the boot with a CD live, netcat allows to copy all the data, change the configurare hardware and install the VMware Tools), or try to find 3rd party tool.

  PS: thread placed in the converter box.

  André

• CentOS P2V fails after 63% - unexpected EOF in archive.

  Hello.

  This is Centos 6.2
  / Home is a volume logic running ext4.
  / is also an ext4 running of the logical volume and it can copy only.

  / is 50 GB

  / Home is 405 GB would that be a problem?

  FAILED: An error occurred during conversion: "/ usr/lib/vmware-converter/bin/ssh - z f /usr/lib/vmware-converter/ssh.conf [email protected] Pei 22" tar - one-file system - sparse-C/home - CF-. » | /bin/tar_1.20--numerique-proprietaire--restauration-directory-retard - C/mnt/p2v-src-root/home y - xf - read from the remote host 10.0.0.4: connection reset by the pair/bin/tar_1.20: Unexpected EOF in archive/bin/tar_1.20: Unexpected EOF in archive/bin/tar_1.20: error is not recoverable:

  out now (code 2 back)"

  I had to disable SSL in the converter and move the machine from the dmz to the LAN network.
  Thank you guys.

• P2V failed with RHEL5 and standalone converter 5.0

  Hello

  I'm p2v a RHEL 5 stand-alone Converter 5.0 physical physical server. The conversion will work fine until it reaches 95% and it bomb errors below. I tried several times and it has always failed to 95% with the same mistakes.

  =======

  FAILED: An error occurred during conversion: "/usr/lib/vmware-converter/copyFileSystem.sh sshClient-/ usr/lib/vmware-converter/ssh - root - host 10.0.0.64 - port 22 user - sourceMountPoint /-targetMountPoint/mnt/p2v-src-root / sshConfigFile--/usr/lib/vmware-converter/ssh.conf--sourceTarOption--rare ' failed. Return code: 2; message: / usr/lib/vmware-converter/ssh - z f /usr/lib/vmware-converter/ssh.conf [email protected] Pei 22 "tar - one-file-system - sparse-C / / CF-. » | tar - digital-owner/mnt/p2v-src-root - C / y - xf - tar:. / tmp/.font-unix/fs7100: socket ignored tar: ./tmp/keyring-YYWlLJ/socket: socket ignored tar: ./tmp/keyring-9uz5dz/socket: socket ignored tar:. / tmp/mapping-root: socket ignored tar:. / tmp/mapping-chris: socket ignored tar:. / var/log/memcached.log: be a member of invalid rare archives:. / var/log/memcached.log: file changed as we read tar: ./var/lib/log_daemon: socket ignored tar: ./var/named/chroot/var/run/dbus/system_bus_socket: socket ignored tar: ./var/run/dbus/system_bus_socket: socket ignored tar: ./var/run/heartbeat / register: socket ignored tar: ./var/run/cman_admin: socket ignored tar: ./var/run/audispd_events: socket ignored tar:. / var/run/acpid.socket: socket ignored tar:. / var/run/clumond.sock: socket ignored tar:. / var/run/pcscd.comm: socket ignored tar: ./var/run/sdp: socket ignored tar: ./var/run/cman_client: socket ignored tar: ./var/run/avahi-daemon/socket: socket ignored tar: ./var/run/saslauthd/mux: socket ignored tar:. / var/run/cluster/rgmanager.sk: socket ignored tar:. / var/run/cluster/ccsd.sock: socket ignored tar:. / var/run/cups/cups.sock: socket ignored tar:
  Previous error messages error output delay

  ===========

  10.0.0.64 is the source IP address of the physical machine. I have other physical servers on the network with the same configuration or similar, I have no problem with their conversion.

  Anyone know what is happening here? I checked the configuration of sshd source machine, everything looks ok Protocol 2 only.

  I have attached the log converter with more information assistance.

  Thank you

  S

  HM, looking more carefully at the newspaper these lines are strange:

  --> tar:. / var/log/memcached.log: invalid rare archives members

  --> tar:. / var/log/memcached.log: file changed as we read it

  I do not have this file in my RHEL5, but my guess is tar fails because of this. Other messages of tar are ignoring sockets unix which is not a problem. So, do you have idea what this file is, it is currently in use, can you stop the creative process or just restart with no logging at the moment of conversion?

• Cannot exit Mode without fail and display problems

  Hi, ive got a problem my pc won't start in safe mode, when I start my pc just after the bios page there is a black page and MMM in the top of the page and DDD in the middle of the page, then it will not start windows, it will remain a black page. a few times he randomly let me get on pc works fine then screen gets loads of yellow on lines then freezes and only the mouse moves but lag on screen then I should use mode without fail of ideas what it could be? also when the pc works fine I start world of warcraft and the screen will split into thousands of pieces and fill it with the color. I do virus scans etc and nothing.

  Hello

  What operating system is installed on the computer?

  Method 1:

  Check a drive for errors
  http://Windows.Microsoft.com/en-us/Windows7/check-a-drive-for-errors

  Warning of Chkdsk.

  Important: If all data on the hard disk may be lost when running chkdsk, as the chkdsk attempts to repair that affected sector.

  Method 2:

  You can also uninstall and reinstall display drivers and check.
  
  a. click Start, type Device Manager in the start search box and press on Enter.
  b. find graphics card and even expand it.
  c. Select the display adapter you want to to uninstall.
  d. right-click and select Uninstall.
  Follow the on-screen instructions. Restart the computer, it will automatically re - install the drivers.

• How can I fix this Shutdwn FATALE: WUCheckForUpdatesAtShutdown failed and WUAutoUpdateAtShutdown problem?

  Recently, I checked WindowsUpdate.log my computer, I have continued to see the next line of the FATAL error writing here whenever I start the computer and about to close. He said something like this:

  2010-07-29 00:56:47:906 1156 4 c 0 Misc = logging initialized (build: 7.4.7600.226, tz: + 0800) =.
  2010-07-29 00:56:47:906 1156 4 c 0 Misc = process: C:\WINDOWS\Explorer.EXE
  2010-07-29 00:56:47:906 1156 4 c 0 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
  2010-07-29 00:56:47:906 1156 4 c 0 Shutdwn install at shutdown: no updates to install
  2010-07-29 00:56:47:906 1156 4 c 0 FATAL Shutdwn: WUCheckForUpdatesAtShutdown failed, hr = 8024 A 000
  2010-07-29 00:57:09:578 484 e60 Misc = logging initialized (build: 7.4.7600.226, tz: + 0800) =.
  2010-07-29 00:57:09:578 484 e60 Misc = process:------? \C:\WINDOWS\system32\winlogon.exe
  2010-07-29 00:57:09:578 484 e60 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
  2010-07-29 00:57:09:578 484 e60 Shutdwn FATALE: WUAutoUpdateAtShutdown failed, hr = 8024 A 000

  I don't know what the problem with my computer, the newspaper of keep generating these FATAL errors each and every time. I'm sorry that I can't get anything else in the newspaper other than that because I didn't know that old newspapers have been removed by the cleaner software.

  So far, here are the problems I've met so far in my computer with this FATAL, but I don't know if it actually caused that:

  • My browser was arrested by force when I clicked on a link. It happens rarely and on some microsoft sites.
  • It is difficult to describe it. Once in a while, my computer will boot in a strange pattern, unless I'm defragging my computer. Caps/number on the keypad lock remains light throughout the loading screen until half out of the light, the letters of words like "press ESC to go to config" came out slowly and one by one. Usually the lock of the Caps/number will blink for some time and remain extinguished after the initialization of the operating system.

  These are the things that I have tried or done to try to solve the problem but until now none of them work:

  • I have manually update Windows and installed the SP3 for my XP, thinking he's going to replace corrupted files.
  • I have stop/restart automatic update and the PIECES in the service.msc window services. Whatever it is, there's always this error FATAL so I decided to disable both services at the moment.
  • I tried to use a MS-DOS batch file called WUFix.bat that someone provided to fix my problem, WindowsUpdate.log still gives the same once I used it and restart my computer later.
  • I thought that the c:\windows\system32\wuaueng.dll file was corrupted so I decided to replace it with a new one, but still nothing changes.

  I think it's all the details I gave to my problem, I tried not to do anything else major other I listed out above. I still think that's the problem with the file since the FATAL c:\windows\system32\wuaueng.dll came right after this and it has to do with Windows updates and everything. This error has been there for a few weeks and even if there is no critical errors have occurred to date, it is still bugging me.

  If there is no solution that I can do to solve this problem, I would be happy if you can explain step by step. Any help will be appreciated. Thank you

  EDIT: I do not understand why this is posted in the Windows 7 forum when I chose Windows XP. Anyway, hope someone can help me with this.

  Does this mean I should keep the auto update turned on all the time in order to avoid the error reappear?

  Yes. ~ Robear Dyer (PA Bear) ~ MS MVP (that is to say, mail, security, Windows & Update Services) since 2002 ~ WARNING: MS MVPs represent or work for Microsoft

• vRealize 7 - NSX Automation deployments fail due to problems of certificate with vRealize Orchestrator

  Hello community,

  After you have installed the latest version of vRA, vRO, and NSX I run questions when you apply components that use components of the NSX. First of all: details of the version:

  -vRA: 7.0.0 (build 3292778)

  -vRO: 7.0.0.16989 (build 331003)

  -NSX: 6.2.1 (build 3300239)

  vRO plugin versions are delivered with the vRO version listed above with the exception of the plugin NSX, which has been updated to the latest version (1.0.3 published on 17.12.15).

  In the configured tenant vRO is configured as endpoint. I can check the data collection is running and working. I can see the plugin NSX for vRO runs the workflow 'create endpoint NSX' from time to time using the configured user of vRA VRO.

  In the configured tenant vRO is thus configured as server default for ASD vRO. Connection test is successful. When you save the config I'm prompted to approve the vRO certificate, which I confirm. Note that the thumbprint specified matches the footprint of the vRO certificate that I get during the visit of the vRO system on https://vro:8281. I am able to navigate the vRO vRA designer workflows, therefore: connection seems established.

  Within vRO the vRA COFFEE and plug-ins IAAS have been saved successfully. I am able to browse the inventory of plugin for both plugins.

  To solve the problem, I created a new unified plan within the design section of vRA with the following configuration:

  -Transport box: my area of transport configured NSX (checked: manual creation on this area using NSX works very well)

  -Routed res pol. Bridge: my reference for the dash cluster to use Pol

  -The only component dragged to canvas is a 'network and safety'-> 'On-Demand NAT Network' that uses a profile preset 1-to-many network as is "Parent network profile" without manual modification.

  -Note that, although there is a plan very simple example to illustrate the problem, it happens with any model that I have set up if any component is confgured requiring the NSX plugin for vRO.

  "Whenever I ask this plan, the request fails with the error message:" ","application [fa1e0689-0d06-4308-a914-e498c0d1fd99]: 404 not found "

  Looking in vCenter, NSX and vRO I can check that nothing is really trigged when you ask for the action plan.

  Consider the vRA /storage/log/vmware/vcac/catalina.log becomes very visible:

  com.vmware.vcac.iaas.vco.network.helper.VcoEndpointSelector.isEndpointAlive:88 -
  vRealize Orchestrator endpoint with url [https://s00-vro.my.domain:8281/vco] is not alive. 
  Exception message:> [Host name 's00-vro.my.domain' does not match the certificate subject provided by the peer (CN=s00-vro.my.domain, OU=VMware, O=My Company, C=DE)]
  
  com.vmware.vcac.iaas.vco.network.helper.VcoEndpointSelector.getFirstAliveEndpointByPriority:200
  - vRealize Orchestrator endpoint [https://s00-vro.my.domain:8281/vco] with priority 1 is not alive. Skipping.
  
  org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolv
  er.logException:189 - Handler execution resulted in exception: Endpoint not found. There are no vRealize Orchestrator endpoints that are alive.
  
  com.vmware.vcac.platform.service.rest.resolver.ApplicationExceptionHandler.handleHttpStatusCodeException:673 - 404 Not Found
  org.springframework.web.client.HttpClientErrorException: 404 Not Found
  ...
  ...
  ...
  
  

  Please note that I double checked the certificate. This is a self-signed certificate created using the 7.0 vRO new control panel, the one I get when you go to https://vro:8281. It is valid and the object (issed to CN) matches perfectly the hostname entered the ASD and endpoint configuration in the vRA. It is separable and time on all components of the server is in sync with the use NTP.

  Now, I even re-generated certificate and re-registered and rebooted all the components, but while I can see that the certificate has been updated all components I always get the same question.

  Never had this problem with the previous version of the NSX / vRA / vRO. I checked the documentation if nothing has changed here, but did not find what I'm doing wrong. Anythimg I'm missing here? Any bug?

  OK, this seems to be the issue. So put atleast to previous day since version ofvRO (cannot check if it's true for charges vRO 7 installs as well but it is probably) vRO 'control center' will generate certificates based SHA1 vRA love not for actions that use the endpoint in the vRA vRO. ASD seems to work without these problems.

  Sidenote: VRO upgraded installs will also come with SHA1 based CERT if they use a self-signed cert created by vRO. However: you would think that it is sufficient to recreate the cert using the control center. But it turns out it isn't, because it will generate a (new) based SHA1 cert.

  What I did to solve the problem:

  1. create a vRO SSH2 based certificate without the cert extensions, similar to the one that ships with built-in vRA vRO. I tend to use xCA for these jobs, but openSSL will do as well. The exact format required for the certificate of vRO is not documented, but I can make sure you need it like this: PEM certificate in key private and public including format PKCS #1, formatted as follows:

  -----BEGIN RSA PRIVATE KEY-----
  (Your private Key: your_vro_server.key)
  -----END RSA PRIVATE KEY-----
  -----BEGIN CERTIFICATE-----
  (Your primary certificate: your_vro_server.crt)
  -----END CERTIFICATE-----
  -----BEGIN CERTIFICATE-----
  (Your intermediate certificate: intermed.crt)
  -----END CERTIFICATE-----
  -----BEGIN CERTIFICATE-----
  (Your root certificate: root.crt)
  -----END CERTIFICATE-----
  

  I had problems when I used the key extensions so I would say you don't use and don't create a very basic cert without extensions V3, as indicated on the right of the image to my last post (ideally, you want to have a cert with the same properties as the cert is used by the device of integrated vRO vRA unless of course different CN) etc.).

  2. use the vRO control center located at https://your-externa-vro:8283 / vco-controlcenter / #/ and move to--> Orchestrator Server SSL certificate certificates. Use the action to import to import your PEM cert. It should tell you that you need to restart your device vRO. Then RESTART the device (for not just restart the service, this seems not be sufficient).

  3 al ' vRA remove the Endpoint vRO everywhere wherever it has been configured. Also, I removed the vRO to the ASD config just to make sure that nothings left.

  4 reboot the vRA power (IAAS can be left as what). I needed to do this because I have seen that the keystore at some point would keep beeing crushed by CERT vRA (?), I deleted it (AND I checked that they are deleted) reappears in the keystore after a while. After a reboot, the problem was gone, the keystore was clean.

  5. Add the configuration of endpoint and ASD vRO. Accept the certificate.

  6. the works.

  Therefore, while I have no more time to solve the problems more than I guess the problem is the SHA1 function certificate generated by the device of vRO. The internal unit is equipped with a SHA2 based cert that works and after that change the external device SHA1 cert in a basic cert SHA2 all works.

• P2V fails @ 1% cannot create the VSS (0 x 80042316) snapshot

  Hi all

  I try to convert the old Win2k3 server in my environment vSphere using vCenter Converter Standalone (I tried version 5.0 and 5.5) and job is failing at the first % with the error:

  Failed: Failed to create a snapshot VSS of the source volumes. Error code: 2147754774 (0 x 80042316)

  On the source computer there is no error in the event log.

  PS. is there still chance to download vcenter converter prior to version 4.0?

  Thank you!

  Hello

  I had similar problem. Once the restart VSS services helped (or was that restarting the server?), in the second case, it did not help and we used the old version of the converter with bootable CD. I don't know where to download now, however.

• Lack of P2V - failed: error. ManagedDiskOpenFault.summary

  Hello

  I tried to use the 5.5 converter to convert a physical server Win 2008 R2, I used the local administrator to connect the physical, but labour failed to 1%, the error is FAILED: fault. ManagedDiskOpenFault.summary. I download the log file to analyze.

  Hello

  check if necessary firewall ports are accessible: KB VMware: VMware vCenter Converter 4.x/5.x required ports

  Creting the P2V job are you using the host name of the physical server and this solves by DNS control-workstation where the converter is installed?

  cykVM

• P2V fails after 1%

  I'm trying to convert a Windows XP PC, as a virtual machine on the server ESXi (3.5.0). I am using vCenter Standalone Converter 4.3.0. Still, the conversion fails at 1%. Someone has encountered this before and if so, how do I get this to work?

  Thank you very much.

  Hi Plamen,

  Thanks a lot for this sort. It was just to add to the source host file suggests. As a matter of interest matter what version of vCenter Converter Standalone client is used for P2V machines, based on the version of ESXi, they will be stored / race of?

• 5.0 VMware Server 2012 P2V fails with BSOD

  Someone at - it successful Windows Server 2012 with VMware 5.0 installation? I have not tried since an ISO, but when I tried a P2V server restarts periodically and says then there is a problem and that I should look for more information on the 'system thread unhandled exception (winhv.sys)' error as it collects more information!

  Thank you

  Mark

  Construction 623860 is ESXi 5.0 Update 1, so it's ok. You can find an overview of the large version/construction at http://vsphere-land.com/vinfo/release-build-info

  Roles that are installed in the system Windows 2012 (Hyper-V,...)?

  BTW. the converted virtual computer runs on a virtual IDE drive. During the conversion of a physical system, you must always set the type of appropriate ("LSI Logic SAS controller" in this case) in the Converter Wizard.

  André

• P2V fails with "error: an error occurred during the reconfiguration.

  Hi, we're starting everything just to P2V of our servers and start easy (I thought) qith our WSUS server. Every time I start the job fails on 98% with the error "error: an error occurred during the reconfiguration. I tried to re-boot, I tried to tell the wizard not to include a disk which is compressed. and I tried making minimal changes to the settings all with the same error...

  I don't know what to try next...

  I have attached the diagnostic logs in the hope that some kind soul can point me in the right direction...

  Thank you very much

  Matt

  Have you tried to remove the/3 GB switch to the boot.ini file?

• P2v fails after you have 'created' machine

  I am to convert a physical machine to the virtual. I have run the migration with the last update of the converter, select the machine, fill all the credentials as normal working I put on a lun CF with plenty of space. It starts the conversion, but once he 'created' vi machine he thinks thirty seconds, then work is the removal of the machine and the conversion fails gives an error "system FAILED error: found during surgery.

  Anyone have any idea why this is happening when I can convert to other machines without problem in the virtual environment

  Gregg

  Good for you

  André