Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 576725 Details for
Bug 811497
Deadlock in qemu driver on forced console connection
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Leaves the console connection in a state, where the next forced connection causes a deadlock.
console_deadlock.py (text/x-python), 619 bytes, created by
Peter Krempa
on 2012-04-11 09:26:32 UTC
(
hide
)
Description:
Leaves the console connection in a state, where the next forced connection causes a deadlock.
Filename:
MIME Type:
Creator:
Peter Krempa
Created:
2012-04-11 09:26:32 UTC
Size:
619 bytes
patch
obsolete
>#!/usr/bin/env python >import time >import libvirt >from libvirt import libvirtError > >guest = "RHEL_x64" >device = "serial0" >data = "abcd" >expect = "cdef" >timeout = 5 > >uri = "qemu:///system" >reply = "" > >conn = libvirt.open(uri) >dom = conn.lookupByName(guest) > >stream = conn.newStream(libvirt.VIR_STREAM_NONBLOCK) > >dom.openConsole(device, stream, libvirt.VIR_DOMAIN_CONSOLE_SAFE) > >stream.send(data) > >while timeout > 0 and len(reply) < len(expect): > stream.send("") > recv = stream.recv(10) > > if recv == -2: > time.sleep(0.1) > timeout -= 0.1 > else: > reply += recv > >stream.finish() >conn.close()
<b>You cannot view the attachment while viewing its details because your browser does not support IFRAMEs. <a href="attachment.cgi?id=576725">View the attachment on a separate page</a>.</b>
View Attachment As Raw
Actions:
View
Attachments on
bug 811497
: 576725