Vm-Seires Hyper-V stuck PA-HDF Login

[pattarachaiKH]

Hi Expert ,

I have some issues about I test the PA Vm-Series on Hyper-V including on My laptop 

However, I found an issue about the console showing PA-HDF longer time I understood that may be the initial boot but I waited more than 1 hour on another guest's VM, and not PA is working properly please help me check.

Thank you

[aleksandar.astardzhiev]

Hi @pattarachaiKH ,

I have experienced the same problem and I don't believe there is a solution.

The workaround I did recently was to run GNS3 VM in Hyper-V and run PAN VM-Series inside GNS3 as KVM/Qemu.

[frigault]

I have the same issue. It used to work fine with Windows 10, but I could not make it work on Windows 11 so far.

Checking the logs I read in md_out.log

2024-08-30 04:00:12 No SYSD ACL configuration for parrot
2024-08-30 04:00:23 PyEXC type: <class 'KeyError'>
PyEXC value: 'memory'
Traceback (most recent call last):
  File "/etc/md.d//brdagent.py", line 73, in <module>
2024-08-30 04:00:23     init_brdagent()
  File "/etc/md.d//brdagent.py", line 53, in init_brdagent
2024-08-30 04:00:23     memory = platform['memory']
2024-08-30 04:00:23 MDCH-gdb: Unexpected NULL in tasks-file list.2024-08-30 04:00:23
2024-08-30 04:00:23 MDCH-sysdagent: Unexpected NULL in tasks-file list.
2024-08-30 04:00:25 net.netfilter.nf_conntrack_helper = 1
2024-08-30 04:00:27 Zram swap is turned on now
2024-08-30 04:00:27 -:root:ALL2024-08-30 04:00:27
2024-08-30 04:00:27 Done with ZRAM mem_limit 1475MB configuration
2024-08-30 04:00:27 Done with ZRAM mem_limit 1475MB configuration

in sysd.log

/etc/cfgdb/common/finalnew-curr-relinfo.cfgdb.xml:1: parser error : Start tag expected, '<' not found
""<?xml version="1.0" encoding="UTF-8"?>
^
*
* Sysd Startup
*

This is the powershell script I'm using to create the VM

$name="palo"
$descr="PAN-OS for VM-Series"
New-VM -Name $name -MemoryStartupBytes 6144MB -Generation 1 -BootDevice VHD -VHDPath .\Downloads\PA-VM-HPV-11.1.4.vhdx -SwitchName "br-ext"
Set-VM $name -MemoryMinimumBytes 6144MB -MemoryMaximumBytes 6144MB -CheckpointType disabled -Notes ${descr} -ProcessorCount 2 -AutomaticStartAction Nothing -AutomaticStopAction ShutDown
Set-VMMemory $name -DynamicMemoryEnabled $false
Add-VMNetworkAdapter -SwitchName br-mine -VmName $name -Name mine
Add-VMNetworkAdapter -SwitchName br-mine2 -VmName $name -Name mine2
Get-VM $name | Disable-VMIntegrationService  -Name "Time Synchronization"
Get-VM $name | Disable-VMIntegrationService  -Name "Key-Value Pair Exchange"
Get-VM $name | Disable-VMIntegrationService  -Name "VSS"

 if anyone could confirm it's possible to create a vm-series VM on Hyper-V on Windows 11 that would be great... until then I'll stop trying.

EDIT: I think I managed to make it work in my crash and burn lab with a hack. Attach the vhdx (PA-VM-HPV-11.1.4.vhdx in my case) to a Linux VM, mount the second partition (an ext4 partition with label sysroot0) and create an env file under the existing etc folder under it:

mkdir /mnt/2
mount /dev/disk/by-label/sysroot0 /mnt/2
echo "MY_POD_UID=42" > /mnt/2/etc/env
umount /mnt/2

then detach the disk. After that the Palo Alto VM boots fine. The VM UUID is 42 and the CPU ID is HPV:81d0c6e83f02732.