Jump to content
Welcome to our new Citrix community!
  • 1

Hypervisor 8.2 on desktop mainboard MSI B450M Pro-VDH?


Hans Mittenbacher

Question

Hi,

 

for my home/playground I try to install Hypervisor Express 8.2 on a desktop hardware MSI B450M Pro-VDH with an AMD Ryzen7.
Formerly I had a similar setup (little older  MSI B350M Pro with Ryzen7 and Hypervisor Express 8.1 ) that was running fine. Now I wanted to upgarde my HW a little bit and do a fresh install. Unfortunately the setup from an USB Stick gets stuck at (safe mode)
 

[...]
*** Serial input to DOM0 (type CTRL-a three times to switch input)
Freed 600kB init memory
mapping kernel into physical memory
about to get started...
Hardware Dom0 halted: halting machine

 

I know, that this HW is not officially supported, but is there a chance to get this up and running? Can I load additional device drivers or use other kernel versions/flavours? What else can I do, don't want the hardware to be wasted, was not so cheap :-}

Best regards, Alex



 

Link to comment

4 answers to this question

Recommended Posts

  • 0

Hi

 

I'm experiencing a similar issue with Xen Hypervisor 8.2 Express and a following server:

 

  cpu       |  1x AMD Ryzen 9 5950X / Tray (100-000000059A)
  ssd       |  2x U.2 NVMe 3,84 TB (Gen 3) (Enterprise)   
  mainboard |  1x Asus PRO WS 565-ACE                     
  other     |  1x NVMe PCIe to U.2 Adapter (Gen 4)       
  psu       |  1x 250 Watt                               
  ram       |  4x DDR4-2667 32768 MB ECC

 

Looks like in both cases it's AMD Ryzen involved, but too early to make conclusions.

Didn't find a workaround yet.

 

Regards,

Alex

xen_installation_issue.png

Link to comment
  • 0

Please refer to this thread for a workaround

I tested it with Xen Server 8.2 

 

Find grub.cfg on the install USB. Open it and modify dom0_mem=max:8192M to dom0_mem=max:2048M:

 

menuentry "install" {

    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:2048M com1=115200,8n1 console=com1,vga

    module2 /boot/vmlinuz console=hvc0 console=tty0

    module2 /install.img

}

 

Also it may be necessary to update file boot/isolinux/isolinux.cfg. I wasn't able to do it because the installation USB stick that my dedicated server provider attached contained two partitions. The first one contained boot/isolinux/isolinux.cfg and was read only. The second one contained EFI/xenserver/grub.cfg and was writable. Luckily there was a choice in the BIOS boot menu to boot from the second partition.

 

bios_boot_menu.png

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...