Custom Query (16612 matches)
Results (16 - 18 of 16612)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #21313 | invalid | ВМ | ||
| Description |
Моя вм с Windows Xp прерывается, я не знаю почему. |
|||
| #10801 | fixed | ~25 MB memory leak when changing nic1 from null to nat => Fixed in SVN | ||
| Description |
Hello, Running this .bat :a "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" controlvm "xp" nic1 null sleep 5s "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" controlvm "xp" nic1 nat sleep 5s goto a would increase the private memory of VirtualBox.exe (as seen by Process Explorer) by about 25 MB every time nic1 is switched from null to nat. (a lot faster if you remove the sleeps) VirtualBox.exe starts with about 70-80 MB private memory and will grow fast after running the batch. I've reproduced this with two VMs, one with Ubuntu 64, running or in VirtualBox's BIOS also, and one without a hard drive attached (XP, 32 bit), direcly in BIOS (I've pressed F12 when booting). My initial problem was a crash in VBoxDD.dll which I've tried to reproduce (then I've only switched the nic a couple of times, to 'bridged' too). Host: Windows 7 x64, SP1. |
|||
| #5137 | fixed | ~/.VirtualBox/VirtualBox.xml problems. | ||
| Description |
Hey I now spent a few days hacking back together the media registry... I rebooted my machine, and - oops - the file was back to a version about 2 weeks ago (!!!). i suspect that the problem was that i was running one VM in headless mode (as service), and others through the gui. my suspicion is that the headless vm wrote back VirtualBox.xml, overwriting the intermediate changes... this was really BAD! onther thing i'd suggest, is that the media registry structure should be pretty much different: there should be no need to keep all snapshots of harddisks in the media registry; why not do it like all others, and make each snapshot know it's "parent". this way, onlye the VM itself would need to know the "top-most" disk attached to the VM. This would also ease the implementation of the enhancement ticket i just filed (#5136). Also it seems that if during creation of a snapshot an ISO image is mounted, and the ISO is removed from disk afterwards, the media registry refuses to remove the file from the registry - seems like a snapshot wanting this file locks it somehow... |
|||

