On Tue, 9 Jan 2024 at 16:31, Peter Maydell wrote:
>
> On Tue, 9 Jan 2024 at 16:24, Michael Tokarev wrote:
> >
> > 09.01.2024 16:52, Peter Maydell:
> > ..
> > > Oh, your kernel isn't an LPAE one (i.e. CONFIG_LPAE is not
> > > set). That will obviously never be able to access registers
> > > above
On Tue, 9 Jan 2024 at 16:24, Michael Tokarev wrote:
>
> 09.01.2024 16:52, Peter Maydell:
> ..
> > Oh, your kernel isn't an LPAE one (i.e. CONFIG_LPAE is not
> > set). That will obviously never be able to access registers
> > above the 4GB mark (though the kernel's error message in this
> > situati
On 1/9/24 15:31, Peter Maydell wrote:
> On Tue, 9 Jan 2024 at 14:21, Alex Bennée wrote:
>>
>> Peter Maydell writes:
>>
>>> On Tue, 9 Jan 2024 at 11:33, Peter Maydell wrote:
On Mon, 8 Jan 2024 at 17:38, Michael Tokarev wrote:
> Speaking of config. This is standard debian config, I'm
09.01.2024 16:52, Peter Maydell:
..
Oh, your kernel isn't an LPAE one (i.e. CONFIG_LPAE is not
set). That will obviously never be able to access registers
above the 4GB mark (though the kernel's error message in this
situation is a bit unhelpful and could perhaps be improved).
If I set CONFIG_LPA
Peter Maydell writes:
> On Tue, 9 Jan 2024 at 14:21, Alex Bennée wrote:
>>
>> Peter Maydell writes:
>>
>> > On Tue, 9 Jan 2024 at 11:33, Peter Maydell
>> > wrote:
>> >> On Mon, 8 Jan 2024 at 17:38, Michael Tokarev wrote:
>> >> > Speaking of config. This is standard debian config, I'm attachi
On Tue, 9 Jan 2024 at 14:21, Alex Bennée wrote:
>
> Peter Maydell writes:
>
> > On Tue, 9 Jan 2024 at 11:33, Peter Maydell wrote:
> >> On Mon, 8 Jan 2024 at 17:38, Michael Tokarev wrote:
> >> > Speaking of config. This is standard debian config, I'm attaching one
> >> > to this email. It can b
Peter Maydell writes:
> On Tue, 9 Jan 2024 at 11:33, Peter Maydell wrote:
>> On Mon, 8 Jan 2024 at 17:38, Michael Tokarev wrote:
>> > Speaking of config. This is standard debian config, I'm attaching one
>> > to this email. It can be found in the package, eg
>> > http://deb.debian.org/debian/p
On Tue, 9 Jan 2024 at 11:33, Peter Maydell wrote:
> On Mon, 8 Jan 2024 at 17:38, Michael Tokarev wrote:
> > Speaking of config. This is standard debian config, I'm attaching one
> > to this email. It can be found in the package, eg
> > http://deb.debian.org/debian/pool/main/l/linux/linux-image-6
On Mon, 8 Jan 2024 at 17:38, Michael Tokarev wrote:
>
> 08.01.2024 20:07, Peter Maydell wrote:
> ..
> > I'm trying to figure out what kind of kernel config causes
> > this. If I do an upstream build of v6.6.9 with this config:
> > https://people.linaro.org/~peter.maydell/arm-6.6.9-config
> >
> > t
On Thu, 4 Jan 2024 at 17:17, Michael Tokarev wrote:
>
> 04.01.2024 19:25, Michael Tokarev wrote:
> ...
> > this archive contains kernel+initrd. I run it this way:
> >
> > qemu-system-arm -append root=LABEL=debvm -nographic -machine type=virt \
> > -drive media=disk,format=raw,file=vmlinuz,if=vi
On Thu, 4 Jan 2024 at 17:17, Michael Tokarev wrote:
>
> 04.01.2024 19:25, Michael Tokarev wrote:
> ...
> > this archive contains kernel+initrd. I run it this way:
> >
> > qemu-system-arm -append root=LABEL=debvm -nographic -machine type=virt \
> > -drive media=disk,format=raw,file=vmlinuz,if=vi
04.01.2024 19:25, Michael Tokarev wrote:
...
this archive contains kernel+initrd. I run it this way:
qemu-system-arm -append root=LABEL=debvm -nographic -machine type=virt \
-drive media=disk,format=raw,file=vmlinuz,if=virtio,snapshot=on \
-no-user-config -m 1G -kernel vmlinuz -initrd initr
04.01.2024 17:41, Peter Maydell wrote:
..
Can you provide a complete repro case including full command
line and all image files needed to run it, please?
Sure, please excuse me for not doing this at the very beginning.
The test is just standard debian kernel+initrd (I used sid/unstable
kernel,
On Thu, 21 Dec 2023 at 11:51, Michael Tokarev wrote:
>
> It looks like virtio-pci is entirely broke in qemu-system-arm, at least in tcg
> mode running on x86. The guest (current linux system) just does not detect
> any virtio-pci devices at all.
>
> When 8.1 is booting, the following messages are
On Thu, 4 Jan 2024 at 14:09, Peter Maydell wrote:
>
> On Thu, 21 Dec 2023 at 22:00, Alex Bennée wrote:
> > modified tests/avocado/tuxrun_baselines.py
> > @@ -168,7 +168,7 @@ def run_tuxtest_tests(self, haltmsg):
> > def common_tuxrun(self,
> >csums=None,
> >
On Thu, 21 Dec 2023 at 22:00, Alex Bennée wrote:
> modified tests/avocado/tuxrun_baselines.py
> @@ -168,7 +168,7 @@ def run_tuxtest_tests(self, haltmsg):
> def common_tuxrun(self,
>csums=None,
>dt=None,
> - drive="virtio-b
Alex Bennée writes:
> Michael Tokarev writes:
>
>> It looks like virtio-pci is entirely broke in qemu-system-arm, at least in
>> tcg
>> mode running on x86. The guest (current linux system) just does not detect
>> any virtio-pci devices at all.
>>
>> When 8.1 is booting, the following messages
Michael Tokarev writes:
> It looks like virtio-pci is entirely broke in qemu-system-arm, at least in tcg
> mode running on x86. The guest (current linux system) just does not detect
> any virtio-pci devices at all.
>
> When 8.1 is booting, the following messages are displayed (debian initramfs):
It looks like virtio-pci is entirely broke in qemu-system-arm, at least in tcg
mode running on x86. The guest (current linux system) just does not detect
any virtio-pci devices at all.
When 8.1 is booting, the following messages are displayed (debian initramfs):
Loading, please wait...
Starting
19 matches
Mail list logo
