[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1600563] Re: min_io_size is currently limited to size uint16_t
From: |
Thomas Huth |
Subject: |
[Bug 1600563] Re: min_io_size is currently limited to size uint16_t |
Date: |
Thu, 22 Apr 2021 05:16:10 -0000 |
The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.
If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1600563
Title:
min_io_size is currently limited to size uint16_t
Status in QEMU:
Incomplete
Bug description:
I am using LVM VGs on MD-raid1 for hosting my KVM volumes. On the
host, a VG looks like this:
Disk /dev/vm/vol202a: 60 GiB, 64424509440 bytes, 125829120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 131072 bytes / 131072 bytes
In order to replicate the block device characteristics in the guest, I
am using the following extra parameters:
-set device.scsi0-0-0-0.logical_block_size=512
-set device.scsi0-0-0-0.physical_block_size=4096
-set device.scsi0-0-0-0.min_io_size=131072
This doesn't work as qemu complains that min_io_size needs to be of
type uint16_t.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1600563/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1600563] Re: min_io_size is currently limited to size uint16_t,
Thomas Huth <=