[Qemu-devel] Isuue assiging devices using VFIO on x86

[Qemu-devel] Isuue assiging devices using VFIO on x86

[Bhushan Bharat-R65777]

Hi Alex,

In my susyem I have following devices:

I tried assigning a following PCI devices:
00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI Controller (rev 03)
00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER Controller (rev 03)
00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller (rev 03)

and getting below error:

---------------
Command:
-------
qemu-system-x86_64 -enable-kvm  -nographic  -kernel /boot/vmlinuz-3.6.0-rc2+ -initrd /boot/initramfs-3.6.0-rc2+.img -append "root=/dev/sda1" -m 1024 -drive file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device vfio-pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device vfio-pci,host=0000:00:03.3

Error prints:
----
qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning, device 0000:00:03.0 does not support reset

qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: VFIO 0000:00:03.0 BAR 0 is too small to mmap, this may affect performance.

qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning, device 0000:00:03.2 does not support reset

qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning, device 0000:00:03.3 does not support reset

qemu: hardware error: register_ioport_read: invalid opaque for address 0x3f6
CPU #0:
EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc
ESI=00002800 EDI=80002804 EBP=00006fc0 ESP=00006f38
EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
GDT=     000fcd68 00000037
IDT=     000fdb60 00000000
CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
Aborted (core dumped)

--------------------

Linux: http://github.com/awilliam/linux-vfio.git next
Qemu: https://github.com/awilliam/qemu-vfio.git  iommu-group-vfio

Any idea what's is the issue.

Thanks
-Bharat

Re: [Qemu-devel] Isuue assiging devices using VFIO on x86

[Alex Williamson]

On Tue, 2012-08-28 at 09:23 +0000, Bhushan Bharat-R65777 wrote:
> Hi Alex,
> 
> In my susyem I have following devices:
> 
> I tried assigning a following PCI devices:
> 00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI Controller (rev 03)
> 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER Controller (rev 03)
> 00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller (rev 03)
> 
> and getting below error:
> 
> ---------------
> Command:
> -------
> qemu-system-x86_64 -enable-kvm  -nographic  -kernel /boot/vmlinuz-3.6.0-rc2+ -initrd /boot/initramfs-3.6.0-rc2+.img -append "root=/dev/sda1" -m 1024 -drive file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device vfio-pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device vfio-pci,host=0000:00:03.3
> 
> Error prints:
> ----
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning, device 0000:00:03.0 does not support reset
> 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: VFIO 0000:00:03.0 BAR 0 is too small to mmap, this may affect performance.
> 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning, device 0000:00:03.2 does not support reset
> 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning, device 0000:00:03.3 does not support reset
> 
> qemu: hardware error: register_ioport_read: invalid opaque for address 0x3f6
> CPU #0:
> EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc
> ESI=00002800 EDI=80002804 EBP=00006fc0 ESP=00006f38
> EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
> SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
> TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
> GDT=     000fcd68 00000037
> IDT=     000fdb60 00000000
> CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
> DR6=00000000ffff0ff0 DR7=0000000000000400
> EFER=0000000000000000
> FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
> XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
> XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
> XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
> Aborted (core dumped)
> 
> --------------------
> 
> Linux: http://github.com/awilliam/linux-vfio.git next
> Qemu: https://github.com/awilliam/qemu-vfio.git  iommu-group-vfio
> 
> Any idea what's is the issue.

Please try the vfio-pci-for-qemu-1.2-v3 qemu-vfio.git tag, I'm not even
sure what's in that old iommu-group-vfio branch.  Thanks,

Alex

Re: [Qemu-devel] Isuue assiging devices using VFIO on x86

[Bhushan Bharat-R65777]

> -----Original Message-----
> From: Alex Williamson [mailto:alex.williamson@redhat.com]
> Sent: Tuesday, August 28, 2012 9:27 PM
> To: Bhushan Bharat-R65777
> Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> Subject: Re: Isuue assiging devices using VFIO on x86
> 
> On Tue, 2012-08-28 at 09:23 +0000, Bhushan Bharat-R65777 wrote:
> > Hi Alex,
> >
> > In my susyem I have following devices:
> >
> > I tried assigning a following PCI devices:
> > 00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI
> Controller (rev 03)
> > 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER Controller
> (rev 03)
> > 00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT
> Controller (rev 03)
> >
> > and getting below error:
> >
> > ---------------
> > Command:
> > -------
> > qemu-system-x86_64 -enable-kvm  -nographic  -kernel /boot/vmlinuz-3.6.0-rc2+ -
> initrd /boot/initramfs-3.6.0-rc2+.img -append "root=/dev/sda1" -m 1024 -drive
> file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device vfio-
> pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device vfio-
> pci,host=0000:00:03.3
> >
> > Error prints:
> > ----
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning, device
> 0000:00:03.0 does not support reset
> >
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: VFIO 0000:00:03.0 BAR
> 0 is too small to mmap, this may affect performance.
> >
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning, device
> 0000:00:03.2 does not support reset
> >
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning, device
> 0000:00:03.3 does not support reset
> >
> > qemu: hardware error: register_ioport_read: invalid opaque for address 0x3f6
> > CPU #0:
> > EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc
> > ESI=00002800 EDI=80002804 EBP=00006fc0 ESP=00006f38
> > EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> > ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
> > SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
> > TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
> > GDT=     000fcd68 00000037
> > IDT=     000fdb60 00000000
> > CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
> > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> DR3=0000000000000000
> > DR6=00000000ffff0ff0 DR7=0000000000000400
> > EFER=0000000000000000
> > FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> > FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> > FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> > FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> > FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> > XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
> > XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
> > XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
> > XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
> > Aborted (core dumped)
> >
> > --------------------
> >
> > Linux: http://github.com/awilliam/linux-vfio.git next
> > Qemu: https://github.com/awilliam/qemu-vfio.git  iommu-group-vfio
> >
> > Any idea what's is the issue.
> 
> Please try the vfio-pci-for-qemu-1.2-v3 qemu-vfio.git tag, I'm not even
> sure what's in that old iommu-group-vfio branch.  Thanks,

Can you share the command to configure qemu?

Thanks
-Bharat

> 
> Alex
> 

Re: [Qemu-devel] Isuue assiging devices using VFIO on x86

[Alex Williamson]

On Tue, 2012-08-28 at 17:10 +0000, Bhushan Bharat-R65777 wrote:
> 
> > -----Original Message-----
> > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > Sent: Tuesday, August 28, 2012 9:27 PM
> > To: Bhushan Bharat-R65777
> > Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> > Subject: Re: Isuue assiging devices using VFIO on x86
> > 
> > On Tue, 2012-08-28 at 09:23 +0000, Bhushan Bharat-R65777 wrote:
> > > Hi Alex,
> > >
> > > In my susyem I have following devices:
> > >
> > > I tried assigning a following PCI devices:
> > > 00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI
> > Controller (rev 03)
> > > 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER Controller
> > (rev 03)
> > > 00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT
> > Controller (rev 03)
> > >
> > > and getting below error:
> > >
> > > ---------------
> > > Command:
> > > -------
> > > qemu-system-x86_64 -enable-kvm  -nographic  -kernel /boot/vmlinuz-3.6.0-rc2+ -
> > initrd /boot/initramfs-3.6.0-rc2+.img -append "root=/dev/sda1" -m 1024 -drive
> > file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device vfio-
> > pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device vfio-
> > pci,host=0000:00:03.3
> > >
> > > Error prints:
> > > ----
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning, device
> > 0000:00:03.0 does not support reset
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: VFIO 0000:00:03.0 BAR
> > 0 is too small to mmap, this may affect performance.
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning, device
> > 0000:00:03.2 does not support reset
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning, device
> > 0000:00:03.3 does not support reset
> > >
> > > qemu: hardware error: register_ioport_read: invalid opaque for address 0x3f6
> > > CPU #0:
> > > EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc
> > > ESI=00002800 EDI=80002804 EBP=00006fc0 ESP=00006f38
> > > EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> > > ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
> > > SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
> > > TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
> > > GDT=     000fcd68 00000037
> > > IDT=     000fdb60 00000000
> > > CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
> > > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> > DR3=0000000000000000
> > > DR6=00000000ffff0ff0 DR7=0000000000000400
> > > EFER=0000000000000000
> > > FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> > > FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> > > FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> > > FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> > > FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> > > XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
> > > XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
> > > XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
> > > XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
> > > Aborted (core dumped)
> > >
> > > --------------------
> > >
> > > Linux: http://github.com/awilliam/linux-vfio.git next
> > > Qemu: https://github.com/awilliam/qemu-vfio.git  iommu-group-vfio
> > >
> > > Any idea what's is the issue.
> > 
> > Please try the vfio-pci-for-qemu-1.2-v3 qemu-vfio.git tag, I'm not even
> > sure what's in that old iommu-group-vfio branch.  Thanks,
> 
> Can you share the command to configure qemu?

