Bug 697811
| Summary: | Network connection crashes in virtual machine when trying to update | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Honza Horak <hhorak> |
| Component: | qemu | Assignee: | Fedora Virtualization Maintainers <virt-maint> |
| Status: | CLOSED DEFERRED | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | amit.shah, berrange, dwmw2, ehabkost, hbrock, itamar, jaswinder, jforbes, knoel, scottt.tw, tburke, virt-maint |
| 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: | 2012-05-29 00:08:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Honza Horak
2011-04-19 11:00:26 UTC
As root, please provide the output of virsh dumpxml $vmname Is any specific package being installed at when the network crash? Where exactly in the yum command do things go strange? (In reply to comment #1) > Is any specific package being installed at when the network crash? Where > exactly in the yum command do things go strange? It happens during downloading packages, but by different package every-time, not by a specific one. What's more, I've tried to reproduce this failure again on repository http://lab.rhts.englab.brq.redhat.com/distros/pub/rhel/rel-eng/latest-RHEL-5-Server/tree-x86_64/ (because the previous one exists no more) and it failed twice on one virtual machine, but succeeded on the second machine. I will attach outputs of "virsh dumpxml $vmname" of both machines in the next comment. Created attachment 513217 [details]
output of "virsh..." for the machine where I've noticed no failure
Created attachment 513218 [details]
output of "virsh..." for the machine where I've noticed two failures
(In reply to comment #2) > (because the previous one exists no more) and it failed twice on one virtual > machine, but succeeded on the second machine. I will attach outputs of "virsh > dumpxml $vmname" of both machines in the next comment. I've forgot to mention that internet connection crashed during downloading package approx. 230/480 the first time, but the "yum update" succeeded the third time (I don't remember details about the second try). It seems like the connection crashed after some time every-time, but the third attempt didn't last long enough, because many packages had been already downloaded from previous attempts -- so "yum update" finished successfully. Hmm, really not sure what could cause your network connection to just go down. Whatever it is, probably outside the scope of virt-manager or libvirt, so reassigning to qemu. Any error messages in /var/log/libvirt/qemu/$vmname.log ? (In reply to comment #6) > Any error messages in /var/log/libvirt/qemu/$vmname.log ? There is no error nor warning. Is there anything in dmesg after the guest network fails? Created attachment 514164 [details] dmesg from guest after network crashed (In reply to comment #8) > Is there anything in dmesg after the guest network fails? I don't understand the messages very much, so I'm attaching dmesg output from guest now and the last part of dmesg from my physical machine will follow. Created attachment 514166 [details]
dmesg from physical machine after network crashed
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Given that F15 is end of life in less than a month, it's unlikely this will get fixed before hand. Honza, if you can reproduce this issue with a later Fedora version, please reopen and we can go from there. |