Custom Query (16363 matches)
Results (1495 - 1497 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1530 | duplicate | FreeBSD 7 sigreturn | ||
| Description |
I am running Virtual Box 1.6.0, now maintained by Sun Microsystems. I am running HOST: Windows x86 Vista Home Premium: Service Pack 1 GUEST: FreeBSD7-RELEASE I have ran into the same issues. I just did a fresh install and ran into this problem, just as soon as I started to install nmap from ports: /usr/ports/security/nmap As I was installing nmap a few programs were needed such as: gmake and gettext. As soon as gettext started to extract after being downloaded I ran into the problem: sigreturn: eflags = 0x80282 Here is some output: cd /usr/ports/security/nmap make install && make clean => Attempting to fetch from http://ftp.gnu.org/gnu/gettext/. gettext-0.16.1.tar.gz 100% of 8339 kB 77 kBps 00m00s ===> Extracting for gettext-0.16.1_3 => MD5 Checksum OK for gettext-0.16.1.tar.gz. => SHA256 Checksum OK for gettext-0.16.1.tar.gz. sigreturn: eflags = 0x80282 I see this problem resides in FreeBSD6.2-RELEASE, and is also present in FreeBSD7-RELEASE. Any ideas? Thanks. |
|||
| #1531 | fixed | Keyboard in guest very sluggish, some key strokes not captured | ||
| Description |
This problem has been described in full on the vbox-users mailing list. http://vbox.innotek.de/pipermail/vbox-users/2008-May/003217.html Since sending that post, I've downgraded to virtualbox 1.5.6, and things are working just as they used to. This leads me to believe the problem is with vbox 1.6.0 itself, and not with my hardware. I also installed a winxp guest for testing purposes to see if I have the same problem there, and the keyboard works just fine in the winxp guest under vbox 1.6.0. So, the problem seems to be with the gnu/linux guest only. I've attached a log of my gnu/linux guest vm running under vbox 1.6.0. The problem was so bad that I couldn't even type root <enter> my_password <enter> in order to login, and shut down the machine properly via halt. I had to use "vboxmanage controlvm debian poweroff". |
|||
| #1532 | invalid | cannot use an cloned vdi in Suse 10.3 | ||
| Description |
I clone an hd vdi using VBoxManage clonevdi, then I try to use it for a new Virtual machine. At the begininng the VM boot correctly (ask me which type of boot to use) then try to run the SO but stops and give the message: resume device not find.... waiting for device...... want me to fall back...... se attach I Use VirtualBox on Suse 10.3 and I Cloned a Suse 10.3 SO. I work under root and I moved ./virtualBox/VDI folder under /var Thanks Giangiacomo |
|||

