| Summary: | Virtualbox Windows guest & old guest additions | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marc Krämer <mageia> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | jim, marja11 |
| Version: | Cauldron | Keywords: | FOR_ERRATA6 |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | virtualbox-5.1.10-3.mga6.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Marc Krämer
2016-11-29 00:49:20 CET
Samuel Verschelde
2016-11-29 10:24:09 CET
Keywords:
(none) =>
FOR_ERRATA6 @ tmb Is my assumption correct that this can't ever be fixed? CC:
(none) =>
marja11 I don't think that this will be a problem when mga6 is released. cauldron has virtualbox-5.1.10. An update for mga5 to 5.1.10 is currently in testing and should be pushed to updates soon. Thus Windows guests should already have the latest guest additions when the upgrade is done. CC:
(none) =>
jim So this will be a problem to mga5 users when virtualbox is pushed to update. What you should have in mind is, not every guest system is started on a daily base. In first place I was looking for things that don't work in mga6 (no big deals - good job done). Only Windows had this problem which was easy to solve via recovery mode. It is a bad behaviour by virtualbox to freeze on old guest additions. I thought it should be noted in case some one else has the same problem. was present in errata Resolution:
(none) =>
FIXED |