Fix HyperV XML: System.Xml.XmlElement & The minimum amount #13691

g0tmi1k · 2025-07-09T22:30:51Z

ERROR:

New-VagrantVMXML : Cannot convert the "System.Xml.XmlElement" value of type "System.Xml.XmlElement"
to type "System.Int32

Valid XML config, which was causing the crash:

  <memory>
    <bank>
      <dynamic_memory_enabled type="bool">[...]</dynamic_memory_enabled>
      <limit type="integer">[...]</limit>
      <reservation type="integer">[...]</reservation>
      <size type="integer">[...]</size>
    </bank>
  </memory>

Invalid XML config, what was passing (but would then fail later as dynamic_memory_enabled is missing):

  <memory>
    <Bank>2048</Bank>
  </memory>

$memory -> $memoryNode
There is another variable $Memory, so renamed to make it clear.

<Bank> -> <bank> (lowercase b)
REF: https://github.com/mwrock/packer-templates/blob/a96114e3b0918f19cbb6907b797cdd26749cfd11/hyper-v-output/Virtual%20Machines/vm.XML#L397

hashicorp-cla-app · 2025-07-09T23:10:36Z

All committers have signed the CLA.

ERROR: > New-VagrantVMXML : Cannot convert the "System.Xml.XmlElement" value of type "System.Xml.XmlElement" to type "System.Int32 Valid XML config, which was causing the crash: ```xml <memory> <bank> <dynamic_memory_enabled type="bool">[...]</dynamic_memory_enabled> <limit type="integer">[...]</limit> <reservation type="integer">[...]</reservation> <size type="integer">[...]</size> </bank> </memory> ``` Invalid XML config, what was passing (but would then fail later as `dynamic_memory_enabled` is missing): ```xml <memory> <Bank>2048</Bank> </memory> ``` - - - `$memory` -> `$memoryNode` There is another variable `$Memory`, I believe this is the reason why it was crashing. - - - `<Bank>` -> `<bank>` (lowercase b) REF: https://github.com/mwrock/packer-templates/blob/a96114e3b0918f19cbb6907b797cdd26749cfd11/hyper-v-output/Virtual%20Machines/vm.XML#L397

g0tmi1k · 2025-07-10T10:58:58Z

OS Version

PS C:\> systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows Server 2019 Standard Evaluation
OS Version:                10.0.17763 N/A Build 17763
PS C:\>

Preparation

PS C:\Users\root\Desktop> & 'C:\Program Files\Vagrant\bin\vagrant.exe' box list
There are no installed boxes! Use `vagrant box add` to add some.
PS C:\Users\root\Desktop>
PS C:\Users\root\Desktop> & 'C:\Program Files\Vagrant\bin\vagrant.exe' box add test .\kali-linux-rolling-hyperv-amd64.box
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'test' (v0) for provider:
    box: Unpacking necessary files from: file://C:/Users/root/Desktop/kali-linux-rolling-hyperv-amd64.box
    box:
==> box: Successfully added box 'test' (v0) for ''!
PS C:\Users\root\Desktop>
PS C:\Users\root\Desktop> mkdir -f test


    Directory: C:\Users\root\Desktop


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        7/10/2025  12:02 AM                test


PS C:\Users\root\Desktop>
PS C:\Users\root\Desktop> cd .\test\
PS C:\Users\root\Desktop\test>
PS C:\Users\root\Desktop\test> & 'C:\Program Files\Vagrant\bin\vagrant.exe' init -f -m test
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
PS C:\Users\root\Desktop\test>

Error/Crash 1

PS C:\Users\root\Desktop\test> & 'C:\Program Files\Vagrant\bin\vagrant.exe' up
Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...
==> default: Verifying Hyper-V is accessible...
==> default: Importing a Hyper-V instance
    default: Creating and registering the VM...
An error occurred while executing a PowerShell script. This error
is shown below. Please read the error message and see if this is
a configuration error with your system. If it is not, then please
report a bug.

Script: import_vm.ps1
Error:

Cannot convert the "System.Xml.XmlElement" value of type "System.Xml.XmlElement" to type "System.Int32".
PS C:\Users\root\Desktop\test>

Configs/Environment

PS C:\Users\root\Desktop\test> Get-ChildItem -Recurse  ~/.vagrant.d/boxes/test/


    Directory: C:\Users\root\.vagrant.d\boxes\test


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        7/10/2025   3:54 AM                0


    Directory: C:\Users\root\.vagrant.d\boxes\test\0


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        7/10/2025   3:54 AM                hyperv


    Directory: C:\Users\root\.vagrant.d\boxes\test\0\hyperv


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        7/10/2025   3:54 AM                Virtual Hard Disks
d-----        7/10/2025   3:54 AM                Virtual Machines
-a----        7/10/2025   3:54 AM            232 info.json
-a----        7/10/2025   3:54 AM             91 metadata.json
-a----        7/10/2025   3:53 AM            311 Vagrantfile


    Directory: C:\Users\root\.vagrant.d\boxes\test\0\hyperv\Virtual Hard Disks


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----        7/10/2025   3:54 AM    17641242624 kali-linux-rolling-hyperv-amd64.vhdx


    Directory: C:\Users\root\.vagrant.d\boxes\test\0\hyperv\Virtual Machines


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----        7/10/2025   3:54 AM           1214 box.xml


