Custom Query (16363 matches)
Results (826 - 828 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #842 | duplicate | Segmentation fault on registration => Fixed in 1.5.4 | ||
| Description |
After filling out the registration form I'm getting this: /usr/bin/VirtualBox: line 1: 22361 Segmentation fault LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/lib/virtualbox" /usr/lib/virtualbox/VirtualBox $@ System: AMD Athlon(tm) 64 Processor 3000+ RAM: 1.5 G SuSE 10.3 |
|||
| #843 | fixed | Using Remote Desktop crashes VM | ||
| Description |
I have a server (IP 10.27.27.3) running W2003 Server SE. It is running two VMs (W2K Pro) set up with Host Interface networking. They are both visible on the network - one with IP ...31 and the other ...32. Remote Desktop is not enabled on the real server. If I try Remote Desktop Connection from my PC (W2K Pro) to either 10.27.27.31 or 10.27.27.32 it fails to connect. If I try 10.27.27.3 (the actual server) I get an odd view of one or other of the two VMs!! and either immediately or after about a second or two I get a message that the connection has been broken. When I look at the server I find that the VM in question is no longer there - it has aborted! I have tried this several times and sometimes it was one and sometimes the other of the two VMs that had been aborted. I then enabled Remote Desktop on the server and now RD to 10.27.27.3 works as expected - it connects to the server and requests a logon. Connections to the VM's IP addresses fail. I have enabled the Remote Display on ports 3331 and 3332 respectively for the two VMs and connections still fail (using 10.27.27.31:3331/2) I don't know if this is a problem or lack of knowledge on my part. |
|||
| #844 | worksforme | Compatibility with VB 1.3.8 | ||
| Description |
After upgrading VB 1.3.8 to 1.5.2 on linux (the binary version) I have problems running VMs from older version of VB. They don't even start just their status is changet to Aborted (I hope it is this word in english - I am using Slovak language mutation). When I downgrade VB back to 1.3.8 - the machines work again. Is there some workaround? |
|||

