Hello. I had a similar issue which I solved by adding my ALLOW
line to the top of the list in the usb-policy.conf file. I didn't deep dive to find out why this was necessary in my case. Worth a try in your case as well.
.joel
Hello. I had a similar issue which I solved by adding my ALLOW
line to the top of the list in the usb-policy.conf file. I didn't deep dive to find out why this was necessary in my case. Worth a try in your case as well.
.joel
Hello.
@JamfoFL said in Xen Orchestra from Sources unreachable after applying XCPng Patch updates:
This is very odd. When I check to see if the Orchestra status is running, everything looks OK:
This doesn't look ok. The process behind this service has actually exited. Suggest you start/restart this service and check if XO is reachable. If it's not, dive into the logs and look for clues why the process is exiting. You may want to also try manually running /etc/init.d/orchestra
and see if that produces any helpful output.
But when I try to run the command you sent over, I get an error message stating "Unit xo-server.service" could not be found". However, when I check in the very same folder from which I am running the command, I can see xo-server.service right there.
Not taking away from the points others have made about .service
files needing to be in the correct location, but in your case, worrying about the xo-server.service
file is probably a dead end. It appears whoever installed XO created the systemd service as orchestra
. You needn't try and "fix" the fact you don't have an xo-server.service
.
.joel
Teddy, can the packages from your repo be installed alongside the 8.3 updates released yesterday and the 8.3 security updates released shortly before that?
I was able to root cause this, and with a small kernel patch, the PV drivers attach now. I've submitted the patch to OpenBSD for review (https://marc.info/?l=openbsd-tech&m=173154320510806&w=2).
One a side note, if anyone is reading this and knows how to "hide" the 9pfs device from a VM, such that the VM doesn't try to probe the device and load a driver for it, that would also likely solve this issue for OpenBSD VMs without needing a kernel patch.
.joel
Hi @nullstream-0, have you tried booting a -current snapshot to see if something was changed post 7.6-release?
What does dmesg look like on the 7.6 VM? In particular, lines related to pvbus, xen, xbf, and xnf (dmesg | grep -E "OpenBSD|pvbus|xen|xbf|xnf"
).
.joel