unable to assign devices with VT-d in KVM

unable to assign devices with VT-d in KVM

[Erez Shitrit]

Hi,
I am KVM newbie, trying to run and use the KVM.
When I tried to assign pci device to new virtual machine I got the next
error:
 
/usr/local/bin/qemu-system-x86_64: invalid option -- '-pcidevice'

I followed the instructions in the
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
page,
I am using RH5_4 with the new kernel for rh5.5: 2.6.18-prep (2.6.18.197)
I run the next command
/usr/local/bin/qemu-system-x86_64 -m 512 -boot c -net none -hda
/sdb5/images/test2.img -pcidevice host=04:00.0

And I got 

/usr/local/bin/qemu-system-x86_64: invalid option -- '-pcidevice'


The qemu-system-x86_64 version is:
	QEMU PC emulator version 0.11.91, Copyright (c) 2003-2008
Fabrice Bellard

What I missed?

Thanks, Erez

Re: unable to assign devices with VT-d in KVM

[Thomas Mueller]

> 
> 
> The qemu-system-x86_64 version is:
> 	QEMU PC emulator version 0.11.91, Copyright (c) 2003-2008
> Fabrice Bellard

there should be somewhere "kvm" or "qemu-kvm" in it. 


my version looks like that:
QEMU PC emulator version 0.11.0 (qemu-kvm-0.11.0), Copyright (c) 
2003-2008 Fabrice Bellard


looks like you're using plain qemu.


- Thomas

Re: unable to assign devices with VT-d in KVM

[Avi Kivity]

On 12/27/2009 12:07 PM, Erez Shitrit wrote:
> Hi,
> I am KVM newbie, trying to run and use the KVM.
> When I tried to assign pci device to new virtual machine I got the next
> error:
>
> /usr/local/bin/qemu-system-x86_64: invalid option -- '-pcidevice'
>
> I followed the instructions in the
> http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
> page,
> I am using RH5_4 with the new kernel for rh5.5: 2.6.18-prep (2.6.18.197)
> I run the next command
> /usr/local/bin/qemu-system-x86_64 -m 512 -boot c -net none -hda
> /sdb5/images/test2.img -pcidevice host=04:00.0
>
> And I got
>
> /usr/local/bin/qemu-system-x86_64: invalid option -- '-pcidevice'
>
>
> The qemu-system-x86_64 version is:
> 	QEMU PC emulator version 0.11.91, Copyright (c) 2003-2008
> Fabrice Bellard
>
> What I missed?
>
>    

You're running the upstream qemu, which doesn't support device assignment.

Download qemu-kvm-0.12.1.1 from http://linux-kvm.org.

-- 
error compiling committee.c: too many arguments to function

RE: unable to assign devices with VT-d in KVM

[Erez Shitrit]

Thanks,
Now, it seams that I have a problem with the kvm, whenever I tried to
create a new virtual machine and the kvm module is loaded I got kernel
panic in the virtual machine.

The panic:

" ...
Code: 0f 30 b8 76 00 13 00 89 d9 0f 30 48 c7 c6 17 41 2a 80 89 fa
RIP [<ffffffff8007d43d>] setup_k7_watchdog+0x2d/0x7a
RSP <ffff81003ffb7e50>
<0>Kernel panic - not syncing: Fatal exception
...
"

(If I remove the kvm module it works)

The kvm version:
kvm-83-105.el5_4.13

The KVM did not arrived with the RH5.4 distribution, I installed it
manually.
>From the package: kvm-83-105.el5_4.13.x86_64.rpm

Do I need specific version of the kvm with that qemu ?

Thanks again, Erez
  

-----Original Message-----
From: Avi Kivity [mailto:avi@redhat.com] 
Sent: Sunday, December 27, 2009 1:10 PM
To: Erez Shitrit
Cc: kvm@vger.kernel.org
Subject: Re: unable to assign devices with VT-d in KVM

On 12/27/2009 12:07 PM, Erez Shitrit wrote:
> Hi,
> I am KVM newbie, trying to run and use the KVM.
> When I tried to assign pci device to new virtual machine I got the 
> next
> error:
>
> /usr/local/bin/qemu-system-x86_64: invalid option -- '-pcidevice'
>
> I followed the instructions in the
> http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
> page,
> I am using RH5_4 with the new kernel for rh5.5: 2.6.18-prep 
> (2.6.18.197) I run the next command
> /usr/local/bin/qemu-system-x86_64 -m 512 -boot c -net none -hda 
> /sdb5/images/test2.img -pcidevice host=04:00.0
>
> And I got
>
> /usr/local/bin/qemu-system-x86_64: invalid option -- '-pcidevice'
>
>
> The qemu-system-x86_64 version is:
> 	QEMU PC emulator version 0.11.91, Copyright (c) 2003-2008
Fabrice 
> Bellard
>
> What I missed?
>
>    

You're running the upstream qemu, which doesn't support device
assignment.

Download qemu-kvm-0.12.1.1 from http://linux-kvm.org.

--
error compiling committee.c: too many arguments to function

Re: unable to assign devices with VT-d in KVM

[Avi Kivity]

On 12/27/2009 03:09 PM, Erez Shitrit wrote:
> Thanks,
> Now, it seams that I have a problem with the kvm, whenever I tried to
> create a new virtual machine and the kvm module is loaded I got kernel
> panic in the virtual machine.
>
> The panic:
>
> " ...
> Code: 0f 30 b8 76 00 13 00 89 d9 0f 30 48 c7 c6 17 41 2a 80 89 fa
> RIP [<ffffffff8007d43d>] setup_k7_watchdog+0x2d/0x7a
> RSP<ffff81003ffb7e50>
> <0>Kernel panic - not syncing: Fatal exception
> ...
> "
>
> (If I remove the kvm module it works)
>
> The kvm version:
> kvm-83-105.el5_4.13
>
> The KVM did not arrived with the RH5.4 distribution, I installed it
> manually.
>  From the package: kvm-83-105.el5_4.13.x86_64.rpm
>
> Do I need specific version of the kvm with that qemu ?
>
>    

What guest kernel are you running?  What qemu command line?

Looks like your guest thinks it's running on an Athlon.  What's your 
host cpu type?

-- 
error compiling committee.c: too many arguments to function

RE: unable to assign devices with VT-d in KVM

[Erez Shitrit]

The qemu commandline is:
	/usr/local/bin/qemu-system-x86_64 -m 1024 -boot c -net none -hda
/sdb5/images/test2.img        
The guest kernel is rh5.4
The cpu type is: 
	Intel(R) Xeon(R) CPU           X5550  @ 2.67GHz
With VT-d enabled.

I loaded kvm and kvm-intel

[root@sw379 2.6.18-179-prep]# lsmod | grep kvm
kvm_intel              86248  0
kvm                   223520  1 kvm_intel

Thanks, Erez

-----Original Message-----
From: Avi Kivity [mailto:avi@redhat.com] 
Sent: Sunday, December 27, 2009 3:37 PM
To: Erez Shitrit
Cc: kvm@vger.kernel.org
Subject: Re: unable to assign devices with VT-d in KVM

On 12/27/2009 03:09 PM, Erez Shitrit wrote:
> Thanks,
> Now, it seams that I have a problem with the kvm, whenever I tried to 
> create a new virtual machine and the kvm module is loaded I got kernel

> panic in the virtual machine.
>
> The panic:
>
> " ...
> Code: 0f 30 b8 76 00 13 00 89 d9 0f 30 48 c7 c6 17 41 2a 80 89 fa RIP 
> [<ffffffff8007d43d>] setup_k7_watchdog+0x2d/0x7a RSP<ffff81003ffb7e50>

> <0>Kernel panic - not syncing: Fatal exception ...
> "
>
> (If I remove the kvm module it works)
>
> The kvm version:
> kvm-83-105.el5_4.13
>
> The KVM did not arrived with the RH5.4 distribution, I installed it 
> manually.
>  From the package: kvm-83-105.el5_4.13.x86_64.rpm
>
> Do I need specific version of the kvm with that qemu ?
>
>    

What guest kernel are you running?  What qemu command line?

Looks like your guest thinks it's running on an Athlon.  What's your
host cpu type?

--
error compiling committee.c: too many arguments to function

Re: unable to assign devices with VT-d in KVM

[Avi Kivity]

On 12/27/2009 03:48 PM, Erez Shitrit wrote:
> The qemu commandline is:
> 	/usr/local/bin/qemu-system-x86_64 -m 1024 -boot c -net none -hda
> /sdb5/images/test2.img
> The guest kernel is rh5.4
> The cpu type is:
> 	Intel(R) Xeon(R) CPU           X5550  @ 2.67GHz
> With VT-d enabled.
>
> I loaded kvm and kvm-intel
>
> [root@sw379 2.6.18-179-prep]# lsmod | grep kvm
> kvm_intel              86248  0
> kvm                   223520  1 kvm_intel
>    

Can you try adding -cpu qemu64,vendorid=GenuineIntel?

Also try not top-posting.

-- 
error compiling committee.c: too many arguments to function

Re: unable to assign devices with VT-d in KVM

[Avi Kivity]

On 12/27/2009 03:51 PM, Avi Kivity wrote:
>
> Can you try adding -cpu qemu64,vendorid=GenuineIntel?
>

Sorry, the correct option is -cpu qemu64,vendor=GenuineIntel.

