Bug 912417 - KVM VM with physical device attached will not start
Summary: KVM VM with physical device attached will not start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-18 16:06 UTC by Joe
Modified: 2013-04-19 23:41 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-19 23:40:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
dmesg output (86.79 KB, application/octet-stream)
2013-02-18 16:10 UTC, Joe 		no flags Details
KVM log file (31.24 KB, application/octet-stream)
2013-02-18 16:11 UTC, Joe 		no flags Details
QEMU config file (13.71 KB, application/octet-stream)
2013-02-18 16:11 UTC, Joe 		no flags Details
lspci output (56.26 KB, application/octet-stream)
2013-02-18 16:12 UTC, Joe 		no flags Details
Grub2 config file (4.94 KB, application/octet-stream)
2013-02-18 16:12 UTC, Joe 		no flags Details
/var/log/messages file (570.91 KB, application/octet-stream)
2013-02-18 16:13 UTC, Joe 		no flags Details
VM xml file (2.95 KB, text/xml)
2013-02-18 16:14 UTC, Joe 		no flags Details
Tarball of all previous log files (137.93 KB, application/x-gzip)
2013-02-18 16:14 UTC, Joe 		no flags Details
View All

Description Joe 2013-02-18 16:06:30 UTC 
Description of problem:
A KVM that has a physical PCIe device attached to it will not start. The following error is seen the the VM's log file:
assigned_dev_register_regions: Error: Couldn't mmap 0xfe200000!


Version-Release number of selected component (if applicable):
Fedora 18
libvirt 0.10.2
QEMU 1.2.2


How reproducible:
Every time

Steps to Reproduce:
1. Create a vm using virt-manager, assign a physical device
2. Start VM
3.
  
Actual results:
VM does not start

Expected results:
VM should start


Additional info:
Hardware:
ASRock 990FX Extreme3 AM3+ /w IOMMU enabled
Comment 1 Joe 2013-02-18 16:10:32 UTC 
Created attachment 698958 [details]
dmesg output
Comment 2 Joe 2013-02-18 16:11:03 UTC 
Created attachment 698959 [details]
KVM log file
Comment 3 Joe 2013-02-18 16:11:36 UTC 
Created attachment 698960 [details]
QEMU config file
Comment 4 Joe 2013-02-18 16:12:05 UTC 
Created attachment 698961 [details]
lspci output
Comment 5 Joe 2013-02-18 16:12:44 UTC 
Created attachment 698962 [details]
Grub2 config file
Comment 6 Joe 2013-02-18 16:13:23 UTC 
Created attachment 698963 [details]
/var/log/messages file
Comment 7 Joe 2013-02-18 16:14:06 UTC 
Created attachment 698964 [details]
VM xml file
Comment 8 Joe 2013-02-18 16:14:51 UTC 
Created attachment 698965 [details]
Tarball of all previous log files
Comment 9 Cole Robinson 2013-04-01 20:28:57 UTC 
Joe, can you still reproduce with latest F18 bits, including rebooting into the latest kernel?
Comment 10 Joe 2013-04-19 23:40:54 UTC 
Appears to be fixed as of 3.6.10 kernel
Comment 11 Joe 2013-04-19 23:41:33 UTC 
(In reply to comment #10)
> Appears to be fixed as of 3.6.10 kernel

s/3.6.10/3.8.7
Note You need to log in before you can comment on or make changes to this bug.