Linux 9p file system development
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Eric Van Hensbergen <ericvh@kernel.org>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
	Dominique Martinet <asmadeus@codewreck.org>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	v9fs@lists.linux.dev
Subject: Re: hangs after merge window changes
Date: Wed, 17 Jul 2024 14:42:52 -0700	[thread overview]
Message-ID: <20240717144221.0c5afd01@kernel.org> (raw)
In-Reply-To: <CAFkjPTnktf6puYAyg4pNh8RtQvSuQnSo5VCQvinv=Cw9m1s9xQ@mail.gmail.com>

On Wed, 17 Jul 2024 13:01:26 -0500 Eric Van Hensbergen wrote:
> I held way back on adding anything new over the past cycle, so this
> sounds likely some external change maybe perturbing an older issue.

Ah :(

> What guest side mount options, qemu options and qemu version are you
> using?

I use virtme-ng, according to ps qemu gets called with:

/usr/local/bin/qemu-system-x86_64 -name virtme-ng -m 1G -fsdev local,id=virtfs5,path=/,security_model=none,readonly=on,multidevs=remap -device virtio-9p-pci,fsdev=virtfs5,mount_tag=/dev/root -machine accel=kvm:tcg -device i6300esb,id=watchdog0 -cpu host -parallel none -net none -echr 1 -chardev file,path=/proc/self/fd/2,id=dmesg -device virtio-serial-pci -device virtconsole,chardev=dmesg -chardev stdio,id=console,signal=off,mux=on 

-serial chardev:console -mon chardev=console -vga none -display none -smp 4 -kernel ./arch/x86/boot/bzImage -append virtme_hostname=virtme-ng nr_open=1073741816 virtme_link_mods=/home/virtme/testing-1/.virtme_mods/lib/modules/0.0.0 virtme_rw_overlay0=/etc virtme_rw_overlay1=/lib virtme_rw_overlay2=/home virtme_rw_overlay3=/opt virtme_rw_overlay4=/srv virtme_rw_overlay5=/usr virtme_rw_overlay6=/var virtme_rw_overlay7=/tmp console=hvc0 earlyprintk=serial,ttyS0,115200 virtme_console=ttyS0 psmouse.proto=exps virtme_chdir=home/virtme/testing-1 rootfstype=9p rootflags=version=9p2000.L,trans=virtio,access=any raid=noautodetect ro init=/home/virtme/virtme-ng/virtme/guest/virtme-init

QEMU version is 8.2.1 (built from source)

> Dominique, you aware of anything coming in that might have messed with
> this?  Maybe the new common code refactoring underpinning
> readahead/etc.?

  parent reply	other threads:[~2024-07-17 21:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 17:24 hangs after merge window changes Jakub Kicinski
2024-07-17 18:01 ` Eric Van Hensbergen
2024-07-17 20:45   ` Dominique Martinet
2024-07-17 23:30     ` Jakub Kicinski
2024-07-18  1:14       ` Dominique Martinet
2024-07-18  3:54         ` Mateusz Guzik
2024-07-18  4:08           ` Mateusz Guzik
2024-07-18 10:42             ` Jan Kara
2024-07-18 10:57               ` Mateusz Guzik
2024-07-18 11:40                 ` Mateusz Guzik
2024-07-18 12:16                   ` Jan Kara
2024-07-18 12:29                     ` Mateusz Guzik
2024-07-17 21:42   ` Jakub Kicinski [this message]
2024-07-17 22:00     ` Eric Van Hensbergen

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=20240717144221.0c5afd01@kernel.org \
    --to=kuba@kernel.org \
    --cc=asmadeus@codewreck.org \
    --cc=ericvh@kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=v9fs@lists.linux.dev \
    /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