PS C:\Users\root\Desktop\test>
PS C:\Users\root\Desktop\test> cat 'C:\Users\root\.vagrant.d\boxes\test\0\hyperv\Virtual Machines\box.xml'
<?xml version="1.0"?>
<configuration>
  <properties>
    <subtype type="integer">1</subtype>
    <name type="string">kali-linux-rolling-hyperv-amd64</name>
  </properties>
  <settings>
    <processors>
      <count type="integer">2</count>
    </processors>
    <memory>
      <bank>
        <dynamic_memory_enabled type="bool">False</dynamic_memory_enabled>
        <limit type="integer">1048576</limit>
        <reservation type="integer">512</reservation>
        <size type="integer">2048</size>
      </bank>
    </memory>
  </settings>
  <AltSwitchName type="string">Default Switch</AltSwitchName>
  <boot>
    <device0 type="string">Optical</device0>
  </boot>
  <secure_boot_enabled type="bool">False</secure_boot_enabled>
  <secure_boot_template type="string">MicrosoftWindows</secure_boot_template>
  <tpm_enabled type="bool">True</tpm_enabled>
  <notes type="string">
  </notes>
  <vm-controllers>
    <scsi ChannelInstanceGuid="x">
      <controller0>
        <drive0>
          <pathname type="string">..\Virtual Hard Disks\kali-linux-rolling-hyperv-amd64.vhdx</pathname>
          <type type="string">VHD</type>
        </drive0>
      </controller0>
    </scsi>
  </vm-controllers>
</configuration>
PS C:\Users\root\Desktop\test>

g0tmi1k · 2025-07-10T11:40:51Z

Error/Crash 2

PS C:\Users\root\Desktop\test> notepad C:\Program Files\Vagrant\embedded\gems\gems\vagrant-2.4.7\plugins\providers\hyperv\scripts\utils\VagrantVM\VagrantVM.psm1
PS C:\Users\root\Desktop\test>
PS C:\Users\root\Desktop\test> & 'C:\Program Files\Vagrant\bin\vagrant.exe' up
Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...
==> default: Verifying Hyper-V is accessible...
==> default: Importing a Hyper-V instance
    default: Creating and registering the VM...
An error occurred while executing a PowerShell script. This error
is shown below. Please read the error message and see if this is
a configuration error with your system. If it is not, then please
report a bug.

Script: import_vm.ps1
Error:

Failed to modify device 'Memory'.

Invalid startup memory amount assigned for 'kali-linux-rolling-hyperv-amd64'.

'kali-linux-rolling-hyperv-amd64' failed to modify device 'Memory'. (Virtual machine ID 1E3B2EE9-8290-4F63-A21B-7B3C2741BD2E)

Invalid startup memory amount assigned for 'kali-linux-rolling-hyperv-amd64'. The minimum amount of memory you can assign to this virtual machine is '32' MB. (Virtual machine ID 1E3B2EE9-8290-4F63-A21B-7B3C2741BD2E)
PS C:\Users\root\Desktop\test>

ERROR: > Invalid startup memory amount assigned for '[...]'. The minimum amount of memory you can assign to this virtual machine is '[...]'. Happens for: Memory, MaxMemory, CPUCount

g0tmi1k · 2025-07-10T11:46:48Z

Working!

PS C:\Users\root\Desktop\test> notepad C:\Program Files\Vagrant\embedded\gems\gems\vagrant-2.4.7\plugins\providers\hyperv\scripts\utils\VagrantVM\VagrantVM.psm1^C
PS C:\Users\root\Desktop\test>
PS C:\Users\root\Desktop\test> & 'C:\Program Files\Vagrant\bin\vagrant.exe' up
Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...
==> default: Verifying Hyper-V is accessible...
==> default: Importing a Hyper-V instance
    default: Creating and registering the VM...
    default: Successfully imported VM
    default: Configuring the VM...
    default: Setting VM Enhanced session transport type to disabled/default (VMBus)
==> default: Starting the machine...
==> default: Waiting for the machine to report its IP address...
    default: Timeout: 120 seconds
    default: IP: 192.168.100.56
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 192.168.100.56:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Preparing SMB shared folders...
    default: You will be asked for the username and password to use for the SMB
    default: folders shortly. Please use the proper username/password of your
    default: account.
    default:
    default: Username (user[@domain]): root
    default: Password (will be hidden):

