On Tue, May 23, 2023 at 06:32:07PM +0300, David Abdurachmanov wrote:
> On Tue, May 23, 2023 at 6:12 PM Andrea Bolognani wrote:
> > Put it another way: do you have any objections to loading
> > qemu-riscv64_smode/u-boot.bin via -kernel as the default boot
> > strategy for riscv64 VMs? That's what
On Tue, May 23, 2023 at 6:35 PM Richard W.M. Jones wrote:
>
> On Tue, May 23, 2023 at 06:32:07PM +0300, David Abdurachmanov wrote:
> > On Tue, May 23, 2023 at 6:12 PM Andrea Bolognani
> > wrote:
> > >
> > > On Tue, May 23, 2023 at 04:05:04PM +0300, David Abdurachmanov wrote:
> > > > On Tue, May
On Tue, May 23, 2023 at 06:32:07PM +0300, David Abdurachmanov wrote:
> On Tue, May 23, 2023 at 6:12 PM Andrea Bolognani wrote:
> >
> > On Tue, May 23, 2023 at 04:05:04PM +0300, David Abdurachmanov wrote:
> > > On Tue, May 23, 2023 at 3:18 PM Andrea Bolognani
> > > wrote:
> > > > On Tue, May 23,
On Tue, May 23, 2023 at 08:12:17AM -0700, Andrea Bolognani wrote:
> On Tue, May 23, 2023 at 04:05:04PM +0300, David Abdurachmanov wrote:
> > On Tue, May 23, 2023 at 3:18 PM Andrea Bolognani
> > wrote:
> > > On Tue, May 23, 2023 at 11:59:41AM +0100, Richard W.M. Jones wrote:
> > > > I just came
On Tue, May 23, 2023 at 6:12 PM Andrea Bolognani wrote:
>
> On Tue, May 23, 2023 at 04:05:04PM +0300, David Abdurachmanov wrote:
> > On Tue, May 23, 2023 at 3:18 PM Andrea Bolognani
> > wrote:
> > > On Tue, May 23, 2023 at 11:59:41AM +0100, Richard W.M. Jones wrote:
> > > > I just came across
On Tue, May 23, 2023 at 04:05:04PM +0300, David Abdurachmanov wrote:
> On Tue, May 23, 2023 at 3:18 PM Andrea Bolognani wrote:
> > On Tue, May 23, 2023 at 11:59:41AM +0100, Richard W.M. Jones wrote:
> > > I just came across this thread while trying to update the libvirt
> > > instructions on that
On Tue, May 23, 2023 at 5:15 PM Richard W.M. Jones wrote:
>
> On Tue, May 23, 2023 at 04:05:04PM +0300, David Abdurachmanov wrote:
> > We run QEMU in a similar way as any other board.
> >
> > So it's U-Boot SPL, which then loads U-Boot ITB (which typically
> > contains U-Boot proper, OpenSBI
On Tue, May 23, 2023 at 04:05:04PM +0300, David Abdurachmanov wrote:
> We run QEMU in a similar way as any other board.
>
> So it's U-Boot SPL, which then loads U-Boot ITB (which typically
> contains U-Boot proper, OpenSBI FW_DYNAMIC generic binary, and DTB).
> U-Boot SPL transfers control to
On Tue, May 23, 2023 at 3:18 PM Andrea Bolognani wrote:
>
> On Tue, May 23, 2023 at 11:59:41AM +0100, Richard W.M. Jones wrote:
> > I just came across this thread while trying to update the libvirt
> > instructions on that page. Specifically I need to add these to the
> > qemu command line:
> >
On Tue, May 23, 2023 at 11:59:41AM +0100, Richard W.M. Jones wrote:
> I just came across this thread while trying to update the libvirt
> instructions on that page. Specifically I need to add these to the
> qemu command line:
>
> -bios /path/to/u-boot-spl.bin
> -device
On Wed, Mar 22, 2023 at 11:37:10AM -0500, Andrea Bolognani wrote:
> On Wed, Mar 22, 2023 at 10:36:20AM -0300, Daniel Henrique Barboza wrote:
> > I'm not sure if the OS overwrites the firmware when running bare metal.
> > Usually
> > they provide different OS images for QEMU/libvirt and bare metal
On Mon, Apr 10, 2023 at 07:50:36PM -0300, Daniel Henrique Barboza wrote:
> On 4/7/23 15:12, Andrea Bolognani wrote:
> > On Tue, Mar 28, 2023 at 04:46:45PM -0300, Daniel Henrique Barboza wrote:
> So, I talked with Canonical a few months back about this package. I'm using a
> F37
> dev box and I
On Tue, Apr 11, 2023 at 01:14:27PM +0200, Gerd Hoffmann wrote:
> > The second approach is the one described in the Ubuntu wiki[3], and
> > also requires passing two files to QEMU, except this time they come
> > from the opensbi and u-boot-qemu packages respectively. The usage
> > looks like
> >
>
Hi,
> The second approach is the one described in the Ubuntu wiki[3], and
> also requires passing two files to QEMU, except this time they come
> from the opensbi and u-boot-qemu packages respectively. The usage
> looks like
>
> -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf
>
On 4/7/23 15:12, Andrea Bolognani wrote:
On Tue, Mar 28, 2023 at 04:46:45PM -0300, Daniel Henrique Barboza wrote:
On 3/22/23 13:37, Andrea Bolognani wrote:
On Wed, Mar 22, 2023 at 10:36:20AM -0300, Daniel Henrique Barboza wrote:
I'm not sure if the OS overwrites the firmware when running
On Fri, Apr 07, 2023 at 11:12:22AM -0700, Andrea Bolognani wrote:
> Getting the Fedora version to work would be trickier. As far as I can
> tell, there's currently no spec-compliant way to describe a firmware
> that requires both -bios and -kernel to be used at the same time.
> Should the spec be
On Tue, Mar 28, 2023 at 04:46:45PM -0300, Daniel Henrique Barboza wrote:
> On 3/22/23 13:37, Andrea Bolognani wrote:
> > On Wed, Mar 22, 2023 at 10:36:20AM -0300, Daniel Henrique Barboza wrote:
> > > I'm not sure if the OS overwrites the firmware when running bare metal.
> > > Usually
> > > they
On 3/22/23 13:37, Andrea Bolognani wrote:
On Wed, Mar 22, 2023 at 10:36:20AM -0300, Daniel Henrique Barboza wrote:
I'm not sure if the OS overwrites the firmware when running bare metal. Usually
they provide different OS images for QEMU/libvirt and bare metal systems,
probably
to account
On Wed, Mar 22, 2023 at 04:52:34PM +, Daniel P. Berrangé wrote:
> On Wed, Mar 22, 2023 at 11:37:10AM -0500, Andrea Bolognani wrote:
> > Note that the firmware descriptor format already supports u-boot as
> > the firmware type. So in the long run ideally you'd only need to
> > specify
> >
> >
On Wed, Mar 22, 2023 at 11:37:10AM -0500, Andrea Bolognani wrote:
> On Wed, Mar 22, 2023 at 10:36:20AM -0300, Daniel Henrique Barboza wrote:
> > I'm not sure if the OS overwrites the firmware when running bare metal.
> > Usually
> > they provide different OS images for QEMU/libvirt and bare metal
On Wed, Mar 22, 2023 at 10:36:20AM -0300, Daniel Henrique Barboza wrote:
> I'm not sure if the OS overwrites the firmware when running bare metal.
> Usually
> they provide different OS images for QEMU/libvirt and bare metal systems,
> probably
> to account for these differences. Baking the
On Wed, Mar 22, 2023 at 10:40:33AM -0300, Daniel Henrique Barboza wrote:
> On 3/22/23 10:02, Andrea Bolognani wrote:
> > On Wed, Mar 22, 2023 at 09:32:21AM -0300, Daniel Henrique Barboza wrote:
> > > VIR_DOMAIN_LOADER_TYPE_OTHER seems more appropriate to indicate that the
> > > firmware
> > >
On 3/22/23 10:05, Daniel P. Berrangé wrote:
On Wed, Mar 22, 2023 at 06:10:18AM -0300, Daniel Henrique Barboza wrote:
Today, trying to boot a RISC-V Fedora Rawhide image in a RISC-V QEMU domain
results in the following error:
error: Failed to start domain 'riscv-fedora'
error: internal
On 3/22/23 10:02, Andrea Bolognani wrote:
On Wed, Mar 22, 2023 at 09:32:21AM -0300, Daniel Henrique Barboza wrote:
On 3/22/23 06:42, Daniel Henrique Barboza wrote:
On 3/22/23 06:25, Daniel P. Berrangé wrote:
On Wed, Mar 22, 2023 at 06:10:18AM -0300, Daniel Henrique Barboza wrote:
+ if
On Wed, Mar 22, 2023 at 09:32:21AM -0300, Daniel Henrique Barboza wrote:
> On 3/22/23 06:42, Daniel Henrique Barboza wrote:
> > On 3/22/23 06:25, Daniel P. Berrangé wrote:
> > > On Wed, Mar 22, 2023 at 06:10:18AM -0300, Daniel Henrique Barboza wrote:
> > > > + if (loader->type !=
On Wed, Mar 22, 2023 at 06:10:18AM -0300, Daniel Henrique Barboza wrote:
> Today, trying to boot a RISC-V Fedora Rawhide image in a RISC-V QEMU domain
> results in the following error:
>
>
> error: Failed to start domain 'riscv-fedora'
> error: internal error: process exited while connecting
On 3/22/23 06:42, Daniel Henrique Barboza wrote:
On 3/22/23 06:25, Daniel P. Berrangé wrote:
On Wed, Mar 22, 2023 at 06:10:18AM -0300, Daniel Henrique Barboza wrote:
Today, trying to boot a RISC-V Fedora Rawhide image in a RISC-V QEMU domain
results in the following error:
error:
On 3/22/23 06:25, Daniel P. Berrangé wrote:
On Wed, Mar 22, 2023 at 06:10:18AM -0300, Daniel Henrique Barboza wrote:
Today, trying to boot a RISC-V Fedora Rawhide image in a RISC-V QEMU domain
results in the following error:
error: Failed to start domain 'riscv-fedora'
error: internal
On Wed, Mar 22, 2023 at 06:10:18AM -0300, Daniel Henrique Barboza wrote:
> Today, trying to boot a RISC-V Fedora Rawhide image in a RISC-V QEMU domain
> results in the following error:
>
>
> error: Failed to start domain 'riscv-fedora'
> error: internal error: process exited while connecting
Today, trying to boot a RISC-V Fedora Rawhide image in a RISC-V QEMU domain
results in the following error:
error: Failed to start domain 'riscv-fedora'
error: internal error: process exited while connecting to monitor:
2023-03-20T17:31:02.650862Z qemu-system-riscv64: Some ROM regions are
30 matches
Mail list logo
