RBVM Bugs: Difference between revisions
Jump to navigation
Jump to search
(Updated bugs list) |
(Updated) |
||
| Line 2: | Line 2: | ||
# '''Minor Bug:''' 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 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) | # '''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) '''Fixed in rev 70, removed use of PTYs''' | ||
# '''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 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. Addressed a little in rev 70, still not quite there. | ||
# '''Moderate Bug:''' 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. | ||
# '''Improvement:''' Logging and debug levels, etc, need to be cleaned up properly. | # '''Improvement:''' Logging and debug levels, etc, need to be cleaned up properly. | ||
# '''Moderate Bug:''' If new VMs are created as root, the mode and ownerships of the VM images under /var/lib/rbvm/images is completely wrong - VM will refuse to start as the rbvm user can't read/write the image. '''Fixed in rev 66''' | # '''Moderate Bug:''' If new VMs are created as root, the mode and ownerships of the VM images under /var/lib/rbvm/images is completely wrong - VM will refuse to start as the rbvm user can't read/write the image. '''Fixed in rev 66''' | ||
# '''Improvement:''' Add extra columns (MAC, IP, status) to homepage. '''Added in rev 65''' | # '''Improvement:''' Add extra columns (MAC, IP, status) to homepage. '''Added in rev 65''' | ||
# '''Improvement:''' Add hardware options to front end (NIC controller, etc). Backend added in rev 70 | |||
# '''Improvement:''' Boot device selection '''Added in rev 69''' | |||
Revision as of 13:33, 5 March 2010
This page lists bugs with the redbrick VM system (at https://vmweb.redbrick.dcu.ie, documentation here).
- Minor Bug: VM names can be set to empty string. Cosmetic bug only.
- 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) Fixed in rev 70, removed use of PTYs
- 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. Addressed a little in rev 70, still not quite there.
- Moderate Bug: Session cache should be cleared when the system starts up, otherwise lock errors cause some peoples' sessions to asplode.
- Improvement: Logging and debug levels, etc, need to be cleaned up properly.
- Moderate Bug: If new VMs are created as root, the mode and ownerships of the VM images under /var/lib/rbvm/images is completely wrong - VM will refuse to start as the rbvm user can't read/write the image. Fixed in rev 66
- Improvement: Add extra columns (MAC, IP, status) to homepage. Added in rev 65
- Improvement: Add hardware options to front end (NIC controller, etc). Backend added in rev 70
- Improvement: Boot device selection Added in rev 69