philippeannet's Posts

The situation is not black/white... from all my VM's (9), only one had trouble (corrupted file system inside the VM) after I had restored my Mac (2TB SSD, 1.3 used). So while I'll definitely put som... See more...
The situation is not black/white... from all my VM's (9), only one had trouble (corrupted file system inside the VM) after I had restored my Mac (2TB SSD, 1.3 used). So while I'll definitely put some additional measures in place to snapshot complete VM's from time to time, TM's ability to revert to some precise moment can be quite handy... I'm running TimeMachine on Synology with an 8TB disk (which is used only for my Mac), so I can certainly grab a few hundreds GB to snapshot the VM's from time to time on top of the TM backup.
well... you don't control that once TM is in auto mode... yes, some backups are taken while VM's are running obviously, and some not... But it's definitely a good lesson: DO NOT COUNT on TimeMachine... See more...
well... you don't control that once TM is in auto mode... yes, some backups are taken while VM's are running obviously, and some not... But it's definitely a good lesson: DO NOT COUNT on TimeMachine for taking VM backups ! I'm still not 100% sure, as I tried many 'variations', from the very first version I had (January 2022, til November 2022), and none of these worked correctly. The most 'plausible' explanation being that some file(s) of the earliest backup I have of that VM was or became corrupt, and I did not restore anything since January this year, so I didn't notice that. I'm likely to be able to reconstruct the missing or corrupt files to some extent, but gee, what a useless way to spend one's time...
Yes... TM used to backup the whole Mac. And all my VM's are stored locally. It's not the first time I restore my Mac (or change Mac), never had trouble. My impression is indeed that some 'root' file... See more...
Yes... TM used to backup the whole Mac. And all my VM's are stored locally. It's not the first time I restore my Mac (or change Mac), never had trouble. My impression is indeed that some 'root' file has somehow became corrupt on TM, and that would explain why, whatever version I restore, I get the same file-system issues (which I did NOT have at the date the backup is from)... If the TM backup was fine, I should be able to restore a working version of that VM, by getting back to some date in the past 10 months, but that doesn't work for me. Strange though that just that one VM is affected...??
just looking for someone who maybe came across similar issue(s). My 2019 MBP had a h/w issue, and had its mainboard changed (thus ssd inclusive). I was using the last 12.x Fusion Pro, with macOS Mo... See more...
just looking for someone who maybe came across similar issue(s). My 2019 MBP had a h/w issue, and had its mainboard changed (thus ssd inclusive). I was using the last 12.x Fusion Pro, with macOS Monterey 12.6.1. The repaired Mac came back with Ventura installed. After restoring the latest Time Machine backup, I had many compatibility issues reported by macOS, and I decided to upgrade to Fusion 13, something I'd have done soon anyway. Then, when I booted my Windows (10, 7, XP) VM's, it just asked whether they were copied or moved, and whether or not to upgrade these. They all started flawlessly. My Ubuntu 16.04 instead didn't boot, booting only showed the Grub menu, but no disk. I Looked in the logs but found nothing to chew, then I started the VM from CD (Ubuntu 22.04), and mounted the disk (/dev/sda1). I reported quite a bunch of errors, so I ran fsck, but afterwards many files (in particular, those I really needed...) contained just garbage... The very strange thing, is that I know I've used that VM successfully many, many times in the last past months, and now, regardless what backup I take from Time Machine (got about 10 months of history), 1) it doesn't boot, and 2) if I start from a live Ubuntu, the same files are always corrupted... Something looks basically wrong here (why the heck can't I start any of the previous versions of that VM), but I really can't figure out what... any idea/suggestion welcome.
  This discussion is basically not really relevant... I'm running a bunch of x86 and x64 VMs on my Intel MBP, and I'll continue to do so... Regardless how good the emulator, I'm not willing to put ... See more...
  This discussion is basically not really relevant... I'm running a bunch of x86 and x64 VMs on my Intel MBP, and I'll continue to do so... Regardless how good the emulator, I'm not willing to put any additional sources of problems on my way, just for the sake of NOT keeping my Intel Mac... Yes, it would be nice, but even if it was supported, at the slightest problem, you'd have to suspect the emulator, and any fix would undoubtedly require weeks, or even months to pop up... something professionals can't live with ! And as we have absolutely no clue on what will be working or available in 12 months from now, this debate is not likely to come to a sound conclusion... just some sort of 'religious' thoughts and wishes... So, for the foreseeable future, fact is: professionals will stick to Intel Macs for Intel VMs, and have another (ARM) Mac for whatever they need it for. 
