@olivierlambert oh, sorry, got too carried away and did not notice this is 8.3 beta.

@Andrew said in Homogeneous pools, how similar do the CPUs need to be?:

@CodeMercenary ... The pool will use the features of the lowest CPU...

So this will make a pool of 5 machines with one old CPU use only the available features of the old CPU?
So if I need some newest cryptographic extensions for OpenVPN or something similar they will not be available on the whole pool if one server CPU does not support them?

Is this to support migrations only? It would be better to just say "this guest from this host can not be migrated, it has to be shut down to move" or something similar.

@Andrew
You gave me the idea to boot it in UEFI mode. This loads much further down, almost finishes compared to BIOS. Might be that the guest does not support 1.3 NVMe.

Is there a way in XCP-ng to change the controller/disk type to SCSI or SATA or something like that. In ESXI it is easy to do, I can not find this option here. This might then work!

nvme0: NVMe spec version 1.3
panic[cpu1]/thread=fffffe00233cdc20: programming error: invalid NS/format in cmd fffffe16dbc1dd40

Warning - stack not written to the dump buffer
fffffe00233cd710 genunix:dev_err+81 ()
fffffe00233cd750 nvme:nvme_check_generic_cmd_status+236 ()
fffffe00233cd7d0 nvme:nvme_set_features+e5 ()
fffffe00233cd800 nvme:nvme_write_cache_set+47 ()
fffffe00233cd8a0 nvme:nvme_init+9f0 ()
fffffe00233cd970 nvme:nvme_attach+51b ()
fffffe00233cd9e0 genunix:devi_attach+b1 ()
fffffe00233cda20 genunix:attach_node+8b ()
fffffe00233cda70 genunix:i_ndi_config_node+118 ()
fffffe00233cdaa0 genunix:i_ddi_attachchild+3e ()
fffffe00233cdae0 genunix:devi_attach_node+64 ()
fffffe00233cdb50 genunix:config_immediate_children+b0 ()
fffffe00233cdba0 genunix:devi_config_common+6a ()
fffffe00233cdc00 genunix:mt_config_thread+10b ()
fffffe00233cdc10 unix:thread_start+b ()

@Danp Just now tried on Xen 4.17. Still the same. Seems as @Andrew said, on older XCP it did still work.

@Danp Do you think this is hypervisor problem or guest problem?

@Andrew
Wow, interesting... I am installing this on 8.3 beta 4 (the latest). I thought it is broken in the new 8.3, but is broken for 8.2.1 too...

I tried Solaris 11.4 again (the free one) and I could perhaps make it work if I could enter the console at boot to set grub. The console just ignores my keystrokes. I am now completely out.

@DustinB
Yep, this is the problem we are having.

Interestingly it works in ESXI and Proxmox. Some simple thing maybe in the XCP-ng setting to make it work would be a dream

xpvd is Xen Paravirtualized Driver?

It seems its not the disk controller driver problem, as the setup finishes ok. Some device is being started thereafter (svga? network?) which causes the crash.

@olivierlambert oh, sorry, got too carried away and did not notice this is 8.3 beta.

OmniOS is used by many people as storage solution with ZFS and passthrough devices (SSD&HDD) for NFS and SMB sharing. We have been using it for years on ESXI. Now because of ESXI Exodus, we have tried to set it up on XCP-ng.

OmniOS guest fails to boot in XCP-ng on version 8.2, 8.3.

Same goes for Illumos and Solaris 11.4.

Installation of OmniOS is fine: create a new vm, set viridian=false and installation progress smoothly.

When booting from freshly installed disk it panics with:
WARNING: Couldn't initialize xpv framework

panic[cpu0]/thread=ffffffffffbca07e0: unable to configure /xpvd nexus

I've tried several version of OmniOS (and latest OpenIndiana), I also tried Solaris 11.4, tried disabling apix with apix_enable=0 in /etc/system and all without success.
The same setup in xcp-ng 8.0 works like a charm with working PV-drivers (but no tools).

The interesting thing is that there is an OmniOS image for AMAZON AWS - https://omnios.org/setup/aws which runs on XEN (or did they go to KVM?) so it should actually run? How can I get it to run... it seems very close.

Anyone with an idea of a workaround or even better, a resolution to this.

@stormi
OmniOS guest fails to boot in xcp-ng on version 8.3.

Installation is fine: create a new vm, set viridian=false and installation progress smoothly. I've noticed that installation seem to lack PV-drivers.

When booting from freshly installed disk it panics with:
panic[cpu0]/thread=ffffffffffbc490c0: unable to configure /xpvd nexus

I've tried several version of OmniOS (and latest OpenIndiana), I also tried Solaris 11.4, tried disabling apix with apix_enable=0 in /etc/system and all without success.
The same setup in xcp-ng 8.0 works like a charm with working PV-drivers (but no tools).

Anyone with an idea of a workaround or even better, a resolution to this.