Vagrant requires administrator access to create SMB shares and
may request access to complete setup of configured shares.
==> default: Mounting SMB shared folders...
    default: C:/Users/root/Desktop/test => /vagrant
PS C:\Users\root\Desktop\test> & 'C:\Program Files\Vagrant\bin\vagrant.exe' ssh
Linux kali 6.12.33+kali-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.12.33-1kali1 (2025-06-25) x86_64

The programs included with the Kali GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Kali GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
┌──(vagrant㉿kali)-[~]
└─$

g0tmi1k · 2025-07-10T11:54:46Z

I agree'd to the CLA, but its not picking it up for some reason?

taru-garg-hashicorp · 2025-07-11T04:16:45Z

I agree'd to the CLA, but its not picking it up for some reason?

Could you visit the CLA link once again? I am guessing there might have been some issue in the service

g0tmi1k · 2025-07-11T06:09:49Z

Could you visit the CLA link once again? I am guessing there might have been some issue in the service

Hey @taru-garg-hashicorp
Thanks for getting back to me.

I tired using the link in the first comment.
Clicking on recheck just took be straight back to GitHub.
If I used the link in the GitHub actions (three dots -> view details), then it works.

In short. Should now be done!

taru-garg-hashicorp

Thanks a lot for the contribution! These changes look good!

g0tmi1k · 2025-07-15T05:28:37Z

You are welcome @taru-garg-hashicorp .

Thanks for the review!

g0tmi1k requested a review from a team as a code owner July 9, 2025 22:30

g0tmi1k force-pushed the memory-bank branch 2 times, most recently from f847001 to ecf2a26 Compare July 9, 2025 23:10

g0tmi1k force-pushed the memory-bank branch from ecf2a26 to 3869cd1 Compare July 10, 2025 10:23

g0tmi1k force-pushed the memory-bank branch from 3869cd1 to 64ad31b Compare July 10, 2025 10:50

g0tmi1k changed the title ~~Fix HyperV XML: Cant convert System.Xml.XmlElement~~ Fix HyperV XML: System.Xml.XmlElement & The minimum amount Jul 10, 2025

Fix HyperV XML: The minimum amount of...

5ee0521

ERROR: > Invalid startup memory amount assigned for '[...]'. The minimum amount of memory you can assign to this virtual machine is '[...]'. Happens for: Memory, MaxMemory, CPUCount

taru-garg-hashicorp approved these changes Jul 15, 2025

View reviewed changes

taru-garg-hashicorp merged commit d3a14ba into hashicorp:main Jul 18, 2025
10 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Fix HyperV XML: System.Xml.XmlElement & The minimum amount #13691

Fix HyperV XML: System.Xml.XmlElement & The minimum amount #13691

g0tmi1k commented Jul 9, 2025 •

edited

Loading

Uh oh!

hashicorp-cla-app bot commented Jul 9, 2025 •

edited

Loading

Uh oh!

g0tmi1k commented Jul 10, 2025 •

edited

Loading

Uh oh!

g0tmi1k commented Jul 10, 2025

Uh oh!

g0tmi1k commented Jul 10, 2025 •

edited

Loading

Uh oh!

g0tmi1k commented Jul 10, 2025

Uh oh!

taru-garg-hashicorp commented Jul 11, 2025

Uh oh!

g0tmi1k commented Jul 11, 2025

Uh oh!

taru-garg-hashicorp left a comment

Uh oh!

g0tmi1k commented Jul 15, 2025

Uh oh!

Uh oh!

Uh oh!

Fix HyperV XML: System.Xml.XmlElement & The minimum amount #13691

Fix HyperV XML: System.Xml.XmlElement & The minimum amount #13691

Conversation

g0tmi1k commented Jul 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

hashicorp-cla-app bot commented Jul 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

g0tmi1k commented Jul 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

OS Version

Preparation

Error/Crash 1

Configs/Environment

Uh oh!

g0tmi1k commented Jul 10, 2025

Error/Crash 2

Uh oh!

g0tmi1k commented Jul 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Working!

Uh oh!

g0tmi1k commented Jul 10, 2025

Uh oh!

taru-garg-hashicorp commented Jul 11, 2025

Uh oh!

g0tmi1k commented Jul 11, 2025

Uh oh!

taru-garg-hashicorp left a comment

Choose a reason for hiding this comment

Uh oh!

g0tmi1k commented Jul 15, 2025

Uh oh!

Uh oh!

Uh oh!

g0tmi1k commented Jul 9, 2025 •

edited

Loading

hashicorp-cla-app bot commented Jul 9, 2025 •

edited

Loading

g0tmi1k commented Jul 10, 2025 •

edited

Loading

g0tmi1k commented Jul 10, 2025 •

edited

Loading