Bug 958936
| Summary: | Kernel crashes when running KVM using macvtap driver in bridge mode | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dawid Zamirski <dzrudy> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 19 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-05-08 17:54:12 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 954181 *** |
Created attachment 742829 [details] The photo of the kernel crash. Description of problem: My Windows virtual machine crashes shortly after boot if the NIC in Virt Manager is set to use macvtap driver in bridge mode. The crash brings down the host PC with kernel oops message. Version-Release number of selected component (if applicable): kernel-3.9.0-301.fc19.x86_64 (also happened using earlier versions) qemu-common.x86_64 2:1.4.1-1.fc19 @updates-testing qemu-guest-agent.x86_64 2:1.4.1-1.fc19 @updates-testing qemu-img.x86_64 2:1.4.1-1.fc19 @updates-testing qemu-kvm.x86_64 2:1.4.1-1.fc19 @updates-testing qemu-system-x86.x86_64 virt-manager-0.10.0-0.1.gitd3f9bc8e.fc19.noarch Steps to Reproduce: 1. Setup the VM to use NIC in bridge mode using macvtap driver 2. Start the VM and wait a few minutes 3. Host system will crash Expected results: Should run just fine as it did in Fedora 18 Additional info: Attaching a photo of the kernel oops message as I could not find it in the logs after hard reboot.