Description of problem: Attach console to a guest which already has console attached would cause race contention, so that both consoles of the guest would get stuck. It would make sense to add a file lock to prevent access to console of a guest when the guest already has a console attached, either in xend or in xenconsole. Version-Release number of selected component (if applicable): xen-3.0.3-131.el5 How reproducible: Always. Steps to Reproduce: 1. Start a pv guest and attach console to the guest via xm console. 2. In another terminal, attach the console to the same guest via xm console. 3. Actual results: The both consoles get stuck, and print strange outputs. Expected results: xend or xenconsole should prevent attaching console to a guest which already has a console attached. A warning should be printed so that customers could know that it is not a supported behaviour. Additional info: Upstream also have such issues, although they support multiple consoles for pv guest. When you attach the same console(with the same console id) more than once, the consoles would get stuck.
reproduce the bug on xen-3.0.3-132.el5 and verify the bug on xen-3.0.3-135.el5. Steps: 1. Start a pv guest and attach console to the guest via xm console. 2. In another terminal, attach the console to the same guest via xm console. On xen-3.0.3-132.el5, the both consoles get stuck, and print strange outputs. On xen-3.0.3-135.el5, the second console can not be attached, and proper message show in second termimal: # xm con 11 Another console has already been attached to guest The first console still works fine. So change this bug to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0160.html