Custom Query (16363 matches)
Results (2059 - 2061 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3459 | worksforme | XP Host freezes after pressing start | ||
| Description |
Since the release of virtualbox 2.1.0 my computer completely freezes when i start a vm. When i press start the "bios" screen from the vm comes up and then the host pc completely freezes. Even my mouse doens`t respond. Only a full reset of the host pc i can get the computer to turn normal again. 2.1.2 and 2.1.4 are having the same problem. Virtualbox 2.0.6 is working for me (so i downgrade every time) and is the only version which is stable for me. No vbox log is created and also no windows logs can be found. The freeze occur if i am using the host network interface but also on NAT and all the other network options. My host even freeze if i do the following: 2.0.6 on host. > Win xp guest > i install virtualbox 2.1.4 in guest > launch a newly created vm in the guest (so no os installed yet) > host pc freezes. System specs: Motherboard: Asus p5q-pro Cpu: Intel E8400 dual core Memory: kingston 2gb Graphics: Ati hd 3450 Network card: Realtek 8139 Windows xp pro sp3 completely up-to-date |
|||
| #9511 | obsolete | USB WiFi ath9k_htc device not initialized in Linux guest | ||
| Description |
I'm running VirtualBox 4.1.2 in Ubuntu 10.04 host with Gentoo Linux as the guest. I've been trying to use a USB WiFi device (Atheros chipset) in the guest OS, but so far no luck yet.
[ 3.282211] ath9k_htc 1-1:1.0: usb_probe_interface [ 3.282222] ath9k_htc 1-1:1.0: usb_probe_interface - got id [ 3.772725] usb 1-1: ath9k_htc: Transferred FW: ar9271.fw, size: 51312 [ 4.772194] ath9k_htc 1-1:1.0: ath9k_htc: Target is unresponsive [ 4.772287] Failed to initialize the device [ 4.774250] ath9k_htc: probe of 1-1:1.0 failed with error -22 [ 4.775452] usbcore: registered new interface driver ath9k_htc # lsusb | grep -i ath Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n My guess is that the USB WiFi device itself and the setup in the Linux guest might not be an issue, because when I use a real machine, everything works perfectly. sol |
|||
| #20680 | invalid | Possible bug in showvminfo after snapshot deleted | ||
| Description |
after the creation and subsequent deletion of a snapshot with live option the vboxmanage showvminfo command shows in the storage section the path of the snapshots and not that of the vhds. SATA (0, 0): /VirtualBox/MyVm/Snapshots/{540ceec8-aa9a-43f8-9de7-d825 b008d08d}.vdi (UUID: 540ceec8-aa9a-43f8-9de7-d825b008d08d) SATA (1, 0): /VirtualBox/MyVm/Snapshots/{5af2833c-59ba-4cea-a67a-bfb9 507b225e}.vdi (UUID: 5af2833c-59ba-4cea-a67a-bfb9507b225e) instead if I look at the properties of the virtual machine from the virtualbox console (gui) the disks are correct (and obviously the presence of snapshots is not reported) |
|||

