xcp
xcp copied to clipboard
xcp-ng
Unable to create FreeBSD/i386 virtual machine with default VM settings on XCP-ng v7.6.0
... because of qemu-system-i386 segmentation fault. For example, that:
[174942.297943] qemu-system-i38[4902]: segfault at 0 ip 0000559747390019 sp 00007ffd10684590 error 4 in qemu-system-i386[559746ff3000+4ef000]
"Old and proven" qemu-dm works, though. So, "xe vm-param-set uuid=<UUID> platform:device-model=qemu-trad" allows me to install VM, but I lose USB passthrough that way.
Thanks for your report.
Does it work in XenServer 7.6? I'd like to rule out an XCP-ng-specific bug and report the bug to them too. They and we will probably need more details to reproduce (installation steps, what template, what ISO image, etc.).
Does it work in XenServer 7.6?
I don't know because I don't have XenServer v7.6 installed on any host under my administrative control, unfortunately.
I'd like to rule out an XCP-ng-specific bug and report the bug to them too.
I'm quite in doubt that XCP-ng project this or that way has touched so low-level parts of Xen as device model, so, I can suggest Citrix and XenServer developers check their code against my report, but it seems to me that FreeBSD is absent in the list of guest operating systems supported by XenServer.
They and we will probably need more details to reproduce (installation steps, what template, what ISO image, etc.).
As you can see from my report, device model segmentation fault prevents FreeBSD kernel from boot, so, question about installation steps is not so relevant as it seems. :)
Steps to reproduce:
- Install XCP-ng;
- Download FreeBSD/i386 v12.0-RELEASE DVD from official FreeBSD FTP site (NB: only /i386 has trouble discussed, /amd64 works fine!);
- Create virtual machine from 'Other install media';
- Try to boot VM.
You will see boot loader messages. After kernel has begun to load, you will see messages from drivers being initialised, which will suddenly stop after some time.
'dmesg' on hypervisor host will show you qemu segmentation fault at that time.
NB: Although VM will be created with Hyper-V interface (Viridian) enabled which will be found by FreeBSD kernel, disabling it will not cure segfault.
JFYI: I had installed FreeBSD/i386 with device model switched to qemu-trad, re-built FreeBSD kernel with PAE support enabled and have switched device model back to qemu-upstream-compat -- no luck, unfortunately. :( Just to clarify, no USB/PCI/GPU pass-through or somewhat other troublesome things have been done.
Various users report FreeBSD VMs working fine for them in recent XCP-ng. Have you had the opportunity to test with XCP-ng 8.1 or 8.2?
Various users report FreeBSD VMs working fine for them in recent XCP-ng.
Yes, FreeBSD/x86_64 works fine for long time.
Have you had the opportunity to test with XCP-ng 8.1 or 8.2?
I've already tested it and found as not working -- FreeBSD/i386 crashes DM qemu at least on 8.1.