All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Bareiro <daniel-listas@gmx.net>
To: KVM General <kvm@vger.kernel.org>
Subject: Re: PCI-passthrough on AMD - OpenVox A400P
Date: Sun, 14 Apr 2013 13:16:30 -0300	[thread overview]
Message-ID: <20130414161630.GA11937@defiant.freesoftware> (raw)
In-Reply-To: <1365530785.16420.155.camel@bling.home>

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

On Tuesday, 09 April 2013 12:06:25 -0600,
Alex Williamson wrote:

> > I've a cluster (active/passive) with two KVM VM with Asterisk and
> > Pacemaker+Corosync. I wonder if anyone tried to use a OpenVox A400P
> > card from a virtual machine.
> > 
> > My idea is to have both nodes accessing this card. I don't know if
> > it is possible, I wish that in this scenario when a node is
> > accessing the card, the other don't use it.
> > 
> > Of course this is a scenario for testing, but I wonder if I can do
> > this kind of configuration on the cluster over virtual machines.
> > 
> > Hardware:
> > Motherboard: ASUS M2N32-SLI DELUXE ACPI BIOS Revision 0706
> > Processor:   AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
> > 
> > The hardware seems to support IOMMU, but it is not enabled:
> > 
> > # dmesg | grep -i iommu
> > [    0.000000] Please enable the IOMMU option in the BIOS setup
> > [    0.654618] PCI-DMA: using GART IOMMU.
> > [    0.654623] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
> > 
> > 
> > Software versions:
> > 
> > # uname -a
> > Linux ss01 2.6.39-bpo.2-amd64 #1 SMP Thu Aug 4 11:42:06 UTC 2011 x86_64 GNU/Linux
> > 
> > # kvm --version
> > QEMU emulator version 1.1.2 (qemu-kvm-1.1.2+dfsg-5~bpo60+1, Debian), Copyright (c) 2003-2008 Fabrice Bellard

Hi, Alex.

 
> AFAIK, Athlon64 does not support AMD-Vi, which is the IOMMU support
> you'd need.

I will investigate this issue and then tell you.

> PCI passthrough also only works for VMs running on the same system
> where the card is installed, and doesn't offer multiplexing of a
> single device.  Thanks,

The two cluster nodes are running on the same host. On the issue of
multiplexing, was mostly a curiosity. For testing, I do not care to have
to manually link and unlink the PCI device.


Moreover, is having a problem with the mailing list? For some time I did
not write and since I was not receiving emails from October last year, I
signed up again with the same account that I was using before; but since
9 April that I do not receive emails from the list.

Interestingly I got your reply but did not get the email I sent to the
list. Today I wrote an email to the Pacemaker list with the same account
I used to sign up here, and I received it with no problems.


Thanks for your reply.


Regards,
Daniel
-- 
Daniel Bareiro - System Administrator
Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Squeeze - Linux user #188.598

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2013-04-14 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 17:58 PCI-passthrough on AMD - OpenVox A400P Daniel Bareiro
2013-04-09 18:06 ` Alex Williamson
2013-04-14 16:16   ` Daniel Bareiro [this message]
2013-04-14 18:08     ` Daniel Bareiro

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=20130414161630.GA11937@defiant.freesoftware \
    --to=daniel-listas@gmx.net \
    --cc=dbareiro@gmx.net \
    --cc=kvm@vger.kernel.org \
    /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.