Nothing special: ./configure

I sometimes set --prefix or --target-list, but nothing that changes the
binaries.  Thanks,

Alex

Re: [Qemu-devel] Isuue assiging devices using VFIO on x86

[Bhushan Bharat-R65777]

> -----Original Message-----
> From: Alex Williamson [mailto:alex.williamson@redhat.com]
> Sent: Wednesday, August 29, 2012 12:16 PM
> To: Bhushan Bharat-R65777
> Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> Subject: Re: Isuue assiging devices using VFIO on x86
> 
> On Tue, 2012-08-28 at 17:10 +0000, Bhushan Bharat-R65777 wrote:
> >
> > > -----Original Message-----
> > > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > > Sent: Tuesday, August 28, 2012 9:27 PM
> > > To: Bhushan Bharat-R65777
> > > Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> > > Subject: Re: Isuue assiging devices using VFIO on x86
> > >
> > > On Tue, 2012-08-28 at 09:23 +0000, Bhushan Bharat-R65777 wrote:
> > > > Hi Alex,
> > > >
> > > > In my susyem I have following devices:
> > > >
> > > > I tried assigning a following PCI devices:
> > > > 00:03.0 Communication controller: Intel Corporation 4 Series
> > > > Chipset HECI
> > > Controller (rev 03)
> > > > 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER
> > > > Controller
> > > (rev 03)
> > > > 00:03.3 Serial controller: Intel Corporation 4 Series Chipset
> > > > Serial KT
> > > Controller (rev 03)
> > > >
> > > > and getting below error:
> > > >
> > > > ---------------
> > > > Command:
> > > > -------
> > > > qemu-system-x86_64 -enable-kvm  -nographic  -kernel
> > > > /boot/vmlinuz-3.6.0-rc2+ -
> > > initrd /boot/initramfs-3.6.0-rc2+.img -append "root=/dev/sda1" -m
> > > 1024 -drive
> > > file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device vfio-
> > > pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device
> > > vfio-
> > > pci,host=0000:00:03.3
> > > >
> > > > Error prints:
> > > > ----
> > > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning,
> > > > device
> > > 0000:00:03.0 does not support reset
> > > >
> > > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: VFIO
> > > > 0000:00:03.0 BAR
> > > 0 is too small to mmap, this may affect performance.
> > > >
> > > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning,
> > > > device
> > > 0000:00:03.2 does not support reset
> > > >
> > > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning,
> > > > device
> > > 0000:00:03.3 does not support reset
> > > >
> > > > qemu: hardware error: register_ioport_read: invalid opaque for
> > > > address 0x3f6 CPU #0:
> > > > EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc ESI=00002800
> > > > EDI=80002804 EBP=00006fc0 ESP=00006f38
> > > > EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> > > > ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > > CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
> > > > SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > > DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > > FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > > GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT TR =0000 00000000
> > > > 0000ffff 00008b00 DPL=0 TSS32-busy
> > > > GDT=     000fcd68 00000037
> > > > IDT=     000fdb60 00000000
> > > > CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
> > > > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> > > DR3=0000000000000000
> > > > DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000000
> > > > FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> > > > FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> > > > FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> > > > FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> > > > FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> > > > XMM00=00000000000000000000000000000000
> > > > XMM01=00000000000000000000000000000000
> > > > XMM02=00000000000000000000000000000000
> > > > XMM03=00000000000000000000000000000000
> > > > XMM04=00000000000000000000000000000000
> > > > XMM05=00000000000000000000000000000000
> > > > XMM06=00000000000000000000000000000000
> > > > XMM07=00000000000000000000000000000000
> > > > Aborted (core dumped)
> > > >
> > > > --------------------
> > > >
> > > > Linux: http://github.com/awilliam/linux-vfio.git next
> > > > Qemu: https://github.com/awilliam/qemu-vfio.git  iommu-group-vfio
> > > >
> > > > Any idea what's is the issue.
> > >
> > > Please try the vfio-pci-for-qemu-1.2-v3 qemu-vfio.git tag, I'm not
> > > even sure what's in that old iommu-group-vfio branch.  Thanks,
> >
> > Can you share the command to configure qemu?
> 
> Nothing special: ./configure
> 
> I sometimes set --prefix or --target-list, but nothing that changes the
> binaries.  Thanks,

Hello Alex,
I am using " ./configure --target-list=x86_64-softmmu --enable-kvm " .
QEMU repo is at:
commit 3b4672f6614e07f9dc0a85a12a8c89d480a2493c
Author: Alex Williamson <alex.williamson@redhat.com>
Date:   Tue Aug 14 14:07:19 2012 -0600

    vfio: Enable vfio-pci and mark supported
    
    Signed-off-by: Alex Williamson <alex.williamson@redhat.com>

Linux Repo is at :
commit d9875690d9b89a866022ff49e3fcea892345ad92
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Aug 16 14:51:24 2012 -0700

    Linux 3.6-rc2

---------------------------

Then I bound 3 pci devices with VFIO and run below command to launch VM
qemu-system-x86_64 -enable-kvm  -nographic  -kernel /boot/vmlinuz-3.6.0-rc2+ -initrd /boot/initramfs-3.6.0-rc2+.img -append "root=/dev/sda1" -m 1024 -drive file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device vfio-pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device vfio-pci,host=0000:00:03.3

Then I was getting below errors: 
qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed to set iommu for container: Operation not permitted

qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed to setup container for group 2

qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed to get group 2

qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Device 'vfio-pci' could not be initialized
---------

Then I set /sys/module/vfio_iommu_type1/parameters/allow_unsafe_interrupts = 1

And getting below error:

qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning, device 0000:00:03.0 does not support reset

qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning, device 0000:00:03.2 does not support reset

qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning, device 0000:00:03.3 does not support reset

qemu: hardware error: register_ioport_read: invalid opaque for address 0x3f6
CPU #0:
EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc
ESI=00002800 EDI=80002804 EBP=00006fc0 ESP=00006f38
EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
GDT=     000fcd68 00000037
IDT=     000fdb60 00000000
CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
DR6=00000000ffff0ff0 DR7=0000000000000400
EFER=0000000000000000
FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
Aborted (core dumped)

Thanks a lot for your help
-Bharat

Re: [Qemu-devel] Isuue assiging devices using VFIO on x86

[Alex Williamson]

On Wed, 2012-08-29 at 07:11 +0000, Bhushan Bharat-R65777 wrote:
> 
> > -----Original Message-----
> > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > Sent: Wednesday, August 29, 2012 12:16 PM
> > To: Bhushan Bharat-R65777
> > Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> > Subject: Re: Isuue assiging devices using VFIO on x86
> > 
> > On Tue, 2012-08-28 at 17:10 +0000, Bhushan Bharat-R65777 wrote:
> > >
> > > > -----Original Message-----
> > > > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > > > Sent: Tuesday, August 28, 2012 9:27 PM
> > > > To: Bhushan Bharat-R65777
> > > > Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> > > > Subject: Re: Isuue assiging devices using VFIO on x86
> > > >
> > > > On Tue, 2012-08-28 at 09:23 +0000, Bhushan Bharat-R65777 wrote:
> > > > > Hi Alex,
> > > > >
> > > > > In my susyem I have following devices:
> > > > >
> > > > > I tried assigning a following PCI devices:
> > > > > 00:03.0 Communication controller: Intel Corporation 4 Series
> > > > > Chipset HECI
> > > > Controller (rev 03)
> > > > > 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER
> > > > > Controller
> > > > (rev 03)
> > > > > 00:03.3 Serial controller: Intel Corporation 4 Series Chipset
> > > > > Serial KT
> > > > Controller (rev 03)
> Hello Alex,
> I am using " ./configure --target-list=x86_64-softmmu --enable-kvm " .
> QEMU repo is at:
> commit 3b4672f6614e07f9dc0a85a12a8c89d480a2493c
> Author: Alex Williamson <alex.williamson@redhat.com>
> Date:   Tue Aug 14 14:07:19 2012 -0600
> 
>     vfio: Enable vfio-pci and mark supported
>     
>     Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> 
> Linux Repo is at :
> commit d9875690d9b89a866022ff49e3fcea892345ad92
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Thu Aug 16 14:51:24 2012 -0700
> 
>     Linux 3.6-rc2
> 
> ---------------------------
> 
> Then I bound 3 pci devices with VFIO and run below command to launch VM
> qemu-system-x86_64 -enable-kvm  -nographic  -kernel /boot/vmlinuz-3.6.0-rc2+ -initrd /boot/initramfs-3.6.0-rc2+.img -append "root=/dev/sda1" -m 1024 -drive file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device vfio-pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device vfio-pci,host=0000:00:03.3
> 
> Then I was getting below errors: 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed to set iommu for container: Operation not permitted
> 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed to setup container for group 2
> 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed to get group 2
> 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Device 'vfio-pci' could not be initialized
> ---------
> 
> Then I set /sys/module/vfio_iommu_type1/parameters/allow_unsafe_interrupts = 1
> 
> And getting below error:
> 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning, device 0000:00:03.0 does not support reset
> 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning, device 0000:00:03.2 does not support reset
> 
> qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning, device 0000:00:03.3 does not support reset
> 
> qemu: hardware error: register_ioport_read: invalid opaque for address 0x3f6
> CPU #0:
> EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc
> ESI=00002800 EDI=80002804 EBP=00006fc0 ESP=00006f38
> EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
> SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT
> TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy
> GDT=     000fcd68 00000037
> IDT=     000fdb60 00000000
> CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
> DR6=00000000ffff0ff0 DR7=0000000000000400
> EFER=0000000000000000
> FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000
> XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000
> XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000
> XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000
> Aborted (core dumped)
> 
> Thanks a lot for your help

You're assigning a device that's getting programmed to to overlap ioport
space with another device.  Can I ask why you're trying to assigning
rather sensitive chipset components to a guest?  I can see you might
want to assign the IDE controller, but the serial KT controller and HECI
controller really have no business being exposed to the guest.  There
are certainly going to be combinations of assigning devices that don't
make sense, but I don't know how to generically prevent them.  Those
kind of sanity checks are probably better left for a libvirt interfaces
than for qemu itself.  What happens if you only expose 3.2?  Thanks,

Alex

Re: [Qemu-devel] Isuue assiging devices using VFIO on x86

[Bhushan Bharat-R65777]

> -----Original Message-----
> From: Alex Williamson [mailto:alex.williamson@redhat.com]
> Sent: Wednesday, August 29, 2012 8:44 PM
> To: Bhushan Bharat-R65777
> Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> Subject: Re: Isuue assiging devices using VFIO on x86
> 
> On Wed, 2012-08-29 at 07:11 +0000, Bhushan Bharat-R65777 wrote:
> >
> > > -----Original Message-----
> > > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > > Sent: Wednesday, August 29, 2012 12:16 PM
> > > To: Bhushan Bharat-R65777
> > > Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> > > Subject: Re: Isuue assiging devices using VFIO on x86
> > >
> > > On Tue, 2012-08-28 at 17:10 +0000, Bhushan Bharat-R65777 wrote:
> > > >
> > > > > -----Original Message-----
> > > > > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > > > > Sent: Tuesday, August 28, 2012 9:27 PM
> > > > > To: Bhushan Bharat-R65777
> > > > > Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> > > > > Subject: Re: Isuue assiging devices using VFIO on x86
> > > > >
> > > > > On Tue, 2012-08-28 at 09:23 +0000, Bhushan Bharat-R65777 wrote:
> > > > > > Hi Alex,
> > > > > >
> > > > > > In my susyem I have following devices:
> > > > > >
> > > > > > I tried assigning a following PCI devices:
> > > > > > 00:03.0 Communication controller: Intel Corporation 4 Series
> > > > > > Chipset HECI
> > > > > Controller (rev 03)
> > > > > > 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT
> > > > > > IDER Controller
> > > > > (rev 03)
> > > > > > 00:03.3 Serial controller: Intel Corporation 4 Series Chipset
> > > > > > Serial KT
> > > > > Controller (rev 03)
> > Hello Alex,
> > I am using " ./configure --target-list=x86_64-softmmu --enable-kvm " .
> > QEMU repo is at:
> > commit 3b4672f6614e07f9dc0a85a12a8c89d480a2493c
> > Author: Alex Williamson <alex.williamson@redhat.com>
> > Date:   Tue Aug 14 14:07:19 2012 -0600
> >
> >     vfio: Enable vfio-pci and mark supported
> >
> >     Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> >
> > Linux Repo is at :
> > commit d9875690d9b89a866022ff49e3fcea892345ad92
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > Date:   Thu Aug 16 14:51:24 2012 -0700
> >
> >     Linux 3.6-rc2
> >
> > ---------------------------
> >
> > Then I bound 3 pci devices with VFIO and run below command to launch
> > VM
> > qemu-system-x86_64 -enable-kvm  -nographic  -kernel
> > /boot/vmlinuz-3.6.0-rc2+ -initrd /boot/initramfs-3.6.0-rc2+.img
> > -append "root=/dev/sda1" -m 1024 -drive
> > file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device
> > vfio-pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device
> > vfio-pci,host=0000:00:03.3
> >
> > Then I was getting below errors:
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed
> > to set iommu for container: Operation not permitted
> >
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed
> > to setup container for group 2
> >
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed
> > to get group 2
> >
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Device
> > 'vfio-pci' could not be initialized
> > ---------
> >
> > Then I set
> > /sys/module/vfio_iommu_type1/parameters/allow_unsafe_interrupts = 1
> >
> > And getting below error:
> >
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning,
> > device 0000:00:03.0 does not support reset
> >
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning,
> > device 0000:00:03.2 does not support reset
> >
> > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning,
> > device 0000:00:03.3 does not support reset
> >
> > qemu: hardware error: register_ioport_read: invalid opaque for address
> > 0x3f6 CPU #0:
> > EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc ESI=00002800
> > EDI=80002804 EBP=00006fc0 ESP=00006f38
> > EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> > ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
> > SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT TR =0000 00000000
> > 0000ffff 00008b00 DPL=0 TSS32-busy
> > GDT=     000fcd68 00000037
> > IDT=     000fdb60 00000000
> > CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
> > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> > DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400
> > EFER=0000000000000000 FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> > FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> > FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> > FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> > FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> > XMM00=00000000000000000000000000000000
> > XMM01=00000000000000000000000000000000
> > XMM02=00000000000000000000000000000000
> > XMM03=00000000000000000000000000000000
> > XMM04=00000000000000000000000000000000
> > XMM05=00000000000000000000000000000000
> > XMM06=00000000000000000000000000000000
> > XMM07=00000000000000000000000000000000
> > Aborted (core dumped)
> >
> > Thanks a lot for your help
> 
> You're assigning a device that's getting programmed to to overlap ioport space
> with another device.  Can I ask why you're trying to assigning rather sensitive
> chipset components to a guest?  I can see you might want to assign the IDE
> controller, but the serial KT controller and HECI controller really have no
> business being exposed to the guest.  There are certainly going to be
> combinations of assigning devices that don't make sense, but I don't know how to
> generically prevent them.  Those kind of sanity checks are probably better left
> for a libvirt interfaces than for qemu itself.  What happens if you only expose
> 3.2?  Thanks,

Thanks Alex, Now I tried assigning a network interface to guest. On guest I can see the device by "lspci"  command but I do not see the interface in "ifconfig -a".

In fact I can see 2 PCI Ethernet device by "lspci"  command but not interface by "ifconfig -a" command.

Guest>lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 VGA compatible controller: Cirrus Logic GD 5446
00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03)  ----- QEMU emulated
00:04.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)   ----- directly assigned

Any idea what is wrong?

Thanks
-Bharat

Re: [Qemu-devel] Isuue assiging devices using VFIO on x86

[Alex Williamson]

