Custom Query (16363 matches)
Results (1810 - 1812 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1849 | fixed | direct COM port connection on solaris is not working => Fixed in SVN | ||
| Description |
when enabling COM port as Host Device on Solaris host machine in any Guest it prints out the error VERR_PDM_DRIVER_NOT_FOUND output of: #VBoxManage showvminfo test VirtualBox Command Line Management Interface Version 1.6.2 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Name: test Guest OS: OpenSolaris UUID: dae0987b-2957-4aa5-d385-d80bf105d567 Config file: /root/.VirtualBox/Machines/test/test.xml Memory size: 512MB VRAM size: 8MB Boot menu mode: message and menu ACPI: on IOAPIC: off PAE: off Time offset: 0 ms Hardw. virt.ext: off State: powered off (since 2008-07-18T00:22:01.726000000) Monitor count: 1 Floppy: empty SATA: disabled Primary master: /root/.VirtualBox/VDI/test.vdi (UUID: 30f09791-8463-4312-3a96-ac7bbc53bb49) DVD: empty NIC 1: MAC: 00144FFFFFFE, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps NIC 2: disabled NIC 3: disabled NIC 4: disabled UART 1: I/O base: 0x03f8, IRQ: 4, attached to device '/devices/isa/asy@1,3f8:a' UART 2: disabled Audio: disabled (Driver: Unknown, Controller: Unknown) Clipboard Mode: Bidirectional VRDP: disabled USB: disabled USB Device Filters: <none> Shared folders: <none> Guest: Statistics update: disabled important line: UART 1: I/O base: 0x03f8, IRQ: 4, attached to device '/devices/isa/asy@1,3f8:a' changing it to /dev/term/a or /dev/ttya doesn't help running as root also didn't help. Looks like it is not recognized on solaris. |
|||
| #1850 | worksforme | command line VBoxManage modifyvm -uartmode is not working | ||
| Description |
VBoxManage modifyvm S10 -uartmode1 server "/tmp/vb1" is not working. Same setting, but configured through GUI is working fine. Calling it acording to VBoxManage usage help. I need this to have hands of installation and configuration of Virtualbox and Vm's through command line and telnet. output of command: # VBoxManage modifyvm S10 -uartmode1 '/tmp/vb1'
VirtualBox Command Line Management Interface Version 1.6.2
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.
[!] FAILED calling uart->SetHostMode (PortMode::HostDevice) at line 5180!
[!] Primary RC = NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value
[!] Full error info present: true , basic error info present: true
[!] Result Code = NS_ERROR_INVALID_ARG (0x80070057) - Invalid argument value
[!] Text = Cannot set the host device mode of the serial port 0 because the device path is empty or null
[!] Component = SerialPort, Interface: ISerialPort, {937f6970-5103-4745-b78e-d28dcf1479a8}
[!] Callee = ISerialPort, {937f6970-5103-4745-b78e-d28dcf1479a8}
output of VBoxManage showvminfo before running command # VBoxManage showvminfo S10 VirtualBox Command Line Management Interface Version 1.6.2 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Name: S10 Guest OS: Solaris UUID: 04e68f9c-7dd4-4a41-c693-58a7dd45d00b Config file: /root/.VirtualBox/Machines/S10/S10.xml Memory size: 512MB VRAM size: 8MB Boot menu mode: message and menu ACPI: on IOAPIC: off PAE: off Time offset: 0 ms Hardw. virt.ext: off State: powered off (since 2008-07-16T23:42:42.000000000) Monitor count: 1 Floppy: empty SATA: disabled Primary master: /root/.VirtualBox/VDI/S10.vdi (UUID: 15acc63d-e232-4ef7-3797-8bce6caedd65) DVD: /net/dorfl.czech/export/install/iso/solaris_media/s10u6/03/i86pc/solarisdvd.iso (UUID: 393b9add-c0e6-4a77-44a5-f35dff664778) NIC 1: MAC: 080027A0754B, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps NIC 2: disabled NIC 3: disabled NIC 4: disabled UART 1: I/O base: 0x03f8, IRQ: 4, disconnected UART 2: disabled Audio: disabled (Driver: Unknown, Controller: Unknown) Clipboard Mode: Bidirectional VRDP: disabled USB: disabled USB Device Filters: <none> Shared folders: <none> Guest: Statistics update: disabled vminfo after configuring through gui: # VBoxManage showvminfo S10 VirtualBox Command Line Management Interface Version 1.6.2 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Name: S10 Guest OS: Solaris UUID: 04e68f9c-7dd4-4a41-c693-58a7dd45d00b Config file: /root/.VirtualBox/Machines/S10/S10.xml Memory size: 512MB VRAM size: 8MB Boot menu mode: message and menu ACPI: on IOAPIC: off PAE: off Time offset: 0 ms Hardw. virt.ext: off State: powered off (since 2008-07-16T23:42:42.000000000) Monitor count: 1 Floppy: empty SATA: disabled Primary master: /root/.VirtualBox/VDI/S10.vdi (UUID: 15acc63d-e232-4ef7-3797-8bce6caedd65) DVD: /net/dorfl.czech/export/install/iso/solaris_media/s10u6/03/i86pc/solarisdvd.iso (UUID: 393b9add-c0e6-4a77-44a5-f35dff664778) NIC 1: MAC: 080027A0754B, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps NIC 2: disabled NIC 3: disabled NIC 4: disabled UART 1: I/O base: 0x03f8, IRQ: 4, attached to pipe (server) '/tmp/vb1' UART 2: disabled Audio: disabled (Driver: Unknown, Controller: Unknown) Clipboard Mode: Bidirectional VRDP: disabled USB: disabled USB Device Filters: <none> Shared folders: <none> Guest: Statistics update: disabled |
|||
| #1851 | fixed | Telnet connection to VM's com port | ||
| Description |
This would be appreciated by many people trying to automate VBox installations and VM testing. Proposal: another option in COM port, like Host Pipe but lets say Host Port which will forward everithing from VM's ttya to some TCP port. User than can telnet to that port on host machine and with for example expect automate installation, machine configuration, running of tests, or whatever. I have written small python server which simulates this behaviour. it is in attachment. it is just some quick proof of concept written in 10 mins. it is using Host Pipe configuration and is simply reading from unix socket configured there and formwarding everithing to TCP, same can be done with program called socat. there are still some issues though. Like sending inputs twice. This with adition to ticket http://www.virtualbox.org/ticket/1850 will lead to fully automated installtion and testing of VirtualBox. |
|||

