Bug 7273 - virtualbox wrongly caches boot isos on VM reset
Summary: virtualbox wrongly caches boot isos on VM reset
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-31 19:13 CEST by Thierry Vignaud
Modified: 2022-07-12 14:35 CEST (History)
1 user (show)

See Also:
Source RPM: virtualbox
CVE:
Status comment:


Attachments

Description Thierry Vignaud 2012-08-31 19:13:26 CEST
virtualbox caches boot isos
When on replaces the boot iso and restart the VM, virtualbox continues to use the boot iso until the VM is stop then start (instead of reset & the like).
This makes debuging ISOs harder than needed
Thierry Vignaud 2012-09-01 00:11:10 CEST

Summary: virtualbox caches boot isos => virtualbox wrongly caches boot isos on VM reset

Thierry Vignaud 2012-09-01 00:11:17 CEST

Hardware: i586 => All

Comment 1 Thierry Vignaud 2012-09-29 17:05:07 CEST
acutally, virt-manager has the same bug
Comment 2 Marja Van Waes 2015-04-14 20:10:49 CEST
No action since over 2,5 yrs ago and still assigned to Bug Squad

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully updated Mageia 4
Comment 3 Marja Van Waes 2015-04-14 20:16:50 CEST
Now really closing :-/

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 4 Thierry Vignaud 2015-04-15 06:24:51 CEST
That's still true

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Comment 5 Samuel Verschelde 2016-10-15 20:26:56 CEST
(In reply to Thierry Vignaud from comment #4)
> That's still true

Shouldn't this be reported upstream instead (to both virt-manager and virtualbox if it's still valid in both)? Of course we can keep this bug report open to keep track of the upstream issues but my understanding is that it's not something we can fix in packaging.

Assignee: bugsquad => pkg-bugs
Status: REOPENED => NEW
CC: (none) => tmb

Comment 6 sturmvogel 2022-07-09 12:26:44 CEST
Any news on this or can we close this now (6 years later) based on comment 5 as OLD?
Comment 7 Thierry Vignaud 2022-07-12 14:35:43 CEST
Ok

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.