In windows 10 the PCI device and the PCI Simple Communications Controller have the missing driver icon.Right click on the PCI device and select update driver -> click on Browse my computer for driver softwareSpecify the cdrom as the search location and click Next, this will install the Balloon driver.
Because I realized my process many times and because I didn't wrote it before this howto, I may omit something. Please contact me if you got any problem while trying to create your master XP image. I gave so many hours to set up this receipe that I certainly encounteered a problem you may encounteer too. Use the discussion page for this howto to get an answer.
I managed to create a windows XP FOG image virtually able to run on any hardware configuration. My goal is to have one and only one FOG image for this operating system. I'm currently working with 2 FOG images:
After days trying to boot with a single image, I found that there is an issue with disks related to the 128 GB limit and the BIOS setting LARGE/LBA. I didn't found the exact thing which causes the blinking cursor of death while working on my receipe. That's why I decided to use 2 FOG images, as described above. I only know there is someting wrong related to the partition boot code in a NTFS partition (see this interesting page about NTFS partition boot code).
I successfully tested both images I did on an 10 GB disk and a 160 GB disk on some systems. It seems my first tries were on a computer with a compatibility issue, I couldn't find for now. There is a chance only one XP image will work on any disk size. You may create only one XP installation and use it on all drives size you can find.
When running VMWare player, the guest OS runs on a CPU similar to the physical CPU running the virtual machine. If you install windows XP on an non-intel CPU, the Intelppm service will not install. Therefore, you must use an physical Intel CPU to run your virtual machines.
Therefore, I advice you to use VMWare Player only for testing purposes. When you feel ready for production, consider using a physical Intel based computer to create your master image. You will have to follow this how-to on your physical computer, exactly as you would do (or already done) on your virtual machine.
Install windows XP in a regular way, and use if possible a SP3 CD or ISO image. Do not install windows XP with the zero touch method provided by VMWare player. Install all hotfixes, .NET Frameworks, last version of IE. Do not install VMWare tools, or any driver. Do not install any software (adobe reader, java, office or any frequently used software) You can install them using FOG's Snapin feature. Do not activate your windows installation (if you used Home, Professionnal or Media Center)
Use Autoit to compile this script into an exe. This is for french windows XP ! Edit the file with the three lines below to make it for english windows XP. The new exe file must be in c:\\sysprep.
If you didn't captured a FOG image of your master (virtual) computer before launching the reseal process do it now. If something goes wrong while sysprep is running, you may be happy to have an easy roolback.
Note: I read somewhere that sysprep is alternatively long and fast. I saw that is true. If you want to add a single driver for a new hardware, you may deploy a master computer with your sealed XP image and re-seal it a second time with your new driver. (use the sysprep folder you ever keep near you in an USB stick).
With a 100 Mb/s network my images are about 1.5 GB and are downloaded in less than 2 minutes. After some reboots your windows XP is ready. From the image push to a working desktop on the target computer, the elapsed time is less than 10 minutes.
I noticed this issue after I released my second version of disk image for my own purpose. I checked my first disk image and it works well. I did some tries on my virtual machine: install the universal USB driver instead of the intel one, create my XP instalation withou plugging any USB device, and installing windows on a VM without any USB port. None of these tries was successful. I'm nearly sure that the only workaround is to create your master XP image from a physical computer. The major difference between my first final image and my second one is virtualization. I'm nearly sure building the master XP installation on a pure physical computer will work better with USB. I'll give a try soon.
A found a computer with ATI chipset which doesn't work with SATA when it is set to AHCI mode or native mode (deployed with XP). I had to set the SATA to IDE mode. Googling showed a similar problem on a gigabyte mainboard with the same ATI chipset, whereas windows has been installed a classic way. A change on the driver's .inf file found in a forum didn't help. If performance is not critical, try to use IDE (or legacy) mode in the BIOS setup.
NOTE Although the final image will be around the same size as the actual amount of data on the server, the Proxmox VE server should have enough free space to fit the total physical disk of the server unless you plan to shrink the windows disks. once migrated to Proxmox VE.
NOTE: Depending on your hardware, you may need to boot the .vmdk file using VMware Workstation or Player before moving the file to the Proxmox VE server. This allows windows to install additional drivers for the disk controller. If promoted to convert the disk to Workstation 9.x compatibility, say Yes. You won't know if you need this step until starting the Windows VM in the final step. If you get a blue screen during boot, you should try this step.
In VMware ESXi navigate to your virtual machine in the tree on the left.Choose Actions->Export.This will download disk images and information about your virtual machine in the .ovf format in the browser.Move those files to a storage that is accessible by your Proxmox VE host.
With some configurations you get a single (.ova) archive file that contains all .vmdk disk images and the small XML description .ovf file. If this is the case, then you have to extract it before you continue with qm importovf.
In the next step the some-image.img refers to the disk image you want to import and the some-storage refers to the name of a target storage, as listed in pvesm status.Please adapt those to the respective values.
This document explains the common pitfalls and how to workaround these. We assume that either a physical Windows installation or a VMware image is the source of migration. It is also assumed that a suitable virtual disk image (either VDI or VMDK for VirtualBox >= 1.4) is already present.
For reasons we don't understand, Windows memorizes which IDE/ATA controller it was installed on and fails to boot in case the controller changes. This is very annoying because you will run into this problem with basically all migrated images. The solution here is to perform several modifications to the Windows registry. This can be done while the installation is still running on the original system because all it does is relax the IDE checks. Therefore the installation will continue to work on the original system after the modification.The easiest way is to use the excellent MergeIDE utility from the German c't computer magazine. Alternatively, instructions in Microsoft's knowledge base article can be followed:
When the AutoPlay window is displayed (prompting you to run the VBoxWindowsAdditions.exe program) as shown in Figure 6.12, close the window without installing the Guest Additions. Closing the window leaves the ISO image used to install the Guest Additions inserted in the virtual CD/DVD drive. You need to install the VirtualBox Guest Additions from the command line to get all the features we need.
Yeah I went to these instructions: _Windowsbooted off of an install disk image and ran the repair installation option and that did fix it. Now it boots up. Still, that was a lot of trouble to go through and Windows even insists on immediate \"activation\". There's probably a better way.
Make sure, that you deinstall the vmware-tools before you start. On my pc, the vmware-tools cant be removed when the machine is not running under vmware.And the vmware-tools keep a hand on the virutal network cards, even when running in VirtualBox.
About VMware PlayerVMware Player, which offers free software to host virtual machines, can run guest virtual machines produced by other VMware products, but cannot itself create new virtual machines. VMware's website provides many free virtual-disk images of preconfigured operating-systems and applications, many of them community-contributed. Freeware tools also exist for creating VMs, mounting, manipulating and converting VMware disks and floppies, so VMware Player users can create, run and maintain virtual machines for free (even for commercial use).VMware Player Features. Copy and paste. Copy text and files between the virtual machine and the host PC. Drag and drop. 153554b96e