This evening, I started with a
100%-patched-up-to-date Windows XP SP2 VM inside
Parallels (I ran Windows Update until there were no
more patches to apply). Then I went through the
whole migration, Windows re-install, and
HAL-replacement process. The VM's network still
worked.
Of course, the reinstall clobbered all those patches.
So I once again ran Windows Update until it had no
more patches. And then, once again, I did the
Windows re-install. The network still worked.
100%-patched-up-to-date Windows XP SP2 VM inside
Parallels (I ran Windows Update until there were no
more patches to apply). Then I went through the
whole migration, Windows re-install, and
HAL-replacement process. The VM's network still
worked.
Of course, the reinstall clobbered all those patches.
So I once again ran Windows Update until it had no
more patches. And then, once again, I did the
Windows re-install. The network still worked.
Brian, I really appreciate your efforts, outstanding support! I am glad I switched to VMWare.
I have now for the third time re-installed Windows into my working VM and for the third time I got the exact same result.
Strange, huh?
Now, using a text editor, edit the .vmx file. Delete
any lines that start off with ethernet0.virtualDev,
and put in a new line like this one at the very end:
[code]
ethernet0.virtualDev = "e1000"
[/code]
any lines that start off with ethernet0.virtualDev,
and put in a new line like this one at the very end:
[code]
ethernet0.virtualDev = "e1000"
[/code]
I did all that and guess what? It did not work.
First of all there was no ethernet0.virtualDev line in the vmx file. Here is the full .vmx file the way it was created by Fusion, I added the 'ethernet0.virtualDev = "e1000"' at the end:[code]
config.version = "8"
virtualHW.version = "6"
scsi0.present = "TRUE"
memsize = "512"
MemAllowAutoScaleDown = "FALSE"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "/Users/jens/Documents/Virtual Machines/Image from Parallels/Image from Parallels.vmdk"
ide1:0.present = "TRUE"
ide1:0.autodetect = "TRUE"
ide1:0.deviceType = "cdrom-raw"
floppy0.present = "FALSE"
usb.present = "TRUE"
ehci.present = "TRUE"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
pciBridge0.present = "TRUE"
isolation.tools.hgfs.disable = "FALSE"
displayName = "Windows XP"
guestOS = "winxphome"
nvram = "Windows XP.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
RemoteDisplay.vnc.port = "0"
tools.upgrade.policy = "upgradeAtPowerCycle"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.suspend = "soft"
powerType.reset = "soft"
svga.vramSize = "134217728"
mks.enable3d = "TRUE"
numvcpus = "2"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.writeAccess = "TRUE"
sharedFolder0.hostPath = "/Users/jens/Desktop/ShareWin"
sharedFolder0.guestName = "Sharewin"
sharedFolder0.expiration = "never"
sharedFolder.maxNum = "1"
uuid.location = "56 4d 20 89 82 b1 1c 9b-d6 4f 89 a2 d2 0a b8 59"
uuid.bios = "56 4d 20 89 82 b1 1c 9b-d6 4f 89 a2 d2 0a b8 59"
mks.keyboardFilter = "allow"
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
scsi0.pciSlotNumber = "16"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
tools.syncTime = "FALSE"
ide1:0.startConnected = "TRUE"
ide1:0.fileName = "auto detect"
ethernet0.present = "TRUE"
ethernet0.connectionType = "nat"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.addressType = "generated"
ethernet0.pciSlotNumber = "32"
ethernet0.generatedAddress = "00:0c:29:0a:b8:59"
ethernet0.generatedAddressOffset = "0"
ethernet0.virtualDev = "e1000"
[/code]
After starting up the VM and installing the Intel Software the network adapter shows again with a yellow "!". When I open the properties, it stops and says "failed to obtain the GUID" and then "Error getting the adapter Info" (See attached screenshots).
Please let me know if I can give you any further information to diagnose this.
Thank you so much for your support!
Jens
PS: I have used TextWrangler to edit the .vmx file
Attachments:
-
Screenshot_1.png (39.2 K)
-
Screenshot_2.png (39.9 K)
First of all there was no ethernet0.virtualDev
line in the vmx file.
line in the vmx file.
That's expected. The absence of that line just tells Fusion to assume the default kind of virtual Ethernet adapter. I just wanted to make sure you didn't accidentally wind up with two ethernet0.virtualDev lines in your .vmx file.
After starting up the VM and installing the Intel
Software the network adapter shows again with a
yellow "!". When I open the properties, it stops and
says "failed to obtain the GUID"
Software the network adapter shows again with a
yellow "!". When I open the properties, it stops and
says "failed to obtain the GUID"
Now that's interesting! May I suggest powering down the VM and editing its .vmx file once more, this time deleting all the lines that refer either to a UUID or to a Mac address. (Fusion will regenerate them, with fresh values, on power-on.)
So you'd delete these lines:
[code]
uuid.location = "56 4d 20 89 82 b1 1c 9b-d6 4f 89 a2 d2 0a b8 59"
uuid.bios = "56 4d 20 89 82 b1 1c 9b-d6 4f 89 a2 d2 0a b8 59"
ethernet0.generatedAddress = "00:0c:29:0a:b8:59"
ethernet0.generatedAddressOffset = "0"
[/code]
I am still concerned that this may not solve your problem, because I myself didn't have to do it when I moved my own XP VM to use the PRO/1000. But the Intel driver installer's complaint about a GUID is suggestive, so we might as well try.
By the way, do you have the Parallels VM from which the Fusion VM was cloned powered on during this time? I can't think of any reason why that would cause this problem, but I'm basically out of rational theories at this point, so we may as well start exploring the supernatural.
Anyway, let's not lose sight of the whole cost/benefit picture: ultimately, conversion is intended to save the time of rebuilding a VM from scratch. At some point, when weird conversion issues arise, troubleshooting them starts to cost more time than rebuilding. And this issue is quite weird. If I were you, I would start considering a rebuild under Fusion.
I also think that you should go find the guy at that Kuala Lumpur flea market and get your ringgit back.
I am still concerned that this may not solve your
problem, because I myself didn't have to do it when I
moved my own XP VM to use the PRO/1000. But the
Intel driver installer's complaint about a GUID is
suggestive, so we might as well try.
problem, because I myself didn't have to do it when I
moved my own XP VM to use the PRO/1000. But the
Intel driver installer's complaint about a GUID is
suggestive, so we might as well try.
Brian, unfortunately that did not fix it. Same results...
By the way, do you have the Parallels VM from which
the Fusion VM was cloned powered on during this time?
I can't think of any reason why that would cause
this problem, but I'm basically out of rational
theories at this point, so we may as well start
exploring the supernatural.
the Fusion VM was cloned powered on during this time?
I can't think of any reason why that would cause
this problem, but I'm basically out of rational
theories at this point, so we may as well start
exploring the supernatural.
No, I've deleted Parallels and the old VM after I successfully converted to Fusion. I even unplugged the Firewire Backup Drive to be sure...
I've also done the Windows "upgrade" a fourth time, this time to a ACPI Uniprocessor HAL, same results.
Anyway, let's not lose sight of the whole
cost/benefit picture: ultimately, conversion is
intended to save the time of rebuilding a VM from
scratch. At some point, when weird conversion issues
arise, troubleshooting them starts to cost more time
than rebuilding. And this issue is quite weird. If
I were you, I would start considering a rebuild under
Fusion.
cost/benefit picture: ultimately, conversion is
intended to save the time of rebuilding a VM from
scratch. At some point, when weird conversion issues
arise, troubleshooting them starts to cost more time
than rebuilding. And this issue is quite weird. If
I were you, I would start considering a rebuild under
Fusion.
Yes, I think I'll just stop here. I think it'll be better if I just setup a new VM from scratch.
Would you recommend a free backup software so I don't have to re-install all the software?
I also think that you should go find the guy at that
Kuala Lumpur flea market and get your ringgit back.
Kuala Lumpur flea market and get your ringgit back.
I don't think I'll have too much luck with that either...
Again, thanks so much for your help!
Have a great day!
Jens
