VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2467 - 2469 of 16363)

Ticket Resolution Summary Owner Reporter
#2523 duplicate Aladdin Hardlock / HASP Drivers and Dongles do not work in Windows 2000+ ashman
Description

The installation of Aladdin Hardlock / HASP drivers and thus usage of these dongles does not work in Windows 2000 with Service Pack 4. This might also apply to Windows XP (I know it was a problem in 1.5.x) and Windows Vista with different Service Pack versions.

If you install the Aladdin "HASP SRM Run-time Command-line Installation" drivers a Blue Screen of Death is triggered and in another case the VM crashed. Also the guest OS might not boot again after the driver installation. I think this can be tested without an attached dongle by just installing the drivers.

I try this on WindowsXP Service Pack 3 with later updates applied. The VirtualBox settings are pretty much standard except that USB Controller and USB 2.0 support is activated, RAM is set to 512MB and network support is deactivated. The VM Additions are installed. Processor is a Athlon X2.

HASP SRM Run-time Command-line Installation:

Driver download page:

http://www.aladdin.com/support/hasp-srm/vendor.aspx

Direct driver download:

ftp://ftp.aladdin.com/pub/hasp/srm/Runtime_%28Drivers%29/HASP_SRM_Runtime_cmd_line.zip

#2524 fixed data corruption under heavy I/O load on host Georg Moritz
Description

Heavy I/O load on the host leads to ide dma timeouts, device resets, incorrect read/write operations and ultimately to data corruption in the VBox.

It looks like iowait conditions on the host don't lead to a blocking of the virtual

vb10:~# tail -n 0 -f /var/log/messages
Oct 27 18:28:35 vb10 kernel: [ 1559.569320] hdb: dma_timer_expiry: dma status == 0x61
Oct 27 18:28:45 vb10 kernel: [ 1569.569594] hdb: DMA timeout error
Oct 27 18:28:45 vb10 kernel: [ 1569.570105] hdb: dma timeout error: status=0x48 { DriveReady DataRequest }
Oct 27 18:28:45 vb10 kernel: [ 1569.570127] ide: failed opcode was: unknown
Oct 27 18:28:45 vb10 kernel: [ 1569.570766] hda: DMA disabled
Oct 27 18:28:45 vb10 kernel: [ 1569.572039] hdb: DMA disabled
Oct 27 18:29:20 vb10 kernel: [ 1599.568186] ide0: reset timed-out, status=0x90
Oct 27 18:29:20 vb10 kernel: [ 1604.572374] hda: status timeout: status=0x90 { Busy }
Oct 27 18:29:20 vb10 kernel: [ 1604.572396] ide: failed opcode was: unknown
Oct 27 18:29:20 vb10 kernel: [ 1604.580286] Clocksource tsc unstable (delta = 4687228551 ns)
Oct 27 18:30:00 vb10 kernel: quest: I/O error, dev hdb, sector 506799
Oct 27 18:30:01 vb10 kernel: [ 1635.421648] __ratelimit: 5022 messages suppressed
Oct 27 18:30:01 vb10 kernel: [ 1635.421648] lost page write due to I/O error on hdb1
Oct 27 18:31:02 vb10 kernel: nd_request: I/O error, dev hdb, sector 551111
Oct 27 18:31:09 vb10 kernel: [ 1714.280038] __ratelimit: 5014 messages suppressed
Oct 27 18:31:09 vb10 kernel: [ 1714.280038] lost page write due to I/O error on hdb1
Oct 27 18:31:20 vb10 kernel: [ 1725.024393] lost page write due to I/O error on hdb1
Oct 27 18:31:26 vb10 kernel: [ 1730.728966] lost page write due to I/O error on hdb1
Oct 27 18:31:29 vb10 kernel: [ 1733.614585] lost page write due to I/O error on hdb1
Oct 27 18:31:29 vb10 kernel: [ 1733.905566] lost page write due to I/O error on hdb1
Oct 27 18:31:31 vb10 kernel: [ 1736.305170] __ratelimit: 10 messages suppressed
Oct 27 18:31:31 vb10 kernel: [ 1736.305403] lost page write due to I/O error on hdb1
Oct 27 18:31:36 vb10 kernel: [ 1741.416768] __ratelimit: 23 messages suppressed
Oct 27 18:31:36 vb10 kernel: [ 1741.417144] lost page write due to I/O error on hdb1
Oct 27 18:31:41 vb10 kernel: [ 1746.255712] __ratelimit: 21 messages suppressed
Oct 27 18:31:41 vb10 kernel: [ 1746.255917] lost page write due to I/O error on hdb1
Oct 27 18:31:46 vb10 kernel: [ 1751.279075] __ratelimit: 22 messages suppressed
Oct 27 18:31:46 vb10 kernel: [ 1751.279288] lost page write due to I/O error on hdb1
Oct 27 18:31:51 vb10 kernel: [ 1756.235377] __ratelimit: 20 messages suppressed
Oct 27 18:31:51 vb10 kernel: [ 1756.235377] lost page write due to I/O error on hdb1
Oct 27 18:31:56 vb10 kernel: [ 1761.304274] __ratelimit: 20 messages suppressed
Oct 27 18:31:56 vb10 kernel: [ 1761.304455] lost page write due to I/O error on hdb1
Oct 27 18:32:01 vb10 kernel: 009488] end_request: I/O error, dev hdb, sector 580247
Oct 27 18:32:03 vb10 kernel: r, dev hdb, sector 601439
Oct 27 18:32:03 vb10 kernel: [ 1767.301521] __journal_remove_journal_head: freeing b_frozen_data
^C
vb10:~# ls -l /data
ls: cannot access /data/lost+found: Input/output error
total 260968
-rw-r----- 1 root root 266964992 2008-10-27 18:30 foo.img
d????????? ? ?    ?            ?                ? lost+found
vb10:~#

It looks like iowait conditions on the host don't lead to the blocking of the virtual pci bus, which results in the disk driver to run into timeouts as per the pci spec.

Setup:

Host: 8 CPUs, 32 GB RAM, 2.8 TB RAID 5 divided into 32 logical volumes of 83 GB each, running debian lenny

VBoxes: 768 MB RAM, 1 GB ext3 root fs (hda), 11 GB ext3 data fs (hdb), running debian lenny

I have been testing throughput and stability running iozone simultaneously in different numbers of VBoxes. Corruption rate was 0 out of 4 (0/4), 5/8 and 16/16.

#2525 obsolete Keyboard and mouse freeze, Vista host, Ubuntu guest Natovr
Description

When I start up Ubuntu under Vista host, my keyboard and mouse freezes. The freeze happens as soon as I can see the Ubuntu GUI. I can't get host control back because the keyboard is frozen. I can't shut down the virtual machine because the mouse is frozen. Sceen activity continues, but no interface with the host or guest. I have to do a force shut-down to exit this state...

Also, this seems to be a random error... the graphics card driver crashes and the computer restarts by itself. I updated the driver yesterday (27 Oct 2008)

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy