[Qemu-devel] MSI support for e1000 Qemu in 0.13.0

I am trying to enable MSI interrupts in em driver on freebsd guest OS, using Qemu e1000 emulation in 0.13.0, but it does not seem to work. After adding MSI support in driver, pci_msi_count() returns 0, which means probably e1000 does not support it in 0.13.0? How can I make e1000 device (or

[Qemu-devel] SMBIOS support in Qemu?

Hi, Which version of Qemu contains the Smbios code? If I have to get the code in my repo, is there any place I can get the complete set of patches? Thanks Anjali

[Qemu-devel] SMBIOS support in Qemu?

Hi, Which version of Qemu contains the Smbios code? If I have to get the code in my repo, is there any place I can get the complete set of patches? Thanks Anjali

[Qemu-devel] Passing in additional info to guest OS and e1000 test suite?

Hi, - If I want to pass in additional arguments to the guest OS while booting(in particular which slot I want to map a nic to) - is there any way to do it? Some kind of configuration file that I can pass in would also be ok for me. - Is there a KVM/Qemu/e1000 test suite that is already available

Re: [Qemu-devel] Hitting 29 NIC limit

Can you send me pointers to the qdev documentation? How can I use it? Will it allow us to scale above the 32 PCI limit? Anjali On 10/14/10 2:57 PM, Anthony Liguori anth...@codemonkey.ws wrote: On 10/14/2010 04:42 PM, Richard W.M. Jones wrote: On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel

Re: [Qemu-devel] Hitting 29 NIC limit

Thanks. Does this work for e1000 as well? Also, does it support pci hotplug? Anjali On 10/14/10 3:09 PM, Anthony Liguori anth...@codemonkey.ws wrote: On 10/14/2010 05:00 PM, Anjali Kulkarni wrote: Can you send me pointers to the qdev documentation? How can I use it? Will it allow us to scale

[Qemu-devel] Hitting 29 NIC limit (was Re: 8 NIC limit - patch - places limit at 32)

Hi, Using the legacy way of starting up NICs, I am hitting a limitation after 29 NICs ie no more than 29 are detected (that's because of the 32 PCI slot limit on a single bus- 3 are already taken up) I had initially increased the MAX_NICS to 48, just on my tree, to get to more, but ofcource that

[Qemu-devel] Hitting 29 NIC limit

Hi, Using the legacy way of starting up NICs, I am hitting a limitation after 29 NICs ie no more than 29 are detected (that's because of the 32 PCI slot limit on a single bus- 3 are already taken up) I had initially increased the MAX_NICS to 48, just on my tree, to get to more, but ofcource

[Qemu-devel] Question about using multiple Qemu emulation devices/NICs at one time

Hi, Has anyone tried to use many Qemu devices/NICs at one time with the same guest? Ie let the guest think it has say 3 or 4 virtual NICs? I see that after about 2, it seems to be a little unstable - I got a em0 watchdog timeout once. So, I wanted to know is there any known issue with having

[Qemu-devel] Question about e1000 NIC emulation in Qemu - chipset used

Hi, I am using Qemu for emulation of my virtual e1000 NIC, and my driver for the e1000 is a modified version of 82547EI. (Modified because it is userspace and plugs into other modules - but the device access specific parts are not modified). I wanted to know which chipset exactly does Qemu

[Qemu-devel] Question about starting 2 VMs using Qemu

Hi, I can start my freebsd based image in Qemu, and I use tap interface for connectivity to the host or external world, but when I try to fire up 2 instances, using tap, it fails. For the second invocation, it gives me the error: [r...@ipg-virt01 tmp]# ./qemu-system-x86_64 -m 512 anjali.img -net

[Qemu-devel] Question about mmap from user space and accessing emulated device bar0 contents

Hi, I am not sure if this is the right forum for my questions - I am using Qemu+KVM on centOS to run my freebsd based virtual OS. The Qemu emulates one of my nics - yukon -II 88E8022 chip. Now, my yukon driver exists in kernel as well as user space(and I will use the one which I want based on