[-- Attachment #1: Type: text/plain, Size: 7626 bytes --]

On Aug 29, 2012 11:03 AM, "Bhushan Bharat-R65777" <R65777@freescale.com>
wrote:
>
>
>
> > -----Original Message-----
> > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > Sent: Wednesday, August 29, 2012 8:44 PM
> > To: Bhushan Bharat-R65777
> > Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> > Subject: Re: Isuue assiging devices using VFIO on x86
> >
> > On Wed, 2012-08-29 at 07:11 +0000, Bhushan Bharat-R65777 wrote:
> > >
> > > > -----Original Message-----
> > > > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > > > Sent: Wednesday, August 29, 2012 12:16 PM
> > > > To: Bhushan Bharat-R65777
> > > > Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> > > > Subject: Re: Isuue assiging devices using VFIO on x86
> > > >
> > > > On Tue, 2012-08-28 at 17:10 +0000, Bhushan Bharat-R65777 wrote:
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Alex Williamson [mailto:alex.williamson@redhat.com]
> > > > > > Sent: Tuesday, August 28, 2012 9:27 PM
> > > > > > To: Bhushan Bharat-R65777
> > > > > > Cc: kvm@vger.kernel.org; Avi Kivity; qemu-devel@nongnu.org
> > > > > > Subject: Re: Isuue assiging devices using VFIO on x86
> > > > > >
> > > > > > On Tue, 2012-08-28 at 09:23 +0000, Bhushan Bharat-R65777 wrote:
> > > > > > > Hi Alex,
> > > > > > >
> > > > > > > In my susyem I have following devices:
> > > > > > >
> > > > > > > I tried assigning a following PCI devices:
> > > > > > > 00:03.0 Communication controller: Intel Corporation 4 Series
> > > > > > > Chipset HECI
> > > > > > Controller (rev 03)
> > > > > > > 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT
> > > > > > > IDER Controller
> > > > > > (rev 03)
> > > > > > > 00:03.3 Serial controller: Intel Corporation 4 Series Chipset
> > > > > > > Serial KT
> > > > > > Controller (rev 03)
> > > Hello Alex,
> > > I am using " ./configure --target-list=x86_64-softmmu --enable-kvm " .
> > > QEMU repo is at:
> > > commit 3b4672f6614e07f9dc0a85a12a8c89d480a2493c
> > > Author: Alex Williamson <alex.williamson@redhat.com>
> > > Date:   Tue Aug 14 14:07:19 2012 -0600
> > >
> > >     vfio: Enable vfio-pci and mark supported
> > >
> > >     Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> > >
> > > Linux Repo is at :
> > > commit d9875690d9b89a866022ff49e3fcea892345ad92
> > > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > > Date:   Thu Aug 16 14:51:24 2012 -0700
> > >
> > >     Linux 3.6-rc2
> > >
> > > ---------------------------
> > >
> > > Then I bound 3 pci devices with VFIO and run below command to launch
> > > VM
> > > qemu-system-x86_64 -enable-kvm  -nographic  -kernel
> > > /boot/vmlinuz-3.6.0-rc2+ -initrd /boot/initramfs-3.6.0-rc2+.img
> > > -append "root=/dev/sda1" -m 1024 -drive
> > > file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device
> > > vfio-pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device
> > > vfio-pci,host=0000:00:03.3
> > >
> > > Then I was getting below errors:
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed
> > > to set iommu for container: Operation not permitted
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed
> > > to setup container for group 2
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed
> > > to get group 2
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Device
> > > 'vfio-pci' could not be initialized
> > > ---------
> > >
> > > Then I set
> > > /sys/module/vfio_iommu_type1/parameters/allow_unsafe_interrupts = 1
> > >
> > > And getting below error:
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning,
> > > device 0000:00:03.0 does not support reset
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning,
> > > device 0000:00:03.2 does not support reset
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning,
> > > device 0000:00:03.3 does not support reset
> > >
> > > qemu: hardware error: register_ioport_read: invalid opaque for address
> > > 0x3f6 CPU #0:
> > > EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc ESI=00002800
> > > EDI=80002804 EBP=00006fc0 ESP=00006f38
> > > EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> > > ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
> > > SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT TR =0000 00000000
> > > 0000ffff 00008b00 DPL=0 TSS32-busy
> > > GDT=     000fcd68 00000037
> > > IDT=     000fdb60 00000000
> > > CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
> > > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> > > DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400
> > > EFER=0000000000000000 FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> > > FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> > > FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> > > FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> > > FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> > > XMM00=00000000000000000000000000000000
> > > XMM01=00000000000000000000000000000000
> > > XMM02=00000000000000000000000000000000
> > > XMM03=00000000000000000000000000000000
> > > XMM04=00000000000000000000000000000000
> > > XMM05=00000000000000000000000000000000
> > > XMM06=00000000000000000000000000000000
> > > XMM07=00000000000000000000000000000000
> > > Aborted (core dumped)
> > >
> > > Thanks a lot for your help
> >
> > You're assigning a device that's getting programmed to to overlap
ioport space
> > with another device.  Can I ask why you're trying to assigning rather
sensitive
> > chipset components to a guest?  I can see you might want to assign the
IDE
> > controller, but the serial KT controller and HECI controller really
have no
> > business being exposed to the guest.  There are certainly going to be
> > combinations of assigning devices that don't make sense, but I don't
know how to
> > generically prevent them.  Those kind of sanity checks are probably
better left
> > for a libvirt interfaces than for qemu itself.  What happens if you
only expose
> > 3.2?  Thanks,
>
> Thanks Alex, Now I tried assigning a network interface to guest. On guest
I can see the device by "lspci"  command but I do not see the interface in
"ifconfig -a".
>
> In fact I can see 2 PCI Ethernet device by "lspci"  command but not
interface by "ifconfig -a" command.
>
> Guest>lspci
> 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev
02)
> 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
> 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton
II]
> 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
> 00:02.0 VGA compatible controller: Cirrus Logic GD 5446
> 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet
Controller (rev 03)  ----- QEMU emulated
> 00:04.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network
Connection (rev 02)   ----- directly assigned
>
> Any idea what is wrong?

It's hard to debug without a guest dmesg, but the datasheet for this device
doesn't mention MSI, which is currently a requirement for vfio. Legacy
interrupt support is still being developed. Does it support MSI? Please
provide guest dmesg and full lspci for the device. Thanks,

Alex

