Custom Query (16363 matches)
Results (1627 - 1629 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1558 | fixed | PC-BSD v1.5 x86 & x64 dies during installation in VirtualBox v1.6.0 | ||
| Description |
I´m running VirtualBox v1.6 on a Windows XP SP2 Host here. Guest was PC-BSD v1.5 x86 as well as PC-BSD v1.5 x64 PC-BSD dies during the installation (see attached screen shot). Seems to me that PC-BSD is unable to load the shell. I tried both Free-BSD as well as None/Unknown for the Guest OS. None of them seems to work. The problem seems not to be related to the Host CPU. I tried at home (Opteron 170 with 2GB RAM) as well as at work (Core2 Duo T7500 with 2GB RAM). I tried both SATA as well as EIDE for the virtual HDD but this didn´t help either. Sorry to say but VMWare Server 1.0.4 installs and runs PC-BSD fine on my work PC. Installation worked like a charm without any hickups and the FreeBSD VMWare extensions work fine for PC-BSD. |
|||
| #4197 | invalid | VirtualBox not working with FreeNAS iSCSI targets | ||
| Description |
I'm using an Ubuntu 8.10 AMD64 host here running VirtualBox 2.2.2 r46594. I've set up an iSCSI target using FreeNAS with the following version: 0.69.1 Omnius (revision 4554) built on Sat Apr 18 23:20:57 UTC 2009 I've added the iSCSI target I generated to the available VBox medias with the following command: VBoxManage addiscsidisk --server 192.168.0.166 --target iqn.1994-04.org.netbsd.iscsi-target:target0 The target was correctly added (at least VBox doesn`t report any issues). Unfortunately VBox reports the iSCSI target always as not ready / unaccessable. When I attach the target to a VM and start the machine with an ISO attached for guest OS installation the following message appears: Medium '192.168.0.166|iqn.1994-04.org.netbsd.iscsi-target:target0' is not accessible. Could not open the hard disk '192.168.0.166|iqn.1994-04.org.netbsd.iscsi-target:target0'. VD: error opening image file '192.168.0.166|iqn.1994-04.org.netbsd.iscsi-target:target0' (VERR_TIMEOUT). Fehlercode: NS_ERROR_FAILURE (0x80004005) Komponente: Machine Interface: IMachine {13420cbb-175a-4456-85d0-301126dfdec7} I can at least confirm that iSCSI targets generated with FreeNAS work fine with a WinXP host and the Microsoft iSCSI initiator. I can perfectly access those targets, format the "disk" and assign them to the host. On the other hand I could use the VBox iSCSI feature by setting up an iSCSI target with the userspace implementation on my Ubuntu host. Strange.... |
|||
| #4198 | obsolete | OpenGL "speed issue" with Quake2 | ||
| Description |
I've been experimenting with gaming within a VBox guest since the support for Guest OpenGL has been added. Unfortunately Quake 2 has some problems with VBox OpenGL. It's not that the OpenGL driver is too slow but there a inconsistent timing issues causing the game to be unplayable. Interestingly enough OpenGL itself seems to be very performant. Using the old 3Fingers demo (crusher.dm2 and massive1.dm2) I get around 90 and 100 FPS which equals the performance I got back then with my PII-400 and 2x12 MB Voodoo2 in SLI mode. I would call this bad. Since gtk-recordmydesktop is not fast enough to capture those speedissues I decided to capture a small video with my digicam. At first you'll see the two demos I mentioned and the fast rendering speed. Then I launch the first intro demo where you experience the slowdowns. At last I start a single player game where I guess the problem becomes obvious. You can have a look at the video over at youtube: http://www.youtube.com/watch?v=Mw9-igE0neI A movie can say more than thousand words :) I have attached my VBox.log Host is an Ubuntu 8.10 AMD64 machine running VBox 2.2.2 Guest is a WinXP SP2 with the latest guest additions installed and 3D accelleration enabled. The VM has 1024 MB RAM and 128 MB graphic memory. Physical host: Opteron 170 3 GB RAM GeForce 7900GS graphic adapter with 256 MB RAM |
|||

