Re: upgrading my dom0 box (again?) - foolish?

[Jeff Rizzo <riz%tastylime.net@localhost>]

On 10/24/25 12:22, Jeff Rizzo wrote:
> This is very helpful.  As I've been digging back in, luckily a lot of 
> this is becoming familiar again.  :)   I've so
>
> far managed to at least remember how /boot.cfg and all that fits in, 
> and I've done a from-scratch reboot just
>
> to make sure it all comes back as expected - thus far, no problems, so 
> I'll follow your suggestion and try
>
> Xen 4.18 next!

OK, some successes and some failures.  First, as you noted, I needed a 
9.4 kernel in order to boot Xen 4.18 - the Xen kernel crashed under 9.2.


Without installing the newer xentools418 package, however, I can't 
launch any domUs (xl fails noisily).  I'm

hesitant to install it, though, because I will have to uninstall 
xentools411 since they install to the same

locations - and then I'm stuck if there are any problems.  One of the 
problems I foresee is that it looks as if

PAE guest support is removed in 4.18; it is claimed that I should be 
able to run my PAE guest with "pvshim", but

when I follow the suggestion here:

https://wiki.xenproject.org/wiki/Run_PV_in_PVH_container

(the suggestion being, 'add type="pvh" and pvshim=1 to the domU 
config'), the domU does not run successfully under Xen 4.11 (which I 
think it *should* since 4.11 appears to support this according to that 
webpage).

...the domU crashes repeatedly (I'll paste the console message below).


So... I definitely need this particular domU to work.  I'm hesitant to 
make any further changes which will make

it impossible (or very difficult) to roll back to Xen 4.11 until I get 
this sorted out.  I could (eventually) reinstall

this domU as amd64 - but that's a bit more involved and will delay this 
project.

Looking for recommendations at this point...


Here is the domU crash on the dom0 console, it does this every 15 
seconds or so:

[  82.4194064] xbd backend: attach device vg0-boogersroot (size 2097152) 
for domain 14
[  82.4994050] xbd backend: attach device vg0-boogersusr (size 20971520) 
for domain 14
[  82.5394046] xbd backend: attach device vg0-boogersvar (size 20971520) 
for domain 14
[  82.5594032] xbd backend: attach device vg0-boogersswap (size 2097152) 
for domain 14
[  82.5794032] xbd backend: attach device vg0-boogerswork (size 
257368064) for domain 14
(XEN) d14v0 Triple fault - invoking HVM shutdown action 1
(XEN) *** Dumping Dom14 vcpu#0 state: ***
(XEN) ----[ Xen-4.11.4nb6  x86_64  debug=n   Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    0000:[<000000000034cd3f>]
(XEN) RFLAGS: 0000000000010006   CONTEXT: hvm guest (d14v0)
(XEN) rax: 00000000336ec506   rbx: 0000000000a2d000   rcx: 0000000000000000
(XEN) rdx: 0000000000000030   rsi: 0000000000000000   rdi: 0000000000000000
(XEN) rbp: 00000000ffffffff   rsp: 00000000003dffe8   r8: 0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 0000000000000011   cr4: 0000000000000000
(XEN) cr3: 0000000000000000   cr2: 0000000000000000
(XEN) fsb: 0000000000000000   gsb: 0000000000000000   gss: 0000000000000000
(XEN) ds: 0000   es: 0018   fs: 0030   gs: 0000   ss: 0018   cs: 0000
[  83.3793907] xbd backend: detach device vg0-boogersroot for domain 14
[  83.3893904] xbd backend: detach device vg0-boogersusr for domain 14
[  83.4093893] xbd backend: detach device vg0-boogersvar for domain 14
[  83.4293889] xbd backend: detach device vg0-boogersswap for domain 14
[  83.4493888] xbd backend: detach device vg0-boogerswork for domain 14