[-- Attachment #2: Type: text/html, Size: 10734 bytes --]

Re: [Qemu-devel] Isuue assiging devices using VFIO on x86

[Bhushan Bharat-R65777]

[-- Attachment #1.1: Type: text/plain, Size: 8594 bytes --]

PFA file which have full dmeg and lspci of assigned device

Thanks
-Bharat

From: alex.l.williamson@gmail.com [mailto:alex.l.williamson@gmail.com] On Behalf Of Alex Williamson
Sent: Wednesday, August 29, 2012 11:53 PM
To: Bhushan Bharat-R65777
Cc: kvm@vger.kernel.org; avi@redhat.com; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Isuue assiging devices using VFIO on x86


On Aug 29, 2012 11:03 AM, "Bhushan Bharat-R65777" <R65777@freescale.com<mailto:R65777@freescale.com>> wrote:
>
>
>
> > -----Original Message-----
> > From: Alex Williamson [mailto:alex.williamson@redhat.com<mailto:alex.williamson@redhat.com>]
> > Sent: Wednesday, August 29, 2012 8:44 PM
> > To: Bhushan Bharat-R65777
> > Cc: kvm@vger.kernel.org<mailto:kvm@vger.kernel.org>; Avi Kivity; qemu-devel@nongnu.org<mailto:qemu-devel@nongnu.org>
> > Subject: Re: Isuue assiging devices using VFIO on x86
> >
> > On Wed, 2012-08-29 at 07:11 +0000, Bhushan Bharat-R65777 wrote:
> > >
> > > > -----Original Message-----
> > > > From: Alex Williamson [mailto:alex.williamson@redhat.com<mailto:alex.williamson@redhat.com>]
> > > > Sent: Wednesday, August 29, 2012 12:16 PM
> > > > To: Bhushan Bharat-R65777
> > > > Cc: kvm@vger.kernel.org<mailto:kvm@vger.kernel.org>; Avi Kivity; qemu-devel@nongnu.org<mailto:qemu-devel@nongnu.org>
> > > > Subject: Re: Isuue assiging devices using VFIO on x86
> > > >
> > > > On Tue, 2012-08-28 at 17:10 +0000, Bhushan Bharat-R65777 wrote:
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Alex Williamson [mailto:alex.williamson@redhat.com<mailto:alex.williamson@redhat.com>]
> > > > > > Sent: Tuesday, August 28, 2012 9:27 PM
> > > > > > To: Bhushan Bharat-R65777
> > > > > > Cc: kvm@vger.kernel.org<mailto:kvm@vger.kernel.org>; Avi Kivity; qemu-devel@nongnu.org<mailto:qemu-devel@nongnu.org>
> > > > > > Subject: Re: Isuue assiging devices using VFIO on x86
> > > > > >
> > > > > > On Tue, 2012-08-28 at 09:23 +0000, Bhushan Bharat-R65777 wrote:
> > > > > > > Hi Alex,
> > > > > > >
> > > > > > > In my susyem I have following devices:
> > > > > > >
> > > > > > > I tried assigning a following PCI devices:
> > > > > > > 00:03.0 Communication controller: Intel Corporation 4 Series
> > > > > > > Chipset HECI
> > > > > > Controller (rev 03)
> > > > > > > 00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT
> > > > > > > IDER Controller
> > > > > > (rev 03)
> > > > > > > 00:03.3 Serial controller: Intel Corporation 4 Series Chipset
> > > > > > > Serial KT
> > > > > > Controller (rev 03)
> > > Hello Alex,
> > > I am using " ./configure --target-list=x86_64-softmmu --enable-kvm " .
> > > QEMU repo is at:
> > > commit 3b4672f6614e07f9dc0a85a12a8c89d480a2493c
> > > Author: Alex Williamson <alex.williamson@redhat.com<mailto:alex.williamson@redhat.com>>
> > > Date:   Tue Aug 14 14:07:19 2012 -0600
> > >
> > >     vfio: Enable vfio-pci and mark supported
> > >
> > >     Signed-off-by: Alex Williamson <alex.williamson@redhat.com<mailto:alex.williamson@redhat.com>>
> > >
> > > Linux Repo is at :
> > > commit d9875690d9b89a866022ff49e3fcea892345ad92
> > > Author: Linus Torvalds <torvalds@linux-foundation.org<mailto:torvalds@linux-foundation.org>>
> > > Date:   Thu Aug 16 14:51:24 2012 -0700
> > >
> > >     Linux 3.6-rc2
> > >
> > > ---------------------------
> > >
> > > Then I bound 3 pci devices with VFIO and run below command to launch
> > > VM
> > > qemu-system-x86_64 -enable-kvm  -nographic  -kernel
> > > /boot/vmlinuz-3.6.0-rc2+ -initrd /boot/initramfs-3.6.0-rc2+.img
> > > -append "root=/dev/sda1" -m 1024 -drive
> > > file=/home/kvmdev/debian_squeeze_amd64_standard.qcow2 -device
> > > vfio-pci,host=0000:00:03.0 -device vfio-pci,host=0000:00:03.2 -device
> > > vfio-pci,host=0000:00:03.3
> > >
> > > Then I was getting below errors:
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed
> > > to set iommu for container: Operation not permitted
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed
> > > to setup container for group 2
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: vfio: failed
> > > to get group 2
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Device
> > > 'vfio-pci' could not be initialized
> > > ---------
> > >
> > > Then I set
> > > /sys/module/vfio_iommu_type1/parameters/allow_unsafe_interrupts = 1
> > >
> > > And getting below error:
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.0: Warning,
> > > device 0000:00:03.0 does not support reset
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.2: Warning,
> > > device 0000:00:03.2 does not support reset
> > >
> > > qemu-system-x86_64: -device vfio-pci,host=0000:00:03.3: Warning,
> > > device 0000:00:03.3 does not support reset
> > >
> > > qemu: hardware error: register_ioport_read: invalid opaque for address
> > > 0x3f6 CPU #0:
> > > EAX=80000003 EBX=3ffe0e80 ECX=80000003 EDX=00000cfc ESI=00002800
> > > EDI=80002804 EBP=00006fc0 ESP=00006f38
> > > EIP=3ffec005 EFL=00000086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> > > ES =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > CS =0008 00000000 ffffffff 00c09b00 DPL=0 CS32 [-RA]
> > > SS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > DS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > FS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > GS =0010 00000000 ffffffff 00c09300 DPL=0 DS   [-WA]
> > > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT TR =0000 00000000
> > > 0000ffff 00008b00 DPL=0 TSS32-busy
> > > GDT=     000fcd68 00000037
> > > IDT=     000fdb60 00000000
> > > CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000
> > > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> > > DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400
> > > EFER=0000000000000000 FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80
> > > FPR0=0000000000000000 0000 FPR1=0000000000000000 0000
> > > FPR2=0000000000000000 0000 FPR3=0000000000000000 0000
> > > FPR4=0000000000000000 0000 FPR5=0000000000000000 0000
> > > FPR6=0000000000000000 0000 FPR7=0000000000000000 0000
> > > XMM00=00000000000000000000000000000000
> > > XMM01=00000000000000000000000000000000
> > > XMM02=00000000000000000000000000000000
> > > XMM03=00000000000000000000000000000000
> > > XMM04=00000000000000000000000000000000
> > > XMM05=00000000000000000000000000000000
> > > XMM06=00000000000000000000000000000000
> > > XMM07=00000000000000000000000000000000
> > > Aborted (core dumped)
> > >
> > > Thanks a lot for your help
> >
> > You're assigning a device that's getting programmed to to overlap ioport space
> > with another device.  Can I ask why you're trying to assigning rather sensitive
> > chipset components to a guest?  I can see you might want to assign the IDE
> > controller, but the serial KT controller and HECI controller really have no
> > business being exposed to the guest.  There are certainly going to be
> > combinations of assigning devices that don't make sense, but I don't know how to
> > generically prevent them.  Those kind of sanity checks are probably better left
> > for a libvirt interfaces than for qemu itself.  What happens if you only expose
> > 3.2?  Thanks,
>
> Thanks Alex, Now I tried assigning a network interface to guest. On guest I can see the device by "lspci"  command but I do not see the interface in "ifconfig -a".
>
> In fact I can see 2 PCI Ethernet device by "lspci"  command but not interface by "ifconfig -a" command.
>
> Guest>lspci
> 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
> 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
> 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
> 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
> 00:02.0 VGA compatible controller: Cirrus Logic GD 5446
> 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03)  ----- QEMU emulated
> 00:04.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)   ----- directly assigned
>
> Any idea what is wrong?

It's hard to debug without a guest dmesg, but the datasheet for this device doesn't mention MSI, which is currently a requirement for vfio. Legacy interrupt support is still being developed. Does it support MSI? Please provide guest dmesg and full lspci for the device. Thanks,

Alex

