All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Kiwi <kkiwi@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, clg@kaod.org
Cc: qemu-ppc <qemu-ppc@nongnu.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Lindsay Ryan <Ryan.Lindsay@petermac.org>,
	"qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org>
Subject: Re: need help with my config
Date: Fri, 30 Jul 2021 12:09:03 -0300	[thread overview]
Message-ID: <CAELHpAAyLcpisUdxqL_7j=Gh47YM6ZjAQuZmRy_4jZQi2P9TqA@mail.gmail.com> (raw)
In-Reply-To: <82ae0532-50c2-7a67-af16-04226cb2986b@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 3629 bytes --]

Just making sure Cedric is also seeing this...

 -Klaus

On Fri, Jul 30, 2021 at 10:27 AM Philippe Mathieu-Daudé <philmd@redhat.com>
wrote:

> Cc'ing qemu-ppc@
>
> On 7/30/21 6:25 AM, Lindsay Ryan wrote:
> > Hi
> > I'm trying to emulate some physical IBM Power 9's that we have. There
> > seems to be plenty of examples of using x86_64 qemu, but slightly less
> > for Power. Unless it's specifically for installing AIX
> > Anyway, I'm trying to boot the VM as I guess a bare metal Power 9 box,
> > then install redhat from Iso on a disk and have it on the network.
> >
> > ./qemu-system-ppc64 -cpu POWER9 -smp cpus=4 -machine pseries -m 4096 -M
> > accel=tcg  -serial stdio -nodefaults -nographic -device
> > megasas,id=scsi0,bus=pci.0,addr=0x5 -drive
> >
> file=/home/hdisk1.qcow2,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none
> > -device
> >
> scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
> > -cdrom /mnt/images/rhel-8.4-ppc64le-boot.iso -monitor
> > telnet:0.0.0.0:3344,server,nowait -netdev
> > bridge,id=net0,helper=qemu-bridge-helper,br=bridge0,id=hostnet0
> >
> > So the megasas gets detected as a raid controller. Yay.
> > But my qcow2 disk image doesn't seem to be plugged into it correctly as
> > it's not detected.
> > It sees the cdrom image and I can boot from it.
> > The other thing I can't get working is the network card.
> >
> > On this host system I have some other x86 kvm's running. So Ideally if I
> > could plug the nic on this vm into
> > 7: virbr0
> >
> > 6: bridge0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> > state UP group default qlen 1000
> >     link/ether 00:25:b5:04:2a:1e brd ff:ff:ff:ff:ff:ff
> >     inet 10.126.24.82/24 brd 10.126.24.255 scope global noprefixroute
> > bridge0
> >        valid_lft forever preferred_lft forever
> >     inet6 fe80::76a8:89ec:fc62:9c94/64 scope link noprefixroute
> >        valid_lft forever preferred_lft forever
> > 7: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> > state UP group default qlen 1000
> >     link/ether 52:54:00:51:db:be brd ff:ff:ff:ff:ff:ff
> >     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
> >        valid_lft forever preferred_lft forever
> >
> > If I can't do that, then I really only need the ppc64 guest to have
> > access out to the internet and I can nat anything incoming
> >
> > Any help, particularly about how to plug virtual disk drives into
> > virtual disk controllers would be helpful
> > regards
> >
> >
> > Ryan Lindsay BEng, MSc.
> > Linux Storage Administrator
> > Research Computing Facility
> >
> >
> > *Disclaimer: *This email (including any attachments or links) may
> > contain confidential and/or legally privileged information and is
> > intended only to be read or used by the addressee. If you are not the
> > intended addressee, any use, distribution, disclosure or copying of this
> > email is strictly prohibited. Confidentiality and legal privilege
> > attached to this email (including any attachments) are not waived or
> > lost by reason of its mistaken delivery to you. If you have received
> > this email in error, please delete it and notify us immediately by
> > telephone or email. Peter MacCallum Cancer Centre provides no guarantee
> > that this transmission is free of virus or that it has not been
> > intercepted or altered and will not be liable for any delay in its
> receipt.
> >
>
>
>

-- 
Klaus Heinrich Kiwi <kkiwi@redhat.com>
Manager, Software Engineering - Red Hat Virtualization

[-- Attachment #2: Type: text/html, Size: 4722 bytes --]

  reply	other threads:[~2021-07-30 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MEYP282MB168775224F9A7690C9F5AEF9F9EC9@MEYP282MB1687.AUSP282.PROD.OUTLOOK.COM>
2021-07-30 13:25 ` need help with my config Philippe Mathieu-Daudé
2021-07-30 15:09   ` Klaus Kiwi [this message]
2021-07-30 16:50   ` Cédric Le Goater
2021-08-02 23:22     ` Lindsay Ryan
2021-08-03  7:52       ` Cédric Le Goater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAELHpAAyLcpisUdxqL_7j=Gh47YM6ZjAQuZmRy_4jZQi2P9TqA@mail.gmail.com' \
    --to=kkiwi@redhat.com \
    --cc=Ryan.Lindsay@petermac.org \
    --cc=clg@kaod.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.