I used Paragon Go Virtual to create a Virtual Image (I hope I am using the correct term).
I specified Oracle VirtualBox as the format.
A file with a 'vmdk' suffix was created.
According to the instructions on Paragon's Web site the steps to import this image are:
1. File / Import Appliance
2. Browse to the 'vmdk' image (which I have copied to the local hard disk of the Virtual Host computer).
VirtualBox is looking for a file with a 'ovf' extension and ignores the file from Paragon.
I then added the 'vmdk' file using the Virtual Media Manager but it is still being ignored during the Import Appliance.
This is my first attempt at importing an appliance and I really appreciate all assistance.
Thank you in advance.
Importing a Paragon Go Virtual VMDK
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Importing a Paragon Go Virtual VMDK
During the creation of the VMDK file it will also create the OVF file. You need both in the same directory to be able to import the package.
See Chapter 1.11. Importing and exporting virtual machines in your VirtualBox users manual.
See Chapter 1.11. Importing and exporting virtual machines in your VirtualBox users manual.
-
allanc
- Posts: 14
- Joined: 5. Nov 2009, 02:48
- Primary OS: MS Windows XP
- VBox Version: OSE other
- Guest OSses: XP PRO
Re: Importing a Paragon Go Virtual VMDK
Yes, Thank you.Perryg wrote:During the creation of the VMDK file it will also create the OVF file. You need both in the same directory to be able to import the package.
See Chapter 1.11. Importing and exporting virtual machines in your VirtualBox users manual.
I did not notice the 'ovf' file on the external hard drive that I used to transfer the files between computer.
I think it is because the file was so small and had a different prefix compared to the VMDK.
Now, I have a Blue Screen of Death when I run the client in regular Windows Mode which does not occur in Safe Mode.
Do you happen to have an efficient method to track this down?
There is no indication on the BSOD of any .dll , .sys, etc that may be causing the crash.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Importing a Paragon Go Virtual VMDK
This usually means a driver issue or the selected options do not match the second machine.
Common problems are IO APIC on in the guest settings when the original was not setup for SMP.
Common problems are IO APIC on in the guest settings when the original was not setup for SMP.
-
allanc
- Posts: 14
- Joined: 5. Nov 2009, 02:48
- Primary OS: MS Windows XP
- VBox Version: OSE other
- Guest OSses: XP PRO
Re: Importing a Paragon Go Virtual VMDK
Is this setting something I change on the source XP machine as part of the Paragon Go Virus process?Perryg wrote:This usually means a driver issue or the selected options do not match the second machine.
Common problems are IO APIC on in the guest settings when the original was not setup for SMP.
Or, on the Virtual Machine Host before I import the appliance?
In the Virtual Client settings there is a warning to not disable the IO APIC settings after having installed a Windows Guest operating system.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Importing a Paragon Go Virtual VMDK
Just after the import and before you start the guest for the first time.
Take the check out of IO APIC and see if it works. You are trying to make an OS that already has drivers and settings installed work in a different computer (emulated)
Take the check out of IO APIC and see if it works. You are trying to make an OS that already has drivers and settings installed work in a different computer (emulated)
-
allanc
- Posts: 14
- Joined: 5. Nov 2009, 02:48
- Primary OS: MS Windows XP
- VBox Version: OSE other
- Guest OSses: XP PRO
Re: Importing a Paragon Go Virtual VMDK
I do not think that it resolved the issue.Perryg wrote:Just after the import and before you start the guest for the first time.
Take the check out of IO APIC and see if it works. You are trying to make an OS that already has drivers and settings installed work in a different computer (emulated)
Safe mode loads a lot of drivers and then hangs after hotcore3.sys.
Regular Windows mode just displays a black screen and then nothing happens.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Importing a Paragon Go Virtual VMDK
http://www.google.com/search?q=hotcore3.sys+paragon
Seems they have a problem (paragon), plus their support site is down at the moment.
Seems they have a problem (paragon), plus their support site is down at the moment.