All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Davydov <pavel.davydov@hp.com>
To: Fam Zheng <famz@redhat.com>
Cc: kvm@vger.kernel.org, Marco Vinicio Caamano Castro <marco.caamano@hp.com>
Subject: Re: Virtio IRQ problem
Date: Mon, 13 Jul 2015 10:41:42 -0600	[thread overview]
Message-ID: <55A3EA46.7040009@hp.com> (raw)
In-Reply-To: <20150712233151.GA28998@ad.nay.redhat.com>

The proprietary system doesn't have a virtio driver, that is the problem.

What are the steps that Linux performs to work correctly with virtio 
devices?

Thank you,
Pavel

On 07/12/2015 05:31 PM, Fam Zheng wrote:
> On Fri, 07/10 22:34, Pavel Davydov wrote:
>> Hello,
>>
>> I've got the following problem with KVM:
>>
>> I'm running a proprietary OS under KVM, the OS is neither Linux/Unix, nor
>> Windows, and I don't get any IRQs from Virtio device. The Virtio device in
>> the system I'm running is a PCI Ethernet device. The device is detected
>> correctly, the IRQ line is also identified, its matches with the IRQ line
>> number retrieved by running lspci command when Linux is run instead of the
>> proprietary system.
>>
>> When Linux is run on exactly the same virtual machine configuration (with
>> the Virtio device), the Virtio device is detected and works correctly, there
>> is traffic between the host and the guest.
> Linux does more than detection, you need to have drivers running in the guest
> for virtio devices.
>
> Does your proprietary system have virtio device drivers?
>
> Fam
>
>> When the only change in the configuration is that the type of the virtual
>> network interface is changed from Virtio to E1000, in both OSes: the
>> proprietary OS and Linux, the virtual network interface works correctly.
>>
>> The question is: what steps is Virtio driver to perform to enable the IRQs?
>> (Obviously, Linux driver for Virtio performs these steps, the IRQs are
>> generated under Linux VM).
>>
>> Any hint would be appreciated.
>>
>> Thank you,
>> Pavel
>> --
>> 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


  reply	other threads:[~2015-07-13 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11  4:34 Virtio IRQ problem Pavel Davydov
2015-07-12 23:31 ` Fam Zheng
2015-07-13 16:41   ` Pavel Davydov [this message]
2015-07-14  2:33     ` Fam Zheng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55A3EA46.7040009@hp.com \
    --to=pavel.davydov@hp.com \
    --cc=famz@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=marco.caamano@hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.