Custom Query (16363 matches)
Results (85 - 87 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2123 | fixed | Virtual Machine state change on GUI crash | ||
| Description |
As described in other tickets, creation of a new virtual disk may crash the GUI. Creation was invoked via "Hard Disks" of a V.M. In that case, the state of the V.M. changed from "Powered off" to "Aborted" as can be seen on GUI restart. This seems to have no further implications, but is confusing and incorrect. |
|||
| #2131 | worksforme | Memory leak during Linux installs? | ||
| Description |
Host is Vista Home Premium with all patches, but no SP1. Created a fresh 8 GByte *.vdi from VBoxAdmin. Created a new machine for "openSUSE", 512 MByte RAM, 8 MByte VGA, enabled access to Host DVD drive including pass thru, enabled audio using "Windows" driver. Booted from PC-Welt Linux DVD 4/2008 containing OpenSuse 11 and other, booted OpenSuse in 800x600 for install. Physical memory usage indicated by Task Manager rose at one point near start of install by a few 100 MByte, but still not too dangerous, approx 1.3 GByte in use then, 0.5 GByte before start of virtual machine. Choose some more software packages during install, in my case some fileservers and command and kernel development. Installation runs, the V.B. window ist partially covered most of the time, I have only occassionally a look on it, click into, go back by Ctrl (host key). Installation seems complete, Guest reboots, Physical memory usage increases sharply to 1.62 GByte. But even TopToBottomNT process monitor shows only "Process total address space is 700328 K" for the VirtualBox.exe actually running the Guest (the other with GUI is still there, but neither it nor the VBoxServ.exe has dramatic memory usage). I manually counted the 1024 Kb allocations and it were only approx 500, very few larger ones (up to 8 Mb) between them in the list. But all the memory freed after shutting down Guest (clean power down from within it, after it booted from its *.vdi). I tried the same install a second time and got the same result again. Of course I did not exactly the same in parallel on that computer, but nearly the same, little *.pdf reading and web browsing. Checked all the svchost.exe for excessive total address space, but none. This time I will not boot into just installed Linux, but start Rescue Live-CD from this menu, and then mem test. (My mem is ok, but just as a machine stress.) Task Manager dump of this VirtualBox.exe is 650 MByte only. I shortly started another Live-CD inside the DVD and (seen later) probaly at same time mem usage increased again by apporx 200 to 300 MByte, but returned to 1.62 G after return to primary boot menu. Ok, power off. Physical mem usage down to 791 MByte, there is still something missing, at first time it went down to 500. Is it Vista or VirtualBox? The *.log and *.xml are attached. |
|||
| #2137 | obsolete | USB issues | ||
| Description |
Win XP SP3 Host, W2000 SP4 Guest with Additions, trying USB assignment for a multi card reader (USB 2.0 enabled). Needed to unplug and reconnect after V.B. driver installed automatically on Host, otherwise card reader was busy and could not be connected to Guest (message of V.B. when device clicked to checkmark it). Accessed by Guest. Unchecked it, Guest complained about prohibited removal, but it is at Host again. No crash like with Vista (see #2114). But the V.B.exe running Guest consumes 50 % of the 2 core CPU completely now, although inside Guest Task Manager shows 97 % idle. Clean off&start, V.B. does not remember I un-checkmarked card reader, and again 50 % CPU already while Guest is waiting in login dialog. Strange - CPU fan runs only slowly. Clean off, USB off, start. No excessive CPU usage! Trying USB 1.1 for Guest only, but device at Host and Host port are 2.0. Same 50 % CPU. Clean USB device eject from Guest, CPU 50 %. Card reader unplugged, 50%. It is VBoxSVC.exe which is hogging CPU! Plug in, the same. Guest clean off, VBoxSVC.exe 50 %. GUI closed, the same. Host reboot. (Task Manager did not show "User name" for processes directly after startup, seems to be it needs fome background service for this, which was still not running, although desktop was present.) V.B. GUI started, VBoxSVC.exe 0 %. Again USB 2.0. Booting Guest, while in boot selector of W2000 50 % VirtualBox.exe (as already know from other tries). While in Login dialog, VirtualBox.exe changed between 10 and 50 %, now with Desktop it is 50 % most of the time. Guest clean off, no excessive CPU usage. Trying clean USB device removal in Guest again. It is still VirtualBox.exe at 50 %. Unplug. Still VirtualBox.exe at 50 %. This time VBoxSVC.exe stays at 0 %, ok. Remember: Guest was USB 2.0 this time, 1.1 previous try. Again with USB 1.1, GUI and VBoxSVC.exe kept running between Guest starts. Plugin while Guest started. Login, VirtualBox.exe at 50 %, clean removal, unplug, VirtualBox.exe well below 10 %. Clean off (shutdown). No excessive CPU usage. Problem only partially reproducable. Configured the Linux v.m. with USB 2.0 and cardreader. Booting rescue CD from DVD there. Found /dev/sda to sdd during startup, Guest is text display, top shows 0% CPU there, but VirtualBox.exe goes up and down between approx 10 and 50 %, I assign it fixed to CPU0 now and see a graph close to a sine wave now, from 30 to 100 % usage of this core, higher Task Manager refresh rate: it is longer at 100 %, shorter near 30 %, period is 6 to 7 seconds. Accessing (reading) a SDHC card in card reader seems to work, at least fdisk "p"rint. dd with 1M blocksize gets only 4.1 MByte/s (under Vista 7.3 MByte/s), no higher CPU usage than without dd. Unplugging card reader. CPU waveform unchanged. Plug in. Un-checking in V.B. menu. It appears at Host with the SDCH card inside. Same CPU wave. Guest "halt" command, Guest off, CPU near 0 %. Disabled USB support and did same Guest startup. CPU near 0 % at command prompt. Clean off. Activate USB (not 2.0) controller only, no devices attached to Guest. CPU near 0 % at command prompt. Cannot attach any of the 4 USB devices, because V.B. running Guest shows all as "Zustand: Beschäftigt" (busy) in menu - no, I can, just click. Try it with mouse at different Host port this time, Host installs "VirtualBox USB" for this port, too, but looks for it longer than before, mouse is again / still under Host control. Try clicking again "Zustand: gefangen" (no, mouse / keyboard were not captured by Guest, no, message box about beeing busy with earlier request, unplug & plug, "Zustand: nicht unterstützt", but click, "Devices" menu remains marked (pressed). This core is quite constant near 50 % with VirtualBox.exe. V.B. running Guest does no longer respond, seems to be busy internally, Process Monitor does not show any operations for it. Last message in *.log is "OHCI: USB suspended". Turn off by window close and Windows force-kill. CPU 0 %. But GUI shows machine still as running. GUI terminated and started. It hangs with empty white window, but no CPU load, VBoxSVC.exe is running, GUI does not respond, force-kill-click. VBoxSVC still in background, usually terminates with last VirtualBox.exe. Killing it. GUI start, ok, machines are Ausgeschaltet (off), ok. Looks like GUI hangs i VBoxSVC.exe hangs. Bad design, timeouts missing. |
|||