-- 
error compiling committee.c: too many arguments to function

RE: unable to assign devices with VT-d in KVM

[Erez Shitrit]

[I hope I didn't duplicate my response]
I tried it, still have kernel-panic,
Currently the message is:
"
....
MP-BIOS bug: 8254 timer not connected to IO-APIC
Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the
'noapic' kernel parameter
"

Thanks, Erez  

-----Original Message-----
From: Avi Kivity [mailto:avi@redhat.com] 
Sent: Sunday, December 27, 2009 4:36 PM
To: Erez Shitrit
Cc: kvm@vger.kernel.org
Subject: Re: unable to assign devices with VT-d in KVM

On 12/27/2009 03:51 PM, Avi Kivity wrote:
>
> Can you try adding -cpu qemu64,vendorid=GenuineIntel?
>

Sorry, the correct option is -cpu qemu64,vendor=GenuineIntel.

--
error compiling committee.c: too many arguments to function

Re: unable to assign devices with VT-d in KVM

[Sheng Yang]

On Monday 28 December 2009 00:42:37 Erez Shitrit wrote:
> [I hope I didn't duplicate my response]
> I tried it, still have kernel-panic,
> Currently the message is:
> "
> ....
> MP-BIOS bug: 8254 timer not connected to IO-APIC
> Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the
> 'noapic' kernel parameter
> "

It's seems due to timer interrupt injection delayed.

Though I hit this sometime, it's not always happen. 

What's your guest kernel version?

This panic is quite annoying, I think we should try to fix this...

-- 
regards
Yang, Sheng

> 
> Thanks, Erez
> 
> -----Original Message-----
> From: Avi Kivity [mailto:avi@redhat.com]
> Sent: Sunday, December 27, 2009 4:36 PM
> To: Erez Shitrit
> Cc: kvm@vger.kernel.org
> Subject: Re: unable to assign devices with VT-d in KVM
> 
> On 12/27/2009 03:51 PM, Avi Kivity wrote:
> > Can you try adding -cpu qemu64,vendorid=GenuineIntel?
> 
> Sorry, the correct option is -cpu qemu64,vendor=GenuineIntel.
> 
> --
> error compiling committee.c: too many arguments to function
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: unable to assign devices with VT-d in KVM

[Sheng Yang]

On Monday 28 December 2009 00:42:37 Erez Shitrit wrote:
> [I hope I didn't duplicate my response]
> I tried it, still have kernel-panic,
> Currently the message is:
> "
> ....
> MP-BIOS bug: 8254 timer not connected to IO-APIC
> Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the
> 'noapic' kernel parameter
> "

BTW, maybe you give --no-hpet a try in qemu command line.

-- 
regards
Yang, Sheng

> 
> Thanks, Erez
> 
> -----Original Message-----
> From: Avi Kivity [mailto:avi@redhat.com]
> Sent: Sunday, December 27, 2009 4:36 PM
> To: Erez Shitrit
> Cc: kvm@vger.kernel.org
> Subject: Re: unable to assign devices with VT-d in KVM
> 
> On 12/27/2009 03:51 PM, Avi Kivity wrote:
> > Can you try adding -cpu qemu64,vendorid=GenuineIntel?
> 
> Sorry, the correct option is -cpu qemu64,vendor=GenuineIntel.
> 
> --
> error compiling committee.c: too many arguments to function
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

RE: unable to assign devices with VT-d in KVM

[Erez Shitrit]

I tried it also, the same result :( 

Any idea? 

Thanks, Erez
-----Original Message-----
From: Sheng Yang [mailto:sheng@linux.intel.com] 
Sent: Tuesday, December 29, 2009 7:30 AM
To: kvm@vger.kernel.org
Cc: Erez Shitrit; Avi Kivity
Subject: Re: unable to assign devices with VT-d in KVM

On Monday 28 December 2009 00:42:37 Erez Shitrit wrote:
> [I hope I didn't duplicate my response] I tried it, still have 
> kernel-panic, Currently the message is:
> "
> ....
> MP-BIOS bug: 8254 timer not connected to IO-APIC Kernel panic - not 
> syncing: IO-APIC + timer doesn't work! Try using the 'noapic' kernel 
> parameter "

BTW, maybe you give --no-hpet a try in qemu command line.

--
regards
Yang, Sheng

> 
> Thanks, Erez
> 
> -----Original Message-----
> From: Avi Kivity [mailto:avi@redhat.com]
> Sent: Sunday, December 27, 2009 4:36 PM
> To: Erez Shitrit
> Cc: kvm@vger.kernel.org
> Subject: Re: unable to assign devices with VT-d in KVM
> 
> On 12/27/2009 03:51 PM, Avi Kivity wrote:
> > Can you try adding -cpu qemu64,vendorid=GenuineIntel?
> 
> Sorry, the correct option is -cpu qemu64,vendor=GenuineIntel.
> 
> --
> error compiling committee.c: too many arguments to function
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in the 
> body of a message to majordomo@vger.kernel.org More majordomo info at

> http://vger.kernel.org/majordomo-info.html
> 

Re: unable to assign devices with VT-d in KVM

[Sheng Yang]

On Wednesday 30 December 2009 00:10:42 Erez Shitrit wrote:
> I tried it also, the same result :(
> 
> Any idea?

What's your guest kernel version? I'd like to reproduce it.

-- 
regards
Yang, Sheng

> 
> Thanks, Erez
> -----Original Message-----
> From: Sheng Yang [mailto:sheng@linux.intel.com]
> Sent: Tuesday, December 29, 2009 7:30 AM
> To: kvm@vger.kernel.org
> Cc: Erez Shitrit; Avi Kivity
> Subject: Re: unable to assign devices with VT-d in KVM
> 
> On Monday 28 December 2009 00:42:37 Erez Shitrit wrote:
> > [I hope I didn't duplicate my response] I tried it, still have
> > kernel-panic, Currently the message is:
> > "
> > ....
> > MP-BIOS bug: 8254 timer not connected to IO-APIC Kernel panic - not
> > syncing: IO-APIC + timer doesn't work! Try using the 'noapic' kernel
> > parameter "
> 
> BTW, maybe you give --no-hpet a try in qemu command line.
> 
> --
> regards
> Yang, Sheng
> 
> > Thanks, Erez
> >
> > -----Original Message-----
> > From: Avi Kivity [mailto:avi@redhat.com]
> > Sent: Sunday, December 27, 2009 4:36 PM
> > To: Erez Shitrit
> > Cc: kvm@vger.kernel.org
> > Subject: Re: unable to assign devices with VT-d in KVM
> >
> > On 12/27/2009 03:51 PM, Avi Kivity wrote:
> > > Can you try adding -cpu qemu64,vendorid=GenuineIntel?
> >
> > Sorry, the correct option is -cpu qemu64,vendor=GenuineIntel.
> >
> > --
> > error compiling committee.c: too many arguments to function
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in the
> > body of a message to majordomo@vger.kernel.org More majordomo info at
> >
> > http://vger.kernel.org/majordomo-info.html
> 

RE: unable to assign devices with VT-d in KVM

[Erez Shitrit]

The guest is RH5.4 
The host is RH5.5 (rh version 179)

-----Original Message-----
From: Sheng Yang [mailto:sheng@linux.intel.com] 
Sent: Wednesday, December 30, 2009 3:18 AM
To: Erez Shitrit
Cc: kvm@vger.kernel.org; Avi Kivity
Subject: Re: unable to assign devices with VT-d in KVM

On Wednesday 30 December 2009 00:10:42 Erez Shitrit wrote:
> I tried it also, the same result :(
> 
> Any idea?

What's your guest kernel version? I'd like to reproduce it.

--
regards
Yang, Sheng

> 
> Thanks, Erez
> -----Original Message-----
> From: Sheng Yang [mailto:sheng@linux.intel.com]
> Sent: Tuesday, December 29, 2009 7:30 AM
> To: kvm@vger.kernel.org
> Cc: Erez Shitrit; Avi Kivity
> Subject: Re: unable to assign devices with VT-d in KVM
> 
> On Monday 28 December 2009 00:42:37 Erez Shitrit wrote:
> > [I hope I didn't duplicate my response] I tried it, still have 
> > kernel-panic, Currently the message is:
> > "
> > ....
> > MP-BIOS bug: 8254 timer not connected to IO-APIC Kernel panic - not
> > syncing: IO-APIC + timer doesn't work! Try using the 'noapic' kernel

> > parameter "
> 
> BTW, maybe you give --no-hpet a try in qemu command line.
> 
> --
> regards
> Yang, Sheng
> 
> > Thanks, Erez
> >
> > -----Original Message-----
> > From: Avi Kivity [mailto:avi@redhat.com]
> > Sent: Sunday, December 27, 2009 4:36 PM
> > To: Erez Shitrit
> > Cc: kvm@vger.kernel.org
> > Subject: Re: unable to assign devices with VT-d in KVM
> >
> > On 12/27/2009 03:51 PM, Avi Kivity wrote:
> > > Can you try adding -cpu qemu64,vendorid=GenuineIntel?
> >
> > Sorry, the correct option is -cpu qemu64,vendor=GenuineIntel.
> >
> > --
> > error compiling committee.c: too many arguments to function
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in 
> > the body of a message to majordomo@vger.kernel.org More majordomo 
> > info at
> >
> > http://vger.kernel.org/majordomo-info.html
>