Description of problem: On rhel5.4-Client-i386, run command # virsh domblkstat test1 hda, output error info: error: Failed to get block stats test1 hda error: internal error read_bd_stats: Frontend block device not connected Version-Release number of selected component (if applicable): RHEL5.4-Client-i386 libvirt-0.6.3-17.el5 xen-3.0.3-92.el5 How reproducible: 100% Steps to Reproduce: 1. # virsh define xen-fv-i386.xml 2. # virsh start test1 3. # virsh domblkstat test1 hda Actual results: Output: error: Failed to get block stats test1 hda error: internal error read_bd_stats: Failed to read any block statistics Expected results: Output hda stat info Additional info: Attach capabilities info (capabilities), guest xml info (xen-fv-i386.xml), version info (version), debug info (debug.log)
Created attachment 355909 [details] capabilities info
Created attachment 355910 [details] guest xml info
Created attachment 355911 [details] version info
Created attachment 355912 [details] debug info
Attach /var/log/xen/xend.log
Created attachment 355913 [details] xend.log
This function works for kvm guest
Yes, this is known to be broken for xen HVM guests. I'll put it on the list to look at for 5.5. Chris Lalancette
No, this should work for HVM guests if you have paravirt drivers installed in the HVM guest. Can you provide the output of 'xenstore-ls', and confirm whether or not the guest is using paravirt drivers, or plain IDE emulated drivers ?
Attach xenstore-ls
Created attachment 356116 [details] xenstore-ls
The xenstore logs show the front end devices are not connected, so the guest must be using the emulated IDE/RTL8139 drivers, and not the Xen paravirt block/net drivers. I/O stats are not available with emulated drivers, so the virsh error message is expected behaviour.
This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).
Clearing out old flags for reporting purposes. Chris Lalancette