I am using a driver from user-space using vfio.
During intensive testing, when my application crashes.
I try to re-run the same, when I get a bind-failure.
Error code, is E_BUSY.
The point of error is when I try to open a group
ret = open(/dev/vfio/xx,O_RDWR)
I traced down what could be the
Hi,
I want to use a ram disk as a block device for my kernel.( i am
measuring file io on ram )
I am trying to boot a kernel from using /dev/ram0. However I am getting
No root Device found
qemu-system-x86_64 -m 8G -hda disk.img -kernel vmlinuz-3.10.0-rc6
-initrd
the qmp -interface uses linked lists as a replacement for array
type structures.
Can anybody clarify my doubt and whether is it possible to use arrays as
in my case.
Regards
Saptarshi Sen
Hi,
I am trying to monitor the disk access pattern from the guest.
and i am using an IDE as my virtual hard drive. My observation is that
the sector reads are not 512 bytes aligned.
I am gathering the stats from hw/ide/core.c in the function
ide_dma_cb. variable :sector_num
Hi,
Is it possible from qemu userspace to identify what type of file access
( DIRECT or SYNC or ASYNC )the guest is performing on its files also along
with their file-names if possible.
I tried to trace bdrv events but I am not able to correctly identify.
Regards
Sen
Hi,
I am observing a strange phenomenon with balloon using KVM as hypervisor.
I set balloon value to an arbitratrilylow value so that the guest system is
out of memory. The VM freezes therafter. But if Iquery the balloon status
through qmp-shell, the qmp interface interacts with the balloon
Hi all,
I am experimenting with the Virtio- balloon driver in qemu.
When I set the balloon size to a arbitrary low value. I see
the actual value of the balloon set is not what I intended
but to a level probably decided by the system.
I am not able to explain this part who
HI,
I am using the following command for booting a CENTOS image. Although
the system boots initially but at the
end, it throws an error No root Device found
qemu/qemu-system-x86_64 -m 512 -kernel vmlinuz-2.6.32-71.el6.i686
-initrd initramfs-2.6.32-71.el6.i686.img -append root=/dev/hda1
