All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2847560 ] Guest hang with exhausted IRQ sources error if 8 VFs assigne
Date: Mon, 31 Aug 2009 05:58:07 +0000	[thread overview]
Message-ID: <E1Mhzu3-0007x8-7z@3bkjzd1.ch3.sourceforge.com> (raw)

Bugs item #2847560, was opened at 2009-08-30 22:58
Message generated for change (Tracker Item Submitted) made by jiajun
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2847560&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: kernel
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jiajun Xu (jiajun)
Assigned to: Nobody/Anonymous (nobody)
Summary: Guest hang with exhausted IRQ sources error if 8 VFs assigne

Initial Comment:
Environment:
------------
Host OS (ia32/ia32e/IA64): ia32e
Guest OS (ia32/ia32e/IA64): ia32e 
Guest OS Type (Linux/Windows): Linux
kvm.git Commit: 779cc54dbccaa3a00d70a9d61d090be5d9ccc903
qemu-kvm Commit: 9e3269181e9bc56feb43bcd4e8ce0b82cd543e65
Host Kernel Version: 2.6.31-rc5
Hardware: NHM-EP


Bug detailed description:
--------------------------
If boot a guest with 8 VFs assigned, guest will hang at stage of "Starting
udev:". And dmesg will shows that "kvm: exhaust allocatable IRQ sources!"

If boot a guest with 6 VFs assigned, guest can boot up and VF can work well in
guest.

Dmesg info:
########
pci-stub 0000:01:10.0: enabling device (0000 -> 0002)
assign device: host bdf = 1:10:0
pci-stub 0000:01:10.1: enabling device (0000 -> 0002)
assign device: host bdf = 1:10:1
pci-stub 0000:01:10.2: enabling device (0000 -> 0002)
assign device: host bdf = 1:10:2
pci-stub 0000:01:10.3: enabling device (0000 -> 0002)
assign device: host bdf = 1:10:3
pci-stub 0000:01:10.4: enabling device (0000 -> 0002)
assign device: host bdf = 1:10:4
pci-stub 0000:01:10.5: enabling device (0000 -> 0002)
assign device: host bdf = 1:10:5
pci-stub 0000:01:10.6: enabling device (0000 -> 0002)
assign device: host bdf = 1:10:6
pci-stub 0000:01:10.7: enabling device (0000 -> 0002)
assign device: host bdf = 1:10:7
pci-stub 0000:01:10.0: irq 91 for MSI/MSI-X
pci-stub 0000:01:10.0: irq 92 for MSI/MSI-X
pci-stub 0000:01:10.0: irq 93 for MSI/MSI-X
pci-stub 0000:01:10.1: irq 97 for MSI/MSI-X
pci-stub 0000:01:10.1: irq 98 for MSI/MSI-X
pci-stub 0000:01:10.1: irq 99 for MSI/MSI-X
pci-stub 0000:01:10.2: irq 100 for MSI/MSI-X
pci-stub 0000:01:10.2: irq 101 for MSI/MSI-X
pci-stub 0000:01:10.2: irq 102 for MSI/MSI-X
pci-stub 0000:01:10.3: irq 103 for MSI/MSI-X
pci-stub 0000:01:10.3: irq 104 for MSI/MSI-X
pci-stub 0000:01:10.3: irq 105 for MSI/MSI-X
pci-stub 0000:01:10.4: irq 106 for MSI/MSI-X
pci-stub 0000:01:10.4: irq 107 for MSI/MSI-X
pci-stub 0000:01:10.4: irq 108 for MSI/MSI-X
pci-stub 0000:01:10.5: irq 112 for MSI/MSI-X
pci-stub 0000:01:10.5: irq 113 for MSI/MSI-X
pci-stub 0000:01:10.5: irq 114 for MSI/MSI-X
pci-stub 0000:01:10.6: irq 115 for MSI/MSI-X
pci-stub 0000:01:10.6: irq 116 for MSI/MSI-X
pci-stub 0000:01:10.6: irq 117 for MSI/MSI-X
kvm: exhaust allocatable IRQ sources!
########

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2847560&group_id=180599

             reply	other threads:[~2009-08-31  5:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31  5:58 SourceForge.net [this message]
2009-11-09  6:00 [ kvm-Bugs-2847560 ] Guest hang with exhausted IRQ sources error if 8 VFs assigne SourceForge.net

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=E1Mhzu3-0007x8-7z@3bkjzd1.ch3.sourceforge.com \
    --to=noreply@sourceforge.net \
    /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.