** Attachment added: "Just in case for use, the config for host"
https://bugs.launchpad.net/qemu/+bug/591666/+attachment/2194877/+files/h-config.gz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/59
If configure guest kernel correctly, it seems that virtio for block is OK!
Could you help or send me your configure file to have a second check
Thanks
version info ===
QEMU 0.14.50 monitor
host kernel: 2.6.39
guest kernel: 2.6.32
config file for kernel info =
** Attachment added: "The disk device on host including virtio block --vda"
https://bugs.launchpad.net/qemu/+bug/591666/+attachment/2194878/+files/1-vdaOnGuest.png
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launc
** Attachment added: "Host get the expect string "helloHpervisor""
https://bugs.launchpad.net/qemu/+bug/591666/+attachment/2194881/+files/3.getStringOnHypervisor.png
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
** Attachment added: "guest write data into vda"
https://bugs.launchpad.net/qemu/+bug/591666/+attachment/2194879/+files/2-write2virtDisk.png
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/591666
T
Hi Eran,
Could you lauch "lspci" command on guestOS to see whether there is a new
pci device hot-plug in?
On the other hand, the guestOS need to be configured with "CONFIG_VIRTIO_PCI",
otherwise it can not
contain the driver to monitor the virtio-pci device.
Thanks
--
You received this bug n
