On Mon, 19 Aug 2019 10:03:35 -0700
Adam Williamson wrote:
> On Mon, 2019-08-19 at 11:46 -0500, Greg Hellings wrote:
> > On Thu, Aug 15, 2019 at 3:42 PM Steven Munroe
> > wrote:
> >
> > > > My qemu boot command is currently:
> > > > qemu-system-ppc64 -m 2048 -smp 2 -machine pseries -cpu power9
On Mon, 2019-08-19 at 11:46 -0500, Greg Hellings wrote:
> On Thu, Aug 15, 2019 at 3:42 PM Steven Munroe wrote:
>
> > > My qemu boot command is currently:
> > > qemu-system-ppc64 -m 2048 -smp 2 -machine pseries -cpu power9 -hda
> > -cdrom
> >
> > Looks like you are running an LE image in the
On Thu, Aug 15, 2019 at 3:42 PM Steven Munroe wrote:
> > My qemu boot command is currently:
> > qemu-system-ppc64 -m 2048 -smp 2 -machine pseries -cpu power9 -hda
> -cdrom
>
> Looks like you are running an LE image in the BE machine:
>
> try qemu-system-ppc64le
>
I can't find that executable
> My qemu boot command is currently:
> qemu-system-ppc64 -m 2048 -smp 2 -machine pseries -cpu power9 -hda -cdrom
Looks like you are running an LE image in the BE machine:
try qemu-system-ppc64le
___
devel mailing list -- devel@lists.fedoraproject.org
On Thu, 15 Aug 2019, Greg Hellings wrote:
I'm trying to track down a build error in my package that appears only on
ppc64le architectures in Rawhide. As I have no access to ppc64le machines,
I'm attempting to boot a VM with qemu. But when I get into the system many
of the more useful commands
Halp!
I'm trying to track down a build error in my package that appears only on
ppc64le architectures in Rawhide. As I have no access to ppc64le machines,
I'm attempting to boot a VM with qemu. But when I get into the system many
of the more useful commands aren't working properly. Like "dnf".
