the version of libvirt is 0.7.6. i find the patch of this problem,now solved. http://libvirt.org/git/?p=libvirt.git;a=commit;h=71e92a1575b6653720b0f4c7a474b6e7baec72f3 thanks. 2011/3/5 Chris Wright <chrisw@xxxxxxxxxxxx>: > * lidong chen (chen.lidong.kernel@xxxxxxxxx) wrote: >> guest os could not access the vf assigned ,and print this error message . >> PCI: device 0000:00:06.0 has unknown header type 7f, ignoring. >> PCI: device 0000:00:07.0 has unknown header type 7f, ignoring. >> PCI: device 0000:00:08.0 has unknown header type 7f, ignoring. >> >> the reason is the config file /sys/bus/pci/devices/xx/config of pci >> device could not access correctly after guestos start, >> the content qemu-kvm read from /sys/bus/pci/devices/xx/config is all FF. > > This is mostly likely a combination of two bugs, both have since been > fixed (starting in v0.8.3). What version of libvirt are you using? > > One is the 82599 VF has an erratum that it does not show that it supports > Function Level Reset (FLR -- SR-IOV VFs are required to support FLR). > The second is libvirt had buggy handling of device reset for devices > that don't support FLR. IIRC, what you are seeing is the result of a > secondary bus reset resetting all devices on that bus (including the PF). > > Try upgrading libvirt. > > thanks, > -chris > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html