pci: assign resource #5
[ 88.906694] ltp_tpci: name = (null), flags = 0, start 0x0, end 0x0
[ 88.906695] ltp_tpci: assign resource #6
[ 88.906695] ltp_tpci: name = :00:07.0, flags = 0, start 0x0, end 0x0
[ 88.906800] ltp_tpci: test-case 13
---- Replied Message
| From | Stefan Ha
i440fx/q35 and virtio/scsi and kernel.
thanks
Replied Message
| From | Michael Tokarev |
| Date | 08/10/2023 17:08 |
| To | longguang.yue ,
qemu-devel ,
linux-kernel |
| Subject | Re: LTP test related to virtio releasing and reassigning resource
leads to guest hung |
10.08.2023 11:57
Hi, all:
A ltp test leads to guest hung(io hung), the test releases virtio device
resource and then reassign.
I find device’s mem prefetchable resource 64-bit is changed.
ltp test:
https://github.com/linux-test-project/ltp/blob/522d7fba4afc84e07b252aa4cd91b241e81d6613/testcases/kernel/device-dr
hi,all
libvirt supply "default", "none", "writethrough", "writeback", "directsync",
"unsafe" disk cache options
1.
as for qemu, how qemu uses those options? and what are the differences?
better tell me where are the codes corresponding to those options?
2.
after a long time of running
hi,all
1.
what is the differences between file and block disk?
which is better?
it seems that qemu always use pread and pwrite , does not care about the type
of vm's disk. am i right?
thanks
hi,all
from the aspect of qemu, there are file and block disk type,
what is the final difference between the two types ?
if its type is block and source is volume or physical disk, who finally
read/write the disk?
i thought block is raw format, so raw driver will do the actual r/w, am i right?
if
