Virtual Machines
1080
Total Pages
1005
Linux-Friendly Pages
75
Pages with Bias
6.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
815 issues found
Showing 526-550 of 815 flagged pages
Virtual Machines
Enable shared disks for Azure Managed Disks
.../main/articles/virtual-machines/disks-shared-enable.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell examples are consistently present and often shown alongside or immediately after CLI examples. PowerShell is a Windows-centric tool, and its heavy presence may create a perception of Windows bias. However, Azure CLI examples are always present and are cross-platform. There are no missing Linux examples, and the documentation explicitly states applicability to both Linux and Windows VMs. No Windows-only tools or patterns are mentioned, and the documentation avoids Windows-specific terminology or instructions.
Recommendations
- Consider explicitly mentioning that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Where PowerShell is referenced, clarify that it is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- If possible, provide bash shell script examples for mounting disks to Linux VMs, especially in the 'Using Azure shared disks with your VMs' section, to further improve Linux parity.
- Add a note in the prerequisites section indicating that Azure CLI is recommended for Linux/macOS users.
Create Pull Request
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally Linux-focused and provides parity between Azure CLI and Azure PowerShell examples for managing VM extensions. However, PowerShell examples are given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. In several sections, PowerShell examples are presented immediately after CLI examples, and the introductory text mentions PowerShell as a method for managing extensions, which may create friction for Linux users who typically use Bash or CLI. Additionally, references to PowerShell are not always accompanied by explicit notes about cross-platform support, potentially confusing Linux users.
Recommendations
- Clearly indicate that Azure PowerShell is cross-platform and can be used on Linux and macOS, or prioritize Azure CLI examples for Linux documentation.
- Present Azure CLI examples before PowerShell examples in all sections, or group PowerShell examples in a separate section for users who prefer it.
- Add Bash script examples where relevant, especially for troubleshooting or automation tasks.
- Explicitly state in the introduction that Azure PowerShell is available for Linux, or link to installation instructions for Linux/macOS.
- Review all references to PowerShell to ensure they do not imply Windows-only usage.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation is focused on Linux, but Windows bias is evident in several areas: PowerShell deployment instructions are provided before Azure CLI instructions, and PowerShell is referenced for troubleshooting and deployment. Azure CLI examples are present, but PowerShell is often given first or exclusively in some troubleshooting sections. There are also references to Windows tools and patterns (e.g., PowerShell, backslash escapes), even though the extension is Linux-specific.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more relevant for Linux users.
- Ensure troubleshooting sections provide Azure CLI commands first, or exclusively, for Linux-focused documentation.
- Remove or minimize references to Windows-specific issues (such as PowerShell escape sequences) unless they are critical for Linux users.
- Where PowerShell is mentioned, clarify its relevance for Linux users (e.g., if using PowerShell Core on Linux).
- Add explicit notes about using Bash or other Linux-native scripting environments for deployment and troubleshooting.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples for deploying the extension, and in some sections (e.g., troubleshooting), PowerShell commands are presented before Azure CLI equivalents. This may create friction for Linux users, as PowerShell is not a native or common tool on Linux. However, Linux-specific instructions and examples are present throughout, and Azure CLI examples are included alongside PowerShell.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more native and widely used on Linux.
- Clearly indicate that PowerShell is optional and primarily for users on Windows or those who have installed PowerShell on Linux.
- Consider removing or de-emphasizing PowerShell examples in Linux-focused documentation, or move them to an appendix or a 'Windows users' section.
- Ensure troubleshooting and deployment instructions prioritize Linux-native tools and workflows.
Virtual Machines
Deprovision or generalize a VM before creating an image
...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, the Windows section includes more detailed prerequisites and troubleshooting steps, and Windows-specific tools (Sysprep, PowerShell) are mentioned. The Linux section is concise and references external distro-specific guides, but both platforms are covered. The Windows section appears after Linux, so there is no 'windows_first' ordering bias, but Windows-specific tools are naturally referenced for Windows VMs. No critical Linux parity issues are present.
Recommendations
- Expand the Linux section to include troubleshooting tips and common issues, similar to the Windows section.
- Add more detailed step-by-step instructions for Linux, including verification steps after deprovisioning.
- Ensure parity in guidance for disk encryption and supported roles/services for Linux distributions, if applicable.
- Consider linking to Linux-specific troubleshooting resources, as is done for Windows.
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform and covers both Linux and Windows. However, there is a subtle Windows-first bias in the 'Recommended OS for Performance' row, which lists Windows Server 2019+ as the recommended OS without mentioning any Linux equivalents. Additionally, while Linux is referenced (e.g., in the lstopo example and OS support for SRIOV RDMA), there are no explicit Linux performance recommendations or Linux-specific best practices, and the only explicit OS recommendation is for Windows.
Recommendations
- Add recommended Linux distributions (e.g., RHEL, Ubuntu, SLES) for performance parity in the 'Recommended OS for Performance' section.
- If Windows Server is recommended for specific features, clarify what those features are and whether Linux alternatives exist.
- Provide Linux-specific best practices or tuning guidance if available, especially since most HPC workloads on HBv3 are likely to run on Linux.
- Consider listing Linux and Windows recommendations together, or in alphabetical order, to avoid implicit prioritization.
Virtual Machines
Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines.
...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows benchmarking (DISKSPD) first, with detailed parameter explanations and example commands, before introducing Linux benchmarking (FIO). The Windows tool DISKSPD is discussed in depth, while FIO for Linux is covered in a separate section. Both platforms are addressed, but Windows is prioritized in ordering and tool discussion.
Recommendations
- Reorder sections so that Linux (FIO) and Windows (DISKSPD) tools are presented equally, or alternate which platform is shown first.
- Provide a summary table comparing DISKSPD and FIO usage for both Windows and Linux, including installation instructions and example commands.
- Ensure parameter explanations and example commands are equally detailed for both tools.
- Add explicit guidance for benchmarking on macOS, if relevant, or clarify platform limitations.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, there is a notable Windows bias: Hyper-V (a Windows-only tool) is consistently presented first in all sections and examples, and references to Windows tools (Hyper-V Manager, convert-vhd cmdlet) are prominent and often precede Linux alternatives. Linux hypervisors and tools are covered in detail, but are positioned after Windows-centric instructions, which may create friction for Linux/macOS users.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V, or at least provide a neutral ordering.
- In introductory notes, mention Linux-native tools (e.g., qemu-img, guestfish) alongside Windows tools, rather than referencing Hyper-V Manager and convert-vhd first.
- Where possible, provide parity in detail and clarity for Linux-native workflows, ensuring they are not dependent on Windows tools or terminology.
- Consider adding a summary table or flowchart at the top to help users quickly identify the relevant workflow for their platform.
- Explicitly state that Hyper-V instructions are for Windows users, and Linux/KVM/VMware instructions are for Linux/macOS users, to reduce confusion.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows guidance, but there is a mild bias in example ordering and language. In the PowerShell section, Windows is shown first in the example, and Linux is mentioned as an alternative. CLI and REST examples are Linux-first. The page does not exclusively mention Windows tools or patterns, and Linux examples are present throughout. However, PowerShell is a Windows-centric tool, and its presence may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- In PowerShell examples, show Linux as the primary example or provide parity by alternating which OS is shown first.
- Explicitly mention that PowerShell can be used cross-platform, or provide Bash/CLI alternatives for all tasks.
- Ensure that Linux and Windows are equally represented in all example code blocks and explanations.
- Consider adding a note for macOS users about CLI usage and any platform-specific considerations.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first or in greater detail. Some sections, such as prerequisites and backup instructions, reference PowerShell cmdlets before CLI equivalents. PowerShell scripts are more verbose and detailed, while CLI examples are concise. There is no evidence of missing Linux examples or exclusive Windows tools; however, the prominence and order of PowerShell content may create minor friction for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and native to Linux.
- Ensure parity in detail and explanation between CLI and PowerShell sections.
- Explicitly note that Azure PowerShell can be used on Linux/macOS via Cloud Shell or installation, to avoid confusion.
- Where possible, highlight CLI as the recommended method for Linux users.
- Review backup and prerequisite instructions to ensure CLI commands are equally prominent.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is overwhelmingly Linux-focused, with all main examples and instructions tailored to Linux distributions (Ubuntu, SUSE, Red Hat). However, a single section at the end provides a PowerShell script for classic VM SKU support, which is Windows-centric and lacks a Linux CLI equivalent. This is a minor bias, as the PowerShell script is only for SKU discovery and not for the core disk expansion tasks.
Recommendations
- Provide an Azure CLI or Bash equivalent for the PowerShell script used to determine VM SKU support for expanding disks without downtime, ensuring Linux users can perform this check without needing Windows tools.
- Clarify that the PowerShell script is optional and only relevant for classic VM SKU users, and link to any existing Linux/CLI alternatives if available.
Virtual Machines
Enable on-demand disk bursting
...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples, but PowerShell (commonly associated with Windows) is presented before CLI. The PowerShell section is detailed and uses Windows-centric terminology (cmdlets), while the CLI section is also present and complete. There are no Linux-specific examples or explicit mentions of Linux tools, but the CLI commands are cross-platform. The Azure portal instructions are platform-neutral. No critical Linux functionality is missing, but Windows/PowerShell patterns are prioritized.
Recommendations
- Consider presenting Azure CLI examples before PowerShell, as CLI is more widely used on Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add a note clarifying that PowerShell is available cross-platform, but CLI is the default on Linux/macOS.
- Where possible, provide bash shell scripting examples for disk operations.
- Ensure terminology is neutral (e.g., 'commands' instead of 'cmdlets' when referring to CLI).
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers both Linux and Windows VMs, and provides both Azure CLI and PowerShell examples. However, the PowerShell example is presented first, which may indicate a minor 'windows_first' bias. No critical sections are Windows-only, and Linux users are able to complete the migration using the Azure CLI example provided.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or alternate their order to avoid implicit Windows prioritization.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider adding Bash shell script examples for Linux users, if relevant.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for most tasks, but PowerShell examples are often presented before CLI examples, which may subtly prioritize Windows users. The 'Assign RBAC role' and 'Assign Azure policy' sections link to both PowerShell and CLI guides, but PowerShell is mentioned first. However, Linux parity is generally maintained, and CLI examples are present throughout. The 'Next steps' section includes both Linux and Windows guides for VHD upload/download.
Recommendations
- Present Azure CLI and PowerShell examples in parallel or alternate their order to avoid implicit prioritization.
- Explicitly state that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Where possible, add Bash or shell script examples for disk operations to further support Linux users.
- Ensure that all screenshots and portal instructions are not Windows-specific (e.g., avoid showing Windows UI elements if not necessary).
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell references, but links to PowerShell custom role creation first and mentions PowerShell alongside CLI for configuring NetworkAccessPolicy. The custom RBAC role section links only to a PowerShell-based guide, and PowerShell is referenced before CLI in the NetworkAccessPolicy section. Linux-specific examples are present (CLI), but Windows tools and patterns are mentioned first or exclusively in some sections.
Recommendations
- Add links to Linux/CLI-based custom RBAC role creation documentation alongside the PowerShell guide.
- Ensure CLI and PowerShell examples are presented together, or alternate which is mentioned first.
- Where possible, provide explicit Linux/macOS command examples for relevant tasks, not just PowerShell.
- Clarify that both CLI and PowerShell are supported and provide parity in instructions.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform, with explicit support for both Linux and Windows VMs. However, there are minor instances of Windows-first bias, such as Windows image sizes being described before Linux in the 'Size requirements' section, and PowerShell being mentioned before CLI in the customer-managed key section. Both Linux and Windows examples and tools are referenced, but Windows is sometimes listed first.
Recommendations
- When describing image sizes or requirements, alternate the order of Linux and Windows examples, or present them together to avoid implicit prioritization.
- In sections referencing command-line tools (e.g., PowerShell and CLI), list both platforms in parallel or alternate their order.
- Ensure that any links to how-to guides or scripts for both Linux and Windows are equally prominent and easy to find.
- If possible, provide explicit Linux/macOS command examples alongside PowerShell, especially in deployment or configuration sections.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM templates. PowerShell is primarily a Windows tool, and its inclusion before Azure CLI may suggest a Windows-first bias. However, all examples and instructions are relevant to Linux VMs, and Linux-specific commands and troubleshooting steps are provided. No critical Linux examples are missing, and Linux tools are adequately covered.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is more cross-platform and commonly used for Linux.
- Clarify that PowerShell examples are for users who prefer PowerShell on Windows or cross-platform PowerShell, but Azure CLI is recommended for Linux environments.
- Consider adding Bash script examples for common deployment scenarios, as Bash is native to Linux.
- Explicitly state that all PowerShell commands are for managing Azure resources, not for running inside Linux VMs.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity between Windows and Linux in most sections, including CLI, REST, and portal instructions. However, there is a mild Windows bias: PowerShell examples are shown with Windows as the default OS, and Windows terminology (Sysprep) is mentioned before Linux equivalents in some places. The PowerShell section uses Windows as the primary example and only briefly notes how to switch to Linux. CLI and REST examples use Linux as the default, balancing the bias. No critical Linux gaps are present.
Recommendations
- In PowerShell examples, provide Linux as the primary example or alternate examples for both OS types.
- When mentioning OS-specific steps (e.g., Sysprep vs waagent), list Linux first or equally.
- Add explicit notes that PowerShell can be used for Linux image management, not just Windows.
- Ensure that all CLI and PowerShell examples show both Linux and Windows usage equally.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first or in more detail, and some backup/encryption instructions reference PowerShell cmdlets before CLI equivalents. There are no missing Linux examples, and the CLI is well covered, but the prominence of PowerShell may create friction for Linux users.
Recommendations
- Where possible, list Azure CLI examples before PowerShell examples, as CLI is cross-platform and native to Linux.
- Ensure all critical instructions reference both CLI and PowerShell equally, avoiding language that suggests PowerShell is the primary or preferred method.
- Highlight that Azure CLI is the recommended tool for Linux users, and clarify that PowerShell is optional.
- Consider adding brief Bash shell scripting examples for disk operations (e.g., mounting disks) where relevant.
- Review backup instructions to ensure CLI methods are described with equal prominence to PowerShell.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation is highly Linux-focused, providing detailed, distribution-specific instructions for expanding disks on Linux VMs in Azure. However, there is a single section at the end that provides a PowerShell script for checking classic VM SKU support, with no equivalent Bash/Azure CLI example. This is a minor instance of Windows/PowerShell bias in an otherwise Linux-centric guide.
Recommendations
- For the 'Expand without downtime classic VM SKU support' section, provide an equivalent Azure CLI or Bash script to check VM SKU capabilities, or clarify if PowerShell is the only supported method for this specific check.
- If possible, add a note explaining why PowerShell is used in this context and whether Linux users can run the script via Azure Cloud Shell or another cross-platform method.
Virtual Machines
Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines.
...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents benchmarking instructions for both Windows (DISKSPD) and Linux (FIO), but Windows content and tooling (DISKSPD) are introduced first and in greater detail. Windows tools are mentioned before Linux equivalents, and the Windows section precedes the Linux section, which may create a perception of Windows priority. However, Linux instructions are thorough and parity is generally maintained.
Recommendations
- Present Linux and Windows tools/examples in parallel or in separate, equally prominent sections.
- Consider starting with a neutral introduction or alternating which platform is presented first.
- Explicitly mention that both DISKSPD (Windows) and FIO (Linux) are recommended tools, and clarify their platform compatibility.
- Add a summary table comparing Windows and Linux benchmarking tools and commands for quick reference.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on enabling Azure Disk Encryption for Linux VMs and provides Linux-specific instructions and examples. However, there are minor instances of Windows bias: PowerShell is mentioned alongside Azure CLI in several places, and PowerShell examples/scripts are referenced before or equally with Linux-native tools. The 'Next steps' and introductory quickstart links list both CLI and PowerShell options, with PowerShell sometimes mentioned first. There are no missing Linux examples or exclusive use of Windows tools, and all technical content is Linux-centric.
Recommendations
- When listing quickstarts or scripts, consistently mention the Azure CLI (Linux-native) option before PowerShell, as the primary audience is Linux administrators.
- Clarify that PowerShell is cross-platform and can be used on Linux, or provide a brief note to avoid confusion.
- Where possible, emphasize Linux-native tools (Azure CLI, Bash scripts) over PowerShell for Linux VM management.
- Ensure that all examples and scripts are available in both Azure CLI and PowerShell, and that Linux-native methods are highlighted as the default.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples and instructions are presented before Azure CLI (which is more native to Linux), and the PowerShell section is more detailed and extensive. There is a minor Windows bias in the ordering and depth of PowerShell coverage, but Linux-native CLI and OS-level commands are also included.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more commonly used on Linux.
- Ensure Azure CLI coverage is as detailed as PowerShell, including all disk scenarios.
- Explicitly state that PowerShell commands can be run from Azure Cloud Shell or a Linux system with PowerShell installed, to avoid confusion.
- Consider adding Bash scripting examples for common tasks, since Bash is native to Linux.
- Review for parity in explanations and screenshots between PowerShell and CLI sections.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in several sections, Windows/Hyper-V instructions are presented first, and references to Windows tools (such as Hyper-V Manager and PowerShell's convert-vhd cmdlet) appear before Linux alternatives. All Linux hypervisor methods are included and detailed, but Windows tools are sometimes mentioned as the default or primary option.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V/Windows-specific instructions.
- When mentioning disk conversion tools, list Linux tools (e.g., qemu-img) before Windows tools (e.g., convert-vhd), or present them together.
- Clarify that Hyper-V Manager and convert-vhd are Windows-only tools, and highlight Linux alternatives for disk conversion and management.
- Ensure that all instructions for disk conversion, VM preparation, and upload are equally detailed for Linux and Windows environments.
- Consider adding a summary table or navigation aid to help users quickly find instructions relevant to their platform.