Custom Query (16363 matches)
Results (1738 - 1740 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9249 | obsolete | Centos 6 install with large packet count fails | ||
| Description |
Base Fedora 15, Guest Centos 6, using net-install iso Did a minimal install and worked. Did a desktop install and system locked up part way through |
|||
| #9254 | obsolete | Siemens SIMATIC USB MPI Adapter fails to install driver | ||
| Description |
Hi I would like to renew the problem PC Adapter USB has not been solved so far and also appears in the latest version of VirtualBox 4.1.0 . Symptoms are the same as in the description "Ticket #7129. " does not finish Windows install the driver. Problem występuje jedynie w wersji VirtualBox dla Linuxa. Ticket #7129.Description Hi; this device is used to connect to Siemens PLC's in the automation industry in order to program the devices. The Siemens device ID of this unit is 6ES7 972-0CB20-0XA0. Siemens provides a driver for this adapter officially at this address: http://support.automation.siemens.com/WW/adsearch/resultset.aspx?region=WW&lang=en&netmode=internet&ui=NDAwMDAxNwAA&term=usb+adapter&ID=27062840&ehbid=27062840 I'm running WinXP on a Linux Mint (Ubuntu) host. Once connected, VBox recognizes the adapter with it's name (SIMATIC USB Adapter) in the right bottom menu including all USB devices. Activating it, WinXP recognizes the adapter, starts to ask questions for the driver and finally finds the previously installed one. But the driver installation progress never ends. This definitly only happens on VBox machines. On a regular installed WinXP computer, the installation and usage of the adapter works correctly. There is a forum thread concerning this, which can be found here: http://forums.virtualbox.org/viewtopic.php?f=2&t=28932 |
|||
| #9270 | obsolete | PCI passthrough fails with general failure | ||
| Description |
A VM with a PCI device attached fails to start with a general failure. The host is a Dell Optiplex 960 with Core2 Duo 8400 (3Ghz), Q45 chipset, latest BIOS with VT-x, VT-d, TXT all on, intel_iommu=on boot option on, running Linux Mint 11. In the attached archive you should find outputs of lshw, lspci, dmesg before and after I try to start the machine, VBox.log, and vboxmanage showvminfo of the VM I'm trying to get working. If this hardware is too old, which is completely understandable, I'd just like to know what's the modern target hardware that is supposed to work. As far as I've been able to research VT-d is supposed to work on my platform. Thanks. |
|||

