At Sun, 01 Jun 2025 07:16:18 +0700, Robert Elz wrote:
Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0
not ELF binary (Was: Re: EFI and Xen))
>
> Date:Sat, 31 May 2025 13:24:33 -0700
> From:"Greg A. Woods"
At Sat, 31 May 2025 13:29:05 -0700, "Greg A. Woods" wrote:
Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0
not ELF binary (Was: Re: EFI and Xen))
>
> [1 ]
> At Fri, 30 May 2025 23:54:32 -0400, Chuck Zmudzinski
> wrote:
> Subject: Re:
Date:Sat, 31 May 2025 13:24:33 -0700
From:"Greg A. Woods"
Message-ID:
| though that would be secondary if there were support to configure a dump
| device after boot. FreeBSD has had a dumpon(8) utility since 2.0.5.
Of course NetBSD can do that, see swapctl(8)
On 5/30/2025 11:57 AM, Julian Coleman wrote:
> Hi,
>
>> Of course this also assumes "booted_partition" is
>> declared as an uint32_t, or equivalent. I could not find its declaration
>> in arch/xen/xen/xen_machdep.c and presumably it is declared in a header
>> somewhere.
>
> Migh
At Fri, 30 May 2025 22:26:48 -0400, Chuck Zmudzinski wrote:
Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0
not ELF binary (Was: Re: EFI and Xen))
>
> I am sure setting bootdev=hd2d will not work. Those are names of
> devices the bootloader understands
On 5/31/2025 4:29 PM, Greg A. Woods wrote:
> At Fri, 30 May 2025 23:54:32 -0400, Chuck Zmudzinski
> wrote:
> Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen
> 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and Xen))
>>
>> On 5/30/2025 4:35 PM, Greg A. Woods
At Fri, 30 May 2025 23:54:32 -0400, Chuck Zmudzinski wrote:
Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0
not ELF binary (Was: Re: EFI and Xen))
>
> On 5/30/2025 4:35 PM, Greg A. Woods wrote:
> > On one such legacy system I pass "bootdev=sd0&qu
On 5/30/2025 4:35 PM, Greg A. Woods wrote:
> At Fri, 30 May 2025 06:29:49 -0400, Chuck Zmudzinski
> wrote:
> Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen
> 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and Xen))
>>
> ...
>> Maybe such simplicity is n
On 5/29/2025 4:02 PM, Greg A. Woods wrote:
> At Thu, 29 May 2025 15:01:50 -0400, Chuck Zmudzinski
> wrote:
>
>> When I pass bootdev=dk12 in boot.cfg, the bootloader strangely tries dk1 as
>> root
>> (which is wrong) and correctly detects dk11 as the dump device. But it never
>> gives me the cha
On 5/30/2025 4:35 PM, Greg A. Woods wrote:
> At Fri, 30 May 2025 06:29:49 -0400, Chuck Zmudzinski
> wrote:
> Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen
> 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and Xen))
>>
>> I am not sure I understand why it
At Fri, 30 May 2025 06:29:49 -0400, Chuck Zmudzinski wrote:
Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0
not ELF binary (Was: Re: EFI and Xen))
>
> I am not sure I understand why it is even necessary to do this search for the
> boot device on modern
On Fri, May 30, 2025 at 10:53:52AM -0400, Chuck Zmudzinski wrote:
[...]
> if (booted_partition & 0xfff0)
> continue;
>
> [...] Of course this also assumes "booted_partition" is
> declared as an uint32_t, or equivalent.
Maybe use
On 5/30/2025 3:36 AM, Manuel Bouyer wrote:
> On Fri, May 30, 2025 at 12:53:08AM -0400, Chuck Zmudzinski wrote:
>> On 5/29/2025 5:20 PM, Chuck Zmudzinski wrote:
>> > On 5/29/2025 3:23 PM, Manuel Bouyer wrote:
>> >> On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
>> >>> [...]
>> >>
On 5/30/2025 6:29 AM, Chuck Zmudzinski wrote:
> On 5/29/2025 4:02 PM, Greg A. Woods wrote:
>> At Thu, 29 May 2025 15:01:50 -0400, Chuck Zmudzinski
>> wrote:
>> ...
>>
>>> When I pass bootdev=dk12 in boot.cfg, the bootloader strangely tries dk1 as
>>> root
>>> (which is wrong) and correctly det
On Fri, May 30, 2025 at 12:02:07PM +0200, Christoph Badura wrote:
> On Thu, May 29, 2025 at 09:23:46PM +0200, Manuel Bouyer wrote:
> > On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
> > > The strange part is that it is necessary to pass -c to the DOM0 in
> > > boot.cfg to
> > >
On 5/29/2025 4:02 PM, Greg A. Woods wrote:
> At Thu, 29 May 2025 15:01:50 -0400, Chuck Zmudzinski
> wrote:
> ...
>
>> When I pass bootdev=dk12 in boot.cfg, the bootloader strangely tries dk1 as
>> root
>> (which is wrong) and correctly detects dk11 as the dump device. But it never
>> gives me
On Thu, May 29, 2025 at 09:23:46PM +0200, Manuel Bouyer wrote:
> On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
> > The strange part is that it is necessary to pass -c to the DOM0 in boot.cfg
> > to
> > actually disable com* and the bootloader does not execute the
> > userconf=
On Fri, May 30, 2025 at 12:53:08AM -0400, Chuck Zmudzinski wrote:
> On 5/29/2025 5:20 PM, Chuck Zmudzinski wrote:
> > On 5/29/2025 3:23 PM, Manuel Bouyer wrote:
> >> On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
> >>> [...]
> >>> When I pass bootdev=dk12 in boot.cfg, the bootlo
On 5/29/2025 5:20 PM, Chuck Zmudzinski wrote:
> On 5/29/2025 3:23 PM, Manuel Bouyer wrote:
>> On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
>>> [...]
>>> When I pass bootdev=dk12 in boot.cfg, the bootloader strangely tries dk1 as
>>> root
>>> (which is wrong) and correctly det
On 5/29/2025 10:24 PM, Chuck Zmudzinski wrote:
> On 5/29/2025 7:39 PM, Manuel Bouyer wrote:
>> On Thu, May 29, 2025 at 05:20:53PM -0400, Chuck Zmudzinski wrote:
>>> On 5/29/2025 3:23 PM, Manuel Bouyer wrote:
>>> > On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
>>> >> [...]
>>>
>
On 5/29/2025 7:39 PM, Manuel Bouyer wrote:
> On Thu, May 29, 2025 at 05:20:53PM -0400, Chuck Zmudzinski wrote:
>> On 5/29/2025 3:23 PM, Manuel Bouyer wrote:
>> > On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
>> >> [...]
>>
>> >
>> > This is because the userconf command from th
On Thu, May 29, 2025 at 05:20:53PM -0400, Chuck Zmudzinski wrote:
> On 5/29/2025 3:23 PM, Manuel Bouyer wrote:
> > On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
> >> [...]
>
> >
> > This is because the userconf command from the boot loader doens't make it
> > to the dom0 kerne
On 5/29/2025 6:26 PM, Greg A. Woods wrote:
> At Thu, 29 May 2025 17:37:10 -0400, Chuck Zmudzinski
> wrote:
> Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen
> 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and Xen))
>>
>> It seems to me our DOM0 c
At Thu, 29 May 2025 17:37:10 -0400, Chuck Zmudzinski wrote:
Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0
not ELF binary (Was: Re: EFI and Xen))
>
> It seems to me our DOM0 config assumes Xen is not successfully hiding the
> serial console used by Xen
On 5/29/2025 5:27 PM, Greg A. Woods wrote:
> At Thu, 29 May 2025 16:30:39 -0400, Chuck Zmudzinski
> wrote:
> Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen
> 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and Xen))
>>
>> Ok, let's see what happens.
At Thu, 29 May 2025 16:30:39 -0400, Chuck Zmudzinski wrote:
Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0
not ELF binary (Was: Re: EFI and Xen))
>
> Ok, let's see what happens. I use this boot command line:
>
> menu=Boot normally with Xen:dev h
On 5/29/2025 3:23 PM, Manuel Bouyer wrote:
> On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
>> [...]
>
> This is because the userconf command from the boot loader doens't make it
> to the dom0 kernel.
> Remember that when booting Xen; Xen is the kernel and XEN3_DOM0 a module.
>
On 5/29/2025 4:30 PM, Chuck Zmudzinski wrote:
> On 5/29/2025 4:02 PM, Greg A. Woods wrote:
>>
>> Do you get similar results if you try to boot GENERIC from that same
>> device? The code in arch/x86/x86/x86_autoconf.c looks like it tries a
>> bit harder, but maybe it fails too?
>
> I boot GENERIC
On 5/29/2025 4:02 PM, Greg A. Woods wrote:
> At Thu, 29 May 2025 15:01:50 -0400, Chuck Zmudzinski
> wrote:
> Subject: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0
> not ELF binary (Was: Re: EFI and Xen))
>>
>> On 5/27/2025 7:37 PM, Greg A. Wood
At Thu, 29 May 2025 15:01:50 -0400, Chuck Zmudzinski wrote:
Subject: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0 not
ELF binary (Was: Re: EFI and Xen))
>
> On 5/27/2025 7:37 PM, Greg A. Woods wrote:
> > However it doesn't look like you're using an o
On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
> [...]
> db{0}>
>
> >
> > Perhaps it has something to do with the fact you're using what Xen calls
> > "com2" for the serial console.
>
> Yes, that is exactly the problem, and since DOM0 cannot detect which port Xen
> is using, o
On 5/27/2025 7:37 PM, Greg A. Woods wrote:
> At Tue, 27 May 2025 12:39:43 -0400, Chuck Zmudzinski
> wrote:
> Subject: [SOLVED] Re: Xen 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and
> Xen)
>>
>> It is definitely not production ready, but I got it to work with the
At Tue, 27 May 2025 12:39:43 -0400, Chuck Zmudzinski wrote:
Subject: [SOLVED] Re: Xen 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and
Xen)
>
> It is definitely not production ready, but I got it to work with the following
> tweaks and hacks.
>
> boot command used:
>
> me
On 5/26/2025 2:06 AM, Manuel Bouyer wrote:
> On Sun, May 25, 2025 at 11:40:12PM -0400, Chuck Zmudzinski wrote:
>> On 5/25/2025 11:25 AM, Manuel Bouyer wrote:
>> > On Sun, May 25, 2025 at 08:54:37AM -0400, Chuck Zmudzinski wrote:
>> >> No difference with the larger conring_size, unfortunately.
>> >
On 5/26/2025 2:06 AM, Manuel Bouyer wrote:
> On Sun, May 25, 2025 at 11:40:12PM -0400, Chuck Zmudzinski wrote:
>> On 5/25/2025 11:25 AM, Manuel Bouyer wrote:
>> > On Sun, May 25, 2025 at 08:54:37AM -0400, Chuck Zmudzinski wrote:
>> >> No difference with the larger conring_size, unfortunately.
>> >
On Sun, May 25, 2025 at 11:40:12PM -0400, Chuck Zmudzinski wrote:
> On 5/25/2025 11:25 AM, Manuel Bouyer wrote:
> > On Sun, May 25, 2025 at 08:54:37AM -0400, Chuck Zmudzinski wrote:
> >> No difference with the larger conring_size, unfortunately.
> >
> > Can you try a -current kernel, or a very rec
On 5/25/2025 11:25 AM, Manuel Bouyer wrote:
> On Sun, May 25, 2025 at 08:54:37AM -0400, Chuck Zmudzinski wrote:
>> No difference with the larger conring_size, unfortunately.
>
> Can you try a -current kernel, or a very recent kernel from the netbsd-10
> branch ? There have been fixes in the last f
On 5/25/2025 11:25 AM, Manuel Bouyer wrote:
> On Sun, May 25, 2025 at 08:54:37AM -0400, Chuck Zmudzinski wrote:
>> No difference with the larger conring_size, unfortunately.
>
> Can you try a -current kernel, or a very recent kernel from the netbsd-10
> branch ? There have been fixes in the last f
On Sun, May 25, 2025 at 08:54:37AM -0400, Chuck Zmudzinski wrote:
> No difference with the larger conring_size, unfortunately.
Can you try a -current kernel, or a very recent kernel from the netbsd-10
branch ? There have been fixes in the last few days that could help with
very recent CPUs
--
Ma
On 5/24/2025 10:09 AM, Manuel Bouyer wrote:
> On Sat, May 24, 2025 at 08:16:42AM -0400, Chuck Zmudzinski wrote:
>> >
>> > N.B. My cpu has 14 cores and 20 threads because there are 6 cores that
>> > have hyperthreading - so it hangs where the hyperthreading starts. Last
>> > thing to try is with
On 5/24/2025 10:09 AM, Manuel Bouyer wrote:
> On Sat, May 24, 2025 at 08:16:42AM -0400, Chuck Zmudzinski wrote:
>> >
>> > N.B. My cpu has 14 cores and 20 threads because there are 6 cores that
>> > have hyperthreading - so it hangs where the hyperthreading starts. Last
>> > thing to try is with
On Sat, May 24, 2025 at 08:16:42AM -0400, Chuck Zmudzinski wrote:
> >
> > N.B. My cpu has 14 cores and 20 threads because there are 6 cores that have
> > hyperthreading - so it hangs where the hyperthreading starts. Last thing to
> > try is with smt=false...
>
>
> Adding smt=false to the Xen c
On 5/24/2025 8:08 AM, Chuck Zmudzinski wrote:
> On 5/24/2025 7:38 AM, Manuel Bouyer wrote:
>> On Sat, May 24, 2025 at 07:00:55AM -0400, Chuck Zmudzinski wrote:
>>> On 5/24/2025 3:40 AM, Manuel Bouyer wrote:
>>> > On Fri, May 23, 2025 at 10:06:05PM -0400, Chuck Zmudzinski wrote:
>>> >> On 5/23/2025
On 5/24/2025 7:38 AM, Manuel Bouyer wrote:
> On Sat, May 24, 2025 at 07:00:55AM -0400, Chuck Zmudzinski wrote:
>> On 5/24/2025 3:40 AM, Manuel Bouyer wrote:
>> > On Fri, May 23, 2025 at 10:06:05PM -0400, Chuck Zmudzinski wrote:
>> >> On 5/23/2025 5:18 PM, Chuck Zmudzinski wrote:
>> >> > On 5/23/202
On Sat, May 24, 2025 at 07:00:55AM -0400, Chuck Zmudzinski wrote:
> On 5/24/2025 3:40 AM, Manuel Bouyer wrote:
> > On Fri, May 23, 2025 at 10:06:05PM -0400, Chuck Zmudzinski wrote:
> >> On 5/23/2025 5:18 PM, Chuck Zmudzinski wrote:
> >> > On 5/23/2025 4:22 PM, Manuel Bouyer wrote:
> >> >> On Fri, M
On 5/24/2025 3:40 AM, Manuel Bouyer wrote:
> On Fri, May 23, 2025 at 10:06:05PM -0400, Chuck Zmudzinski wrote:
>> On 5/23/2025 5:18 PM, Chuck Zmudzinski wrote:
>> > On 5/23/2025 4:22 PM, Manuel Bouyer wrote:
>> >> On Fri, May 23, 2025 at 04:19:46PM -0400, Chuck Zmudzinski wrote:
>> >>> On 5/23/2025
On Fri, May 23, 2025 at 10:06:05PM -0400, Chuck Zmudzinski wrote:
> On 5/23/2025 5:18 PM, Chuck Zmudzinski wrote:
> > On 5/23/2025 4:22 PM, Manuel Bouyer wrote:
> >> On Fri, May 23, 2025 at 04:19:46PM -0400, Chuck Zmudzinski wrote:
> >>> On 5/23/2025 4:15 PM, Manuel Bouyer wrote:
> >>> > On Fri, Ma
On 5/23/2025 5:18 PM, Chuck Zmudzinski wrote:
> On 5/23/2025 4:22 PM, Manuel Bouyer wrote:
>> On Fri, May 23, 2025 at 04:19:46PM -0400, Chuck Zmudzinski wrote:
>>> On 5/23/2025 4:15 PM, Manuel Bouyer wrote:
>>> > On Fri, May 23, 2025 at 04:13:01PM -0400, Chuck Zmudzinski wrote:
>>> >> [...]
>>> >>
On 5/23/2025 5:18 PM, Chuck Zmudzinski wrote:
> On 5/23/2025 4:22 PM, Manuel Bouyer wrote:
>> On Fri, May 23, 2025 at 04:19:46PM -0400, Chuck Zmudzinski wrote:
>>> On 5/23/2025 4:15 PM, Manuel Bouyer wrote:
>>> > On Fri, May 23, 2025 at 04:13:01PM -0400, Chuck Zmudzinski wrote:
>>> >> [...]
>>> >>
On 5/23/2025 4:22 PM, Manuel Bouyer wrote:
> On Fri, May 23, 2025 at 04:19:46PM -0400, Chuck Zmudzinski wrote:
>> On 5/23/2025 4:15 PM, Manuel Bouyer wrote:
>> > On Fri, May 23, 2025 at 04:13:01PM -0400, Chuck Zmudzinski wrote:
>> >> [...]
>> >> I needed to acquire a PCI serial card to get some use
On Fri, May 23, 2025 at 04:19:46PM -0400, Chuck Zmudzinski wrote:
> On 5/23/2025 4:15 PM, Manuel Bouyer wrote:
> > On Fri, May 23, 2025 at 04:13:01PM -0400, Chuck Zmudzinski wrote:
> >> [...]
> >> I needed to acquire a PCI serial card to get some useful messages because
> >> the motherboard does n
On 5/23/2025 4:15 PM, Manuel Bouyer wrote:
> On Fri, May 23, 2025 at 04:13:01PM -0400, Chuck Zmudzinski wrote:
>> [...]
>> I needed to acquire a PCI serial card to get some useful messages because
>> the motherboard does not have a built-in serial port.
>>
>> It appears Xen 4.18.4_20241221nb0 fro
On Fri, May 23, 2025 at 04:13:01PM -0400, Chuck Zmudzinski wrote:
> [...]
> I needed to acquire a PCI serial card to get some useful messages because the
> motherboard does not have a built-in serial port.
>
> It appears Xen 4.18.4_20241221nb0 from pkgsrc crashes on my box before the
> NetBSD do
On 5/14/2025 3:15 AM, Manuel Bouyer wrote:
> On Tue, May 13, 2025 at 10:59:13PM -0400, Chuck Zmudzinski wrote:
>> So, is netbsd/xen supposed to work with UEFI booting, or are there issues? I
>> saw this commit which I thought might have enabled support for booting
>> netbsd/xen on UEFI-only syste
On Wed, 14 May 2025, Chuck Zmudzinski wrote:
On 5/14/2025 1:33 PM, Manuel Bouyer wrote:
On Wed, May 14, 2025 at 09:54:35AM -0400, Chuck Zmudzinski wrote:
Another odd thing I saw with this system (Intel Raptor Lake i5-14500). I first
installed NetBSD 10.1 as a Xen HVM DomU on Xen 4.19.2 distrib
On 5/14/2025 1:33 PM, Manuel Bouyer wrote:
> On Wed, May 14, 2025 at 09:54:35AM -0400, Chuck Zmudzinski wrote:
>> Another odd thing I saw with this system (Intel Raptor Lake i5-14500). I
>> first installed NetBSD 10.1 as a Xen HVM DomU on Xen 4.19.2 distributed by
>> Fedora Linux, with a Fedora 4
On 5/14/2025 1:33 PM, Manuel Bouyer wrote:
> On Wed, May 14, 2025 at 09:54:35AM -0400, Chuck Zmudzinski wrote:
>> Another odd thing I saw with this system (Intel Raptor Lake i5-14500). I
>> first installed NetBSD 10.1 as a Xen HVM DomU on Xen 4.19.2 distributed by
>> Fedora Linux, with a Fedora 4
On Wed, May 14, 2025 at 09:54:35AM -0400, Chuck Zmudzinski wrote:
> Another odd thing I saw with this system (Intel Raptor Lake i5-14500). I
> first installed NetBSD 10.1 as a Xen HVM DomU on Xen 4.19.2 distributed by
> Fedora Linux, with a Fedora 41 Linux PV Dom0 before trying to boot NetBSD PV
On 5/14/2025 3:15 AM, Manuel Bouyer wrote:
> On Tue, May 13, 2025 at 10:59:13PM -0400, Chuck Zmudzinski wrote:
>> So, is netbsd/xen supposed to work with UEFI booting, or are there issues? I
>> saw this commit which I thought might have enabled support for booting
>> netbsd/xen on UEFI-only syste
On Tue, May 13, 2025 at 10:59:13PM -0400, Chuck Zmudzinski wrote:
> On 2/13/2025 10:54 AM, César Catrián C. wrote:
> > Hello,
> >
> >
> > I am migrating a Xen NetBSD 10 system to a new hardware and I would like to
> > know if EFI is supported for XEN to pass on the vga console for keeping on
>
On 2/13/2025 10:54 AM, César Catrián C. wrote:
> Hello,
>
>
> I am migrating a Xen NetBSD 10 system to a new hardware and I would like to
> know if EFI is supported for XEN to pass on the vga console for keeping on
> loading the kernel.
>
> That's because after Xen loading stage at boot, reach
Hello,
I am migrating a Xen NetBSD 10 system to a new hardware and I would like to
know if EFI is supported for XEN to pass on the vga console for keeping on
loading the kernel.
That's because after Xen loading stage at boot, reach the stage of
relinquishing VGA console, it goes blank.
If th
62 matches
Mail list logo
