RBVM Bugs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
# '''Minor:''' VM names can be set to empty string. Cosmetic bug only. | # '''Minor:''' 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 pseudoterminal blocks, causing the power on to fail (and the KVM process to stay running) | # '''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) | ||
# '''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:''' 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:''' 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.
- Minor: 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)
- 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: Session cache should be cleared when the system starts up, otherwise lock errors cause some peoples' sessions to asplode.