From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-s390x@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH RFC] tests/acceptance: add a test for devices on s390x
Date: Thu, 26 Nov 2020 13:05:19 +0100 [thread overview]
Message-ID: <20201126130519.4e178309.cohuck@redhat.com> (raw)
In-Reply-To: <20201125163034.5a935baa.cohuck@redhat.com>
On Wed, 25 Nov 2020 16:30:34 +0100
Cornelia Huck <cohuck@redhat.com> wrote:
> On Wed, 25 Nov 2020 16:03:13 +0100
> Thomas Huth <thuth@redhat.com> wrote:
>
> > On 25/11/2020 14.58, Cornelia Huck wrote:
> > > + def test(self):
> > > +
> > > + """
> > > + :avocado: tags=arch:s390x
> > > + :avocado: tags=machine:s390-ccw-virtio
> > > + """
> > > +
> > > + # XXX: switch to https when debian fixes their certificate
> > > + kernel_url = ('http://archive.debian.org/debian/dists/jessie/main'
> > > + '/installer-s390x/current/images/generic/kernel.debian')
> > > + kernel_hash = '5af1aa839754f4d8817fb5878b4d55dfc887f45d'
> > > + kernel_path = self.fetch_asset(kernel_url, asset_hash=kernel_hash)
> > > +
> > > + initrd_url = ('http://archive.debian.org/debian/dists/jessie/main'
> > > + '/installer-s390x/current/images/generic/initrd.debian')
> > > + initrd_hash = '99252b28306184b876f979585e2d4bfe96b27464'
> > > + initrd_path = self.fetch_asset(initrd_url, asset_hash=initrd_hash)
> > > +
> > > + self.vm.set_console()
> > > + kernel_command_line = (self.KERNEL_COMMON_COMMAND_LINE +
> > > + 'console=sclp0 root=/dev/ram0 BOOT_DEBUG=3')
> > > + self.vm.add_args('-nographic',
> > > + '-kernel', kernel_path,
> > > + '-initrd', initrd_path,
> > > + '-append', kernel_command_line,
> > > + '-device', 'virtio-net-ccw,devno=fe.1.1111',
> > > + '-device', 'virtio-net-pci')
> >
> > Maybe use '-device', 'virtio-net-pci,addr=6' or something similar to check a
> > non-default PCI address, too?
>
> Not sure if addr= will do the trick, I may need to add a zpci device.
It seems I need both a zpci device (to specify the uid) and a newer
kernel (so that the uid is actually used to construct the address in
the guest). I guess I should use snapshots.debian.org to get a stable
link to a newer version?
next prev parent reply other threads:[~2020-11-26 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 13:58 [PATCH RFC] tests/acceptance: add a test for devices on s390x Cornelia Huck
2020-11-25 15:03 ` Thomas Huth
2020-11-25 15:30 ` Cornelia Huck
2020-11-26 12:05 ` Cornelia Huck [this message]
2020-11-26 12:18 ` Thomas Huth
2020-11-26 12:44 ` Cornelia Huck
2020-11-25 16:04 ` Philippe Mathieu-Daudé
2020-11-26 11:32 ` Cornelia Huck
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=20201126130519.4e178309.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=crosa@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).