Hi Kazushi, Make sure unload the driver of the device before assign it.
Regards, Weidong w1ndoz wrote: > Hi > > I'm interested in PCI passthrough support. > > I downloaded Linux Kernel 2.6.28-rc7 and build and ran KVM (which > is KVM-79) on this kernel. > I started KVM with the following command-lines: > $ qemu-system-x86_64 -boot c -m 512 -hda test.qcow -localtime -k > en-us -pcidevice host=00:19.0 > (00:19.0 is Intel(R) PRO/1000 Network Connection Device) > > However, KVM caused the following errors: > Could not notify kernel about assigned device "00:19.0" > register_real_device: Device or resource busy > Segmantation_fault > > dmesg messages were as follows: > $ dmesg > [ 151.483167] [drm] Initialized drm 1.1.0 20060810 > [ 151.525100] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) > -> IRQ 16 > [ 151.525105] pci 0000:00:02.0: setting latency timer to 64 > [ 151.525193] pci 0000:00:02.0: irq 505 for MSI/MSI-X > [ 151.525309] [drm] Initialized i915 1.6.0 20080730 on minor 0 > [ 187.854117] set status page addr 0x00033000 > [ 823.246792] kvm: guest NX capability removed > [ 823.311659] kvm: guest NX capability removed > [ 823.487849] qemu-system-x86[5940]: segfault at 1dc ip 0807c446 > sp 96420110 error 4 in qemu-system-x86_64[8048000+194000] > [ 837.010304] kvm: guest NX capability removed > [ 837.019163] e1000e 0000:00:19.0: BAR 0: can't reserve mem > region [0xe0400000-0xe041ffff] > [ 837.019163] kvm_vm_ioctl_assign_device: Could not get access to > device regions > [ 837.019194] kvm: guest NX capability removed > [ 837.219560] qemu-system-x86[5944]: segfault at 1dc ip 0807c446 > sp 9636b110 error 4 in qemu-system-x86_64[8048000+194000] > > I think that my cpu and my chipset maybe support VT-x and VT-d. > http://www.intel.co.jp/products/desktop/motherboards/dq35jo/dq35jo-overview.htm > CPU: Intel(R) Core(TM) 2 Duo CPU E6 > chipset: Intel(R) Q35 Express Chipset > > Any advive or tips will help ? > > Thanks, > Kazushi -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
