VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1639 - 1641 of 16363)

Ticket Resolution Summary Owner Reporter
#8961 obsolete 4.0.8 - can't pxeboot to install x86_64 guest, similar to case 2536 google
Description

Can't gpxe boot x86_64 guest like Centos5, menu could not be loaded. After changing it to 32bit OS, then gpxe boot would work, but it means gpxe boot could not be supported with x86_64 guest.

#8964 obsolete Software problem with serial port Nike_spb
Description

Hello! My host is Win 7 64b, Intel Core i5 2400 3.1 GHz, 4 Gb RAM. I have successfully set up serial port on my vm (Win XP 32b) as described in different topics: Port1: Checked Port Number: COM1 (also tried COM2, COM3, COM4) Port Mode: Host Device Port/File Path: COM1 (tried others, see further)

The problem is in connecting to devices via com port. It's not a physical problem, because I've tried to use pci2com controller, usb-rs232 adapter and on-board com port. Settings are: 9600 / 8 / odd / 1 / no flow control. I have to use a monitoring program to log what's happening with com port (see all attachments, except vbox.log). I have used 2 different programs OIL-DS 1.3, T-PDS32 for Windows 2.21. OIL-DS 1.3 always works fine. T-PDS32 doesn't work.

Why is this a virtualbox problem?

1) T-PDS32 works great on any other PC (not virtual)

2) T-PDS32 establishes a connection with a PLC after the settings of the com port have been reset by downloading (or trying to) something via this port by another software - OIL-DS. My guess is that it somehow resets port's parameters and after that T-PDS can work for some time. After reconnecting - again connection problem. See the log file tpds_oil_tpds.txt - there I've tried to connect using T-PDS (no success), then OIL-DS, then T-PDS again (successfully).

3) I've tried to establish the connection with com port using OIL-DS both on host and on vm using exactly the same settings. The behaviour is different (see host_log and vm_log files).

In whole I think that means:

1) it's a software problem

2) virtualbox somehow modifyes the data which is send to com port (and in result some programs can work unstable)

Looking forward to your help. Thank you.

#8965 obsolete OpenVPN linux bridge server no longer able to bridge to network after upgrade to 4.0.6 or 4.0.8 James Riggs
Description

I am running an Ubuntu 11.04 server guest OS on a windows 7 64bit host. Ubuntu runs a bridge OpenVPN server. After an upgrade to either 4.0.6 or 4.0.8, clients can connect to the server, but no traffic is passed over the bridge. I can ping the server from the client, but cannot get to any machine on the other side of the bridge.

The bridge device, br0, is made up of the tap0 and eth0 devices.

Once I downgrade VirtualBox back to 4.0.4, the bridge device once again passes traffic.

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