[-- Attachment #1.2: Type: text/html, Size: 14320 bytes --]

[-- Attachment #2: lspci.c --]
[-- Type: text/plain, Size: 29103 bytes --]

00:04.0 Ethernet controller: SysKonnect SK-9E21D 10/100/1000Base-T Adapter, Copper RJ-45 (rev 17)
	Subsystem: SysKonnect SK-9E21D 10/100/1000Base-T Adapter
	Physical Slot: 4
	Flags: fast devsel, IRQ 11
	Memory at febf0000 (64-bit, non-prefetchable) [size=16K]
	I/O ports at c000 [size=256]
	Expansion ROM at febc0000 [disabled] [size=128K]
	Capabilities: [48] Power Management version 2
	Capabilities: [50] Vital Product Data
	Capabilities: [5c] MSI: Enable- Count=1/2 Maskable- 64bit+
	Capabilities: [e0] Express Legacy Endpoint, MSI 00
00: 48 11 00 9e 03 00 10 00 17 00 00 02 10 00 00 00
10: 04 00 bf fe 00 00 00 00 01 c0 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 48 11 d0 21
30: 00 00 bc fe 48 00 00 00 00 00 00 00 0b 01 00 00
40: 00 00 00 00 00 00 00 00 01 50 02 fe 00 20 00 13
50: 03 5c fc 80 00 00 00 78 00 00 00 00 05 e0 82 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 10 00 11 00 c0 0f 28 00 04 24 11 00 11 a4 03 00
f0: 48 00 11 10 00 00 00 00 00 00 00 00 00 00 00 00


-----------------
dmesg
...
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.6.0-rc2+ (kvmdev@localhost.localdomain) (gcc verssion 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC) ) #9 SMP Tue Aug 21 23:32:35 CDT 2012
[    0.000000] Command line: root=/dev/sda1
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009f3ff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009f400-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003fffdfff] usable
[    0.000000] BIOS-e820: [mem 0x000000003fffe000-0x000000003fffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI 2.4 present.
[    0.000000] DMI: Bochs Bochs, BIOS Bochs 01/01/2007
[    0.000000] Hypervisor detected: KVM
[    0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000000] No AGP bridge found
[    0.000000] e820: last_pfn = 0x3fffe max_arch_pfn = 0x400000000
[    0.000000] MTRR default type: write-back
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF uncachable
[    0.000000]   C0000-FFFFF write-protect
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 00E0000000 mask FFE0000000 uncachable
[    0.000000]   1 disabled
[    0.000000]   2 disabled
[    0.000000]   3 disabled
[    0.000000]   4 disabled
[    0.000000]   5 disabled
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000] PAT not supported by CPU.
[    0.000000] found SMP MP-table at [mem 0x000fda60-0x000fda6f] mapped at [fffff8800000fda60]
[    0.000000] initial memory mapped: [mem 0x00000000-0x1fffffff]
[    0.000000] Base memory trampoline at [ffff880000099000] 99000 size 24576
[    0.000000] init_memory_mapping: [mem 0x00000000-0x3fffdfff]
[    0.000000]  [mem 0x00000000-0x3fdfffff] page 2M
[    0.000000]  [mem 0x3fe00000-0x3fffdfff] page 4k
[    0.000000] kernel direct mapping tables up to 0x3fffdfff @ [mem 0x1fdfe000-0x1fffffff]
[    0.000000] RAMDISK: [mem 0x3ee08000-0x3ffeffff]
[    0.000000] ACPI: RSDP 00000000000fd900 00014 (v00 BOCHS )
[    0.000000] ACPI: RSDT 000000003fffe5b0 00038 (v01 BOCHS  BXPCRSDT 00000001 BBXPC 00000001)
[    0.000000] ACPI: FACP 000000003fffff80 00074 (v01 BOCHS  BXPCFACP 00000001 BBXPC 00000001)
[    0.000000] ACPI: DSDT 000000003fffe5f0 01121 (v01   BXPC   BXDSDT 00000001 IINTL 20100528)
[    0.000000] ACPI: FACS 000000003fffff40 00040
[    0.000000] ACPI: SSDT 000000003ffffea0 0009E (v01 BOCHS  BXPCSSDT 00000001 BBXPC 00000001)
[    0.000000] ACPI: APIC 000000003ffffdb0 00078 (v01 BOCHS  BXPCAPIC 00000001 BBXPC 00000001)
[    0.000000] ACPI: HPET 000000003ffffd70 00038 (v01 BOCHS  BXPCHPET 00000001 BBXPC 00000001)
[    0.000000] ACPI: SSDT 000000003ffff720 00644 (v01   BXPC BXSSDTPC 00000001 IINTL 20100528)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at [mem 0x0000000000000000-0x000000003fffdfff]
[    0.000000] Initmem setup node 0 [mem 0x00000000-0x3fffdfff]
[    0.000000]   NODE_DATA [mem 0x3ede1000-0x3ee07fff]
[    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
[    0.000000] kvm-clock: cpu 0, msr 0:1f11c01, boot clock
[    0.000000]  [ffffea0000000000-ffffea0000ffffff] PMD -> [ffff88003d400000-fffff88003e3fffff] on node 0
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x00010000-0x00ffffff]
[    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00010000-0x0009efff]
[    0.000000]   node   0: [mem 0x00100000-0x3fffdfff]
[    0.000000] On node 0 totalpages: 262029
[    0.000000]   DMA zone: 64 pages used for memmap
[    0.000000]   DMA zone: 6 pages reserved
[    0.000000]   DMA zone: 3913 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 4032 pages used for memmap
[    0.000000]   DMA32 zone: 254014 pages, LIFO batch:31
[    0.000000] ACPI: PM-Timer IO Port: 0xb008
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ5 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] ACPI: IRQ10 used by override.
[    0.000000] ACPI: IRQ11 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[    0.000000] nr_irqs_gsi: 40
[    0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[    0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[    0.000000] e820: [mem 0x40000000-0xfeffbfff] available for PCI devices
[    0.000000] Booting paravirtualized kernel on KVM
[    0.000000] setup_percpu: NR_CPUS:4096 nr_cpumask_bits:1 nr_cpu_ids:1 nr_node_ids:1
[    0.000000] PERCPU: Embedded 477 pages/cpu @ffff88003ea00000 s1923776 r8192 d21824 u2097152
[    0.000000] pcpu-alloc: s1923776 r8192 d21824 u2097152 alloc=1*2097152
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] kvm-clock: cpu 0, msr 0:3ebd4c01, primary cpu clock
[    0.000000] KVM setup async PF for cpu 0
[    0.000000] kvm-stealtime: cpu 0, msr 3ea0e240
[    0.000000] Built 1 zonelists in Node order, mobility grouping on.  Total pages: 257927
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: root=/dev/sda1
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] __ex_table already sorted, skipping sort
[    0.000000] Checking aperture...
[    0.000000] No AGP bridge found
[    0.000000] Memory: 981116k/1048568k available (7398k kernel code, 452k absent, 67000k reserved, 6151k data, 3252k init)
[    0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, NN
odes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU lockdep checking is enabled.
[    0.000000]  RCU restricting CPUs from NR_CPUS=4096 to nr_cpu_ids=1.
[    0.000000] NR_IRQS:262400 nr_irqs:256 16
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty0] enabled
[    0.000000] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingoo
 Molnar
