Was it wishful thinking....

[grayfox]

I pushed a Win 7 Fusion ( Mac VMWare) set of VMDK files over to my Fedora Boxen and
tried to create a new VirtualBox VM on the Fedora box using the VMDK's.

I got the 'Starting Windows' display but quickly got a blue screen which (too quickly to read)
changed to a reboot screen from windows ( that claimed damage to win 7).

Is it even possible to port a Fusion VM to Virtual Box?

Thanks for any insights...

Jerry

[vbox4me2]

I think its wishful thinking you get help without providing info we can use, no bsod info, no vm settings from either vmware or vbox, you've been here since 2008, what do you expect? mind-reading or something?

[grayfox]

I think its wishful thinking you get help without providing info we can use, no bsod info, no vm settings from either vmware or vbox, you've been here since 2008, what do you expect? mind-reading or something?

Sigh, no mind-reading, but it would be nice to find a discussion of how to port to VBox, if possible.

Mac Info:
Mac Fusion 3.1.3, Win 7 VM, 1 GB memory allocated, 1 cpu allocated, 20GB Hard Disk (SCSI), Bridged Networking.

What would I have to do to move the Win 7 VM to Virtual Box on a Fedora System (i7 based) running the latest VBox ( 4.1.?)

*AS NOTED* Blue Screen zips by too fast to read.

Jerry

[vbox4me2]

Was it paused/savestated? VM settings identical such as MAC and UUID's? can you get into safemode(f8)? what if you create a new vm and attach vdi? IO APIC used (flip it)?

[ChipMcK]

VMware to VBox considerations
1. VMware tools do not run under VBox - uninstall before bringing vmdk files to VBox
2. Hardware configuration

• Problem areas
  • What kind of drive: ide/scsi
    what kind of controller for the drive
  Where to start
  • Back under VMware, scope out the config (make notes)
    If Windows, Computer Mngmnt - Device Manager and Disk Mngr

Couple of years ago, I moved some vms over to VBox
There is a separate forum for having a OS X host "VirtualBox on Mac OS X Hosts"
Best of Luck

[grayfox]

Some more info:

I did the f8 thingee and selected safe boot.
Got at hang on loading agp440.sys followed by a reboot shortly thereafter

I did the f8 thingee and selected no automatic reboot
Got a stop 7b error with code 0xc00000034

Does any of this ring a bell

Jerry

[ChipMcK]

As I remember, 0x007b is when the controller and the drive are a mismatch -- like a ide on a scsi controller

[mpack]

agp440.sys needs to be disabled. In fact I'm surprised it got loaded on VMware - I doubt the latter emulates an AGP graphics bus.

[grayfox]

agp440.sys needs to be disabled. In fact I'm surprised it got loaded on VMware - I doubt the latter emulates an AGP graphics bus.

I unloaded VMWare Tools, stopped the Fusion VM and copied it to the Fedora box.

It still dies at the agp440.sys loading ( or shortly thereafter....)

How can I disable the agp440.sys thingee, keeping in mind that I am just a simple
minded Windows user ;(

Do I need to worry about disk uuids?

Thanks

Jerry

[BillG]

What is a simple Windows user doing with Mac VMWare files in Unix?

[grayfox]

What is a simple Windows user doing with Mac VMWare files in Unix?

The simple minded was a reference to Windows...

I have more than a passing acquaintance of Mac/Linux stuff.

http://homepage.mac.com/levanj

Actually that probably should read 'at one time', after seventy three years
the rust is starting wear me down...

Jerry

[BillG]

Moving pre-installed vms from one virtualization product to another has plenty of problems (apart from the additions which optimize performance for the particular system used, like VMTools and guest additions). The "hardware" used by each product is different, so the OS has drivers for devices which are not there and does not have drivers for the devices which are.

VirtualBox is better than most because you have more ability to tailor the "hardware" in the vm to match up with the hardware config you have on your virtual hard disk, but there are limits. If the differences are too great, the OS will not boot. You would then need to repair-install the OS to fix up the driver problems. With a Windows OS you have the added problem of activation if the hardware changes much.

There are commercial v2v programs which handle this sort of thing but even those may fail if they strike something unusual which has not been built into the program.

[vbox4me2]

How can I disable the agp440.sys thingee, keeping in mind that I am just a simple
minded Windows user ;(

Boot the VM with a linux liveCD and access the VM disk, rename the driver.
A boot in safemode can work too, then use a cmd prompt.

[mpack]

The complete filename is \Windows\System32\Drivers\agp440.sys. You need to rename or delete that file, using another VM as suggested by Vbox4me2. While you're at it you should also rename or delete intelppm.sys, as that could well be the next driver problem you run into.

[grayfox]

Sigh,

I downloaded a live Fedora iso and booted the rascal in the VM. I was able to mount the
Win 7 VM disk and I renamed the AGP440.sys and the intelppm.sys files.

It did no good, I get the same error codes.

I suspect that the error comes after the drivers are loaded.

I have fiddled with changing various hardware options in the VM but to no avail...

I will keep an eye open for any success stories...

Thanks for bearing with me.

Jerry