xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Adam Szewczyk <szewcson@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [BUG] problems with NICs pass through to OpenBSD guest
Date: Tue, 20 Sep 2022 11:13:13 +0200	[thread overview]
Message-ID: <YymEKZcc+kXyLOHG@MacBook-Air-de-Roger.local> (raw)
In-Reply-To: <CAHsotTj=AEO6wECMcFcFL6oLNtnuJ4-n5+DCOsPdCGkrVHLTqA@mail.gmail.com>

Please avoid top-posting.

On Tue, Sep 20, 2022 at 09:41:48AM +0200, Adam Szewczyk wrote:
> > (XEN)  MSI    132 vec=d9 lowest  edge   assert  log lowest dest=00000100
> > mask=0/  /?
> > (XEN)    IRQ: 132 vec:d9 PCI-MSI         status=030 aff:{8}/{0-11}
> > in-flight=0 d7:151(-M-)

So this is the MSI vector assigned to the OpenBSD domain, and is
indeed masked.

> > openbsd-71                                   7   511     2     -b----
> >  63.0
> > openbsd-71-dm                                8   144     1     -b----
> >  14.0
> >
> 
> How I can enable install this debug hypervisor? I have problems finding
> anything about it.

You will have to ask QubesOS about how to do that.  I have no
experience with QubesOS, and don't know if or where they provide a
debug build of Xen for you to boot.

> I don't have logs with qemu in the name, instead I have gmp-proxy logs. But
> their all looks empty.

Right, QubesOS is also using stubdomains, so it's not clear to me
where those logs are stored.

For debugging purposes, is there a way that you could create the
OpenBSD domain without a stubdomain, and just run QEMU in the control
domain? That would also rule out whether the cause of the malfunction
is due to the usage of stubdomains.

Regards, Roger.


  parent reply	other threads:[~2022-09-20  9:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16  6:22 [BUG] problems with NICs pass through to OpenBSD guest Adam Szewczyk
2022-09-16  9:37 ` Roger Pau Monné
     [not found]   ` <CAHsotTibs204KVYsm5E0x7ogUzpZOdmV4g_6LyD8RSkLnfJ0UA@mail.gmail.com>
2022-09-16 13:09     ` Roger Pau Monné
2022-09-16 13:35       ` Roger Pau Monné
2022-09-16 15:08         ` Adam Szewczyk
2022-09-16 19:26           ` Adam Szewczyk
2022-09-16 20:50             ` Adam Szewczyk
2022-09-19  9:21           ` Roger Pau Monné
2022-09-20  7:41             ` Adam Szewczyk
2022-09-20  8:12               ` Adam Szewczyk
2022-09-20  9:13               ` Roger Pau Monné [this message]
2022-09-21  8:59                 ` Adam Szewczyk

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=YymEKZcc+kXyLOHG@MacBook-Air-de-Roger.local \
    --to=roger.pau@citrix.com \
    --cc=szewcson@gmail.com \
    --cc=xen-devel@lists.xen.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 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).