After creating a Windows 11 ISO, which involves rather intensive writing to disk AND copying the ISO-file using VMware sharing functionality AND system being idle for some time (an hour or two), the next shutdown was hanging. If you make sure that the disk that you use, is doing something while you shutdown Win10 VM, perhaps putting the disk to sleep isn't possible?Īfter all, I was able to reproduce the problem. Windows 10 version is H2 something, very recent.) I don't have any high-end, recent graphics adapter. (System resources were OK, about 6/16 GB allocated, 2/4 cores on i7 were used and like the description tells, system was basically idle while hanging. Since all attempts to use the extra, internal disk, I think the entire system would have hanged if a system disk is used for VMware. My entire system didn't hang up, but that was because it was NOT a system disk, where my VMware was located on my workstation. There are kernel modules in VMware and I guess this is possible (somebody confirm this, please).
So, perhaps a Linux guru could say what has happened, but it kind of looks like VMware shutdown does something horribly wrong for the disk and puts it into sleep in the middle of the shutdown process. Finally it didn't really shut it down but rebooted the system. Then it did (all this was part of the shutdown process) try to unmount and re-mount the disk a few times and failed. That took a very long time, when it tried to send kill the processes several times (including vmware and nautilus) and failed in doing so. I was able to open up a Terminal (so Linux was not frozen) and give "shutdown now". Shutdown was hanging but now there were more applications where it said that disk is put to sleep.
It indeed didn't work, it didn't show up files (other than those that came from the buffer). So, I tried to activate the extra, internal disk with opening Nautilus. According to Kubuntu System Monitor, system didn't do anything, but I said that disk had been put to sleep. Shutting down froze with Windows 10 VM, Host Kubuntu 20.04.2. Not sure why this is, but I got my suspicions today.
0 kommentar(er)