[    0.000000] ... MAX_LOCKDEP_SUBCLASSES:  8
[    0.000000] ... MAX_LOCK_DEPTH:          48
[    0.000000] ... MAX_LOCKDEP_KEYS:        8191
[    0.000000] ... CLASSHASH_SIZE:          4096
[    0.000000] ... MAX_LOCKDEP_ENTRIES:     16384
[    0.000000] ... MAX_LOCKDEP_CHAINS:      32768
[    0.000000] ... CHAINHASH_SIZE:          16384
[    0.000000]  memory used by lock dependency info: 6367 kB
[    0.000000]  per task-struct memory footprint: 2688 bytes
[    0.000000] allocated 4194304 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memorr
y cgroups
[    0.000000] ODEBUG: 17 of 17 active objects replaced
[    0.000000] kmemleak: Kernel memory leak detector disabled
[    0.000000] hpet clockevent registered
[    0.000000] tsc: Detected 3324.848 MHz processor
[    0.002999] Calibrating delay loop (skipped) preset value.. 6649.69 BogoMIPS  
(lpj=3324848)
[    0.003007] pid_max: default: 32768 minimum: 301
[    0.004359] Security Framework initialized
[    0.005020] SELinux:  Initializing.
[    0.006088] SELinux:  Starting in permissive mode
[    0.006495] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.008641] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[    0.010350] Mount-cache hash table entries: 256
[    0.013653] Initializing cgroup subsys cpuacct
[    0.014014] Initializing cgroup subsys memory
[    0.016066] Initializing cgroup subsys devices
[    0.017014] Initializing cgroup subsys freezer
[    0.018010] Initializing cgroup subsys net_cls
[    0.019010] Initializing cgroup subsys blkio
[    0.020006] Initializing cgroup subsys perf_event
[    0.021363] mce: CPU supports 10 MCE banks
[    0.023076] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.023076] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.023076] tlb_flushall_shift is 0x6
[    0.024140] SMP alternatives: switching to UP code
[    0.280746] Freeing SMP alternatives: 24k freed
[    0.282067] ACPI: Core revision 20120711
[    0.311975] ftrace: allocating 24645 entries in 97 pages
[    0.322269] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.322954] smpboot: CPU0: Intel QEMU Virtual CPU version 1.1.50 stepping 03
[    0.325950] Performance Events: unsupported p6 CPU model 2 no PMU driver, soff
tware events only.
[    0.330205] NMI watchdog: disabled (cpu0): hardware events not enabled
[    0.331085] Brought up 1 CPUs
[    0.331953] smpboot: Total of 1 processors activated (6649.69 BogoMIPS)
[    0.336497] devtmpfs: initialized
[    0.340780] atomic64 test passed for x86-64 platform with CX8 and with SSE
[    0.342158] RTC time: 18:23:59, date: 08/29/12
[    0.343476] NET: Registered protocol family 16
[    0.346559] ACPI: bus type pci registered
[    0.348132] PCI: Using configuration type 1 for base access
[    0.364429] bio: create slab <bio-0> at 0
[    0.365498] ACPI: Added _OSI(Module Device)
[    0.365957] ACPI: Added _OSI(Processor Device)
[    0.366959] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.367956] ACPI: Added _OSI(Processor Aggregator Device)
[    0.372782] ACPI: EC: Look up EC in DSDT
[    0.421970] ACPI: Interpreter enabled
[    0.422853] ACPI: (supports S0 S3 S4 S5)
[    0.424915] ACPI: Using IOAPIC for interrupt routing
[    0.492431] ACPI: No dock devices found.
[    0.492930] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pp
ci=use_crs" and report a bug
[    0.494100] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.495936] pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7] (ignoo
red)
[    0.495939] pci_root PNP0A03:00: host bridge window [io  0x0d00-0xffff] (ignoo
red)
[    0.495940] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff
f] (ignored)
[    0.495942] pci_root PNP0A03:00: host bridge window [mem 0xe0000000-0xfebfffff
f] (ignored)
[    0.495956] PCI: root bus 00: using default resources
[    0.495988] pci_root PNP0A03:00: fail to add MMCONFIG information, can't accee
ss extended PCI configuration space under this bridge.
[    0.499059] PCI host bridge to bus 0000:00
[    0.499939] pci_bus 0000:00: busn_res: [bus 00-ff] is inserted under domain [[
bus 00-ff]
[    0.499941] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.500933] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
[    0.501933] pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffffff]
[    0.503053] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
[    0.504155] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
[    0.505503] pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
[    0.507281] pci 0000:00:01.1: reg 20: [io  0xc140-0xc14f]
[    0.508462] pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
[    0.509676] pci 0000:00:01.3: quirk: [io  0xb000-0xb03f] claimed by PIIX4 ACPP
I
[    0.509950] pci 0000:00:01.3: quirk: [io  0xb100-0xb10f] claimed by PIIX4 SMB
[    0.511355] pci 0000:00:02.0: [1013:00b8] type 00 class 0x030000
[    0.512970] pci 0000:00:02.0: reg 10: [mem 0xfc000000-0xfdffffff pref]
[    0.515070] pci 0000:00:02.0: reg 14: [mem 0xfebf4000-0xfebf4fff]
[    0.528060] pci 0000:00:02.0: reg 30: [mem 0xfebe0000-0xfebeffff pref]
[    0.529328] pci 0000:00:03.0: [8086:100e] type 00 class 0x020000
[    0.530003] pci 0000:00:03.0: reg 10: [mem 0xfeb80000-0xfeb9ffff]
[    0.530581] pci 0000:00:03.0: reg 14: [io  0xc100-0xc13f]
[    0.533577] pci 0000:00:03.0: reg 30: [mem 0xfeba0000-0xfebbffff pref]
[    0.534380] pci 0000:00:04.0: [1148:9e00] type 00 class 0x020000
[    0.535160] pci 0000:00:04.0: reg 10: [mem 0xfebf0000-0xfebf3fff 64bit]
[    0.536716] pci 0000:00:04.0: reg 18: [io  0xc000-0xc0ff]
[    0.542015] pci 0000:00:04.0: reg 30: [mem 0xfebc0000-0xfebdffff pref]
[    0.543613] pci 0000:00:04.0: supports D1 D2
[    0.543615] pci 0000:00:04.0: PME# supported from D0 D1 D2 D3hot D3cold
[    0.544487] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    0.561932]  pci0000:00: ACPI _OSC support notification failed, disabling PCII
e ASPM
[    0.562918]  pci0000:00: Unable to request _OSC control (_OSC support mask: 00
x08)
[    0.662037] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[    0.665308] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[    0.668550] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[    0.671810] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[    0.674995] ACPI: PCI Interrupt Link [LNKS] (IRQs 9) *0
[    0.678267] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+memm
,locks=none
[    0.678922] vgaarb: loaded
[    0.679899] vgaarb: bridge control possible 0000:00:02.0
[    0.683156] SCSI subsystem initialized
[    0.683912] ACPI: bus type scsi registered
[    0.685236] libata version 3.00 loaded.
[    0.685630] ACPI: bus type usb registered
[    0.686138] usbcore: registered new interface driver usbfs
[    0.687987] usbcore: registered new interface driver hub
[    0.689027] usbcore: registered new device driver usb
[    0.690501] PCI: Using ACPI for IRQ routing
[    0.690907] PCI: pci_cache_line_size set to 64 bytes
[    0.692246] e820: reserve RAM buffer [mem 0x0009f400-0x0009ffff]
[    0.692264] e820: reserve RAM buffer [mem 0x3fffe000-0x3fffffff]
[    0.693587] NetLabel: Initializing
[    0.693897] NetLabel:  domain hash size = 128
[    0.694897] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.696058] NetLabel:  unlabeled traffic allowed by default
[    0.697052] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[    0.697942] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[    0.700897] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[    0.705240] Switching to clocksource kvm-clock
[    0.839798] pnp: PnP ACPI init
[    0.840823] ACPI: bus type pnp registered
[    0.842051] pnp 00:00: [bus 00-ff]
[    0.842058] pnp 00:00: [io  0x0cf8-0x0cff]
[    0.842064] pnp 00:00: [io  0x0000-0x0cf7 window]
[    0.842075] pnp 00:00: [io  0x0d00-0xffff window]
[    0.842081] pnp 00:00: [mem 0x000a0000-0x000bffff window]
[    0.842087] pnp 00:00: [mem 0xe0000000-0xfebfffff window]
[    0.842358] pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
[    0.842521] pnp 00:01: [io  0x0070-0x0071]
[    0.842593] pnp 00:01: [irq 8]
[    0.842599] pnp 00:01: [io  0x0072-0x0077]
[    0.842819] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.843319] pnp 00:02: [io  0x0060]
[    0.843326] pnp 00:02: [io  0x0064]
[    0.843371] pnp 00:02: [irq 1]
[    0.843583] pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
[    0.844169] pnp 00:03: [irq 12]
[    0.844382] pnp 00:03: Plug and Play ACPI device, IDs PNP0f13 (active)
[    0.844813] pnp 00:04: [io  0x03f2-0x03f5]
[    0.844819] pnp 00:04: [io  0x03f7]
[    0.844864] pnp 00:04: [irq 6]
[    0.844870] pnp 00:04: [dma 2]
[    0.845130] pnp 00:04: Plug and Play ACPI device, IDs PNP0700 (active)
[    0.845950] pnp 00:05: [io  0x0378-0x037f]
[    0.846016] pnp 00:05: [irq 7]
[    0.846252] pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)
[    0.847174] pnp 00:06: [io  0x03f8-0x03ff]
[    0.847219] pnp 00:06: [irq 4]
[    0.847437] pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
[    0.850126] pnp 00:07: [mem 0xfed00000-0xfed003ff]
[    0.850378] pnp 00:07: Plug and Play ACPI device, IDs PNP0103 (active)
[    0.852680] pnp: PnP ACPI: found 8 devices
[    0.853683] ACPI: ACPI bus type pnp unregistered
[    0.877486] pci_bus 0000:00: resource 4 [io  0x0000-0xffff]
[    0.877489] pci_bus 0000:00: resource 5 [mem 0x00000000-0xffffffffff]
[    0.877679] NET: Registered protocol family 2
[    0.879710] TCP established hash table entries: 131072 (order: 9, 2097152 bytt
es)
[    0.883551] TCP bind hash table entries: 65536 (order: 10, 5242880 bytes)
[    0.890150] TCP: Hash tables configured (established 131072 bind 65536)
[    0.891514] TCP: reno registered
[    0.892505] UDP hash table entries: 512 (order: 4, 98304 bytes)
[    0.893641] UDP-Lite hash table entries: 512 (order: 4, 98304 bytes)
[    0.895467] NET: Registered protocol family 1
[    0.896462] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[    0.897523] pci 0000:00:01.0: PIIX3: Enabling Passive Release
[    0.898673] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[    0.899820] pci 0000:00:02.0: Boot video device
[    0.899925] PCI: CLS 64 bytes, default 64
[    0.900468] Unpacking initramfs...
[    1.272352] Freeing initrd memory: 18336k freed
[    1.393958] DMA-API: preallocated 32768 debug entries
[    1.394975] DMA-API: debugging enabled by kernel config
[    1.396236] kvm: no hardware support
[    1.397139] has_svm: not amd
[    1.397955] kvm: no hardware support
[    1.402111] audit: initializing netlink socket (disabled)
[    1.403182] type=2000 audit(1346264641.402:1): initialized
[    1.404295] cryptomgr_test (22) used greatest stack depth: 6120 bytes left
[    1.421972] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    1.452404] VFS: Disk quotas dquot_6.5.2
[    1.453643] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.460134] msgmni has been set to 1952
[    1.461640] SELinux:  Registering netfilter hooks
[    1.464264] cryptomgr_test (29) used greatest stack depth: 5512 bytes left
[    1.466599] cryptomgr_test (34) used greatest stack depth: 5368 bytes left
[    1.467957] alg: No test for stdrng (krng)
[    1.469047] NET: Registered protocol family 38
[    1.470660] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 22
52)
[    1.472446] io scheduler noop registered
[    1.473528] io scheduler deadline registered
[    1.474923] io scheduler cfq registered (default)
[    1.475887] start plist test
[    1.477754] end plist test
[    1.478609] list_sort_test: start testing list_sort()
[    1.483889] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    1.485235] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    1.486293] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    1.488656] acpiphp: Slot [3] registered
[    1.489856] acpiphp: Slot [4] registered
[    1.491198] acpiphp: Slot [5] registered
[    1.492563] acpiphp: Slot [6] registered
[    1.493761] acpiphp: Slot [7] registered
[    1.495118] acpiphp: Slot [8] registered
[    1.496554] acpiphp: Slot [9] registered
[    1.497827] acpiphp: Slot [10] registered
[    1.499078] acpiphp: Slot [11] registered
[    1.500522] acpiphp: Slot [12] registered
[    1.501745] acpiphp: Slot [13] registered
[    1.502953] acpiphp: Slot [14] registered
[    1.504272] acpiphp: Slot [15] registered
[    1.505476] acpiphp: Slot [16] registered
[    1.506753] acpiphp: Slot [17] registered
[    1.507957] acpiphp: Slot [18] registered
[    1.509274] acpiphp: Slot [19] registered
[    1.510476] acpiphp: Slot [20] registered
[    1.511695] acpiphp: Slot [21] registered
[    1.512970] acpiphp: Slot [22] registered
[    1.514215] acpiphp: Slot [23] registered
[    1.515497] acpiphp: Slot [24] registered
[    1.516701] acpiphp: Slot [25] registered
[    1.517907] acpiphp: Slot [26] registered
[    1.519223] acpiphp: Slot [27] registered
[    1.520429] acpiphp: Slot [28] registered
[    1.521730] acpiphp: Slot [29] registered
[    1.522934] acpiphp: Slot [30] registered
[    1.524291] acpiphp: Slot [31] registered
[    1.527865] intel_idle: does not run on family 6 model 2
[    1.528409] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/inpp
ut0
[    1.530155] ACPI: Power Button [PWRF]
[    1.582794] GHES: HEST is not enabled!
[    1.584252] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.612733] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    1.644109] 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    1.647227] Non-volatile memory driver v1.3
[    1.648156] Linux agpgart interface v0.103
[    1.659106] loop: module loaded
[    1.660800] ata_piix 0000:00:01.1: version 2.13
[    1.661198] ata_piix 0000:00:01.1: setting latency timer to 64
[    1.665391] scsi0 : ata_piix
[    1.667649] scsi1 : ata_piix
[    1.669115] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc140 irq 14
[    1.670180] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc148 irq 15
[    1.672136] libphy: Fixed MDIO Bus: probed
[    1.673434] VFIO - User Level meta-driver version: 0.3
[    1.681904] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.683401] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.684513] uhci_hcd: USB Universal Host Controller Interface driver
[    1.686640] usbcore: registered new interface driver usbserial
[    1.687754] usbcore: registered new interface driver usbserial_generic
[    1.692295] modprobe (42) used greatest stack depth: 4640 bytes left
[    1.693449] USB Serial support registered for generic
[    1.694659] usbserial: USB Serial Driver core
[    1.695902] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x66
4 irq 1,12
[    1.699976] serio: i8042 KBD port at 0x60,0x64 irq 1
[    1.701204] serio: i8042 AUX port at 0x60,0x64 irq 12
[    1.703525] mousedev: PS/2 mouse device common for all mice
[    1.706601] input: AT Translated Set 2 keyboard as /devices/platform/i8042/see
rio0/input/input1
[    1.709644] rtc_cmos 00:01: RTC can wake from S4
[    1.716350] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
[    1.717772] rtc0: alarms up to one day, 114 bytes nvram, hpet irqs
[    1.723112] device-mapper: uevent: version 1.0.3
[    1.724879] device-mapper: ioctl: 4.23.0-ioctl (2012-07-25) initialised: dm-dd
evel@redhat.com
[    1.727672] cpuidle: using governor ladder
[    1.728599] cpuidle: using governor menu
[    1.730432] EFI Variables Facility v0.08 2004-May-17
[    1.732561] usbcore: registered new interface driver usbhid
[    1.733717] usbhid: USB HID core driver
[    1.734708] AMD IOMMUv2 driver by Joerg Roedel <joerg.roedel@amd.com>
[    1.735750] AMD IOMMUv2 functionality not available on this system
[    1.737264] drop_monitor: Initializing network drop monitor service
[    1.738560] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.739769] TCP: cubic registered
[    1.740663] Initializing XFRM netlink socket
[    1.743309] NET: Registered protocol family 10
[    1.746153] mip6: Mobile IPv6
[    1.746995] NET: Registered protocol family 17
[    1.749497] PM: Hibernation image not present or could not be loaded.
[    1.749595] registered taskstats version 1
[    1.752755]   Magic number: 8:923:393
[    1.754137] rtc_cmos 00:01: setting system clock to 2012-08-29 18:24:00 UTC ((
1346264640)
[    1.829559] ata1.01: NODEV after polling detection
[    1.830072] ata2.01: NODEV after polling detection
[    1.832658] ata2.00: ATAPI: QEMU DVD-ROM, 1.1.50, max UDMA/100
[    1.834958] ata1.00: ATA-7: QEMU HARDDISK, 1.1.50, max UDMA/100
[    1.836676] ata1.00: 33554432 sectors, multi 16: LBA48
[    1.841821] ata1.00: configured for MWDMA2
[    1.843851] scsi 0:0:0:0: Direct-Access     ATA      QEMU HARDDISK    1.1. PQQ
: 0 ANSI: 5
[    1.847108] sd 0:0:0:0: [sda] 33554432 512-byte logical blocks: (17.1 GB/16.00
 GiB)
[    1.849330] sd 0:0:0:0: [sda] Write Protect is off
[    1.850294] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.851208] ata2.00: configured for MWDMA2
[    1.852501] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doess
n't support DPO or FUA
[    1.854427] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.857809] scsi 1:0:0:0: CD-ROM            QEMU     QEMU DVD-ROM     1.1. PQQ
: 0 ANSI: 5
[    1.862242] sr0: scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[    1.863249] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.866764] sr 1:0:0:0: Attached scsi CD-ROM sr0
[    1.869902] sr 1:0:0:0: Attached scsi generic sg1 type 5
[    1.892657]  sda: sda1 sda2 < sda5 >
[    1.898768] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.903833] Freeing unused kernel memory: 3252k freed
[    1.907213] Write protecting the kernel read-only data: 12288k
[    1.911933] Freeing unused kernel memory: 780k freed
[    1.916842] Freeing unused kernel memory: 1060k freed
[    2.155362] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i80422
/serio1/input/input2
[    2.400274] tsc: Refined TSC clocksource calibration: 3324.848 MHz
[    2.420827] dracut: dracut-013-18.fc16
[    2.529683] udevd[103]: starting version 173
[    2.931889] console_init (117) used greatest stack depth: 4576 bytes left
[    2.965434] dracut: Starting plymouth daemon
[    3.506257] ata_id (149) used greatest stack depth: 4384 bytes left
[    3.941515] blkid (173) used greatest stack depth: 4256 bytes left
[    4.063342] ata_id (199) used greatest stack depth: 3632 bytes left
[    4.366906] Floppy drive(s): fd0 is 1.44M
[    4.395325] FDC 0 is a S82078B
[    4.785587] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystee
m
[    4.805591] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:  
(null)
[    4.951754] dracut: Checking ext3: /dev/sda1
[    4.953106] dracut: issuing e2fsck -a  /dev/sda1
[    5.159669] dracut: /dev/sda1: clean, 25329/1003680 files, 272659/4010752 bloo
cks
[    5.166850] dracut: Remounting /dev/sda1 with -o errors=remount-ro,ro
[    5.199558] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystee
m
[    5.235523] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:  
errors=remount-ro
[    5.282281] dracut: Mounted root filesystem /dev/sda1
[    5.603473] dracut: Switching root
[    6.010197] stty (282) used greatest stack depth: 2064 bytes left
[    6.564068] udev[315]: starting version 164
[    8.575022] Adding 731132k swap on /dev/sda5.  Priority:-1 extents:1 across:77
31132k
[    8.616977] EXT4-fs (sda1): re-mounted. Opts: (null)
[    8.800830] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   12.193450] rc (281) used greatest stack depth: 1760 bytes left

