* Re: [ISSUE] [CLOSED] xen-hypervisor installing into /boot/boot
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17612@inbox.vuxu.org>
@ 2020-08-08 21:11 ` jnbr
0 siblings, 0 replies; only message in thread
From: jnbr @ 2020-08-08 21:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
Closed issue by xelxebar on void-packages repository
https://github.com/void-linux/void-packages/issues/17612
Description:
## Raw Details
$ xbps-query -f xen-hypervisor | grep '^/boot'
/boot/boot/xen-4.10.4.config
/boot/boot/xen-4.10.4.gz
$ sudo xuname
Void 5.3.17_1 x86_64 AuthenticAMD/PV uptodate rrrmFFFFFFFFFFFFFFFFFFFF
$ xbps-query -p pkgver xen-hypervisor
xen-hypervisor-4.10.4_2
## Discussion
The above, of course, causes grub to not detect the presence of xen. I was able to work around this by moving `/boot/boot/*` into `/boot` and running `xbps-reconfigure -f xen-hypervisor`, but that is clearly a hack.
I tried compiling xen locally to see if I could spot something funny, but nothing caught my eye. Am I just missing something silly?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-08-08 21:11 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17612@inbox.vuxu.org>
2020-08-08 21:11 ` [ISSUE] [CLOSED] xen-hypervisor installing into /boot/boot jnbr
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).