Custom Query (16363 matches)
Results (1090 - 1092 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #20954 | invalid | I make a virtual machine and when I make the virtual iso image hard disk it creates but it will just give me errors then i try to add it to the machine. it would be great if you cound fix it. | ||
| #11813 | obsolete | RedHat 5 guest VM mouse clicks stop working | ||
| Description |
I had high hopes for Virtualbox but unless I can get reliable mouse control, I'll have to go with VMWare. My linux VM boots fine and I can login to my O/S account. Mouse works no problem. I then begin launching apps and switching between windows and before long, my mouse clicks are ignored. The pointer is still there and moves just fine, but clicking (left or right buttons) doesn't do anything. I can move the pointer out of the guest VM to the host and mouse clicks are fine. But moving the pointer back to the guest, mouse clicks are ignored. After much frustration, I finally figured out that when the clicks stop working, if I press ALT-tab, mouse clicks begin working again. But after a while they stop and I'm back to pressing ALT-tab. I'm running Windows 7 64 bit host with a RedHat 5.9 64bit guest. Mouse is USB. Guest additions are also installed. What's going on? |
|||
| #2314 | duplicate | excessive syslogging (pgmPoolTracDerefGCPhys) VM halts | ||
| Description |
I've noticed that certain machines seem to freeze, and the syslog gets filled very quickly. I have an AMD Turion 64 bit dual core cpu, but all of my OS's are running i386 (host and all guests). The OS's (or iso's, rather) that display this behavior are the ubuntu-8.04.1-desktop-i386.iso image and some of the recent daily builds of the debian-testing-netinst.iso images. I tried the daily build for 23Sept2008, and that one seems to be ok, but the problem exists in the 16Sept2008 version of the daily build. I'm letting you know this in case you need something to test with, and don't feel like getting the larger ubuntu image. AFAICT, this problem only appears when VT is enabled. I really don't want to go back to disabling VT. Now that I'm used to it, going back makes things seem like they're moving at a snail's pace. Also, why is it that I have to disable VT for all machines, when I only need to disable it for one? It seems that if each machine has an option for using VT, that each one should run according to that setting. I think that if VT has to be enabled/disabled for all machines, then the configuation option should stay with the global preferences, and not be a per machine option. here is a snipped from /var/log/syslog: Sep 23 16:31:07 bard kernel: [15242.263109] !!R0-Assertion Failed!! Sep 23 16:31:07 bard kernel: [15242.263109] Expression: <NULL> Sep 23 16:31:07 bard kernel: [15242.263109] Location : /home/michael/technik/s\ ources/archive/pkg-virtualbox/build-area/virtualbox-ose-1.6.6-dfsg/src/VBox/VMM\ /VMMAll/PGMAllPool.cpp(2738) void pgmPoolTracDerefGCPhys(PGMPOOL*, PGMPOOLPAGE*\ , RTHCPHYS, RTGCPHYS) Sep 23 16:31:07 bard kernel: [15242.263109] Sep 23 16:31:07 bard kernel: [15242.263109] !!R0-Assertion Failed!! Sep 23 16:31:07 bard kernel: [15242.263109] Expression: <NULL> Sep 23 16:31:07 bard kernel: [15242.263109] Location : /home/michael/technik/s\ ources/archive/pkg-virtualbox/build-area/virtualbox-ose-1.6.6-dfsg/src/VBox/VMM\ /VMMAll/PGMAllPool.cpp(2738) void pgmPoolTracDerefGCPhys(PGMPOOL*, PGMPOOLPAGE*\ , RTHCPHYS, RTGCPHYS) Sep 23 16:31:07 bard kernel: [15242.263109] Sep 23 16:31:07 bard kernel: [15242.263109] !!R0-Assertion Failed!! Sep 23 16:31:07 bard kernel: [15242.263109] Expression: <NULL> Sep 23 16:31:07 bard kernel: [15242.263109] Location : /home/michael/technik/s\ ources/archive/pkg-virtualbox/build-area/virtualbox-ose-1.6.6-dfsg/src/VBox/VMM\ /VMMAll/PGMAllPool.cpp(2738) void pgmPoolTracDerefGCPhys(PGMPOOL*, PGMPOOLPAGE*\ , RTHCPHYS, RTGCPHYS) I'm getting about 1900-2000 entries like this per second. This problem doesn't occur consistenly every time the VM is booted, but it occurs probably about 75% of the time, in my experience. At least that's with the ubuntu VM. Running the netinst build from 16Sept2008 will freeze the VM and deluge the syslog every time. |
|||

