-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just to add to this, I just tried vbox 1.5 under another windows
machine, using that machine's physical com1 port as the guest's serial
port, and get the same exact results there also. So, whatever is
causing this, it isn't machine-specific it looks like.

Greg


On Mon, Sep 03, 2007 at 06:41:49PM -0700, Gregory Nowak wrote:
> Hello again.
> 
> Boy, I should probably get the list fool award for today (grin). It
> turns out I wrote too soon when I said that everything works fine for
> me now under vbox 1.5. When I wrote that message, I disabled that
> program I mentioned earlier that was holding on to com2. I tried hyper
> terminal, and that worked, I started up my vm and that worked, so I
> assumed all was fine, and wrote my previous message. What I forgot was
> that in my playing around to get to the bottom of the problem, I had
> set -uartmode1 to disconnected. When I did that, everything did work,
> and I saw /dev/ttyS0 in my debian guest, but like I said, it was
> disconnected, and I didn't actually try testing it inside the guest to
> see if it works, and just assumed that it did, and I wrote my previous
> message, saying all is fine.
> 
> Anyway, I have on this system a physical com1, com2, a hardware modem
> that is set to com3. When I set -uartmode1 to any of these, the whole
> system locks up when I try to start the vm, and the end of the
> vbox.log file is just the same as I posted earlier in my first post
> today on this topic. I also have a usb to serial converter which I
> connected, and which does work, (yes, I did actually test it), and is
> set to com4. That doesn't work either when vbox is set to use it, the
> same thing happens as with com1-3. The syntax I'm using is:
> 
> vboxmanage modifyvm debian -uart1 0x03f8 4 -uartmode1 COM2
> 
> , and I get no errors, just the c:\... prompt. Running showvminfo does
> in fact show the first serial port uart1 is attached to device com2.
> 
> The serial portion of the log file doesn't show anything out of the
> ordinary as far as I can tell when it comes to the serial ports. The
> below is from when the vm is configured to use com2 as the serial
> port:
> 
> 00:07:31.792 [/Devices/serial/] (level 2)
> 00:07:31.792
> 00:07:31.792 [/Devices/serial/0/] (level 3)
> 00:07:31.792
> 00:07:31.792 [/Devices/serial/0/Config/] (level 4)
> 00:07:31.792   IRQ    <integer> = 0x0000000000000004 (4)
> 00:07:31.792   IOBase <integer> = 0x00000000000003f8 (1016)
> 00:07:31.792
> 00:07:31.792 [/Devices/serial/0/LUN#0/] (level 4)
> 00:07:31.792   Driver <string>  = "Host Serial" (cch=12)
> 00:07:31.792
> 00:07:31.792 [/Devices/serial/0/LUN#0/Config/] (level 5)
> 00:07:31.792   DevicePath <string>  = "com2" (cch=5)
> 00:07:31.792
> 
> That is the only reference to the serial port in the log.
> 
> Is there anything else I should look at? Is the syntax I'm using
> wrong? If so, then what is the correct syntax? Has anyone else tried
> out the physical serial port support under a windows host, and does it
> work for you? Again, thanks for any help in advance.
> 
> Greg
> 
> 
> -- 
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
> 
> --
> Free domains: http://www.eu.org/ or mail [EMAIL PROTECTED]
> 
> _______________________________________________
> vbox-users mailing list
> [email protected]
> http://vbox.innotek.de/mailman/listinfo/vbox-users
> 

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG3NVO7s9z/XlyUyARAvwzAJ4sglJwQGQdsIQ4ZsF5kzaz4GX/zgCeIjDc
j5WOsgFH8/22A/I95t32y1Y=
=QmaO
-----END PGP SIGNATURE-----

_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to