Re: [Qemu-devel] Isuue assiging devices using VFIO on x86

[Alex Williamson]

On Wed, 2012-08-29 at 18:42 +0000, Bhushan Bharat-R65777 wrote:
> PFA file which have full dmeg and lspci of assigned device

> On Aug 29, 2012 11:03 AM, "Bhushan Bharat-R65777" <R65777@freescale.com<mailto:R65777@freescale.com>> wrote:
> > Guest>lspci
> > 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
> > 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
> > 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
> > 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
> > 00:02.0 VGA compatible controller: Cirrus Logic GD 5446
> > 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03)  ----- QEMU emulated
> > 00:04.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)   ----- directly assigned

>From attachment:

00:04.0 Ethernet controller: SysKonnect SK-9E21D 10/100/1000Base-T Adapter, Copper RJ-45 (rev 17)
	Subsystem: SysKonnect SK-9E21D 10/100/1000Base-T Adapter
	Physical Slot: 4
	Flags: fast devsel, IRQ 11
	Memory at febf0000 (64-bit, non-prefetchable) [size=16K]
	I/O ports at c000 [size=256]
	Expansion ROM at febc0000 [disabled] [size=128K]
	Capabilities: [48] Power Management version 2
	Capabilities: [50] Vital Product Data
	Capabilities: [5c] MSI: Enable- Count=1/2 Maskable- 64bit+
	Capabilities: [e0] Express Legacy Endpoint, MSI 00

This isn't the 82567LM device reported previously, are we now switching
to this device being assigned?  I don't know what driver this device is
supposed to use nor do I see any attempt to load a driver for this
device in the guest dmesg.  Are you sure the driver is loaded?  Thanks,

Alex