Hi Mohit,
Hope you're doing well.
Q1:
The issue you're encountering with Kali Linux going blank with a ticking cursor after a restart in Hyper-V could be caused by several factors. Here are some steps you can take to troubleshoot and resolve the issue:
- Ensure that Hyper-V Integration Services are installed and up to date within the Kali Linux virtual machine. These services provide enhanced functionality and performance for virtual machines running on Hyper-V. You can install Integration Services from the "Action" menu in Hyper-V Manager while the virtual machine is running.
- Make sure that your Kali Linux installation is up to date with the latest updates and patches.
- Verify the display settings within Kali Linux to ensure they are compatible with Hyper-V. You may need to adjust the display resolution or other settings to resolve compatibility issues. You can do this by accessing the display settings through the Kali Linux desktop environment or command line.
- In Hyper-V settings for the virtual machine, enable Enhanced Session Mode if it's not already enabled. This mode provides enhanced integration features, including improved display and input device support. To enable Enhanced Session Mode, go to the virtual machine settings in Hyper-V Manager, select "Integration Services," and check the box for "Enhanced Session Mode."
- If Secure Boot is enabled in the virtual machine settings, try disabling it to see if it resolves the issue. Secure Boot can sometimes cause compatibility issues with certain operating systems or boot processes.
- In addition, you may need to reinstall Kali Linux. There may have been a problem with the initial installation or configuration that is causing the blank screen issue.
Q2:
Here are some steps you can take to troubleshoot and resolve this issue:
- Ensure that the disk where the virtual machine's files are stored has sufficient free space available. If the disk is full or nearing capacity, Hyper-V may encounter errors when attempting to create checkpoints or perform other disk operations.
- Make sure that no other programs or processes are actively accessing or using the virtual machine's disk files. If another process has locked the disk file, Hyper-V will be unable to create the checkpoint. Close any unnecessary programs or processes that may be using the disk file.
- If you have antivirus software installed on the host system, temporarily disable it and see if the issue persists. Antivirus software may sometimes interfere with Hyper-V operations, including checkpoint creation.
- Check the status of the virtual hard disk (VHDX) associated with the "server" virtual machine. Ensure that the disk file isn't corrupted and that there are no file permission issues preventing Hyper-V from accessing it.
- If none of the above steps resolve the issue, try manually creating a new checkpoint for the virtual machine from Hyper-V Manager. If the checkpoint creation fails again, it may provide more specific error details that can help diagnose the problem.
Best Regards,
Ian Xue
If the Answer is helpful, please click "Accept Answer" and upvote it.