qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: ChangLimin <changlm@chinatelecom.cn>
To: "Sean Kuo" <gcf1129@gmail.com>,
	 "Bug 1917394" <1917394@bugs.launchpad.net>,
	 qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Bug 1917394] [NEW] command lspci does not show the IVSHMEM device
Date: Tue, 2 Mar 2021 15:30:53 +0800	[thread overview]
Message-ID: <2021030215305283912052@chinatelecom.cn> (raw)
In-Reply-To: 161465544550.24578.14846009621606228644.malonedeb@wampee.canonical.com

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

Can you give the lspci messages? The below is my output.  There is a RAM memory device.

$ lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 VGA compatible controller: Device 1234:1111 (rev 02)
00:03.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge
00:04.0 Ethernet controller: Red Hat, Inc. Virtio network device
00:05.0 SCSI storage controller: Red Hat, Inc. Virtio SCSI
00:06.0 Communication controller: Red Hat, Inc. Virtio console
00:10.0 RAM memory: Red Hat, Inc. Inter-VM shared memory (rev 01)
01:07.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge

 
From: sean kuo
Date: 2021-03-02 11:24
To: qemu-devel
Subject: [Bug 1917394] [NEW] command lspci does not show the IVSHMEM device
Public bug reported:
 
qeum version:
QEMU emulator version 4.2.1
 
I met a problem when I tried to use IVSHMEM. Command lspci does not show the IVSHMEM device.
Below is the configuration from my side:
 
1.  guest vm xml configuration.
  <shmem name='ivshmem'>
      <model type='ivshmem-plain'/>
      <size unit='M'>2</size>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x10' function='0x0'/>
    </shmem>
 
2. after the booting up and I found the qemu commandline ideedly  have the device option:
ps aux | grep ivshmem
/usr/bin/qemu-system-x86_64 
      .......(ignore other options)
-object memory-backend-file,id=shmmem-shmem0,mem-path=/dev/shm/hostmem,size=4194304,share=yes -device ivshmem-plain,id=shmem0,memdev=shmmem-shmem0,bus=pcie.0,addr=0x10
 
3. lspci command  not shown the device.
 
4. lshw command indeedly show the device:
 
*-memory UNCLAIMED
             description: RAM memory
             product: Inter-VM shared memory
             vendor: Red Hat, Inc.
             physical id: 10
             bus info: pci@0000:00:10.0
             version: 01
             width: 64 bits
             clock: 33MHz (30.3ns)
             configuration: latency=0
             resources: memory:fcc1c000-fcc1c0ff memory:fdc00000-fdffffff
 
My host and vm os is ubuntu 20.04 and version is:
#49~20.04.1-Ubuntu SMP Fri Feb 5 09:57:56 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
 
** Affects: qemu
     Importance: Undecided
         Status: New
 
-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1917394
 
Title:
  command lspci does not show the IVSHMEM device
 
Status in QEMU:
  New
 
Bug description:
  qeum version:
  QEMU emulator version 4.2.1
 
  I met a problem when I tried to use IVSHMEM. Command lspci does not show the IVSHMEM device.
  Below is the configuration from my side:
 
  1.  guest vm xml configuration.
    <shmem name='ivshmem'>
        <model type='ivshmem-plain'/>
        <size unit='M'>2</size>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x10' function='0x0'/>
      </shmem>
 
  2. after the booting up and I found the qemu commandline ideedly  have the device option:
  ps aux | grep ivshmem
   /usr/bin/qemu-system-x86_64 
        .......(ignore other options)
  -object memory-backend-file,id=shmmem-shmem0,mem-path=/dev/shm/hostmem,size=4194304,share=yes -device ivshmem-plain,id=shmem0,memdev=shmmem-shmem0,bus=pcie.0,addr=0x10
 
  3. lspci command  not shown the device.
 
  4. lshw command indeedly show the device:
 
  *-memory UNCLAIMED
               description: RAM memory
               product: Inter-VM shared memory
               vendor: Red Hat, Inc.
               physical id: 10
               bus info: pci@0000:00:10.0
               version: 01
               width: 64 bits
               clock: 33MHz (30.3ns)
               configuration: latency=0
               resources: memory:fcc1c000-fcc1c0ff memory:fdc00000-fdffffff
 
  My host and vm os is ubuntu 20.04 and version is:
  #49~20.04.1-Ubuntu SMP Fri Feb 5 09:57:56 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
 
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1917394/+subscriptions
 

[-- Attachment #2: Type: text/html, Size: 8728 bytes --]

  reply	other threads:[~2021-03-02  7:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  3:24 [Bug 1917394] [NEW] command lspci does not show the IVSHMEM device sean kuo
2021-03-02  7:30 ` ChangLimin [this message]
2021-03-02  7:59   ` Sean Kuo
2021-03-02  7:59     ` sean kuo
2021-03-02  8:15     ` ChangLimin
2021-03-02  8:22       ` Sean Kuo
2021-03-02  8:22         ` sean kuo
2021-05-13 11:57 ` [Bug 1917394] " Thomas Huth

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=2021030215305283912052@chinatelecom.cn \
    --to=changlm@chinatelecom.cn \
    --cc=1917394@bugs.launchpad.net \
    --cc=gcf1129@gmail.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).