Custom Query (16363 matches)
Results (814 - 816 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1394 | fixed | Fail to start WinXP guest | ||
| Description |
Virtualbox v1.5.6 fails to start WinXP guest. The screen is kept as black and it seems no any activity for guest OS from the icon indication at the bottom of window. The environment I used is summairzed as below: Host PC : Pentium 4 1.5G with 512MB. Host OS : Fedora 7. Virtualbox Version: v1.5.6 Guest OS : Windows XP (The VDI is created in Ubuntu v6.10 with Virtualbox v1.5.2) The geust vdi is successfully to active by Ubuntu v6.10 in the same PC. On the other hand, my another vid (guest os: windows 2000) is successfully to active by Fedora 7 in the same PC. The log information is attached with this report. Please help to confirm the issue. Thanks a lot. |
|||
| #1402 | fixed | Linux guest will not resize | ||
| Description |
Windows guests resize very nicely, but my Debian and Ubuntu guests are static. Getting that same capability for linux would be very useful. |
|||
| #1406 | fixed | Duplicate port forwards should throw error | ||
| Description |
I accidentally setup port forwards with the same name, which caused VirtualBox to hang when starting the VM. Ideally, this should throw up an error message without hanging indefinitely. Example, in [vm].xml: <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" value="TCP"/> <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" value="22"/> <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" value="22"/> <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/Protocol" value="TCP"/> <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/GuestPort" value="80"/> <ExtraDataItem name="VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestssh/HostPort" value="80"/> This will cause an indefinite hang. Changing the name of the second port forward to something else restores normal functionality. Obviously this was my fault for cutting and pasting and not paying attention, but an error message for this type of problem would be a nice addition to stop idiots like me from spending 15 minutes trying to figure out what went wrong! :) |
|||

