I should add this is XCP-ng 8.3.
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: XCP-ng
Description: XCP-ng release 8.3.0 (xenenterprise)
Release: 8.3.0
Codename: xenenterprise
N
Offline
Latest posts made by nullstream 0
-
RE: OpenBSD UEFI install/boot panics.
-
OpenBSD UEFI install/boot panics.
I'm attempting to install OpenBSD with EFI on a new VM instance. Booting BIOS works just fine (blue kernel text) but EFI just refuses to boot the installer.
I've tried the CD ISO installer and I've also tried importing the disk image as a separate VDI. When the installer boots the kernel messages start and then fails after detecting the CDROM. Thinking it might be a OpenBSD7.8 issue I installed the most recent snapshot (trying both ISO and IMG).
I've been able to boot the installer by removing the second VIF (setting VM as a firewall for isolated net) and going into the boot config and using:
boot -c # does boot stuff
disable xbf
quitThe initial panic is:
panic: page full, sc 0xffff800000024c00 gnt 0xffff8000000f8000 (4) ge 0xffff8000000f8078
Is there a config item I'm missing? A google search of the panic values doesn't come up with anything. The seems to be related to EFI grant table sizing but that's a bit outside my wheelhouse.
I was able to complete the boot and install but have to disable xbf each time otherwise it panics (attaching screenshots). Patching to the most recent snapshot doesn't correct it either and I can't add the second VIF without a similar panic. If I patch the boot config to disable xbf it will panic with the second VIF which then also breaks on kernel re-linking.
Any ideas? Is this a Xen issue or an OpenBSD issue?
Not sure where to send this debug details.The xe template-param list is as follows:
[21:55 localhost ~]# xe template-param-list uuid=6d18b41c-035f-ca9b-d6d8-7987ec08dc68 uuid ( RO) : 6d18b41c-035f-ca9b-d6d8-7987ec08dc68 name-label ( RW): FW01.lab.example-site.ca name-description ( RW): user-version ( RW): 1 is-a-template ( RW): false is-default-template ( RW): false is-a-snapshot ( RO): false snapshot-of ( RO): <not in database> snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z snapshot-info ( RO): parent ( RO): <not in database> children ( RO): is-control-domain ( RO): false power-state ( RO): running memory-actual ( RO): 8591990784 memory-target ( RO): 8589934592 memory-overhead ( RO): 71303168 memory-static-max ( RW): 8589934592 memory-dynamic-max ( RW): 8589934592 memory-dynamic-min ( RW): 8589934592 memory-static-min ( RW): 134217728 suspend-VDI-uuid ( RW): <not in database> suspend-SR-uuid ( RW): <not in database> VCPUs-params (MRW): VCPUs-max ( RW): 2 VCPUs-at-startup ( RW): 2 actions-after-shutdown ( RW): Destroy actions-after-softreboot ( RW): Soft reboot actions-after-reboot ( RW): Restart actions-after-crash ( RW): Restart console-uuids (SRO): d74e35cd-b13d-46e6-8361-1f23fb5c0724 hvm ( RO): true platform (MRW): timeoffset: 0; nic_type: e1000; device-model: qemu-upstream-uefi; cores-per-socket: 1; secureboot: false; nx: true; acpi: 1; apic: true; pae: true; hpet: true allowed-operations (SRO): sysprep; metadata_export; changing_dynamic_range; hard_reboot; hard_shutdown; pause; snapshot current-operations (SRO): blocked-operations (MRW): allowed-VBD-devices (SRO): 1; 2; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15; 16; 17; 18; 19; 20; 21; 22; 23; 24; 25; 26; 27; 28; 29; 30; 31; 32; 33; 34; 35; 36; 37; 38; 39; 40; 41; 42; 43; 44; 45; 46; 47; 48; 49; 50; 51; 52; 53; 54; 55; 56; 57; 58; 59; 60; 61; 62; 63; 64; 65; 66; 67; 68; 69; 70; 71; 72; 73; 74; 75; 76; 77; 78; 79; 80; 81; 82; 83; 84; 85; 86; 87; 88; 89; 90; 91; 92; 93; 94; 95; 96; 97; 98; 99; 100; 101; 102; 103; 104; 105; 106; 107; 108; 109; 110; 111; 112; 113; 114; 115; 116; 117; 118; 119; 120; 121; 122; 123; 124; 125; 126; 127; 128; 129; 130; 131; 132; 133; 134; 135; 136; 137; 138; 139; 140; 141; 142; 143; 144; 145; 146; 147; 148; 149; 150; 151; 152; 153; 154; 155; 156; 157; 158; 159; 160; 161; 162; 163; 164; 165; 166; 167; 168; 169; 170; 171; 172; 173; 174; 175; 176; 177; 178; 179; 180; 181; 182; 183; 184; 185; 186; 187; 188; 189; 190; 191; 192; 193; 194; 195; 196; 197; 198; 199; 200; 201; 202; 203; 204; 205; 206; 207; 208; 209; 210; 211; 212; 213; 214; 215; 216; 217; 218; 219; 220; 221; 222; 223; 224; 225; 226; 227; 228; 229; 230; 231; 232; 233; 234; 235; 236; 237; 238; 239; 240; 241; 242; 243; 244; 245; 246; 247; 248; 249; 250; 251; 252; 253; 254 allowed-VIF-devices (SRO): 2; 3; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15 possible-hosts ( RO): 01e5c3b0-dee4-44dc-a5c0-b5b1337ccc98 domain-type ( RW): hvm current-domain-type ( RO): hvm HVM-boot-policy ( RW): BIOS order HVM-boot-params (MRW): firmware: uefi; order: cd HVM-shadow-multiplier ( RW): 1.000 PV-kernel ( RW): PV-ramdisk ( RW): PV-args ( RW): PV-legacy-args ( RW): PV-bootloader ( RW): PV-bootloader-args ( RW): last-boot-CPU-flags ( RO): vendor: GenuineIntel; features: 1fcbfbff-f7fa3203-2c100800-00000021-00000001-000007ab-00000000-00000000-00101000-bc000400-00000000-00000000-00000000-00000000-00000000-00000000-0c000000-40000000-00000000-00000000-00000000-00000000-00000000 last-boot-record ( RO): '' resident-on ( RO): 01e5c3b0-dee4-44dc-a5c0-b5b1337ccc98 affinity ( RW): <not in database> other-config (MRW): auto_poweron: true; xo:6d18b41c: {"creation":{"date":"2026-03-11T02:40:31.505Z","template":"552bce37-51b2-445d-84f2-5f33fa112d7e","user":"ba520305-faf3-43ac-a953-ab0294ece322"}}; base_template_name: Other install media; import_task: OpaqueRef:8e3a92dc-1dd7-e2d7-0080-5513efb192c3; mac_seed: 39acf7ee-823f-6f4f-1688-e0a22bd8ef69; install-methods: cdrom dom-id ( RO): 12 recommendations ( RO): <restrictions><restriction field="memory-static-max" max="137438953472"/><restriction field="vcpus-max" max="64"/><restriction field="has-vendor-device" value="false"/><restriction field="supports-bios" value="yes"/><restriction field="supports-uefi" value="yes"/><restriction field="supports-secure-boot" value="yes"/><restriction max="255" property="number-of-vbds"/><restriction max="7" property="number-of-vifs"/></restrictions> xenstore-data (MRW): vm-data/mmio-hole-size: 268435456; vm-data: ha-always-run ( RW) [DEPRECATED]: false ha-restart-priority ( RW): blobs ( RO): start-time ( RO): 20260311T02:53:47Z install-time ( RO): 20260311T02:40:31Z VCPUs-number ( RO): 2 VCPUs-utilisation (MRO): 0: 0.917; 1: 0.000 os-version (MRO): netbios-name (MRO): PV-drivers-version (MRO): PV-drivers-up-to-date ( RO) [DEPRECATED]: false memory (MRO): disks (MRO): VBDs (SRO): 7261f145-6fb7-be34-a811-69f1cf6f751e; 545cae7f-8980-c73f-00f7-5f42af28de6c networks (MRO): services (MRO): PV-drivers-detected ( RO): false other (MRO): platform-feature-xs_reset_watches: 1; platform-feature-multiprocessor-suspend: 1; has-vendor-device: 0 live ( RO): true guest-metrics-last-updated ( RO): 20260311T02:53:51Z can-use-hotplug-vbd ( RO): unspecified can-use-hotplug-vif ( RO): unspecified cooperative ( RO) [DEPRECATED]: true tags (SRW): appliance ( RW): <not in database> groups ( RW): snapshot-schedule ( RW): <not in database> is-vmss-snapshot ( RO): false start-delay ( RW): 0 shutdown-delay ( RW): 0 order ( RW): 0 version ( RO): 0 generation-id ( RO): hardware-platform-version ( RO): 0 has-vendor-device ( RW): false requires-reboot ( RO): false reference-label ( RO): other-install-media bios-strings (MRO): bios-vendor: Xen; bios-version: ; system-manufacturer: Xen; system-product-name: HVM domU; system-version: ; system-serial-number: ; baseboard-manufacturer: ; baseboard-product-name: ; baseboard-version: ; baseboard-serial-number: ; baseboard-asset-tag: ; baseboard-location-in-chassis: ; enclosure-asset-tag: ; hp-rombios: ; oem-1: Xen; oem-2: MS_VM_CERT/SHA1/bdbeb6e0a816d43fa6d3fe8aaef04c2bad9d3e3d pending-guidances ( RO): vtpms ( RO): pending-guidances-recommended ( RO): pending-guidances-full ( RO):Post disable xbf boot panic:
-
RE: OpenBSD & XCP-ng 8.3, virtio (Net&GuestTools) no longer works.
@knightjoel I have not but glad you found something and I wasn't (at least then) crazy.
-
RE: OpenBSD & XCP-ng 8.3, virtio (Net&GuestTools) no longer works.
@Andrew respectfully, 7.5 has the same issue as does 7.4. As well Xcp-ng 8.2 worked perfectly fine for the Xen PV devices. Totally reproducible.
- Install Xcp-ng 8.2
- Setup/import OpenBSD VM.
- Boot and see xnf devices just fine.
- Upgrade to Xcp-ng 8.3
- Boot the same VM and see the xnf devices show up as re devices (realtek driver) and watch interface give re0: watchdog timeouts during an install but if VM already built you'll be able to see the re# devices but can't assign addresses to them.
The difference appears to be the xen version difference between 8.2 and 8.3.
-
RE: OpenBSD & XCP-ng 8.3, virtio (Net&GuestTools) no longer works.
When doing a fresh install (7.6, install76.iso, amd64), the installation detects the network interface as re0 (as opposed to xnf0). Set the device to 'autoconf' and get kernel 'er0: watchdog timeout' and fails out assigning an IP.
dmesg sees the device as:
re0 at pci0 dev 4 function 0 "Realtek 8139" rev0x20: RTL8139C+ (0x7480), apic 1 int 32 address [MAC ADDR]Power off VM and change to e1000 (from Advanced page of VM) and it detects fine and pulls a lease with dhcp.
Also using BIOS and UEFI setup didn't boot post setup (i think I'm missing the efi partition or something).
-
OpenBSD & XCP-ng 8.3, virtio (Net&GuestTools) no longer works.
I've updated a few systems from 8.2 to 8.3.
What has happened since is none of my OpenBSD VMs were accessible.It looks like the Xen drivers are incompatible with the newer Xen virtio drivers as the network interfaces would show as active devices but couldn't be assigned addresses (the device names show up as 'rl#' instead of 'xnf#.' When I changed the network interfaces in advanced from RL8139 to Intel e1000 network started working again which narrowed me down to the virtio drivers.
Taking it a bit further the hostctl tool communicates with the hypervisor. I was able to get OS name, and the updated em0 devices communicating their IPs back to the management agent. I needed to adjust the script to look for the em# interfaces instead of xnf# interfaces.
With the Xen tools not being detected it doesn't get the shutdown/reboot requests which requires 'forcible' shutdown now.
I'll add more info to this thread as I narrow down the final details.
-
RE: Windows import from ESXi 6.7 to XCP-ng 8.2 (XOA 5.99.1)
@nullstream-0 of course this stares me in the face...
https://xcp-ng.org/docs/guests.html#vm
Which then leaves the question how to enable dynamic memory...
-
RE: Windows import from ESXi 6.7 to XCP-ng 8.2 (XOA 5.99.1)
@nullstream-0
Looks that that did the trick.What was the clue that lead you there, as the error message is pretty inscrutable.
-
RE: Windows import from ESXi 6.7 to XCP-ng 8.2 (XOA 5.99.1)
@nullstream-0
In BIOS, Dell R630.
-- Virtualization Enabled
-- SRV-IO Global Enabled
-- X2Apic EnabledI gather 'virtualization enabled' encompasses IOMMU.
I have a number of BSD and Linux vms on the system as well as a couple Windows Server VMs built directly on the host (ie. not imported).Just having issues with the vm's I'm pulling from the ESXi host (note the VMs were off prior to import and I removed all snapshots and uninstalled the vmware tools on the VMs before attempting the import as noted in the docs.
