You are not logged in.
Pages: 1
I attempted to follow the instructions on : https://wiki.archlinux.org/index.php/Xen
I thought I had everything good, bridge shows, gets IP, even have the option in the boot loader (GRUB) and can start to boot from it
However the Xen system never loads
When checking in the native system all of the xen modules fail to load
I am pretty new to the kernel module troubleshooting game but I was able to find several similar issues with other packages and modules
So I have the following output :
$ sudo systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-03-20 14:49:36 PDT; 49min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 456 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 456 (code=exited, status=1/FAILURE)
Mar 20 14:49:35 castle systemd-modules-load[456]: Failed to insert 'xen_evtchn': No such device
Mar 20 14:49:36 castle systemd-modules-load[456]: Failed to insert 'xen_gntdev': No such device
Mar 20 14:49:36 castle systemd-modules-load[456]: Failed to insert 'xen_gntalloc': No such device
Mar 20 14:49:36 castle systemd-modules-load[456]: Failed to insert 'xen_blkback': No such device
Mar 20 14:49:36 castle systemd-modules-load[456]: Failed to insert 'xen_netback': No such device
Mar 20 14:49:36 castle systemd-modules-load[456]: Failed to insert 'xen_pciback': No such device
Mar 20 14:49:36 castle systemd-modules-load[456]: Failed to insert 'xen_acpi_processor': No such device
Mar 20 14:49:36 castle systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Mar 20 14:49:36 castle systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Mar 20 14:49:36 castle systemd[1]: Failed to start Load Kernel Modules.In native system I enable and start the services status shows:
(probably the same info as above but it looks different so...)
$ sudo systemctl status xenstored xenconsoled xendomains xen-init-dom0
● xenstored.service - The Xen xenstore
Loaded: loaded (/usr/lib/systemd/system/xenstored.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Tue 2018-03-20 15:59:46 PDT; 16s ago
└─ ConditionPathExists=/proc/xen/capabilities was not met
● xenconsoled.service - Xenconsoled - handles logging from guest consoles and hypervisor
Loaded: loaded (/usr/lib/systemd/system/xenconsoled.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Tue 2018-03-20 15:59:46 PDT; 16s ago
└─ ConditionPathExists=/proc/xen/capabilities was not met
● xendomains.service - Xendomains - start and stop guests on boot and shutdown
Loaded: loaded (/usr/lib/systemd/system/xendomains.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Tue 2018-03-20 15:59:46 PDT; 16s ago
└─ ConditionPathExists=/proc/xen/capabilities was not met
● xen-init-dom0.service - xen-init-dom0, initialise Dom0 configuration (xenstore nodes, JSON configuration stub)
Loaded: loaded (/usr/lib/systemd/system/xen-init-dom0.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Tue 2018-03-20 15:59:46 PDT; 16s ago
└─ ConditionPathExists=/proc/xen/capabilities was not metAs I said, new to this level of debugging so I'm not sure what else would be of use. Google only helped find the same errors but with other packages, mainly vbox
Possibly related but indirectly:
When installing the xen package from the aur I had to skip the gpg check and when installing one of the depends (minw-w64-binutils) I had to skip the integrity check.
Last edited by twodox (2018-03-20 23:01:58)
Offline
Looks like the thing you want to focus on is the following:
Condition: start condition failed at Tue 2018-03-20 15:59:46 PDT; 16s ago
└─ ConditionPathExists=/proc/xen/capabilities was not metThis is the reason systemd gives that the service is not started. It's simply saying it expects a file /proc/xen/capabilities (note: /proc/ is a virtual filesystem) to exist, but it does not. Can you see if /proc/xen exists? The Xen archwiki page mentions making a /proc/xen xenfs mount. Have you looked into this?
As for skipping the GPG check, well, that's not ideal. You probably skipped it because the check said it couldn't verify the signature, which it probably couldn't do because you don't have the public key of the GPG key used to sign one of the package sources. For example, looks like the PKGBUILD for the Xen package on the AUR has an expected key. What you should do is confirm online that the key is what you expect, import it, and then verification should work. See https://wiki.archlinux.org/index.php/GnuPG for more details.
As for the integrity check, that should definitely not be skipped. Something's wrong, and if you confirm the PKGBUILD has the wrong hash, you should let the maintainer of the package know.
Last edited by GenkiSky (2018-03-20 23:25:19)
Offline
Confirming that /proc/xen does not exist.
Is it as simple as creating it?
Or is there more stuff in there that xen will need.
I hadn't done anything with the xenfs mountpoint. That looked like it was supposed to be done after booting into the Xen dom0.
As to the others: Would it be advisable to uninstall all the components and get the install correct? Could that be a factor in the issues now?
Not to muddy the waters but when I was looking into getting the gpg key fixed all the gpg commands were failing with server rejections.
Should I post the results I have to the AUR packages or is there a better way to notify the maintainers?
Last edited by twodox (2018-03-20 23:33:03)
Offline
When you use the grub entry for Xen does the dmesg output contain any reference to Xen?
Offline
After a clean install of Arch I tried once again to install Xen and get it running.
Mostly the same situation, however I was able to update the PKGBUILD with the integrity hash so I only skipped the PGP checks
From previous troubleshooting I added
xenfs /proc/xen xenfs defaults 0 0
to /etc/fstab
However when I do the native Arch install fails to boot. But with different errors (it seems) than when I try to boot Xen with Arch dom0.
I am unable to reach even a command line when booting to Xen under any circumstance.
When booting to native Arch I am left with a recovery login to root.
Below is what I was able to gather about xen from there.
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_evtchn': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_gntdev': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_gntalloc': No such device
Mar 25 20:43:37 castle mount[328]: mount: /proc/xen: mount point does not exist.
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_blkback': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_netback': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_pciback': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_acpi_processor': No such device
Mar 25 20:43:37 castle systemd-networkd[393]: xenbr0: netdev ready
Mar 25 20:43:37 castle systemd-networkd[393]: xenbr0: Link is not managed by us
Mar 25 20:43:37 castle systemd-networkd[393]: xenbr0: IPv6 successfully enabled
Mar 25 20:43:37 castle kernel: IPv6: ADDRCONF(NETDEV_UP): xenbr0: link is not ready
Mar 25 20:43:38 castle kernel: xenbr0: port 1(eno1) entered blocking state
Mar 25 20:43:38 castle kernel: xenbr0: port 1(eno1) entered disabled state
Mar 25 20:43:38 castle kernel: xenbr0: port 1(eno1) entered blocking state
Mar 25 20:43:38 castle kernel: xenbr0: port 1(eno1) entered forwarding state
Mar 25 20:43:38 castle kernel: IPv6: ADDRCONF(NETDEV_CHANGE): xenbr0: link becomes ready
Mar 25 20:43:38 castle kernel: xenbr0: port 1(eno1) entered disabled state
Mar 25 20:43:37 castle systemd-networkd[393]: xenbr0: Gained carrier
Mar 25 20:43:39 castle systemd-networkd[393]: xenbr0: Gained IPv6LL
Mar 25 20:43:39 castle systemd-networkd[393]: xenbr0: Lost carrier
Mar 25 20:43:41 castle systemd-networkd[393]: xenbr0: Gained carrier
Mar 25 20:43:41 castle kernel: xenbr0: port 1(eno1) entered blocking state
Mar 25 20:43:41 castle kernel: xenbr0: port 1(eno1) entered forwarding state
Mar 25 20:43:53 castle systemd-networkd[393]: xenbr0: Configured● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2018-03-25 20:43:37 UTC; 1min 37s ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 320 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 320 (code=exited, status=1/FAILURE)
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_evtchn': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_gntdev': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_gntalloc': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_blkback': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_netback': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_pciback': No such device
Mar 25 20:43:37 castle systemd-modules-load[320]: Failed to insert 'xen_acpi_processor': No such device
Mar 25 20:43:37 castle systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Mar 25 20:43:37 castle systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Mar 25 20:43:37 castle systemd[1]: Failed to start Load Kernel Modules.[ 2.616881] IPv6: ADDRCONF(NETDEV_UP): xenbr0: link is not ready
[ 2.735478] xenbr0: port 1(eno1) entered blocking state
[ 2.735480] xenbr0: port 1(eno1) entered disabled state
[ 2.983177] xenbr0: port 1(eno1) entered blocking state
[ 2.983179] xenbr0: port 1(eno1) entered forwarding state
[ 2.983207] IPv6: ADDRCONF(NETDEV_CHANGE): xenbr0: link becomes ready
[ 3.423168] xenbr0: port 1(eno1) entered disabled state
[ 6.348134] xenbr0: port 1(eno1) entered blocking state
[ 6.348137] xenbr0: port 1(eno1) entered forwarding state● proc-xen.mount - /proc/xen
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: exit-code) since Sun 2018-03-25 20:43:37 UTC; 44min ago
Where: /proc/xen
What: xenfs
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 328 ExecMount=/usr/bin/mount xenfs /proc/xen -t xenfs (code=exited, status=32)
Mar 25 20:43:37 castle mount[328]: mount: /proc/xen: mount point does not exist.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.● proc-xen.mount - /proc/xen
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: exit-code) since Sun 2018-03-25 21:41:39 UTC; 51s ago
Where: /proc/xen
What: xenfs
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 647 ExecMount=/usr/bin/mount xenfs /proc/xen -t xenfs (code=exited, status=32)
Mar 25 21:41:39 castle systemd[1]: Mounting /proc/xen...
Mar 25 21:41:39 castle mount[647]: mount: /proc/xen: mount point does not exist.
Mar 25 21:41:39 castle systemd[1]: proc-xen.mount: Mount process exited, code=exited status=32
Mar 25 21:41:39 castle systemd[1]: proc-xen.mount: Failed with result 'exit-code'.
Mar 25 21:41:39 castle systemd[1]: Failed to mount /proc/xen.Without the fstab entry active, Arch native boots normally and works.
With the fstab entry active, Arch native does not boot. Drops to an emergency prompt.
With or without the fstab entry Xen with Arch dom0 does not boot.
In all cases the Xen will stop after initial loading of the system. Somewhere between the kernel loading and LightDM coming up.
Last edited by twodox (2018-03-30 00:07:59)
Offline
Pages: 1