RBVM Bugs: Difference between revisions

From Redbrick Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
This page lists bugs with the redbrick VM system.
This page lists bugs with the redbrick VM system.


# '''Minor:''' VM names can be set to empty string. Cosmetic bug only.
# '''Minor Bug:''' VM names can be set to empty string. Cosmetic bug only.
# '''Major:''' For some reason, on VM power on, the os.read() call on the monitor pseudoterminal blocks occasionally, causing the power on to fail (and the KVM process to stay running)
# '''Major Bug:''' For some reason, on VM power on, the os.read() call on the monitor pseudoterminal blocks occasionally, causing the power on to fail (and the KVM process to stay running)
# '''Moderate:''' VM powered on detection needs work, it should check by MAC address and disk image name to try to detect when a VM power on failure has occurred.
# '''Moderate Feature:''' VM powered on detection needs work, it should check by MAC address and disk image name to try to detect when a VM power on failure has occurred.
# '''Moderate:''' Session cache should be cleared when the system starts up, otherwise lock errors cause some peoples' sessions to asplode.
# '''Moderate Bug:''' Session cache should be cleared when the system starts up, otherwise lock errors cause some peoples' sessions to asplode.

Revision as of 14:31, 25 February 2010

This page lists bugs with the redbrick VM system.

  1. Minor Bug: VM names can be set to empty string. Cosmetic bug only.
  2. Major Bug: For some reason, on VM power on, the os.read() call on the monitor pseudoterminal blocks occasionally, causing the power on to fail (and the KVM process to stay running)
  3. Moderate Feature: VM powered on detection needs work, it should check by MAC address and disk image name to try to detect when a VM power on failure has occurred.
  4. Moderate Bug: Session cache should be cleared when the system starts up, otherwise lock errors cause some peoples' sessions to asplode.