Custom Query (16363 matches)
Results (2263 - 2265 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4111 | fixed | Mac OSX Host: Numlock Misbehaves When Focus Changes from Host-to-Guest | ||
| Description |
I use an Apple extended keyboard (includes numeric keypad). I've noticed odd behavior with numlock for the numeric keypad when focus is switched from the Host-to-Guest. In summary one of two things happens:
This behavior is reproducible with VBox 2.2.2 using Mac OSX (Leopard) Host and WinXP Guest as outlined below. First: Set-up Guest in Fullscreen Mode in its own Space I prefer to run in Fullscreen Mode with a WinXP guest in its own Space. I like to easily switch Spaces back and forth with ctrl-arrow. You can do this if you do the following:
Now on to unusual behavior with a numeric keypad. . . I have an iMac with an Apple wireless extended Mac keyboard (i.e. numeric keypad included) and I do a lot of number entry in my work. With this keyboard the "numlock" is the key combination "shift-clear". When switching Spaces from Mac use (I'll call it a "Mac Space" from here on) back to my VBox guest WinXP ("Guest Space" from now on) the numlock is off. To turn the numlock back on I have to do the "shift-clear" twice to resume use of the numeric keypad in the Guest Space. Now here is another strange thing I noticed, if you switch Spaces 2x using the configuration outlined above the numlock comes back on without activating it. Since this numlock behavior might be a bit hard to follow from the above, you can see it in action for yourself with the following experiment:
Pretty weird! This just demonstrates this problem of the numlock reactivating on every-other Space switch from Mac Space to Guest Space. Otherwise you have to activate the numlock twice to use the numeric keypad after a change in focus. This seems to be a Virtualbox 2.2.2 bug. If you have a work-around to keep a numeric keypad enabled during Host-to-Guest focus changes (as with my Space switching) please let me know. |
|||
| #4114 | fixed | VirtualBox losing LAN connection | ||
| Description |
I am trying to use VB on a Linux host (amd64) and the guest is WinXP. In loading XP in the VB, I can connect to the LAN drive (QNAP 809pro) and all works fine for a while. In using several applications, the main EXE is on the VM-XP local drive and the data for the app is in the LAN drive (mapped). I have tried this on 3 different new PC's so I believe the hardware has been ruled out. I have created 2 new VM's to rule out bad VB install. I will lose connection to the LAN drive when trying to load/save data from the app. I can immediately restart the app and it works as expected as though nothing happend. (Performing this on a dedicated XP box does not suffer disconnects, only on a VirtualBox-VM) I have tried the following. It has helped, but there are still random disconnects. -Hard coded the IP instead of the device name of LAN drive (helped a lot) -Changed Adapter type from PCnet to Intel and installed latest drivers on XP host. (helped rate of disconnects) -Changed Attached to to Bridge instead of NAT to make host on same network. (NAT works better on 1 PC, Bridge works better on 2 others) -Toggled several of the settings above to see if it helped. I believe I have narrowed it down to the NIC driver in the VM? as changes do make a difference in performance regarding disconnects. I do not see any drops that I can tell when trying to access internet, or copying files to/from LAN drive. Only when a local app has it' data on the LAN drive The main culprit in this case is QuickBooks 2009, but I have triggered it on another DB server app where tables existed on the LAN drive. Hard coding the IP as mentioned above did solve this problem for this app, not QB2009. Any thoughts would be appreciated, as I am trying to sell the idea of using VB and Linux in our office and this is a major stumbling block in the process. There seems to be a post related to this: http://forums.virtualbox.org/viewtopic.php?f=2&t=16181&p=78223#p68087 I also see a ticket that may be related? http://www.virtualbox.org/ticket/4063 It seemed to almost gone away for a week, but now it has come back full force, disconnecting at will. I would relate it to the LAN falling asleep and requiring a 'wake up' Regards, Scott. Host: Ubuntu 8.10 (amd64), I7 processor, 10 gig ram Guest: XP Pro (4 gig base memory) VB 2.2.2 r46594, guest additions: latest version |
|||
| #4118 | fixed | Multiple VMs on single TAP device fails | ||
| Description |
When I start multiple VMs that all have Host Interface Networking, and are using the same TAP device, only the one started first successfully start. The subsequently started VM fail with: "Failed to open Host Interface Network device driver (VERR_PDM_HIF_OPEN_FAILED)" The Host OS is Vista 32-bit. The Guest OSes is Linux 64-bit. The virtual NICs are PCnet-FAST III. This configuration works well on Linux with a TAP device. The way I see it, using a single TAP with multiple VMs is the only way to go if you need a configuration where there is two-way communication between both Guest-Host and Guest-Guest. I haven't tested this in a newer version that 2.1.4, because I found no fitting fixed bug rapport in the release notes of the newer versions. The errors reported in the logs: "00:00:01.609 PDM: Failed to construct 'pcnet'/0! VERR_PDM_HIF_OPEN_FAILED (-2852) - Unable to open the host interface. 00:00:01.611 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={e3c6d4a1-a935-47ca-b16d-f9e9c496e53e} aComponent={Console} aText={Failed to open Host Interface Networking device driver (VERR_PDM_HIF_OPEN_FAILED). 00:00:01.611 Unknown error creating VM (VERR_PDM_HIF_OPEN_FAILED)} aWarning=false, preserve=false 00:00:01.619 Power up failed (vrc=VERR_PDM_HIF_OPEN_FAILED, rc=E_FAIL (0X80004005)) 00:01:04.004 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={e3c6d4a1-a935-47ca-b16d-f9e9c496e53e} aComponent={Console} aText={Invalid machine state: 1)} aWarning=false, preserve=false" |
|||

