public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Marc Haber <mh+linux-kernel@zugschlus.de>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	linux-kernel@vger.kernel.org,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux KVM <kvm@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Linux 6.5 speed regression, boot VERY slow with anything systemd related
Date: Fri, 1 Sep 2023 15:24:31 +0300	[thread overview]
Message-ID: <20230901122431.GU11676@atomide.com> (raw)
In-Reply-To: <ZPEPFJ8QvubbD3H9@google.com>

* Sean Christopherson <seanjc@google.com> [230831 22:07]:
> On Tue, Aug 29, 2023, Marc Haber wrote:
> > Hi,
> > 
> > On Tue, Aug 29, 2023 at 10:14:23AM -0700, Sean Christopherson wrote:
> > > On Tue, Aug 29, 2023, Marc Haber wrote:
> > > > Both come from virt-manager, so if the XML helps more, I'll happy to
> > > > post that as well.
> > > 
> > > Those command lines are quite different, e.g. the Intel one has two
> > > serial ports versus one for the AMD VM.
> > 
> > Indeed? I virt-manager, I don't see a second serial port. In either case,
> > only the one showing up in the VM as ttyS0 is being used. But thanks for
> > making me look, I discovered that the machine on the Intel host still
> > used emulated SCSI instead of VirtIO für the main disk. I changed that.
> > 
> > >Unless Tony jumps in with an
> > > idea, I would try massaging either the good or bad VM's QEMU
> > > invocation, e.g. see if you can get the AMD VM to "pass" by pulling in
> > > stuff from the Intel VM, or get the Intel VM to fail by making its
> > > command line look more like the AMD VM.
> > 
> > In Virt-Manager, both machines don't look THAT different tbh. I verified
> > the XML and the differences are not big at all.
> > 
> > Do you want me to try different vCPU types? Currently the VM is set to
> > "Opteron_G3", would you recommend a different vCPU for the host having a
> > "AMD GX-412TC SOC" host CPU?
> 
> I would be surprised if using a different vCPU type fixed anything, but it's not
> impossible that it could help.  In general, unless someone from the serial driver
> side spots an issue, fixing whatever the bug is will likely require a reproducer,
> which in turn likely means narrowing down what exactly is unique about your AMD
> setup.  In other words, if you have cycles to spare, anything you can do to help
> isolate the problem would be appreciated.

Yes two somewhat minimal qemu command lines for working and failing test
case sure would help to debug this.

Regards,

Tony

  reply	other threads:[~2023-09-01 12:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29  6:35 Linux 6.5 speed regression, boot VERY slow with anything systemd related Marc Haber
2023-08-29  8:17 ` Bagas Sanjaya
2023-08-29 13:00   ` Marc Haber
2023-08-29 14:53     ` Sean Christopherson
2023-08-29 15:04       ` Marc Haber
2023-08-29 15:42         ` Sean Christopherson
2023-08-29 16:09           ` Marc Haber
2023-08-29 17:14             ` Sean Christopherson
2023-08-29 20:00               ` Marc Haber
2023-08-31 22:07                 ` Sean Christopherson
2023-09-01 12:24                   ` Tony Lindgren [this message]
2023-09-06 14:41                     ` Marc Haber
2023-09-06 15:21                       ` Tony Lindgren
2023-09-07 10:14                         ` Marc Haber
2023-09-07 10:51                           ` Tony Lindgren
2023-09-08  4:41                             ` Tony Lindgren
2023-09-09 20:08                             ` Marc Haber
2023-09-11 12:53                               ` Tony Lindgren
2023-09-12  6:53                                 ` Marc Haber
2023-09-06 15:26                       ` Tony Lindgren
2023-09-06 20:18                         ` Marc Haber
2023-08-30  6:44     ` Marc Haber
2023-08-29 15:24   ` Marc Haber

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=20230901122431.GU11676@atomide.com \
    --to=tony@atomide.com \
    --cc=bagasdotme@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mh+linux-kernel@zugschlus.de \
    --cc=pbonzini@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=seanjc@google.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