|
|
10.5: Virtualize machine-specific 10.4 in Fusion 2
Well, I can't get past step 2. Obviously it's a VMWare/VMDKMounter issue, but I thought I'd ask in case anyone has experienced this.
10.5: Virtualize machine-specific 10.4 in Fusion 2
I, too, had problems mounting VMs some time ago; now, anyway, I have the latest versions of Leopard, Fusion, and MacFuse (installed separately): so it shouldn't be a version problem. Maybe you could try to reinstall the latest MacFuse from their website, and then reinstall Fusion...?
10.5: Virtualize machine-specific 10.4 in Fusion 2
Thanks for that Sven. Since I tried both, I agree the version of Fuse was probably not the issue and will upgrade again when I get a chance. I haven't really gotten much use out of Fuse lately; I need to check for any new "filesystems" out there that may be of more use.
10.5: Virtualize machine-specific 10.4 in Fusion 2
On my experimental Tiger VM (the one described in the hint), NAT networking works flawlessly, while bridged mode doesn't connect (at least the first time I booted): it looks similar to a problem I had in Ubuntu with bridged networking, where I had to edit /etc/sysctl.conf, adding these lines:
10.5: Virtualize machine-specific 10.4 in Fusion 2
Both NAT and Bridged appear to work fine after a reboot of the host. Pshaw! I rebooted after reinstalling VMWare so I didn't think to do it again.
10.5: Virtualize machine-specific 10.4 in Fusion 2
Same here: both NAT and bridged mode now work in my experimental Tiger VM, too - at least, this problem is solved! ;-) :-) |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.07 seconds |
|