Hi Folks :
I am trying to assinga bcm netextreme II 10 G eth device to a guest using
PCI passthrough in QEMU.
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711
10-Gigabit PCIe
01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711
10-Gigabit PCIe
qemu> d
Hi Folks :
I am trying to write a virtio driver and towards this end I am looking at
the qemu code. I am a little confused about a few things. Unfortunately,
the few comments in the code does not make it clear for me. So I am
wondering if any kind person on this mailing list would be able to help.
ue Swirl wrote:
>> On Fri, Sep 2, 2011 at 6:08 AM, Sinha, Ani wrote:
>>> First off, what is the difference between target_phys_addr_t and
>>> ram_addr_t? I believe the former is a virtual address within the guest but
>>> what is the later? The comment says "addre
Hey guys,
So I am writing a virtIO driver for a device that supports blocking calls like
poll() etc. Now the front end paravirtualized driver mirrors the request to the
backend "host" qemu process that then does the actual call on the host kernel
on behalf of the guest. Now my question is, when
On Sep 11, 2011, at 6:34 AM, Stefan Hajnoczi wrote:
> On Fri, Sep 09, 2011 at 07:45:17PM -0500, Sinha, Ani wrote:
>> So I am writing a virtIO driver for a device that supports blocking calls
>> like poll() etc. Now the front end paravirtualized driver mirrors the
>> r
On Sep 11, 2011, at 6:34 AM, Stefan Hajnoczi wrote:
>
> You may find these posts I wrote helpful, they explain vcpu threads and
> the I/O thread:
> http://blog.vmsplice.net/2011/03/qemu-internals-big-picture-overview.html
> http://blog.vmsplice.net/2011/03/qemu-internals-overall-architecture-and.
>>
>> We are trying to paravirtualize the IPMI device (/dev/ipmi0).
>
> From http://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface:
> "An implementation of IPMI version 1.5 can communicate via a direct
> serial connection or via a side-band local area network (LAN)
> connection to
On Sep 15, 2011, at 4:42 AM, Stefan Hajnoczi wrote:
> On Tue, Sep 13, 2011 at 6:35 PM, Sinha, Ani wrote:
>> Makes sense?
>
> I'm still not sure what the point of multiplexing host IPMI into
> guests is. The guest should not be able to power off the host. It
> shou
Hi Guys :
I am using the virtqueue (virtqueue_pop, virtqueue_push etc) in the emulated
mode (non-kvm mode) from an IO thread (a separate thread different from main
QEMU thread). What I am observing is that the virtqueue memory seems to get
corrupt. Either qemu crashes while performing virtqueue
On Sep 27, 2011, at 12:17 AM, Stefan Hajnoczi wrote:
> On Mon, Sep 26, 2011 at 07:16:56PM -0500, Sinha, Ani wrote:
>> I am using the virtqueue (virtqueue_pop, virtqueue_push etc) in the emulated
>> mode (non-kvm mode) from an IO thread (a separate thread different from main
On Sep 28, 2011, at 1:51 AM, Stefan Hajnoczi wrote:
> On Wed, Sep 28, 2011 at 3:01 AM, Sinha, Ani wrote:
>>
>> On Sep 27, 2011, at 12:17 AM, Stefan Hajnoczi wrote:
>>
>>> On Mon, Sep 26, 2011 at 07:16:56PM -0500, Sinha, Ani wrote:
>>>> I am using the vi
On Sep 28, 2011, at 9:47 AM, Stefan Hajnoczi wrote:
I need a helper thread to do blocking IO. The device IOCTLS are inherently
blocking, unfortunately.
posix-aio-compat.c already implements a threadpool. It is geared
towards using the QEMU block layer (BlockDriverState) but the pure
ioctl code
12 matches
Mail list logo
