Hi Ciro, Nerijus,
On 08/11/2018 01:43 AM, Ciro Santilli wrote:
> Bisected to 17ec075a651a3f9613429c2d97018fce459ed943 hw/arm/virt: Use
> 256MB ECAM region by default
>
> @Eric: do you know what might be the best fix for me?
>
> Just replacing `-M virt` with `-M virt-3.0` did not solve the proble
Hi.
I'd like to resurrect previous discussion [1] regarding slow kernel boot
inside QEMU with virtio-scsi disks attached and blk_mq enabled.
Symptom:
[2.830857] ata1: SATA max UDMA/133 abar m4096@0x98002000 port
0x98002100 irq 36
[2.834559] ata2: SATA max UDMA/133 abar m4096@0x980020
On Sat, Aug 11, 2018 at 5:47 PM, Oleksandr Natalenko
wrote:
> Hi.
>
> I'd like to resurrect previous discussion [1] regarding slow kernel boot
> inside QEMU with virtio-scsi disks attached and blk_mq enabled.
>
> Symptom:
>
> [2.830857] ata1: SATA max UDMA/133 abar m4096@0x98002000 port 0x9800
Subject: Efficacy of jitterentropy RNG on qemu-kvm Guests
To: qemu-discuss@nongnu.org, libvirt-us...@redhat.com,
whonix-de...@whonix.org
Hello. I'm a distro maintainer and was wondering about the efficacy of
entropy daemons like haveged and jitterentropyd in qemu-kvm. One of the
authors of have
Hi.
On 11.08.2018 14:23, Ming Lei wrote:
Please test for-4.19/block:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/log/?h=for-4.19/block
This slow boot issue should have been fixed by the following commits:
1311326cf475 blk-mq: avoid to synchronize rcu inside
blk_clea
On Sat, Aug 11, 2018 at 8:17 AM, Auger Eric wrote:
> Hi Ciro, Nerijus,
>
> On 08/11/2018 01:43 AM, Ciro Santilli wrote:
> > Bisected to 17ec075a651a3f9613429c2d97018fce459ed943 hw/arm/virt: Use
> > 256MB ECAM region by default
> >
> > @Eric: do you know what might be the best fix for me?
> >
> >