I doubt that’s Apple’s strategy... if they were convinced that most of their users were dependent on x86 code, they wouldn’t have made the M1 move at all. I guess their bet is that mature and perfor... See more...
I doubt that’s Apple’s strategy... if they were convinced that most of their users were dependent on x86 code, they wouldn’t have made the M1 move at all. I guess their bet is that mature and performant Mx versions of 99% of all packages will be available by the time the move will be completed... and that x86 dependent users will stick to x86 Macs in the mean time. And the fact that Windows on ARM is likely to somehow catch up in that timeframe as well, won’t push Apple to further invest in full x86 backward compatibility...
I don't know why people are expecting this... it was already stated many times that an ARM version of Fusion will NOT run Intel guests. It would be nice, but as Apple is not ready to share its Intel ... See more...
I don't know why people are expecting this... it was already stated many times that an ARM version of Fusion will NOT run Intel guests. It would be nice, but as Apple is not ready to share its Intel emulator, nor Parallels, nor VMWare will do the huge (!!!!!!!) investments required to develop their own...
Same here !!!!! (Icy Box, i.e. SATA USB 3.0 bridge from JMicron). Had to add the usb.generic.keepStreamsEnabled="FALSE" line in the VMX for it to work in Fusion Pro 11.5, but since the 12 upgrade, n... See more...
Same here !!!!! (Icy Box, i.e. SATA USB 3.0 bridge from JMicron). Had to add the usb.generic.keepStreamsEnabled="FALSE" line in the VMX for it to work in Fusion Pro 11.5, but since the 12 upgrade, no luck !!   :(( VMs are W7 SP1, both x86 and x64, same issue.     Come on VMWare, fix this !!!!!!!!!!
  unable to have JMicron SATA bridges (IcyBox & similar) connected to a Windows 7 VMs under Mac OS Big Sur & Fusion Pro 12.1. Trick with the usb.generic line in the VMX helped solving the issue wit... See more...
  unable to have JMicron SATA bridges (IcyBox & similar) connected to a Windows 7 VMs under Mac OS Big Sur & Fusion Pro 12.1. Trick with the usb.generic line in the VMX helped solving the issue with Fusion 11.5, but since 12, it's no longer working. Without the line neither... The device shows as a USB Mass Storage Device in the device manager, but after a while, it fails, with status "This device cannot start. (Code 10)" Problem is identical with x32 and x64 versions of W7. Yes, latest Intel USB 3.0 drivers installed. Tried more or less everything suggested here in the forum for similar problems, without luck so far.
Hello, just re-ran the W7 perf index in a VM that was copied from a 4.5 years old MBP 15" to the latest MBP 15" (3.1Ghz, Radeon 560 4GB), and guess what....  ZERO (positive) changes !!!!!! Gra... See more...
Hello, just re-ran the W7 perf index in a VM that was copied from a 4.5 years old MBP 15" to the latest MBP 15" (3.1Ghz, Radeon 560 4GB), and guess what....  ZERO (positive) changes !!!!!! Graphics index dropped from 6.5 to 6.0... While I'm still pretty happy with the old MBP, it seems almost unbelievable that the perf hasn't improved a bit (or worse, that it declined...), especially at the graphics level... I did setup the Mac to use ONLY the discrete graphics card. Latest VMWare tools installed, of course... Any ideas/hints ???
Confirmed: the enableGLbasicRenderer does NOT fix the issue for me !
just set the enableGLBasicRenderer trick... will report soon if that brings help...
Same story here...   crashes with W7 Ultimate x86, using Word, recurrent system crashes... everything freezes, touch bar inclusive... Hard reset needed... Since months... unacceptable !!