Bug 613517 - Guest machine is stuck (no ping, no nothing) (host spends 25% in read_hpet)
Summary: Guest machine is stuck (no ping, no nothing) (host spends 25% in read_hpet)
Alias: None
Product: Fedora
Classification: Fedora
Component: kvm   
(Show other bugs)
Version: 13
Hardware: All Linux
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-12 06:05 UTC by Catalin BOIE
Modified: 2011-06-29 13:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-29 13:40:35 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Catalin BOIE 2010-07-12 06:05:03 UTC
Description of problem:
Guest machine is stuck (no ping no nothing).
Also libvirtd seems to not allow me to see the console or the other machines.

Version-Release number of selected component (if applicable):
Host is F13: qemu-kvm-0.12.3-8.fc13.i686.
Guest is F11.

How reproducible:
/usr/bin/qemu-kvm -S -M fedora-13 -enable-kvm -m 1024 -smp 2,sockets=2,cores=1,threads=1 -name support -uuid 26183555-27bb-74c9-fe47-1ac5fc34c0e5 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/support.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot c -drive file=/var/lib/libvirt/images/support.img,if=none,id=drive-ide0-0-0,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=/var/lib/libvirt/images/support-backup.img,if=none,id=drive-ide0-0-1 -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive if=none,media=cdrom,id=drive-ide0-1-0 -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:45:a1:5b,bus=pci.0,addr=0x4 -net tap,fd=53,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
   PerfTop:     821 irqs/sec  kernel:96.1% [1000Hz cycles],  (all, 8 CPUs)

             samples  pcnt function                       DSO
             _______ _____ ______________________________ ___________________

             3889.00 25.1% read_hpet                      [kernel.kallsyms]  
             2509.00 16.2% acpi_idle_do_entry             [kernel.kallsyms]  
             1203.00  7.8% memcmp                         [kernel.kallsyms]  
              794.00  5.1% generic_exec_single            [kernel.kallsyms]  
              455.00  2.9% _raw_spin_lock_irqsave         [kernel.kallsyms]  
              316.00  2.0% find_busiest_group             [kernel.kallsyms]  
              289.00  1.9% hpet_next_event                [kernel.kallsyms]  
              238.00  1.5% _raw_spin_lock                 [kernel.kallsyms]  
              220.00  1.4% schedule                       [kernel.kallsyms]  
              200.00  1.3% memcpy                         /lib64/libc-2.12.so
              181.00  1.2% fget_light                     [kernel.kallsyms]  

strace -v -tt -p 29929:
Process 29929 attached - interrupt to quit
08:56:54.748827 futex(0x85eec0, FUTEX_WAIT_PRIVATE, 2, NULL

Comment 1 Justin M. Forbes 2010-07-15 18:09:46 UTC
This should be resolved with the seabios update in updates-testing. Please test and provide feedback.

Comment 2 Bug Zapper 2011-06-01 14:11:15 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 3 Bug Zapper 2011-06-29 13:40:35 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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