[Call for Testers] VirtualBox 4.2.0 BETA1
Hi guys! It's that time of the year again since Oracle has released VirtualBox 4.2.0 BETA1 yesterday. Many thanks to Alexander Eichner who fixed the last major blocker in the kernel module a few days ago. So the release seems to work quite okay with limited testing. But we had such situations before so the response from the CFT will show us where we really are. Many thanks also to all individuals who send patches and report bugs and especially to Mikhail Tsatsenko who joined the vbox team recently and is doing a great job! Thanks! But please keep in mind that we are still searching for help so if you have some time and motivation to help please join us on IRC for futher details. Please ensure that your Kernel sources match your running kernel before building the virtualbox-ose-kmod-devel port! Changes since VirtualBox 4.1: https://forums.virtualbox.org/viewtopic.php?f=15&t=50763 VirtualBox 4.2.0 BETA1 Ports: http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.0-20120804.tar.gz IRC: #freebsd-vbox on Freenode Bernhard on behalf of the new VirtualBox on FreeBSD Team! -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
VirtualBox on FreeBSD is looking for you!
Hi VirtualBox users! We are again at the point where I am kindly asking if someone is interested to help with the VirtualBox on FreeBSD work. We started with an active team of around 3 people but since about one year I ended up being a lonely ranger. Maintaining such a beast/high profile port by a single person is not possible for a longer period so we should really try to form a team to improve the situation. Additionally I started working on redports.org which requires more and more time so I cannot dedicate all my work to virtualbox. The situation of the port right now is not bad but I always end up fire fighting and only concentrate on serious problems due to the limited time I have. So it happens that people send bugreports and patches for virtualbox and don't get a response for weeks if at all. A lot of bugs that we have since day one are still present and the list of items that we should seriously do is getting longer. Many things of them are userland and porting stuff but there are also a lot of things to do in the kernel modules. Andriy Gapon has rewritten the r0 memory allocation stuff which significantly improved the situation in that area but the networking kernel modules are still in a bad shape. There are various known bugs (performance problems, instabilities, ...) in that area so it would be great if someone with networking expertise could have a look at the code. The USB stuff needs some love too. It is there but only works for a few special combinations of Device and Guest OS. Since VirtualBox 4.1 there is experimental support for PCI Passthrough so if we want that we need some Kernel API for the Intel/AMD IOMMU. I think the IOMMU code has already been written for BeHyVe so we need someone who puts all the stuff together and wants to find out how to integrate that in the kernel and vbox. The vbox developers offered their help on that but they need a Kernel API before we can start talking about it. So what is it that the virtualbox team needs to do? - regulary test latest SVN sources to find new problems early (build, runtime testing, create build fixes) - maintain all 8 ports (changes in CURRENT or other port updates keep breaking virtualbox around once per month) - update ports to new bugfix releases - review patches from the community and send them upstream then nag vbox developers to get them committed - help users to diagnose problems (help debugging, get stacktraces, collect information, give hints) - further porting efforts (coordinate and probably do it yourself) - optionsng adaptions - FreeBSD installer for the vbox additions to be able to build a VBoxAdditions.iso with FreeBSD support - implement vboxsf support (Shared Folders) - PCI Passthrough support - USB support (needs fixing) - Networking support (needs fixing) It is unrealistic that one single person can do a majority of these things so we seriously need a few people from different areas to improve the situation. Be it kernel developers, ports people or just power users that can help testing and diagnosing bugs. If you have an interest in VirtualBox on FreeBSD and a few spare cycles please get in contact with us (me?) to coordinate the further steps. I will do my best to help answering questions and help you with your first steps in vbox land. Don't worry if you think you are not experienced enough for the task. We all started that way and you get the chance to learn a lot - it just needs some time to get used to it. I have also created a dedicated VirtualBox on FreeBSD channel on freenode: #freebsd-vbox so you're welcome to join us! -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: one virtualbox vm disrupts all vms and entire network
On 05.06.2012 20:16, Bernhard Froehlich wrote: On 05.06.2012 19:05, Steve Tuts wrote: On Mon, Jun 4, 2012 at 4:11 PM, Rusty Nejdl wrote: On 2012-06-02 12:16, Steve Tuts wrote: Hi, we have a Dell poweredge server with a dozen interfaces. It hosts a few guests of web app and email servers with VirtualBox-4.0.14. The host and all guests are FreeBSD 9.0 64bit. Each guest is bridged to a distinct interface. The host and all guests are set to 10.0.0.0 network NAT'ed to a cicso router. This runs well for a couple months, until we added a new guest recently. Every few hours, none of the guests can be connected. We can only connect to the host from outside the router. We can also go to the console of the guests (except the new guest), but from there we can't ping the gateway 10.0.0.1 any more. The new guest just froze. Furthermore, on the host we can see a vboxheadless process for each guest, including the new guest. But we can not kill it, not even with "kill -9". We looked around the web and someone suggested we should use "kill -SIGCONT" first since the "ps" output has the "T" flag for that vboxheadless process for that new guest, but that doesn't help. We also tried all the VBoxManager commands to poweroff/reset etc that new guest, but they all failed complaining that vm is in Aborted state. We also tried VBoxManager commands to disconnect the network cable for that new guest, it didn't complain, but there was no effect. For a couple times, on the host we disabled the interface bridging that new guest, then that vboxheadless process for that new guest disappeared (we attempted to kill it before that). And immediately all other vms regained connection back to normal. But there is one time even the above didn't help - the vboxheadless process for that new guest stubbonly remains, and we had to reboot the host. This is already a production server, so we can't upgrade virtualbox to the latest version until we obtain a test server. Would you advise: 1. is there any other way to kill that new guest instead of rebooting? 2. what might cause the problem? 3. what setting and test I can do to analyze this problem? __**_ I haven't seen any comments on this and don't want you to think you are being ignored but I haven't seen this but also, the 4.0 branch was buggier for me than the 4.1 releases so yeah, upgrading is probably what you are looking at. Rusty Nejdl __**_ sorry, just realize my reply yesterday didn't go to the list, so am re-sending with some updates. Yes, we upgraded all ports and fortunately everything went back and especially all vms has run peacefully for two days now. So upgrading to the latest virtualbox 4.1.16 solved that problem. But now we got a new problem with this new version of virtualbox: whenever we try to vnc to any vm, that vm will go to Aborted state immediately. Actually, merely telnet from within the host to the vnc port of that vm will immediately Abort that vm. This prevents us from adding new vms. Also, when starting vm with vnc port, we got this message: rfbListenOnTCP6Port: error in bind IPv6 socket: Address already in use , which we found someone else provided a patch at http://permalink.gmane.org/gmane.os.freebsd.devel.emulation/10237 So looks like when there are multiple vms on a ipv6 system (we have 64bit FreeBSD 9.0) will get this problem. Glad to hear that 4.1.16 helps for the networking problem. The VNC problem is also a known one but the mentioned patch does not work at least for a few people. It seems the bug is somewhere in libvncserver so downgrading net/libvncserver to an earlier version (and rebuilding virtualbox) should help until we come up with a proper fix. You are right about the "Address already in use" problem and the patch for it so I will commit the fix in a few moments. I have also tried to reproduce the VNC crash but I couldn't. Probably because my system is IPv6 enabled. flo@ has seen the same crash and has no IPv6 in his kernel which lead him to find this commit in libvncserver: commit 66282f58000c8863e104666c30cb67b1d5cbdee3 Author: Kyle J. McKay Date: Fri May 18 00:30:11 2012 -0700 libvncserver/sockets.c: do not segfault when listenSock/listen6Sock == -1 http://libvncserver.git.sourceforge.net/git/gitweb.cgi?p=libvncserver/libvncserver;a=commit;h=66282f5 It looks promising so please test this patch if you can reproduce the crash. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: one virtualbox vm disrupts all vms and entire network
On 05.06.2012 19:05, Steve Tuts wrote: On Mon, Jun 4, 2012 at 4:11 PM, Rusty Nejdl wrote: On 2012-06-02 12:16, Steve Tuts wrote: Hi, we have a Dell poweredge server with a dozen interfaces. It hosts a few guests of web app and email servers with VirtualBox-4.0.14. The host and all guests are FreeBSD 9.0 64bit. Each guest is bridged to a distinct interface. The host and all guests are set to 10.0.0.0 network NAT'ed to a cicso router. This runs well for a couple months, until we added a new guest recently. Every few hours, none of the guests can be connected. We can only connect to the host from outside the router. We can also go to the console of the guests (except the new guest), but from there we can't ping the gateway 10.0.0.1 any more. The new guest just froze. Furthermore, on the host we can see a vboxheadless process for each guest, including the new guest. But we can not kill it, not even with "kill -9". We looked around the web and someone suggested we should use "kill -SIGCONT" first since the "ps" output has the "T" flag for that vboxheadless process for that new guest, but that doesn't help. We also tried all the VBoxManager commands to poweroff/reset etc that new guest, but they all failed complaining that vm is in Aborted state. We also tried VBoxManager commands to disconnect the network cable for that new guest, it didn't complain, but there was no effect. For a couple times, on the host we disabled the interface bridging that new guest, then that vboxheadless process for that new guest disappeared (we attempted to kill it before that). And immediately all other vms regained connection back to normal. But there is one time even the above didn't help - the vboxheadless process for that new guest stubbonly remains, and we had to reboot the host. This is already a production server, so we can't upgrade virtualbox to the latest version until we obtain a test server. Would you advise: 1. is there any other way to kill that new guest instead of rebooting? 2. what might cause the problem? 3. what setting and test I can do to analyze this problem? __**_ I haven't seen any comments on this and don't want you to think you are being ignored but I haven't seen this but also, the 4.0 branch was buggier for me than the 4.1 releases so yeah, upgrading is probably what you are looking at. Rusty Nejdl __**_ sorry, just realize my reply yesterday didn't go to the list, so am re-sending with some updates. Yes, we upgraded all ports and fortunately everything went back and especially all vms has run peacefully for two days now. So upgrading to the latest virtualbox 4.1.16 solved that problem. But now we got a new problem with this new version of virtualbox: whenever we try to vnc to any vm, that vm will go to Aborted state immediately. Actually, merely telnet from within the host to the vnc port of that vm will immediately Abort that vm. This prevents us from adding new vms. Also, when starting vm with vnc port, we got this message: rfbListenOnTCP6Port: error in bind IPv6 socket: Address already in use , which we found someone else provided a patch at http://permalink.gmane.org/gmane.os.freebsd.devel.emulation/10237 So looks like when there are multiple vms on a ipv6 system (we have 64bit FreeBSD 9.0) will get this problem. Glad to hear that 4.1.16 helps for the networking problem. The VNC problem is also a known one but the mentioned patch does not work at least for a few people. It seems the bug is somewhere in libvncserver so downgrading net/libvncserver to an earlier version (and rebuilding virtualbox) should help until we come up with a proper fix. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: virtualbox-ose-additions broken?
The bug was just fixed by des in HEAD in r236614 [1]. I've created a patch for 9-STABLE that includes r236177 and r236614 which should fix the virtualbox-ose-additions compile error. http://home.bluelife.at/patches/libsupcpp-fix-new-operator-9-STABLE.diff Feedback would be welcome. [1] http://svnweb.freebsd.org/base?view=revision&revision=236614 -- Bernhard Froehlich http://www.bluelife.at/ On 05.06.2012 12:56, Bernhard Froehlich wrote: We have such an output from 10-current/amd64 now. http://pastebin.com/cVd8ryxG It seems that those 5 symbols are missing for amd64: 90d0 t _Znam 90b0 t _ZnamRKSt9nothrow_t 9220 t _Znwm 93f0 t _ZnwmPv 9110 t _ZnwmRKSt9nothrow_t Add them to Version.map like in r236177 and recompile libsupc++ or world and try again rebuilding vbox additions: http://svnweb.freebsd.org/base/head/gnu/lib/libsupc%2B%2B/Version.map?r1=236177&r2=236176&pathrev=236177 -- Bernhard Froehlich http://www.bluelife.at/ On 05.06.2012 12:06, Bernhard Froehlich wrote: That was a good hint! It seems the newly added libsupc++ causes that problems because until very recently the new operator symbols were not included. They have been added on current as of r236177 http://svnweb.freebsd.org/base?view=revision&revision=236177 On 9-STABLE the situation is that libstdc++/libsupc++ was already MFCd but that fix from head for thew new operator wasn't yet. So it currently fails on 9-STABLE. According to David that fix for the new operator also seems to have no affect on amd64 so the symbols probably have a different name there. I've already talked to DES about that and we need some nm output of latest libsupc++ on HEAD / amd64 to find the symbol names and add them to the map. So who can provide the nm output? -- Bernhard Froehlich http://www.bluelife.at/ On 05.06.2012 10:44, David Morgan wrote: On 10:13 Tue 05 Jun , Andriy Gapon wrote: on 05/06/2012 08:37 Bernhard Fröhlich said the following: > Shit. I have only seen that compile errors on head yet but was unable to find out what caused it. It seems it was MFCd now. Any hints are very appreciated. It looks like a C compiler (cc) is used to link C++ code. I think that adding -lstdc++ may fix the problem, but a better solution would be to use c++ instead of cc. That's correct - re-running the failing command with gcc gives the same error, with g++ it succeeds. If I recall correctly adding -lstdc++ doesn't fix it. A change was made to Version.map for libsupc++ recently, which apparently made this compile correctly on i386, but didn't solve the problem for me on amd64. > Creating a PR is probably worthless as I am usually the only one that looks at them. emulation@ covers a wider audience of people that care about vbox and are able to debug and fix bugs. Thanks for the report and getting my attention! > > > On Mo., 4. Jun. 2012 23:19:19 CEST, Kris Moore wrote: > >> Before I file a PR, is anybody else experiencing this with the latest VB >> on 9-STABLE? >> >> - >> >> kBuild: Linking VBoxClient >> kBuild: Pass - Other Stuff >> kBuild: Pass - Staging >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `VBoxClient::GetClipboardService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `~Service': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `~ClipboardService': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `VBoxClient::GetSeamlessService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `~VBoxGuestThrea
Re: virtualbox-ose-additions broken?
We have such an output from 10-current/amd64 now. http://pastebin.com/cVd8ryxG It seems that those 5 symbols are missing for amd64: 90d0 t _Znam 90b0 t _ZnamRKSt9nothrow_t 9220 t _Znwm 93f0 t _ZnwmPv 9110 t _ZnwmRKSt9nothrow_t Add them to Version.map like in r236177 and recompile libsupc++ or world and try again rebuilding vbox additions: http://svnweb.freebsd.org/base/head/gnu/lib/libsupc%2B%2B/Version.map?r1=236177&r2=236176&pathrev=236177 -- Bernhard Froehlich http://www.bluelife.at/ On 05.06.2012 12:06, Bernhard Froehlich wrote: That was a good hint! It seems the newly added libsupc++ causes that problems because until very recently the new operator symbols were not included. They have been added on current as of r236177 http://svnweb.freebsd.org/base?view=revision&revision=236177 On 9-STABLE the situation is that libstdc++/libsupc++ was already MFCd but that fix from head for thew new operator wasn't yet. So it currently fails on 9-STABLE. According to David that fix for the new operator also seems to have no affect on amd64 so the symbols probably have a different name there. I've already talked to DES about that and we need some nm output of latest libsupc++ on HEAD / amd64 to find the symbol names and add them to the map. So who can provide the nm output? -- Bernhard Froehlich http://www.bluelife.at/ On 05.06.2012 10:44, David Morgan wrote: On 10:13 Tue 05 Jun , Andriy Gapon wrote: on 05/06/2012 08:37 Bernhard Fröhlich said the following: > Shit. I have only seen that compile errors on head yet but was unable to find out what caused it. It seems it was MFCd now. Any hints are very appreciated. It looks like a C compiler (cc) is used to link C++ code. I think that adding -lstdc++ may fix the problem, but a better solution would be to use c++ instead of cc. That's correct - re-running the failing command with gcc gives the same error, with g++ it succeeds. If I recall correctly adding -lstdc++ doesn't fix it. A change was made to Version.map for libsupc++ recently, which apparently made this compile correctly on i386, but didn't solve the problem for me on amd64. > Creating a PR is probably worthless as I am usually the only one that looks at them. emulation@ covers a wider audience of people that care about vbox and are able to debug and fix bugs. Thanks for the report and getting my attention! > > > On Mo., 4. Jun. 2012 23:19:19 CEST, Kris Moore wrote: > >> Before I file a PR, is anybody else experiencing this with the latest VB >> on 9-STABLE? >> >> - >> >> kBuild: Linking VBoxClient >> kBuild: Pass - Other Stuff >> kBuild: Pass - Staging >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `VBoxClient::GetClipboardService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `~Service': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `~ClipboardService': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `VBoxClient::GetSeamlessService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `~VBoxGuestThreadFunction': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `~VBoxGuestSeamlessObserver': >> /usr/ports/emulators/virtualbox-ose-additions/work/Virtual
Re: virtualbox-ose-additions broken?
That was a good hint! It seems the newly added libsupc++ causes that problems because until very recently the new operator symbols were not included. They have been added on current as of r236177 http://svnweb.freebsd.org/base?view=revision&revision=236177 On 9-STABLE the situation is that libstdc++/libsupc++ was already MFCd but that fix from head for thew new operator wasn't yet. So it currently fails on 9-STABLE. According to David that fix for the new operator also seems to have no affect on amd64 so the symbols probably have a different name there. I've already talked to DES about that and we need some nm output of latest libsupc++ on HEAD / amd64 to find the symbol names and add them to the map. So who can provide the nm output? -- Bernhard Froehlich http://www.bluelife.at/ On 05.06.2012 10:44, David Morgan wrote: On 10:13 Tue 05 Jun , Andriy Gapon wrote: on 05/06/2012 08:37 Bernhard Fröhlich said the following: > Shit. I have only seen that compile errors on head yet but was unable to find out what caused it. It seems it was MFCd now. Any hints are very appreciated. It looks like a C compiler (cc) is used to link C++ code. I think that adding -lstdc++ may fix the problem, but a better solution would be to use c++ instead of cc. That's correct - re-running the failing command with gcc gives the same error, with g++ it succeeds. If I recall correctly adding -lstdc++ doesn't fix it. A change was made to Version.map for libsupc++ recently, which apparently made this compile correctly on i386, but didn't solve the problem for me on amd64. > Creating a PR is probably worthless as I am usually the only one that looks at them. emulation@ covers a wider audience of people that care about vbox and are able to debug and fix bugs. Thanks for the report and getting my attention! > > > On Mo., 4. Jun. 2012 23:19:19 CEST, Kris Moore wrote: > >> Before I file a PR, is anybody else experiencing this with the latest VB >> on 9-STABLE? >> >> - >> >> kBuild: Linking VBoxClient >> kBuild: Pass - Other Stuff >> kBuild: Pass - Staging >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `VBoxClient::GetClipboardService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:305: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `~Service': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/VBoxClient.h:38: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o: >> In function `~ClipboardService': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/clipboard.cpp:282: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `VBoxClient::GetSeamlessService()': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless.cpp:58: >> undefined reference to `operator new(unsigned long)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `~VBoxGuestThreadFunction': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/thread.h:33: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `~VBoxGuestSeamlessObserver': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-glue.h:26: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o: >> In function `VBoxGuestWinCleanup(VBoxGuestWinInfo*, void*)': >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/src/VBox/Additions/x11/VBoxClient/seamless-x11.h:81: >> undefined reference to `operator delete(void*)' >> /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freeb
Re: virtualbox-ose-additions broken?
The below link is wrong but here it is: http://wiki.freebsd.org/VirtualBox/ToDo I will add the open problems in a few minutes. -- Bernhard Fröhlich http://www.bluelife.at/ On 05.06.2012 07:45, Bernhard Fröhlich wrote: vbox never had a lot of PRs but we maintain a wiki page with almost all vbox problems that users reported (mailinglists, private mail, irc, ...). http://wiki.freebsd.org/Virtualbox/ToDo I will add the currently missing reports once I am on a device with a proper kwertz keyboard. On Di., 5. Jun. 2012 07:38:32 CEST, Eitan Adler wrote: On 5 June 2012 01:37, Bernhard Fröhlich wrote: > Shit. I have only seen that compile errors on head yet but was unable > to find out what caused it. It seems it was MFCd now. Any hints are > very appreciated. > > Creating a PR is probably worthless as I am usually the only one that > looks at them. emulation@ covers a wider audience of people that care > about vbox and are able to debug and fix bugs. Thanks for the report > and getting my attention! Can you please submit a PR anyways? It is good to have some kind of 'official' record of what needs to be fixed. -- Eitan Adler ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org" ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Can't launch virtualbox-ose-4.1.14
On 09.05.2012 09:55, Quentin SCHWERKOLT wrote: I'm unable to launch VirtualBox-ose 4.1.14 on FreeBSD 9.0-RELEASE and FreeBSD 9-STABLE. I try install it with ports and pkg_add and when I launch VirtualBox, an error window appear witch said: "Failed to create the VirtualBox COM object. The application will now terminate.", and the detail is "Callee RC: NS_ERROR_ABORT (0x80004004)" and a core dump is generated. Please compile the emulators/virtualbox-ose port with DEBUG option enabled and send ~/.VirtualBox/VBoxSVC.log when it fails. As you have a coredump please generate a stacktrace and send that too. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VBox upgrade fails
On 20.04.2012 02:10, Petro Rossini wrote:
On Thu, Apr 19, 2012 at 5:33 PM, AN wrote:
On Thu, 19 Apr 2012, Petro Rossini wrote:
On Thu, Apr 19, 2012 at 6:02 AM, AN wrote:
# portupgrade -va
---> Session started at: Wed, 18 Apr 2012 15:56:15 -0400
---> Upgrade of emulators/virtualbox-ose-kmod started at: Wed, 18
Apr
---> Upgrading 'virtualbox-ose-kmod-4.1.8_1' to
'virtualbox-ose-kmod-4.1.12' (emulators/virtualbox-ose-kmod)
---> Build of emulators/virtualbox-ose-kmod started at: Wed, 18
Apr 2012
---> Building '/usr/ports/emulators/virtualbox-ose-kmod'
===> Cleaning for virtualbox-ose-kmod-4.1.12
cd
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.12/out/freebsd.amd64/release/bin/src
&& make SYSDIR=/usr/src/sys
*** Building 'vboxdrv' module ***
"/usr/share/mk/bsd.own.mk", line 483: MK_CLANG_IS_CC can't be set
by a
user.
*** [all] Error code 1
I think it is a problem with the file /usr/share/mk/bsd.own.mk. I
will
send a message to the ports list.
According to
http://www.freebsd.org/cgi/cvsweb.cgi/src/share/mk/bsd.own.mk,
Revision 1.107.2.5,
this parameter decides whether the CLANG compiler is installed as
/usr/bin/cc.
VirtualBox does not install the cc (that's done by installworld of
the
base system build) so to set the variable here does not make sense
to
me.
The following fix was provided by someone on the ports list.
cd /usr/ports/emulators/virtualbox-ose-kmod/files &&
rm patch-src_VBox_HostDrivers_Support_freebsd_Makefile
patch-src_VBox_HostDrivers_VBoxNetAdp_freebsd_Makefile
patch-src_VBox_HostDrivers_VBoxNetFlt_freebsd_Makefile
and start the update again
VBox upgrade completed successfully.
I am guessing why it was there in the first place:
To test whether the cc is CLANG?
Does VirtualBox compile work on a CLANG compiled system?
No VirtualBox cannot be compiled with CLANG because it doesn't support
global register variables. So you get:
src/recompiler/target-i386/exec.h:41:30: error: global register
variables are not supported
register struct CPUX86State *env asm(AREG0);
The patches were made by sobomax to fix that problem on RELENG_9:
kBuild: Installing
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.12/out/freebsd.amd64/release/bin/src/vboxnetflt/Makefile
cd
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.12/out/freebsd.amd64/release/bin/src
&& make SYSDIR=/usr/src/sys
*** Building 'vboxdrv' module ***
"/usr/src/sys/conf/kmod.mk", line 116: Malformed conditional
(${MK_CLANG_IS_CC} == "no" && ${CC:T:Mclang} != "clang")
"/usr/src/sys/conf/kmod.mk", line 120: if-less endif
"/usr/src/sys/conf/kern.mk", line 18: Malformed conditional
(${MK_CLANG_IS_CC} != "no" || ${CC:T:Mclang} == "clang")
"/usr/src/sys/conf/kern.mk", line 31: if-less endif
"/usr/src/sys/conf/kern.mk", line 101: Malformed conditional
(${MK_CLANG_IS_CC} != "no" || ${CC:T:Mclang} == "clang")
"/usr/src/sys/conf/kern.mk", line 107: if-less endif
make: fatal errors encountered -- cannot continue
*** Error code 1
As it seems those patches cause more problems than they solve so I'm
going to remove them.
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VBox upgrade fails (ML_CLANG_IS_CC again)
On 19.04.2012 09:33, AN wrote:
On Thu, 19 Apr 2012, Petro Rossini wrote:
On Thu, Apr 19, 2012 at 6:02 AM, AN wrote:
# portupgrade -va
---> Session started at: Wed, 18 Apr 2012 15:56:15 -0400
---> Upgrade of emulators/virtualbox-ose-kmod started at: Wed, 18
Apr 2012
15:57:23 -0400
---> Upgrading 'virtualbox-ose-kmod-4.1.8_1' to
'virtualbox-ose-kmod-4.1.12' (emulators/virtualbox-ose-kmod)
---> Build of emulators/virtualbox-ose-kmod started at: Wed, 18
Apr 2012
15:57:23 -0400
---> Building '/usr/ports/emulators/virtualbox-ose-kmod'
===> Cleaning for virtualbox-ose-kmod-4.1.12
cd
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.12/out/freebsd.amd64/release/bin/src
&& make SYSDIR=/usr/src/sys
*** Building 'vboxdrv' module ***
"/usr/share/mk/bsd.own.mk", line 483: MK_CLANG_IS_CC can't be set
by a user.
*** [all] Error code 1
I think it is a problem with the file /usr/share/mk/bsd.own.mk. I
will
send a message to the ports list.
I looked into it.
I tend to believe that the VirtualBox patches for FreeBSD modifying
the Makefiles are the problem.
[root@DellT410two /usr/ports/emulators/virtualbox-ose-kmod]# find .
-type f -exec fgrep -H MK_CLANG_IS_CC {} \;
./files/patch-src_VBox_HostDrivers_VBoxNetAdp_freebsd_Makefile:+MK_CLANG_IS_CC
?= no
./files/patch-src_VBox_HostDrivers_Support_freebsd_Makefile:+MK_CLANG_IS_CC
?= no
./files/patch-src_VBox_HostDrivers_VBoxNetFlt_freebsd_Makefile:+MK_CLANG_IS_CC
?= no
According to
http://www.freebsd.org/cgi/cvsweb.cgi/src/share/mk/bsd.own.mk,
Revision 1.107.2.5,
this parameter decides whether the CLANG compiler is installed as
/usr/bin/cc.
VirtualBox does not install the cc (that's done by installworld of
the
base system build) so to set the variable here does not make sense
to
me.
Regards
Peter
The following fix was provided by someone on the ports list.
cd /usr/ports/emulators/virtualbox-ose-kmod/files &&
rm patch-src_VBox_HostDrivers_Support_freebsd_Makefile
patch-src_VBox_HostDrivers_VBoxNetAdp_freebsd_Makefile
patch-src_VBox_HostDrivers_VBoxNetFlt_freebsd_Makefile
and start the update again
VBox upgrade completed successfully.
I wasn't involved in committing those patches so I've cc'd Maksym
Sobolyev
to see if there is something new about those patches.
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: spit virtualbox-ose-additions to parts?
On 19.04.2012 08:23, Pavel Timofeev wrote: Is it possible to split port's virtualbox-ose-additions to 2 part: base and x11? I mean it would be very usefull when pkgng will be ready. This problem has to be solved on a much higher level and in a general way. The additions are only one small port out of 23500. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox problem booting FreeBSD-9.0-RELEASE-amd64-bootonly.iso
On 16.04.2012 09:08, Craig Rodrigues wrote: Hi, I am trying to run FreeBSD-9.0-RELEASE-amd64-bootonly.iso inside VirtualBox and am having some problems. The error messages I am getting are similar to the ones mentioned here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-December/065079.html [snip] Error message = If I try to mount and then boot it under VirtualBox, I get this error: CPU doesn't support long mode Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS 639kB/523264kB available memory FreeBSD/x86 bootstrap loader, Revision 1.1 (r...@farrell.cse.buffalo.edu, Tue Jan 3 06:51:49 UTC 2012) Can't work out which disk we are booting from. Guess BIOS device 0x not found by probes, defaulting to disk0: FATAL: int13_harddisk: function 42. Can't use 64bits lba Please create a new VM with preset Operating System "BSD" and Version "FreeBSD (64 bit)". -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox-4.1.10: Mouse gets trapped in the FreeBSD-9.0 guest with additions installed
On 04.04.2012 04:03, Yuri wrote: I installed fresh FreeBSD-9.0 VBox i386 and amd64 guests. Both of them fail to have mouse integration, mouse is trapped and window resize doesn't work. Xorg.log gets such errors: ... (II) VBoxVideo(0): VirtualBox guest additions video driver version 4.1.10_OSE (EE) VBoxVideo(0): Failed to initialize the VirtualBox device (rc=-102) - make sure that the VirtualBox guest additions are properly installed. If you are not sure, try reinstalling them. The X Window graphics drivers will run in compatibility mode. ... (II) VBoxVideo(0): Setting screen physical size to 270 x 203 (EE) VBoxVideo(0): Unable to determine whether the virtual machine supports mouse pointer integration - request initialization failed with return code -4 ... (II) PS/2 Mouse: ps2EnableDataReporting: succeeded (EE) VBoxVideo(0): Unable to determine whether the virtual machine supports mouse pointer integration - request initialization failed with return code -4 ... (II) VBoxVideo(0): Printing DDC gathered Modelines: (II) VBoxVideo(0): Modeline "1024x768"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 -hsync -vsync (46.4 kHz) (EE) VBoxVideo(0): Unable to determine whether the virtual machine supports mouse pointer integration - request initialization failed with return code -4 (EE) VBoxVideo(0): Unable to determine whether the virtual machine supports mouse pointer integration - request initialization failed with return code -4 (EE) VBoxVideo(0): Unable to determine whether the virtual machine supports mouse pointer integration - request initialization failed with return code -4 ... And many more times the same message. Basically FreeBSD additions 4.1.10 are broken. I've just verified that the additions haven't regressed since 4.0. So I've installed 4.1.10 additions on PC-BSD 9.0 and X11, mouse and clipboard sharing work the same as before. To be fair seamless mouse did never work but I'm not sure if that is because of our old Xorg stack or an oversight in the additions. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox drama - failing VDI disks, VM not starting headless, Rebuild problems on 8.2 (clang related problem?) and 9-STABLE (libpcre.so.0)
On 02.04.2012 07:42, Petro Rossini wrote:
Hi Adam and all,
at the end my problem description I sent to -virtualization first.
(Thanks Adam, to pointing out that I am barking up the wrong tree;-)
On Mon, Apr 2, 2012 at 3:28 PM, Adam Vande More
wrote:
On Sun, Apr 1, 2012 at 11:44 PM, Petro Rossini
> AFAICT, that error message is related to a permissions issue.
Can you
> supply the VM log when you post the question to emulation?
See you there:-) But there isn't much I found:
00:00:01.368 nspr-2 Loading settings file
"/vboxes/zimbra/zimbra.vbox" with version "1.11-freebsd"
00:00:01.885 Watcher ERROR [COM]: aRC=NS_ERROR_FAILURE
(0x80004005)
aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine}
aText={The virtual machine 'zimbra' has terminated unexpectedly
during
startup with exit code 0}, preserve=false
I would like to see it in full if possible.
[snip]
Hi all,
I had some VirtualBox hassle over the weekend.
It started with thes messages inside the VM, a Ubuntu 10.04 Server
(running Zimbra).
2012-03-30T18:37:11.581591+11:00 mail kernel: [4520695.304357] sd
4:0:0:0: [sdd] Unhandled error code
2012-03-30T18:37:15.201744+11:00 mail kernel: [4520695.304362] sd
4:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
2012-03-30T18:37:15.201753+11:00 mail kernel: [4520695.304366] sd
4:0:0:0: [sdd] CDB: Write(10): 2a 00 02 1d 44 f8 00 00 08 00
2012-03-30T18:37:15.201756+11:00 mail kernel: [4520695.304457]
end_request: I/O error, dev sdd, sector 35472632
2012-03-30T18:37:15.201758+11:00 mail kernel: [4520695.312601]
__ratelimit: 9 callbacks suppressed
2012-03-30T18:37:15.201761+11:00 mail kernel: [4520695.312604] Buffer
I/O error on device sdd, logical block 4434079
2012-03-30T18:37:15.201763+11:00 mail kernel: [4520695.321978] lost
page write due to I/O error on sdd
Two hours later it moves to another disk: "sd 3:0:0:0: [sdc]
Unhandled
error code"
The Linux reacts with a read-only remount - practically the box is
falling over.
The VDI disks are on a ZFS filesystem, and I scrubbed the ZVolume and
looked for other possible problems - host-side all seamt to be okay.
I restarted the system once - and for a few hours it worked, untiul I
see the same problem again.
A second reboot is not that successful, I cannot start the VM
headless
anymore, getting a
Result Code: NS_ERROR_FAILURE (0x4005)
I have a second machine with the same setup and continous mirroring
of
the disks (zfs send/receive) - the same result.
Tried an older ZFS snapshot of the VDI disks - still not starting.
It was FreeBSD 8.2 and VirtualBox 4.0.4, and some people with similar
You took the worst possible versions for your server so I hope it's not
an important one. FreeBSD 8.2 + ZFS has some significant known problems
that were fixed in 8-STABLE after the 8.2 release. Additionally
VirtualBox 4.0 until 4.0.8 is known to be unstable because they did a
lot
of refactoring and rewriting so I wouldn't recommend using it in
production either. Building this all with clang is another risk factor.
I hope you didn't loose any data but you should seriously switch to
FreeBSD 9.0 and VirtualBox 4.1.10.
--
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [patch] VirtualBox-4.0.14 + FreeBSD/CURRENT + VIMAGE: crash on vm shutdown
On 19.03.2012 20:48, Mikolaj Golub wrote: Hi, Here is a patch that fixes the issue I have been observing recently: running on VIMAGE enabled kernel VirtualBox causes the kernel crash when vm is powered off: ng_unref_node(8b156880,0,1,101,0,...) at ng_unref_node+0x74 ng_snd_item(8d060d40,0,8b0e18f0,0,0,...) at ng_snd_item+0x2a5 ng_send_fn(8b156880,0,8b0e18f0,0,0,...) at ng_send_fn+0x35 ng_rmnode_self(8b156880,89f840e0,8b0dbcc0,deec88cc,8b0d9ffa,...) at ng_rmnode_self+0x4a vboxNetFltOsDeleteInstance(89f84010,89f84014,89f84010,deec88ec,8b0da0f4,...) at vboxNetFltOsDeleteInstance+0x63 vboxNetFltRelease(89f84010,0,0,0,89f84014,...) at vboxNetFltRelease+0x6a vboxNetFltPortDisconnectAndRelease(89f84014,2710,87748bd4,87748bd4,deec8930,...) at vboxNetFltPortDisconnectAndRelease+0x64 _end(8b15ed10,89f84210,877456b0,0,deec8990,...) at 0x8cffe057 SUPR0ObjRelease(8b15ed10,89f4b810,deec89c8,deec89a0,0,...) at SUPR0ObjRelease+0x133 _end(8b15eb90,898a0e10,877456b0,0,89f4b810,...) at 0x8cffe4bb supdrvCleanupSession(8162bac0,89f4b810,89f4b810,deec89f4,8160e52f,...) at supdrvCleanupSession+0xef supdrvCloseSession(8162bac0,89f4b810,8ceecb18,deec8a18,8ceecaa0,...) at supdrvCloseSession+0x19 VBoxDrvFreeBSDClose(89ee6c00,3,2000,8adcc5c0,8adcc5c0,...) at VBoxDrvFreeBSDClose+0x2f devfs_close(deec8a78,8ceecaa0,80400,80f8caac,133,...) at devfs_close+0x2ca VOP_CLOSE_APV(81095960,deec8a78,80f8caac,133,2,...) at VOP_CLOSE_APV+0xda vn_close(8ceecaa0,3,8b24b380,8adcc5c0,80f792e0,...) at vn_close+0x190 vn_closefile(89f8cd58,8adcc5c0,0,89f8cd58,0,...) at vn_closefile+0xe4 devfs_close_f(89f8cd58,8adcc5c0,0,0,89f8cd58,...) at devfs_close_f+0x35 _fdrop(89f8cd58,8adcc5c0,0,deec8b80,0,8adcc670,81273398,810a7620,89e50c2c,79d,80f7401d,deec8b90,80a2f81e,89e50c2c,8,80f7401d,79d,0,89f8cd58) at _fdrop+0x43 closef(89f8cd58,8adcc5c0,79d,79a,8adcc670,...) at closef+0x2b0 fdfree(8adcc5c0,0,80f74dc6,107,deec8c18,...) at fdfree+0x3ea exit1(8adcc5c0,0,deec8d1c,80db7aee,8adcc5c0,...) at exit1+0x57a sys_sys_exit(8adcc5c0,deec8cec,80fd0bf8,80f53607,8adbf5c0,...) at sys_sys_exit+0x1d syscall(deec8d28) at syscall+0x2de Xint0x80_syscall() at Xint0x80_syscall+0x21 Sorry for the late response and thanks for the patch. Is this patch still required for 4.1.8? My guess is yes but it would be great if you could confirm that with the latest port. Do you aggree that this patch is under MIT License so that I can push it upstream? -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox missing from pkg FTP
On 14.03.2012 07:20, grarpamp wrote: Hey all. Just noting that VirtualBox has gone missing from the stable dirs other than packages-9-stable. There are still some various VBox components and versions present in the various -stable and -release FTP dirs. But in general, it seems something broke? Besides being outdated itself (3.2.12 vs. 4.1.10, or even 4.0.16 or 3.2.14)... I'm hesitant to use say the 8.2-release (3.2.12) since all my pkgs are 8-stable, and looking its release pkgdeps, it looks like it might bring in a lot of older packages from back then (libs and things)? I honestly don't know what you are complaining about. Is it that 4.1.10 was released less than 24h ago and the ports are not updated yet? Sorry for that, I was traveling yesterday so I was unable to have a look at it yet. Is it because 4.1.8 packages for 8-stable are not available? ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/emulators/ ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8-stable/emulators/ Is it because the packages are not identical to the current ports? The binary packages are currently generated on a low frequency so it will take a few weeks until they are updated. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Screen of Ubuntu64 guest doesn't update when 3D acceleration option is "on"
On 12.03.2012 07:23, Yuri wrote: Once I enabled 3D acceleration in "Display options", Ubuntu64 guest screen stopped updating after guest window is covered by some other host window. So that areas that became invisible are filled with garbage until some window is closed or moved in guest and it repaints the whole screen. This doesn't happen with Windows7 guest with 2D and 3D acceleration. vbox-4.1.8 on 9.0 amd64 host This doesn't sound like it's FreeBSD specific. Have you already searched in their bug database for that? -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [PATCH] VirtualBox 4.1.8 kmod panic with VIMAGE kernel
On 10.03.2012 05:42, Brandon Gooch wrote:
It's my guess that not many people are running VirtualBox on a
VIMAGE-enabled kernel. However, for those of us who do (just me?),
the attached patch is required to prevent a panic when running
VirtualBox in such an environment. The patch belongs to the
emulators/virtualbox-ose-kmod port.
--- src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c.orig 2011-12-19
07:01:06.0 -0600
+++ src/VBox/HostDrivers/VBoxNetAdp/VBoxNetAdp.c2011-12-26
14:54:27.0 -0600
@@ -1189,6 +1189,7 @@
int vboxNetAdpInit(void)
{
unsigned i;
+PVBOXNETADP pVboxnet0;
/*
* Init common members and call OS-specific init.
*/
@@ -1201,7 +1202,8 @@
vboxNetAdpOsInit(&g_aAdapters[i]);
}
-return VINF_SUCCESS;
+/* Create vboxnet0 */
+return vboxNetAdpCreate(&pVboxnet0, NULL);
}
/**
If there is a more appropriate fix, please help me find it,
otherwise,
it would be great to have this committed!
Sorry, that I haven't committed the patch until now. Do you agree that
this patch is licensed under MIT License so I can send it upstream?
Current VIMAGE support is only for vboxnetflt and you are touching
vboxnetadp so that is probably why nobody used it before. Have you
tested it with a non VIMAGE kernel?
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: virtualbox fix for recent current (was Re: svn commit: r232264 - in head/sys: amd64/include i386/include pc98/include x86/include)
On 05.03.2012 13:50, Tijl Coosemans wrote: -Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o.dep -Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o -Wp,-MP -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/testcase/tstVMStructRC.cpp kmk: *** Waiting for unfinished jobs kmk: *** Exiting with status 2 *** [do-build] Error code 2 Stop in /usr/ports/emulators/virtualbox-ose. *** [build] Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. --- Thanks! The patch has been committed now. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: vbox install fails
On 02.03.2012 05:53, AN wrote: uname -a FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r232369: Thu Mar 1 20:26:30 EST 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 Trying to install vbox 4.1.8 and 4.0.6Legacy, I get the following error: kBuild: Compiling tstVMStructRC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/testcase/tstVMStructRC.cpp In file included from /usr/include/sys/types.h:63, from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/include/iprt/types.h:85, from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/include/VBox/types.h:30, from /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/testcase/tstVMStructRC.cpp:33: /usr/include/sys/_stdint.h:74: error: conflicting declaration 'typedef __intptr_t intptr_t' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/include/iprt/stdint.h:162: error: 'intptr_t' has a previous declaration as 'typedef long int intptr_t' /usr/include/sys/_stdint.h:78: error: conflicting declaration 'typedef __uintptr_t uintptr_t' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/include/iprt/stdint.h:165: error: 'uintptr_t' has a previous declaration as 'typedef long unsigned int uintptr_t' kBuild: Generating tstVMStructSize - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstAsmStructsAsm.mac /usr/local/bin/kmk_sed -f /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/testcase/tstAsmStructsAsm-lst.sed --output /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstAsmStructsAsm.mac /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstAsmStructsAsm.mac.lst kBuild: Compiling tstGlobalConfig - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/testcase/tstGlobalConfig.cpp kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o] Error 1 The failing command: @c++ -m32 -c -O2 -g -pipe -pedantic -Wshadow -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-long-long -Wno-variadic-macros -fno-exceptions -O2 -mtune=generic -fno-omit-frame-pointer -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fno-strict-aliasing -fno-stack-protector -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fvisibility-inlines-hidden -fno-rtti -O0 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/PATM -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox-ose\" -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -DIN_RC -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DIN_VMM_RC -DIN_DIS -DIN_RT_RC -DVBOX_WITH_RAW_MODE -DIPRT_DONT_USE_SYSTEM_STDINT_H -Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o.dep -Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o -Wp,-MP -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/tstVMStructRC/tstVMStructRC.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/testcase/tstVMStructRC.cpp kmk: *** Waiting for unfinished jobs kmk: *** Exiting with status 2 *** [do-build] Error code 2 Stop in /usr/ports/emulators/virtualbox-ose. *** [install] Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. [root@FBSD10 /usr/ports/emulators/virtualbox-ose]# Any help fixing this would be appreciated, tia. The port is fixed now and should compile fine. Thanks for your report! -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386
On 22.02.2012 21:07, Cy Schubert wrote: In message , Warren Block writ es: On Wed, 22 Feb 2012, Andriy Gapon wrote: > on 22/02/2012 11:26 Doug Barton said the following: >> Meanwhile, the 4.0 version worked on this same system ... > > The attached patched should try to grab the memory harder. No visible difference here, sorry. Same on my systems (8.2 and 9.0). My main server (9.0 dual core AMD X2) panics with a kernel page fault and hangs. My laptop (9.0 Penium-M) and my testbed (8.2 and 9.0 single core AMD X2) panic like my laptop, no messages, just an immediate reboot. (Something does flash up on the screen but it's there for milliseconds. We decided to backout the patch until this problem is solved. Commit was done a few minutes ago. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386
On 22.02.2012 10:46, Doug Barton wrote: On 02/22/2012 01:41, Bernhard Froehlich wrote: The 4.0.16 version is still available as emulators/virtualbox-ose-legacy I know, that, but kind of beside the point, right? Yes, but some people depend on a working virtualbox and that is their safety net until the problem is sorted out. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386
On 22.02.2012 10:26, Doug Barton wrote: On 02/22/2012 01:20, Andriy Gapon wrote: on 22/02/2012 05:40 Doug Barton said the following: On 02/21/2012 15:51, Andriy Gapon wrote: Could you please substitute the attached patch file for the corresponding file in the port and re-test the port? Good news, the kernel didn't panic. Bad news: supdrvGipCreate: failed to allocate the GIP page. rc=-8 vboxdrv: supdrvInitDevExt failed, rc=-8 module_register_init: MOD_LOAD (vboxdrv, 0xc66f33e0, 0) error 12 Yeah, I kind of expected something like this, because the original panic was in a memory allocation failure path. As to why the memory allocation fails I have no immediate insights. Maybe you genuinely don't have enough contiguous pages below 4GB boundary... It's i386, no PAE, so you could be on to something. I do have more than 4G in the box though: real memory = 6442450944 (6144 MB) avail memory = 3148255232 (3002 MB) Meanwhile, the 4.0 version worked on this same system ... The 4.0.16 version is still available as emulators/virtualbox-ose-legacy and doesn't include the memobj r0 patch so it should still work. (you will need to switch to devel/kBuild for that) -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VBox: "Unsupported version 2 of data unit" after snapshot was restored
On 30.01.2012 10:52, Yuri wrote: On 01/30/2012 01:18, Bernhard Froehlich wrote: From vbox developers: Up to version 4.0 vbox used only version 1 of saved state of the DMA controller. With vbox 4.1 a new version 2 was introduced which cannot be used with an older vbox version. So have you probably created a snapshot with a newer vbox 4.1.x and then switched back to vbox 4.0.x and restored the snapshot there? If that is the case you can restore the snapshot with 4.1.x and be sure that there is no saved state anymore and then switch back to 4.0.x. This snapshot was created in Oct-Nov 2011, I have always been with the port version in 2011. Unless the port version went to 4.1.X and later was downgraded, I probably never used version 4.1.X. Thanks for the logfile. Nothing new in there so the snapshot you have was somehow created or modified by vbox 4.1.x and cannot be used with 4.0.x. You can switch to 4.1.x again which will come to the portstree very soon anyway. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VBox: "Unsupported version 2 of data unit" after snapshot was restored
On 30.01.2012 09:26, Yuri wrote: After I restored the snapshot (of Windows 7 guest) I get such error while launching the machine again: "Unsupported version 2 of data unit '8237A" (instance #0, pass 0x) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION) I am not sure if this is FreeBSD specific or generic. FreeBSD-9.0-STABLE amd64 virtualbox-ose-4.0.14 From vbox developers: Up to version 4.0 vbox used only version 1 of saved state of the DMA controller. With vbox 4.1 a new version 2 was introduced which cannot be used with an older vbox version. So have you probably created a snapshot with a newer vbox 4.1.x and then switched back to vbox 4.0.x and restored the snapshot there? If that is the case you can restore the snapshot with 4.1.x and be sure that there is no saved state anymore and then switch back to 4.0.x. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VBox: "Unsupported version 2 of data unit" after snapshot was restored
On 30.01.2012 09:26, Yuri wrote: After I restored the snapshot (of Windows 7 guest) I get such error while launching the machine again: "Unsupported version 2 of data unit '8237A" (instance #0, pass 0x) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION) I am not sure if this is FreeBSD specific or generic. FreeBSD-9.0-STABLE amd64 virtualbox-ose-4.0.14 Could you please also send the VBox.log? -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox blueports repository moved to redports.org
Thanks, the patch works fine! Do you agree that this patch is under MIT License so that I can push it upstream? -- Bernhard Froehlich http://www.bluelife.at/ On 22.12.2011 05:48, Daichi GOTO wrote: Hi, How about this patch? At least, build is ok (helped by hrs). --- include/iprt/types.h.orig 2011-12-19 21:58:33.0 +0900 +++ include/iprt/types.h2011-12-22 13:34:09.0 +0900 @@ -167,6 +167,10 @@ # if defined(__GNUC__) # if defined(RT_OS_LINUX) && __GNUC__ < 3 typedef uint8_t bool; +# elif defined(RT_OS_FREEBSD) +# ifndef __bool_true_false_are_defined +typedef _Bool bool; +# endif # else # if defined(RT_OS_DARWIN) && defined(_STDBOOL_H) #undef bool On Wed, 21 Dec 2011 09:07:27 +0100 Bernhard Froehlich wrote: That's a known breakage on 10-CURRENT since r228444. No fix available yet. http://svnweb.freebsd.org/base?view=revision&revision=228444 On 21.12.2011 06:33, Daichi GOTO wrote: > Thanks great vbox work ;) > > I tried to build the latest vbox4.1.8 via redports svn to do test > and got the failed. Could the error log help you? > > - > > # pwd > /usr/ports/emulators/virtualbox-ose > # uname -a > FreeBSD parancell-freebsd-head.ongs.co.jp 10.0-CURRENT FreeBSD > 10.0-CURRENT #4 r+5af9280: Wed Dec 21 11:23:48 JST 2011 > r...@parancell-freebsd-head.ongs.co.jp:/usr/obj/usr/src/sys/GENERIC > amd64 > # make install > cd /usr/ports/emulators/virtualbox-ose && make config; > ===> Options unchanged > ===> Installing for virtualbox-ose-4.1.8 > ===> virtualbox-ose-4.1.8 depends on file: /boot/modules/vboxdrv.ko > - not found > ===>Verifying install for /boot/modules/vboxdrv.ko in > /usr/ports/emulators/virtualbox-ose-kmod > cd /usr/ports/emulators/virtualbox-ose-kmod && make config; > ===> Options unchanged > ===> Building for virtualbox-ose-kmod-4.1.8 > cd /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE > && /bin/sh env.sh && cd > > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/src/VBox/HostDrivers > && VBOX_LIBPATH_X11=/usr/local > VBOX_FREEBSD_SRC=skins/default/usr/src/sys > /usr/local/bin/kmk HostDrivers-src vboxdrv-mod VBoxNetFlt-src > VBoxNetAdp-src > /usr/local/share/kBuild/footer-pass2-installs.kmk:67: warning: > overriding recipe for target > > `/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/crc.h' > /usr/local/share/kBuild/footer-pass2-installs.kmk:67: warning: > ignoring old recipe for target > > `/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/crc.h' > /usr/local/share/kBuild/footer-pass2-installs.kmk:67: warning: > overriding recipe for target > > `/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/dist/bin/src/vboxdrv/include/iprt/crc.h' > /usr/local/share/kBuild/footer-pass2-installs.kmk:67: warning: > ignoring old recipe for target > > `/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/dist/bin/src/vboxdrv/include/iprt/crc.h' > /usr/local/share/kBuild/footer-pass2-installs.kmk:67: warning: > overriding recipe for target > > `/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/net.h' > /usr/local/share/kBuild/footer-pass2-installs.kmk:67: warning: > ignoring old recipe for target > > `/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/net.h' > /usr/local/share/kBuild/footer-pass2-installs.kmk:67: warning: > overriding recipe for target > > `/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/dist/bin/src/vboxdrv/include/iprt/net.h' > /usr/local/share/kBuild/footer-pass2-installs.kmk:67: warning: > ignoring old recipe for target > > `/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/dist/bin/src/vboxdrv/include/iprt/net.h' > kmk: Nothing to be done for `HostDrivers-src'. > kBuild: Creating - > > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/obj/vboxdrv-mod/Makefile > kBuild: Installing > > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/Makefile > kBuild: Installing > > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/bin/src/vboxnetadp/Makefile > kBuild: Installing > > /usr/ports/emulators/virtualb
Re: VirtualBox blueports repository moved to redports.org
irs -fdiagnostics-show-option -c SUPDrv.c In file included from include/VBox/types.h:30, from SUPDrvInternal.h:35, from SUPDrv.c:32: include/iprt/types.h:174: error: redefinition of typedef 'bool' @/sys/types.h:271: error: previous declaration of 'bool' was here *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/bin/src/vboxdrv. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.amd64/release/bin/src. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose-kmod. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose-kmod. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. # exit Script done on Wed Dec 21 14:16:10 2011 - On Tue, 20 Dec 2011 13:42:04 +0100 Bernhard Froehlich wrote: Hi VirtualBox Testers! I think it's the right time now to announce that the virtualbox blueports repository that a few of you were using moved to a new location. That is because in the last few months I was heavily working on a new FreeBSD port building cluster called redports.org which is also the new environment where I usually build test all virtualbox versions and the new home of VirtualBox for FreeBSD. redports.org is the successor of the blueports repository but the history was migrated so nothing is lost. Since last week I am back to my usual virtualbox work and have already pushed a few very interesting patches from Andriy Gapon and Ed Schouten upstream. All ports are at their latest available versions now so we are _not_ lagging behind in the development repository. I just do not want to push those versions in the tree before 9.0-RELEASE is out the door. So I am currently waiting for 9.0 to be released and then I will update our virtualbox-ose ports to 4.1.8 and virtualbox-ose-legacy to 4.0.14. If you want to test the latest versions have a look at the new repository: - virtualbox-ose 4.1.8 (0 days old) - virtualbox-ose-devel 4.1.51r39575 (10 days old) - virtualbox-ose-legacy 4.0.14 (2 months old) - phpvirtualbox 4.1-5 (1 month old) Keep in mind that you need to update devel/kBuild first to compile the newer virtualbox versions. Latest kBuild is also included in the repository. For support the IRC channel and mailinglist are still the same :o) Support: IRC: #fbsd-mentors on irc.unixfreunde.de irc://irc.unixfreunde.de/fbsd-mentors Mailinglist: freebsd-emulation (at) FreeBSD.org EMail: vbox (at) FreeBSD.org Development Repository: === Browseable: http://redports.org/browser/virtualbox SVN Checkout: svn co http://svn.redports.org/virtualbox/ tar Archive of repository: http://redports.org/~virtualbox/svn.tar.bz2 RSS Feed: http://redports.org/log/virtualbox?format=rss&limit=25 -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org" ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox 4.1.8 with successful !
On 20.12.2011 04:27, Luiz Gustavo S. Costa wrote: Hi List ! did you install the new version of VirtualBox 4.1.8 on FreeBSD 9 with successfully using the file port of our friend Bernhard Froehlich Thank you Bernhard. Details: [root@desktop] ~# uname -a FreeBSD desktop.luizgustavo.pro.br 9.0-RC2 FreeBSD 9.0-RC2 #0: Sat Nov 12 18:35:25 UTC 2011 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 [root@desktop] ~# pkg_info | grep virtualbox virtualbox-ose-4.1.8 A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.1.8 VirtualBox kernel module for FreeBSD [root@desktop] ~# VBoxManage --version 4.1.8_OSEr75467 Need changes: change version in Makefile: DISTVERSION=4.1.8 and add a new line for download: MASTER_SITES= http://dlc.sun.com.edgesuite.net/virtualbox/4.1.8/ \ http://tmp.chruetertee.ch/ \ Make a new checksum for file: make makesum Best thing would be to use the port from the new repository. It includes a few more interesting patches! http://lists.freebsd.org/pipermail/freebsd-emulation/2011-December/009364.html -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
VirtualBox blueports repository moved to redports.org
Hi VirtualBox Testers! I think it's the right time now to announce that the virtualbox blueports repository that a few of you were using moved to a new location. That is because in the last few months I was heavily working on a new FreeBSD port building cluster called redports.org which is also the new environment where I usually build test all virtualbox versions and the new home of VirtualBox for FreeBSD. redports.org is the successor of the blueports repository but the history was migrated so nothing is lost. Since last week I am back to my usual virtualbox work and have already pushed a few very interesting patches from Andriy Gapon and Ed Schouten upstream. All ports are at their latest available versions now so we are _not_ lagging behind in the development repository. I just do not want to push those versions in the tree before 9.0-RELEASE is out the door. So I am currently waiting for 9.0 to be released and then I will update our virtualbox-ose ports to 4.1.8 and virtualbox-ose-legacy to 4.0.14. If you want to test the latest versions have a look at the new repository: - virtualbox-ose 4.1.8 (0 days old) - virtualbox-ose-devel 4.1.51r39575 (10 days old) - virtualbox-ose-legacy 4.0.14 (2 months old) - phpvirtualbox 4.1-5 (1 month old) Keep in mind that you need to update devel/kBuild first to compile the newer virtualbox versions. Latest kBuild is also included in the repository. For support the IRC channel and mailinglist are still the same :o) Support: IRC: #fbsd-mentors on irc.unixfreunde.de irc://irc.unixfreunde.de/fbsd-mentors Mailinglist: freebsd-emulation (at) FreeBSD.org EMail: vbox (at) FreeBSD.org Development Repository: === Browseable: http://redports.org/browser/virtualbox SVN Checkout: svn co http://svn.redports.org/virtualbox/ tar Archive of repository: http://redports.org/~virtualbox/svn.tar.bz2 RSS Feed: http://redports.org/log/virtualbox?format=rss&limit=25 -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: virtualbox r0 memory management update [Was: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}]
On 06.12.2011 12:14, Andriy Gapon wrote: Meanwhile, here is the code that I came up with: http://people.freebsd.org/~avg/vbox/ For your convenience I have uploaded both the new file and its diff against svn head. I am testing this on FreeBSD head (r228017), so far no breakage observed. I would appreciate reviews and testing of this code. Especially testing with earlier FreeBSD releases. VirtualBox 4.1.6 on FreeBSD 9.0-RC2/amd64 gave me: cc -O2 -pipe -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64 -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c /usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c: In function 'FreeBSDContigPhysAllocHelper': /usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:212: error: incompatible types in initialization *** Error code 1 Stop in /usr/home/decke/rpvbox/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.6_OSE/out/freebsd.amd64/release/bin/src/vboxdrv. *** Error code 1 -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 06.12.2011 12:00, Andriy Gapon wrote: on 06/12/2011 11:40 Bernhard Froehlich said the following: On 06.12.2011 10:08, Andriy Gapon wrote: on 06/12/2011 02:08 Alan Cox said the following: The right thing to do is to MFC vm_page_alloc_contig(). It shouldn't be that hard to merge it. Ah, but we want to be able to run virtualbox on the past releases too. Which releases are we talking about here? VirtualBox was always deprecating older FreeBSD releases much faster than our Security EOL so if we focus on latest 8.x and >= 9.0 I think it should be okay. We have already deprecated 7.x because of some other problems with the userland bits so we can forget about 7.x completely. What is left is 8.1 and 8.2 and both are EOL until mid 2012. So if is possible to get it merged in time for 8.3 and 9.1 (if needed) we should be fine. So we would just say "screw you" to people who stick to e.g. 8.2 at the moment? :) No. We currently have the last 2 virtualbox major versions in the ports tree so if we decide to do such an incompatible change we always have the older version around for 8.2 users for about the next year. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 06.12.2011 10:08, Andriy Gapon wrote: on 06/12/2011 02:08 Alan Cox said the following: The right thing to do is to MFC vm_page_alloc_contig(). It shouldn't be that hard to merge it. Ah, but we want to be able to run virtualbox on the past releases too. Which releases are we talking about here? VirtualBox was always deprecating older FreeBSD releases much faster than our Security EOL so if we focus on latest 8.x and >= 9.0 I think it should be okay. We have already deprecated 7.x because of some other problems with the userland bits so we can forget about 7.x completely. What is left is 8.1 and 8.2 and both are EOL until mid 2012. So if is possible to get it merged in time for 8.3 and 9.1 (if needed) we should be fine. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 05.12.2011 14:06, Andriy Gapon wrote: on 05/12/2011 14:57 Bernhard Froehlich said the following: On 02.12.2011 12:55, Bernhard Froehlich wrote: Patch has been send upstream: https://www.virtualbox.org/pipermail/vbox-dev/2011-December/004842.html Patches have been committed upstream. Thanks a lot guys! https://www.virtualbox.org/changeset/39521 BTW, I think that we additionally need VM_ALLOC_NOBUSY in flags that we pass to vm_phys_alloc_contig. What's the difference of this? BTW you reported about the GCC 4.5 header stuff and it was also already fixed: http://lists.freebsd.org/pipermail/freebsd-emulation/2011-December/009312.html -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 02.12.2011 12:55, Bernhard Froehlich wrote: On 01.12.2011 09:37, Bernhard Froehlich wrote: On 01.12.2011 00:07, Jung-uk Kim wrote: On Wednesday 30 November 2011 05:32 pm, Andriy Gapon wrote: on 26/11/2011 18:33 Gleb Kurtsou said the following: > Using new vm_page_alloc_contig() may be a better option here. > Can't help with patch, stuck with pre Nov 15 CURRENT myself. on 27/11/2011 19:09 Alan Cox said the following: > vm_page_alloc_contig() should be used instead. My take on the patch: http://people.freebsd.org/~avg/vbox-10.patch This is for head only, no check for FreeBSD version. Actually, I did the same thing last night: http://people.freebsd.org/~jkim/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c This is a drop-in replacement for the patch. The only practical difference I see from yours is I used VM_ALLOC_INTERRUPT instead of VM_ALLOC_NORMAL. I believe this function may be used in interrupt context. FYI, I tried FreeBSD 9 and Fedora 10 without problem. Thanks a lot for both patches! Could you please as usual reply and tell me if it is okay to send this patch upstream under MIT license? Once there is some positive feedback I will commit both patches to the ports tree. Patch has been send upstream: https://www.virtualbox.org/pipermail/vbox-dev/2011-December/004842.html Patches have been committed upstream. Thanks a lot guys! https://www.virtualbox.org/changeset/39521 -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: vboxdrv can be unloaded while in use?
On 04.12.2011 22:43, Andriy Gapon wrote: Apparently yes :) Because I was able to kldunload vboxdrv when I had forgotten that I still had one guest running. The system then crashed badly shortly afterwards. Could you test the following patch please? If not I will test it in the evening and crash my machine. http://pastebin.com/5ZhgmHE7 -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 01.12.2011 09:37, Bernhard Froehlich wrote: On 01.12.2011 00:07, Jung-uk Kim wrote: On Wednesday 30 November 2011 05:32 pm, Andriy Gapon wrote: on 26/11/2011 18:33 Gleb Kurtsou said the following: > Using new vm_page_alloc_contig() may be a better option here. > Can't help with patch, stuck with pre Nov 15 CURRENT myself. on 27/11/2011 19:09 Alan Cox said the following: > vm_page_alloc_contig() should be used instead. My take on the patch: http://people.freebsd.org/~avg/vbox-10.patch This is for head only, no check for FreeBSD version. Actually, I did the same thing last night: http://people.freebsd.org/~jkim/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c This is a drop-in replacement for the patch. The only practical difference I see from yours is I used VM_ALLOC_INTERRUPT instead of VM_ALLOC_NORMAL. I believe this function may be used in interrupt context. FYI, I tried FreeBSD 9 and Fedora 10 without problem. Thanks a lot for both patches! Could you please as usual reply and tell me if it is okay to send this patch upstream under MIT license? Once there is some positive feedback I will commit both patches to the ports tree. Patch has been send upstream: https://www.virtualbox.org/pipermail/vbox-dev/2011-December/004842.html -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: "headed" virtualbox + vnc
On 02.12.2011 00:14, Andriy Gapon wrote: on 01/12/2011 22:02 Martin Simmons said the following: On Thu, 01 Dec 2011 14:11:55 +0200, Andriy Gapon said: Is it possible to start a guess VM with GUI and also be able to access it via VNC? All google hits for freebsd+virtualbox+vnc are about VBoxHeadless. Probably not simultaneously, but you can close the GUI with the "Save the machine state" option and then bring it back to life as a headless VM (presumably with vnc). Use VBoxManage controlvm ... savestate to stop the headless VM and then start it again in GUI mode. The reason I am asking is that apparently that feature is available with RDP (via Devices -> Enable Remote Display). So I hoped for the same with VNC. The correct answer is not yet. Currently VNC support is a hack and does not integrate very well. Since VirtualBox 4.0 there is a new plugin API which allows to write a VNC plugin that integrates the same way as RDP but without the GPL licensing issues. Someone already started writing such a VNC plugin but that work has stalled. It's more or less in a working state so they plan to integrate it at some point in the future. We have an highly experimental port of that code available for vbox 4.0.4 but I don't know if we ever got it working. bapt@ has done some work on this so probably he knows something about it. http://redports.org/browser/virtualbox/emulators/virtualbox-extpack-vnc http://redports.org/~virtualbox/svn.tar.bz2 -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Freeze with 10.0 and VirtualBox {4.1.4|4.1.6|4.1.51r38464}
On 01.12.2011 00:07, Jung-uk Kim wrote: On Wednesday 30 November 2011 05:32 pm, Andriy Gapon wrote: on 26/11/2011 18:33 Gleb Kurtsou said the following: > Using new vm_page_alloc_contig() may be a better option here. > Can't help with patch, stuck with pre Nov 15 CURRENT myself. on 27/11/2011 19:09 Alan Cox said the following: > vm_page_alloc_contig() should be used instead. My take on the patch: http://people.freebsd.org/~avg/vbox-10.patch This is for head only, no check for FreeBSD version. Actually, I did the same thing last night: http://people.freebsd.org/~jkim/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c This is a drop-in replacement for the patch. The only practical difference I see from yours is I used VM_ALLOC_INTERRUPT instead of VM_ALLOC_NORMAL. I believe this function may be used in interrupt context. FYI, I tried FreeBSD 9 and Fedora 10 without problem. Thanks a lot for both patches! Could you please as usual reply and tell me if it is okay to send this patch upstream under MIT license? Once there is some positive feedback I will commit both patches to the ports tree. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox 4.0.12 + FreeBSD 7.4-STABLE causes server hangs ...
On 08.11.2011 02:24, Hub- FreeBSD wrote: Has anyone experienced any issues where a server hangs shortly after starting up a VirtualBox guest? I don't have anything to go on for this … server seems to run fine up until I start up the guest OSs, shortly afterwards the server just hangs … No errors in /var/log/messages, nothing on the remote console, it just stops … This is with an Oct 26th 7.4-STABLE kernel … I saw the note on the wiki about VIMAGE causing hangs, but I'm not using VIMAGE, so that isn't it … These are 32bit OSs in the guest … I have three guests that I'm trying to run … right now, I've just started up the one to see if quantity makes a difference … I don't a serial console (remote server) that I can use to break into the debugger ... You could try having a look at ~/VirtualBox VMs//logs/VBox.log and verify that the kernel module is build from the exact same sources as your running kernel. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Virtualbox 4.0.14
On 25.10.2011 15:37, Rusty Nejdl wrote: Is anyone working on porting 4.0.14? Also, is there any update on committing that and kbuild to the ports tree? I checked http://home.bluelife.at/ports/ and don't see anything recent. 4.0.14 and 4.1.4 is ready to be committed to the tree but this will happen after the FreeBSD 9.0 release. Main reason for that is that we need to synchronize this with the kBuild update so we need to throw out 3.2.12 at the same time and also update 4.0.12 to 4.0.14 because 4.0.12 requires the old kBuild that we currently have and 4.0.14 requires the new one. Timing on that is really bad because if we had 2-3 weeks more time I would do a cft and try to get it committed before 9.0 but we are already on RC1 and I don't want to push it in just to release with broken vbox packages. Additionally I've put all my spare time in the last 2 months into redports.org to get it going so I did not have much time for virtualbox. I hope this will change once the first redports beta starts which is planned in about a month but we will see. So if anyone cares to help out on virtualbox this would be a good time now. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: "CPU doesn't support long mode" error message
On Tue, 4 Oct 2011 03:12:12 -0700, Daevid Vincent wrote: > I've been hunting for hours and can't find a solution. > > > > I have a Dell Latitude E6500 notebook. > > http://www.dell.com/us/dfb/p/latitude-e6500/pd > > > > It has an Intel Core 2 Duo CPU P8600 CPU @ 2.4Ghz. with 4 GB RAM > > > > I have enabled all the VT stuff in the BIOS (and even disabled the "Trusted > Execution" checkbox as per this link but have tried with it on too) > > http://communities.vmware.com/docs/DOC-8978 > > Running their "vt.iso" test, I see this: > > CPU <0>: VT is enabled on this core. > > CPU <1>: VT is enabled on this core. > > > > I run a Host Windows7 32-bit OS > > I'm trying to run a Guest VM of FreeBSD 8.2 amd64 64-bit - > > I run this VM on my desktop at work no problem, but that's running Win7 > 64-bit Host, but I was under the impression I could run a 64-bit guest on a > 32-bit host as of the recent versions of VirtualBox. > > > > I've tried various combinations of the guest settings for: > > . Enable IO APIC > > . Enable PAE/NX > > . Enable VT-x/AMD-V > > . Enable Nested Paging > > > > My VBox.log says: > > 00:00:00.683 [/HWVirtExt/] (level 1) > > 00:00:00.683 64bitEnabled= 0x (0) You need to create a 64bit capable VM which you haven't. http://www.virtualbox.org/manual/ch03.html#intro-64bitguests -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox + Bridged Networking
On Thu, 29 Sep 2011 20:29:57 -0400, Hub- FreeBSD wrote: > First, I've searched google hi+low, and this is still eluding me … > > I've got a FreeBSD 8-STABLE box that is up to date as of yesterday … > VirtualBox installed great, I got through the docs on how to create a > Headless VM, it boots, FreeBSD 8 ISO installed on it, everything works > great "stand alone" … but I can't get the network to work. > > Host Machine, ethernet looks like: > > ganymede# ifconfig -a > ale0: flags=8843 metric 0 mtu 1500 > > options=c319a > ether 00:22:15:f1:bc:c5 > inet 192.168.1.2 netmask 0xff00 broadcast 192.168.1.255 > media: Ethernet 100baseTX > status: active > pflog0: flags=0<> metric 0 mtu 33200 > lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet 127.0.0.1 netmask 0xff00 > vboxnet0: flags=8902 metric 0 mtu 1500 > ether 0a:00:27:00:00:00 > ganymede# > > > showvminfo for the VM shows NIC 1 as : > > NIC 1: MAC: 080027F9E7B2, Attachment: Bridged Interface > 'vboxnet0', Cable connected: on, Trace: off (file: none), Type: > 82540EM, Reported speed: 0 Mbps, Boot priority: 0 > > A cut-n-paste of ifconfig in the VPS is attached below... > > > > Yes, I can't ping anywhere … > > I tried to set the bridged device to the ale0 device, which allows me > to ping everywhere *except* the host server … so I'm missing a step > here … > > I've read through http://wiki.freebsd.org/VirtualBox several times … > > The steps i used to create the remote headless were found: > > http://www.virtualbox.org/manual/ch07.html > > So I figure either I'm bridging to the wrong device. or I missing a > configuration step on the Host side of things … but I can't seem to > find anywhere where someone has asked that and gotten an answer and/or > that it is documented … everything seems to point to using the GUI, > which, in this environment, I don' t have access to … > > > So far, though, getting VirtualBox up and running has been fantastic I guess you just used the wrong device that you attached to. When configuring bridging via QT GUI and using bge0 I get: NIC 1: MAC: 080027289A85, Attachment: Bridged Interface 'bge0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0 -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.1.0
On Fri, 26 Aug 2011 00:38:09 -0700, Yuri wrote: > On 08/24/2011 00:43, Bernhard Froehlich wrote: >> There was some similar problem some time ago but I don't know if it's >> the same problem that you see. >> >> http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063322.html > > I am not sure if this is the same problem. Then please set the sysctl on the host as described and see if it helps. >> How about installing the guest additions? >> >> http://wiki.freebsd.org/VirtualBox#head-de5bc57407193ec2728dd102294c6cb3f7609fcb > > Same with guest additions, only on the larger screen size. Have you also modified xorg.conf as described on the Wiki? -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: virtualbox on FreeBSD 8.2
On Thu, 25 Aug 2011 06:29:28 -0600 (MDT), Warren Block wrote: > On Thu, 25 Aug 2011, Bernhard Fröhlich wrote: > >> On Mi., 24. Aug. 2011 22:57:54 CEST, wynk...@wynn.com wrote: >> >>> Here it is: >>> >>> >>> ===> The following configuration options are available for >>> python27-2.7.2_1: THREADS=off "Enable thread support" >>> HUGE_STACK_SIZE=off "Use a larger thread stack" >>> SEM=off "Use POSIX semaphores (experimental)" >>> PTH=off "Use GNU Pth for threading/multiprocessing" >>> UCS4=on "Use UCS4 for unicode support" >>> PYMALLOC=on "Use python's internal malloc" >>> IPV6=on "Enable IPv6 support" >>> FPECTL=off "Enable floating point exception handling" >>> ===> Use 'make config' to modify these settings >>> >>> -Brett >> >> Thats it! Virtualbox needs python threads which is enabled per default for >> python 2.6 and 2.7 but you have disabled it for some reason. >> >> So recompile python 2.7 with the threads option enabled and then compiling >> vbox should work just fine. > > Should the virtualbox port Makefile set BROKEN if Python threads are missing? No. This is a port option that is enabled per default. Modifying port options is always on your own risk and the general rule is that ports don't check that. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.1.0
On Thu, 25 Aug 2011 12:32:52 +0300, m irya wrote: >> >> For 4.1.2 you need to first update devel/kBuild which is also included >> in the archive. If you need to get back to an older vbox version you >> also have to downgrade to the old kBuild version then. >> >> http://home.bluelife.at/ports/virtualbox-cft-20110817.tar.gz >> > > Am I missing something, or the archive link contains only the kBuild > port, but not vbox-4.1.2? Yes, you're right. I've generated a new one: http://home.bluelife.at/ports/virtualbox-cft-20110825.tar.gz -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: virtualbox on FreeBSD 8.2
On Wed, 24 Aug 2011 21:46:37 +0200, Bernhard Froehlich wrote: > On Wed, 24 Aug 2011 14:20:27 -0400 (EDT), wynk...@wynn.com wrote: >> Greeting- >> >> I started with a virgin FreeBSD 8.2 install about a month ago and have been >> trying to build /usr/ports/emulators/virtualbox-ose with no luck ever >> since. >> Ports were installed on the box using portsnap. Over the course of >> last month >> I have updated ports several times in an attempt to get this port to build. >> I have also tried many different config options including with and without X. >> >> >> Here is some important information: >> >> uname -a >> FreeBSD vm0.int.ia 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 #1: Wed Aug >> 10 21:06:16 EDT 2011 >> r...@vm0.int.ia:/usr/src/sys/amd64/compile/VM0 amd64 >> >> >> Now the failed compile output: >> >> >> Script started on Fri Aug 19 00:27:06 2011 >> >> # make >> ===> Building for virtualbox-ose-4.0.12 >> cd /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE && >> /bin/sh env.sh && VBOX_LIBPATH_X11=/usr/local >> VBOX_FREEBSD_SRC=skins/default/usr/src/sys /usr/local/bin/kmk >> /usr/local/share/kBuild/footer.kmk:3132: warning: overriding recipe >> for target >> `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/crc.h' >> /usr/local/share/kBuild/footer.kmk:3132: warning: ignoring old recipe >> for target >> `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/crc.h' >> /usr/local/share/kBuild/footer.kmk:3132: warning: overriding recipe >> for target >> `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/net.h' >> /usr/local/share/kBuild/footer.kmk:3132: warning: ignoring old recipe >> for target >> `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/net.h' >> kBuild: Pass - Build Programs >> kBuild: Installing RuntimeBldProg => >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/lib/RuntimeBldProg.a >> kBuild: Linking bldRTManifest >> kBuild: Pass - Libraries >> kBuild: Compiling VBoxXPCOMCGlue - >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/cbinding/VBoxXPCOMCGlue.c >> kBuild: Compiling VBoxCOM - >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/com.cpp >> kBuild: Compiling VBoxCOM - >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/initterm.cpp >> In file included from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/include/VBox/com/com.h:30, >> from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/initterm.cpp:49: >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/include/VBox/com/defs.h:298:1: >> warning: "FALSE" redefined >> In file included from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub/prinet.h:89, >> from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub/prio.h:51, >> from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsILocalFile.h:17, >> from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/initterm.cpp:43: >> /usr/include/rpc/types.h:58:1: warning: this is the location of the >> previous definition >> In file included from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/include/VBox/com/com.h:30, >> from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/initterm.cpp:49: >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/include/VBox/com/defs.h:299:1: >> warning: "TRUE" redefined >> In file included from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub/prinet.h:89, >> from >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub/prio.h:51, >> from >> /usr/ports/emula
Re: virtualbox on FreeBSD 8.2
On Wed, 24 Aug 2011 14:20:27 -0400 (EDT), wynk...@wynn.com wrote: > Greeting- > > I started with a virgin FreeBSD 8.2 install about a month ago and have been > trying to build /usr/ports/emulators/virtualbox-ose with no luck ever > since. > Ports were installed on the box using portsnap. Over the course of > last month > I have updated ports several times in an attempt to get this port to build. > I have also tried many different config options including with and without X. > > > Here is some important information: > > uname -a > FreeBSD vm0.int.ia 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 #1: Wed Aug > 10 21:06:16 EDT 2011 > r...@vm0.int.ia:/usr/src/sys/amd64/compile/VM0 amd64 > > > Now the failed compile output: > > > Script started on Fri Aug 19 00:27:06 2011 > > # make > ===> Building for virtualbox-ose-4.0.12 > cd /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE && > /bin/sh env.sh && VBOX_LIBPATH_X11=/usr/local > VBOX_FREEBSD_SRC=skins/default/usr/src/sys /usr/local/bin/kmk > /usr/local/share/kBuild/footer.kmk:3132: warning: overriding recipe > for target > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/crc.h' > /usr/local/share/kBuild/footer.kmk:3132: warning: ignoring old recipe > for target > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/crc.h' > /usr/local/share/kBuild/footer.kmk:3132: warning: overriding recipe > for target > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/net.h' > /usr/local/share/kBuild/footer.kmk:3132: warning: ignoring old recipe > for target > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/include/iprt/net.h' > kBuild: Pass - Build Programs > kBuild: Installing RuntimeBldProg => > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/lib/RuntimeBldProg.a > kBuild: Linking bldRTManifest > kBuild: Pass - Libraries > kBuild: Compiling VBoxXPCOMCGlue - > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/cbinding/VBoxXPCOMCGlue.c > kBuild: Compiling VBoxCOM - > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/com.cpp > kBuild: Compiling VBoxCOM - > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/initterm.cpp > In file included from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/include/VBox/com/com.h:30, > from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/initterm.cpp:49: > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/include/VBox/com/defs.h:298:1: > warning: "FALSE" redefined > In file included from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub/prinet.h:89, > from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub/prio.h:51, > from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsILocalFile.h:17, > from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/initterm.cpp:43: > /usr/include/rpc/types.h:58:1: warning: this is the location of the > previous definition > In file included from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/include/VBox/com/com.h:30, > from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/initterm.cpp:49: > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/include/VBox/com/defs.h:299:1: > warning: "TRUE" redefined > In file included from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub/prinet.h:89, > from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub/prio.h:51, > from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsILocalFile.h:17, > from > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/initterm.cpp:43: > /usr/include/rpc/types.h:61:1: warning: this is the location of the > previous definition > kBuild: Compiling VBoxCOM - > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/string.cpp > kBuild: Compiling VBoxCOM - > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Main/glue/AutoLock.cpp > kBuild: Compiling VBoxCOM - > /usr/ports/emulators/virtualbox-ose/work/VirtualBox
Re: Call for Testers: VirtualBox 4.1.0
On Wed, 24 Aug 2011 11:50:21 -0700, Yuri wrote: > On 08/23/2011 18:13, Sean C. Farley wrote: >> >> I have not had time to test v4.1.2 on FreeBSD 8 as a host, but the guest >> additions work well with WinXP as the host and FreeBSD 8 as the guest. I >> think v4.1.2 even fixes a bug where the copy-and-paste between host and >> guest would stop working after running for hours, days or weeks. The >> copy-and-paste hang would even prevent FreeBSD from shutting down cleanly. > > Where is 4.1.2 located? I only see 4.1.0. For 4.1.2 you need to first update devel/kBuild which is also included in the archive. If you need to get back to an older vbox version you also have to downgrade to the old kBuild version then. http://home.bluelife.at/ports/virtualbox-cft-20110817.tar.gz -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox causes kernel panic
On Wed, 24 Aug 2011 09:45:06 +0100, Alvaro Castillo wrote: > On Tue, Aug 23, 2011 at 10:41 AM, Bernhard Froehlich > wrote: >> On Tue, 23 Aug 2011 00:39:37 +0100, Alvaro Castillo wrote: >>> On Mon, Aug 22, 2011 at 12:26 PM, Bernhard Froehlich >>> wrote: >>>> On Mon, 22 Aug 2011 13:14:48 +0200, Bernhard Froehlich wrote: >>>>> On Sat, 20 Aug 2011 19:35:16 +0100, Alvaro Castillo wrote: >>>>>> VirtualBox Version: 4.0.12_OSE r72916 >>>>>> >>>>>> uname -a: FreeBSD shuttle0.lan 9.0-BETA1 FreeBSD 9.0-BETA1 #1: Wed Aug >>>>>> 17 01:21:47 WEST 2011 >>>>>> net...@shuttle0.lan:/usr/obj/usr/src/sys/GALILEO amd64 >>>>>> >>>>>> The kernel panic is occurred when I start a virtual machine with boot >>>>>> from CD/DVD burner/reader device. >>>>>> >>>>>> With or without passthrough. >>>>>> >>>>>> Kernel panic > http://pastie.org/private/0nxanttdmtc9zvtllg0rw >>>>>> >>>>>> atapicam is loaded and hald is working. >>>>> >>>>> I've added the bugreport and stacktrace to our list of known problems >>>>> and will inform you once there is something new about it. >>>>> >>>>> http://wiki.freebsd.org/VirtualBox/ToDo >>>> >>>> I've just seen that the stacktrace does not belong to the panic. So >>>> could you please generate a stacktrace for that panic? >>>> >>>> -- >>>> Bernhard Fröhlich >>>> http://www.bluelife.at/ >>>> >>> Never mind if I have got cd or not have got CD. Causes kernel panic. >>> I cannot report good with gdb because is a kernel panic and cannot use >>> keyboard (change to tty or so) and only can post a "kernel panic" of >>> dmesg says. If you know anyway to change ttyvn in this cases is very >>> helpful. >>> >>> http://pastie.org/private/ca2jupqjv1isnnvozar2w >> >> You can check if a kernel crashdump has been created in /var/crash and >> obtain a stacktrace from that. Or you can try to attach a serial console >> or probably switch to ttyv0 a few seconds before the crash happens (if >> it's reproducible). More information can be found in the Developers >> Handbook: >> >> http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html >> >> -- >> Bernhard Froehlich >> http://www.bluelife.at/ >> > > info http://pastie.org/private/tnhrphtzjkrgbxg9ln2yya > core (fix) http://pastie.org/private/sifv1t9vxf0f4ctfwrpg Thanks a lot for the stacktrace. I was told that this looks like some page fault in pmap_enter. This could either be a FreeBSD bug or a VirtualBox bug but you're the first one to report this so we still have to find out. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.1.0
On Tue, 23 Aug 2011 17:58:18 -0700, Yuri wrote: > I tested 4.1.0 when both host and guest are amd64 FreeBSD-8.2-STABLE. > > What I did: > Installed from stock .iso taken from freebsd.org, installed packages > gnome2, xorg and gdm. > > Two problems: > 1. pkg_add -r keeps stalling while downloading packages from the web. > I know it's not my internet connection because I never see such thing > on my base system. This repeated about 15 times during above mentioned > installs. I had to stop with Ctrl-C and rerun the pkg_add -r command. There was some similar problem some time ago but I don't know if it's the same problem that you see. http://lists.freebsd.org/pipermail/freebsd-stable/2011-July/063322.html > 2. gnome2 when it starts doesn't have mouse and keyboard. Same > starting with startx and with gdm. It shows the screen that can't > receive any mouse clicks or keyboard strokes. How about installing the guest additions? http://wiki.freebsd.org/VirtualBox#head-de5bc57407193ec2728dd102294c6cb3f7609fcb -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.1.0
On Mon, 22 Aug 2011 19:23:30 -0700, Yuri wrote: > vbox-4.1.0 sound is broken. > In Ubuntu-64bit guest install flash plugin and in firefox open > pandora.com and pick some artist (in their flash app). > Music plays but keeps cycling, stopping. > > OSS Host friver. > 8.2-STABLE > > Yuri Are you sure this is a VirtualBox host problem? It doesn't sound like this. Does it only happen with OSS or also PulseAudio or another virtual audio card? (eg. Intel HDA) -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.1.0
On Wed, 17 Aug 2011 18:28:01 +0400, Andrey Fesenko wrote: > On Wed, Aug 17, 2011 at 4:28 PM, Bernhard Froehlich > wrote: >> On Wed, 17 Aug 2011 06:35:26 +0400, Andrey Fesenko wrote: >>> not build after world update r224900 >>> # uname -a >>> FreeBSD beastie.mydomain.local 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224900: >> >> You can either take the patch that was committed a few day ago to the >> ports tree: >> >> http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/virtualbox-ose-kmod/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c?rev=1.3 >> >> or for your convenience i've created a new cft with VirtualBox 4.1.2 >> that also includes this patch: >> >> http://home.bluelife.at/ports/virtualbox-cft-20110817.tar.gz >> > > Ok. Thanks this version build. > > New error kBuild < 0.1.999 in the ports :( Need updates B-deps Sorry, i've forgot to include the updated devel/kBuild port in the archive. It's added now. So you first need to update the devel/kBuild port to 0.1.9998 and then go on with the vbox ports. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.1.0
On Wed, 17 Aug 2011 06:35:26 +0400, Andrey Fesenko wrote: > not build after world update r224900 > # uname -a > FreeBSD beastie.mydomain.local 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224900: > Wed Aug 17 04:48:06 MSK 2011 > andrey@beastie.mydomain.local:/usr/obj/usr/src/sys/W_BOOK amd64 > > end build log > ... > missing-include-dirs -fdiagnostics-show-option -c > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4. > 1.0_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/alloc-r0drv-freebsd.c > ctfconvert -L VERSION alloc-r0drv-freebsd.o > cc -O2 -pipe -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX > -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING > -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64 -fno-strict-aliasing > -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I > include -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 > --param inline-unit-growth=100 --param large > -function-growth=1000 -fno-common -fno-omit-frame-pointer -mno-sse > -mcmodel=kernel -mno-red-zone -mno-mmx - > msoft-float -fno-asynchronous-unwind-tables -ffreestanding > -fstack-protector -std=iso9899:1999 -fstack-prote > ctor -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winl > ine -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > -Wmissing-include-dirs -fdiagnostics-show-opt > ion -c > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.0_OSE/out/freebsd.amd64/release/bin/src/v > boxdrv/r0drv/freebsd/initterm-r0drv-freebsd.c > ctfconvert -L VERSION initterm-r0drv-freebsd.o > cc -O2 -pipe -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX > -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING > -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64 -fno-strict-aliasing > -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I > include -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 > --param inline-unit-growth=100 --param large > -function-growth=1000 -fno-common -fno-omit-frame-pointer -mno-sse > -mcmodel=kernel -mno-red-zone -mno-mmx - > msoft-float -fno-asynchronous-unwind-tables -ffreestanding > -fstack-protector -std=iso9899:1999 -fstack-prote > ctor -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winl > ine -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > -Wmissing-include-dirs -fdiagnostics-show-opt > ion -c > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.0_OSE/out/freebsd.amd64/release/bin/src/v > boxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.0_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/ > r0drv/freebsd/memobj-r0drv-freebsd.c: In function > 'rtR0MemObjFreeBSDPhysPageInit': > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.0_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/ > r0drv/freebsd/memobj-r0drv-freebsd.c:398: error: 'PG_UNMANAGED' > undeclared (first use in this function) > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.0_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/ > r0drv/freebsd/memobj-r0drv-freebsd.c:398: error: (Each undeclared > identifier is reported only once > /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.0_OSE/out/freebsd.amd64/release/bin/src/vboxdrv/ > r0drv/freebsd/memobj-r0drv-freebsd.c:398: error: for each function it > appears in.) > *** Error code 1 You can either take the patch that was committed a few day ago to the ports tree: http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/virtualbox-ose-kmod/files/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c?rev=1.3 or for your convenience i've created a new cft with VirtualBox 4.1.2 that also includes this patch: http://home.bluelife.at/ports/virtualbox-cft-20110817.tar.gz -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: PG_UNMANAGED disappearance in -current
On Thu, 11 Aug 2011 15:44:12 -0400, Jung-uk Kim wrote:
> On Thursday 11 August 2011 02:08 pm, Michael Butler wrote:
>> /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE
>>/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-
>>freebsd.c: In function 'rtR0MemObjFreeBSDPhysPageInit':
>>
>> /usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.0.12_OSE
>>/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-
>>freebsd.c:396: error: 'PG_UNMANAGED' undeclared (first use in this
>> function)
>>
>> Should "pPage->flags = PG_UNMANAGED" now be replaced by some page
>> lock/unlock function which applies "pPage->oflags = VPO_UNMANAGED"?
>
> I am not sure if it is really correct but this patch worked for me:
>
> --- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.orig
> +++ src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c
> @@ -392,8 +392,13 @@
> pPage->wire_count = 1;
> pPage->pindex = iPage;
> pPage->act_count = 0;
> +#if __FreeBSD_version < 90
> pPage->oflags = 0;
> pPage->flags = PG_UNMANAGED;
> +#else
> +pPage->oflags = VPO_UNMANAGED;
> +pPage->flags = 0;
> +#endif
> atomic_add_int(&cnt.v_wire_count, 1);
> }
I have started the same way and then talked to kib. He told me that
vm_phys_alloc_contig() already initializes the page as unmanaged so this
stuff should be a noop in the kmod. I have not runtime tested it myself
though so i would welcome some feedback on that.
http://home.bluelife.at/patches/patch-src-VBox-Runtime-r0drv-freebsd-memobj-r0drv-freebsd.c
---
src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c.orig 2011-04-05
14:34:09.0 +0200
+++ src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c 2011-08-11
15:06:46.0 +0200
@@ -394,9 +394,13 @@
pPage->wire_count = 1;
pPage->pindex = iPage;
pPage->act_count = 0;
-pPage->oflags = 0;
-pPage->flags = PG_UNMANAGED;
atomic_add_int(&cnt.v_wire_count, 1);
+
+#if __FreeBSD_version >= 900040
+Assert(pPage->oflags & VPO_UNMANAGED != 0);
+#else
+Assert(pPage->flags & PG_UNMANAGED != 0);
+#endif
}
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Call for Testers: VirtualBox 4.1.0
Another VirtualBox major release is available since a few weeks and we are proud to provide you a call for testers now. We had very good results during the beta phase so we hope that it will be ready to be committed quite soon. But it all depends on the feedback we get. This VirtualBox release only supports FreeBSD >= 8.0 as host system. If you think you really need FreeBSD 7.x support please get in contact with us. We also want to point out that GNS3 support has been added in VirtualBox 4.1.0 and should be working with our emulators/gns3 port but needs the UDPTUNNEL option to be enabled. Changes in the port since 4.0.12: - VirtualBox updated to 4.1.0 - phpvirtualbox updated to 4.1-1b - FreeBSD 7.x host support dropped - UDPTUNNEL option added [0] - Fix async i/o error checking [1] - Correct fixed memory range for PCI _CRS [2] Submitted by: Mario Lobo [0], Alexander Eichner [1], Jung-uk Kim [2] Reported by: m irya [1], Volodymyr Kostyrko [1] Thanks to all people that have contributed to that release and also reported problems. We really appreciate that! Changelog for 4.1.0: http://www.virtualbox.org/wiki/Changelog FreeBSD specific configuration: http://wiki.freebsd.org/VirtualBox Todo List: http://wiki.freebsd.org/VirtualBox/ToDo Binary packages for FreeBSD 8.2: http://files.etoilebsd.net/vbox/DEBUG/ CFT Ports: http://home.bluelife.at/ports/virtualbox-cft-20110807.tar.gz -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox/fbsd9/amd64 + Ubuntu11.04 guest = crash on install
On Fri, 5 Aug 2011 13:58:16 +0300, m irya wrote: > 2011/8/4 Bernhard Froehlich : >> I think we found the cause of the issue. Could you please throw this >> patch in emulators/virtualbox-ose/files/ and rebuild the port? And then >> please try to reproduce the problem without enabling Host I/O caching. >> >> http://home.bluelife.at/patches/patch-src-VBox-Runtime-r3-freebsd-fileaio-freebsd.cpp >> >> The patch is still untested so please be careful. >> >> -- >> Bernhard Froehlich >> http://www.bluelife.at/ >> > > Back with the test results: > 1) w/o the patch and Host I/O caching for SATA off: Ubuntu-LTS > crashes on boot > 2) w/o the patch and Host I/O caching on: works (so the source of the > problem is correct) > 3) with the patch and caching off: works (so the patch somehow makes > it better) > > Now i'm proceeding with another test case: installing Win7 Home Basic: > 1) w/o the patch and caching off: VBox dies on early installation stage > 2) w/ the patch and caching off: proceeds further, but still dies at a > random point of time while copying files Could you please also generate a stacktrace for this case? I also know a few Windows 7 crashes that are not related to i/o but happen if you enable more than 1 vCPU. So you are probably hitting another bug or some other async i/o bug. > 3) w/ the patch and caching on: finally installed > > i'll do more testing with debug enabled next week. Thanks a lot for your feedback! -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox/fbsd9/amd64 + Ubuntu11.04 guest = crash on install
I think we found the cause of the issue. Could you please throw this patch in emulators/virtualbox-ose/files/ and rebuild the port? And then please try to reproduce the problem without enabling Host I/O caching. http://home.bluelife.at/patches/patch-src-VBox-Runtime-r3-freebsd-fileaio-freebsd.cpp The patch is still untested so please be careful. -- Bernhard Froehlich http://www.bluelife.at/ On Thu, 04 Aug 2011 12:07:47 +0200, Bernhard Froehlich wrote: > This bug is related to async i/o and was already reported once. It is > not reproducible yet but a workaround is to enable "Host I/O Cache" for > the VM. > > AIO: syscall to queue aio requests fails without error code > > -- > Bernhard Fröhlich > http://www.bluelife.at/ > > > On Thu, 4 Aug 2011 09:44:38 +0300, m irya wrote: >> 2011/8/3 Bernhard Froehlich : >>> >>> Please have a look at VBox.log (~/VirtualBox VMs//Logs/VBox.log >>> ) which should contain more useful information. The VirtualBox binary >>> has the suid bit set so coredumps are not produced per default. You need >>> to set kern.sugid_coredump=1 first. >>> >>> sysctl kern.sugid_coredump=1 >>> >>> -- >>> Bernhard Fröhlich >>> http://www.bluelife.at/ >>> >> >> The backtrace of VBoxSDL looks like: >> >> (gdb) bt >> #0 0x000801c8911b in RTLogLoggerEx (pLogger=Cannot access memory >> at address 0x7f043ff8 >> ) at >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Runtime/common/log/logellipsis.cpp:78 >> #1 0x000808e4d143 in pdmacFileAioMgrNormalReqsEnqueue >> (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, >> cReqs=1) >> at >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:553 >> #2 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue >> (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, >> cReqs=1) >> at >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 >> #3 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue >> (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, >> cReqs=1) >> at >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 >> #4 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue >> (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, >> cReqs=1) >> at >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 >> #5 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue >> (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, >> cReqs=1) >> at >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 >> #6 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue >> (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, >> cReqs=1) >> at >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 >> #7 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue >> (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, >> cReqs=1) >> at >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 >> #8 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue >> (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, >> cReqs=1) >> at >> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 >> ... (at least 1 same frames)... >> >> VBox log doesn't contain any useful information either: >> >> 00:00:01.807 VirtualBox 4.0.12_OSE r72916 freebsd.amd64 (Aug 3 2011 >> 23:29:00) release log >> 00:00:01.807 Log opened 2011-08-04T06:27:07.796618000Z >> 00:00:01.807 OS Product: FreeBSD >> 00:00:01.807 OS Release: 9.0-BETA1 >> 00:00:01.807 OS Version: FreeBSD 9.0-BETA1 #15: Wed Aug 3 23:04:12 >> EEST 2011 root@miryanote2:/sys/amd64/compile/MY-LITE >> 00:00:01.808 Host RAM: 2973MB RAM, available: 2260MB >> 00:00:01.808 Executable: /usr/local/lib/virtualbox/VBoxSDL >> 00:00:01.808 Process ID: 16226 >> 00:00:01.808 Package type: BSD_64BITS_GENERIC (OSE) >> 00:00:01.814 Installed Extension Packs: >> 00:00:01.814 None in
Re: VirtualBox/fbsd9/amd64 + Ubuntu11.04 guest = crash on install
This bug is related to async i/o and was already reported once. It is not reproducible yet but a workaround is to enable "Host I/O Cache" for the VM. AIO: syscall to queue aio requests fails without error code -- Bernhard Fröhlich http://www.bluelife.at/ On Thu, 4 Aug 2011 09:44:38 +0300, m irya wrote: > 2011/8/3 Bernhard Froehlich : >> >> Please have a look at VBox.log (~/VirtualBox VMs//Logs/VBox.log >> ) which should contain more useful information. The VirtualBox binary >> has the suid bit set so coredumps are not produced per default. You need >> to set kern.sugid_coredump=1 first. >> >> sysctl kern.sugid_coredump=1 >> >> -- >> Bernhard Fröhlich >> http://www.bluelife.at/ >> > > The backtrace of VBoxSDL looks like: > > (gdb) bt > #0 0x000801c8911b in RTLogLoggerEx (pLogger=Cannot access memory > at address 0x7f043ff8 > ) at > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Runtime/common/log/logellipsis.cpp:78 > #1 0x000808e4d143 in pdmacFileAioMgrNormalReqsEnqueue > (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, > cReqs=1) > at > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:553 > #2 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue > (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, > cReqs=1) > at > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 > #3 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue > (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, > cReqs=1) > at > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 > #4 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue > (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, > cReqs=1) > at > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 > #5 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue > (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, > cReqs=1) > at > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 > #6 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue > (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, > cReqs=1) > at > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 > #7 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue > (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, > cReqs=1) > at > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 > #8 0x000808e4d458 in pdmacFileAioMgrNormalReqsEnqueue > (pAioMgr=0x80bfc4820, pEndpoint=0x80bedd720, pahReqs=0x7f430c20, > cReqs=1) > at > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:610 > ... (at least 1 same frames)... > > VBox log doesn't contain any useful information either: > > 00:00:01.807 VirtualBox 4.0.12_OSE r72916 freebsd.amd64 (Aug 3 2011 > 23:29:00) release log > 00:00:01.807 Log opened 2011-08-04T06:27:07.796618000Z > 00:00:01.807 OS Product: FreeBSD > 00:00:01.807 OS Release: 9.0-BETA1 > 00:00:01.807 OS Version: FreeBSD 9.0-BETA1 #15: Wed Aug 3 23:04:12 > EEST 2011 root@miryanote2:/sys/amd64/compile/MY-LITE > 00:00:01.808 Host RAM: 2973MB RAM, available: 2260MB > 00:00:01.808 Executable: /usr/local/lib/virtualbox/VBoxSDL > 00:00:01.808 Process ID: 16226 > 00:00:01.808 Package type: BSD_64BITS_GENERIC (OSE) > 00:00:01.814 Installed Extension Packs: > 00:00:01.814 None installed! > 00:00:01.815 VBoxSDL: NUM lock initially OFF, CAPS lock initially OFF > 00:00:01.844 SUP: Loaded VMMR0.r0 (/usr/local/lib/virtualbox/VMMR0.r0) > at 0x81120020 - ModuleInit at 81151bf0 and ModuleTerm > at 81151b90 > 00:00:01.844 SUP: VMMR0EntryEx located at 81151ac0, > VMMR0EntryFast at 81151cc0 and VMMR0EntryInt at > 81150ad0 > 00:00:01.881 File system of '/home/mirya/VirtualBox > VMs/Ubuntu-LTS/Snapshots' (snapshots) is unknown > 00:00:01.881 File system of '/home/mirya/VirtualBox > VMs/Ubuntu-LTS/Ubuntu-LTS.vdi' is ufs > 00:00:01.913 VBoxSharedClipboard mode: Bidirectional > 00:00:01.924 * CFGM dump * > 00:00:01.924 [/] (level 0) > 00:00:01.924 CS
Re: FreeBSD in the Oracle Knowledge base (Oracle VM)
On Wed, 3 Aug 2011 22:19:22 +0200, Alexander Leidinger wrote: > Hi, > > today I stumbled upon the possibility to chose FreeBSD as a filter in > the Oracle Support pages. I searched a little bit and found the reason. > It seems Oracle has answers to questions about FreeBSD and virtualbox. > > I thought this may be interesting to someone here. In case someone > knows a little bit more about the level of support Oracle gives > regarding this, I would be interested to hear more about it. That's interesting. Could you share that link? The current status is that FreeBSD is officially not supported at all. Not as Guest and not as Host. For FreeBSD host support they need an OEM customer that requests official support. Klaus told me that they don't have any resources for that at the moment so they would have to hire a few people and it won't be cheap for the OEM. Well. That's the official situation. I don't think waiting for such a customer is worth it. Unofficially the situation looks a lot better. They opened a lot of code from the former closed source blobs and created APIs to extend the functionality. The FreeBSD community is very active with feedback and patches that we push upstream. That works very well and we have good communication with the developers. And then there is Alexander Eichner who did all the initial work and our fast track to get FreeBSD specific patches committed. He is kept very busy recently but is still doing very valuable work for us. It is a bit problematic to get bugs fixed because the vbox code is quite complex and non trivial so we depend a lot on them and cannot debug or fix many problems ourselves. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox/fbsd9/amd64 + Ubuntu11.04 guest = crash on install
On Wed, 3 Aug 2011 09:28:13 +0300, m irya wrote: > Hello, > > I'm trying to install the Ubuntu 11.04 amd64 guest into the Virtualbox > built from ports on amd64 machine. The virtualbox itself (not the > guest OS) crashes at a random points of time during installation on > SIGILL, e.g. the only message in the console is > > Illegal instruction: 4 > > uname -a is > > FreeBSD localhost 9.0-BETA1 FreeBSD 9.0-BETA1 #9: Mon Aug 1 19:34:33 > EEST 2011 root@miryanote2:/sys/amd64/compile/MY-LITE amd64 > > The CPU is i5, the whole CPUID is at the bottom of the message, and > i've tried to build the port with > - -O2 > - -O2 -march=native > - -O2 -march=core2 > > with no luck (all with the stock system gcc 4.2.2pre). Enabling > debugging in port options doesn't help either - no extra info is > output. Neither helps --norawr0 --norawr1 --nohwvirtex --nopatm > --nocsam, it still crashes. In contrast, Ubuntu amd64 10.04.03 > installs and runs w/o problems, but after the recent Ubuntu updates > are applied (perhaps including the more recent linux kernel version), > Vbox crashes the same way when booting it. > > So, > 1) anyone familiar with the problem, are there any workarounds? > 2) how could i at least get the virtualbox processes coredumps to > somehow analyze the problem (whatever i do, i can't find any after it > dies)? Please have a look at VBox.log (~/VirtualBox VMs//Logs/VBox.log ) which should contain more useful information. The VirtualBox binary has the suid bit set so coredumps are not produced per default. You need to set kern.sugid_coredump=1 first. sysctl kern.sugid_coredump=1 -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports: emulation/virtualbox-ose
On Wed, 13 Jul 2011 11:17:45 +0300, Volodymyr Kostyrko wrote: > Hi all. > >> VBoxHeadless -s xp_0 -n -m 18084 > Oracle VM VirtualBox Headless Interface 4.0.10_OSE > (C) 2008-2011 Oracle Corporation > All rights reserved. > > Type Manifest File: /home/arcade/.VirtualBox/xpti.dat > nsNativeComponentLoader: autoregistering begins. > nsNativeComponentLoader: autoregistering succeeded > nNCL: registering deferred (0) > 13/07/2011 11:06:47 Listening for VNC connections on TCP port 18084 > Set framebuffer: buffer=803c04000 w=800 h=600 bpp=32 > Set framebuffer: buffer=80ce47000 w=720 h=400 bpp=32 > 13/07/2011 11:06:50 Got connection from client 10.5.100.44 > 13/07/2011 11:06:50 other clients: > 13/07/2011 11:06:50 Client Protocol Version 3.8 > 13/07/2011 11:06:50 Protocol version sent 3.8, using 3.8 > 13/07/2011 11:06:50 rfbProcessClientSecurityType: executing handler > for type 1 > 13/07/2011 11:06:50 rfbProcessClientSecurityType: returning > securityResult for client rfb version >= 3.8 > 13/07/2011 11:06:50 Pixel format for client 10.5.100.44: > 13/07/2011 11:06:50 8 bpp, depth 8 > 13/07/2011 11:06:50 true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6 > 13/07/2011 11:06:50 rfbProcessClientNormalMessage: ignoring > unsupported encoding type ultraZip > 13/07/2011 11:06:50 Using compression level 9 for client 10.5.100.44 > 13/07/2011 11:06:50 Using image quality level 0 for client 10.5.100.44 > 13/07/2011 11:06:50 Enabling KeyboardLedState protocol extension for > client 10.5.100.44 > 13/07/2011 11:06:50 Enabling NewFBSize protocol extension for client > 10.5.100.44 > 13/07/2011 11:06:50 Enabling LastRect protocol extension for client > 10.5.100.44 > 13/07/2011 11:06:50 Enabling SupportedMessages protocol extension for > client 10.5.100.44 > 13/07/2011 11:06:50 Enabling SupportedEncodings protocol extension > for client 10.5.100.44 > 13/07/2011 11:06:50 Enabling ServerIdentity protocol extension for > client 10.5.100.44 > 13/07/2011 11:06:50 Using tight encoding for client 10.5.100.44 > Set framebuffer: buffer=80da04000 w=640 h=480 bpp=32 > 13/07/2011 11:06:51 Sending rfbEncodingNewFBSize for resize to (640x480) > Set framebuffer: buffer=80ce47000 w=720 h=400 bpp=32 > 13/07/2011 11:07:04 Sending rfbEncodingNewFBSize for resize to (720x400) > Set framebuffer: buffer=80dc04000 w=640 h=480 bpp=32 > 13/07/2011 11:07:04 Sending rfbEncodingNewFBSize for resize to (640x480) > > !!Assertion Failed!! > Expression: i < 0 > Location : > /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.10_OSE/src/VBox/Devices/USB/DevOHCI.cpp(1695) > bool ohci_in_done_queue_check(OHCI*, uint32_t) > TD 0x02210080 (i=1) > Trace/BPT trap > > The machine has only: > > Pointing Device: USB Tablet > Keyboard Device: USB Keyboard > > I personally think USB support is not mature enough for stable use. Yes, we know and I fully agree that it's not stable yet. I've added the report to the ToDo list. http://wiki.freebsd.org/VirtualBox/ToDo -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: ports: emulators/virtualbox-ose --pagefusion
On Wed, 13 Jul 2011 11:24:24 +0300, Volodymyr Kostyrko wrote: > Hi all. > >> VBoxHeadless -s xp_0 -n -m 18084 > > Oracle VM VirtualBox Headless Interface 4.0.10_OSE > (C) 2008-2011 Oracle Corporation > All rights reserved. > > Type Manifest File: /home/arcade/.VirtualBox/xpti.dat > nsNativeComponentLoader: autoregistering begins. > nsNativeComponentLoader: autoregistering succeeded > nNCL: registering deferred (0) > 13/07/2011 11:18:27 Listening for VNC connections on TCP port 18084 > Set framebuffer: buffer=803c04000 w=800 h=600 bpp=32 > Set framebuffer: buffer=80d20f000 w=720 h=400 bpp=32 > Set framebuffer: buffer=80da04000 w=640 h=480 bpp=32 > 13/07/2011 11:18:31 Got connection from client 10.5.100.44 > 13/07/2011 11:18:31 other clients: > 13/07/2011 11:18:31 Client Protocol Version 3.8 > 13/07/2011 11:18:31 Protocol version sent 3.8, using 3.8 > 13/07/2011 11:18:31 rfbProcessClientSecurityType: executing handler > for type 1 > 13/07/2011 11:18:31 rfbProcessClientSecurityType: returning > securityResult for client rfb version >= 3.8 > 13/07/2011 11:18:31 Pixel format for client 10.5.100.44: > 13/07/2011 11:18:31 8 bpp, depth 8 > 13/07/2011 11:18:31 true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6 > 13/07/2011 11:18:31 rfbProcessClientNormalMessage: ignoring > unsupported encoding type ultraZip > 13/07/2011 11:18:31 Using compression level 9 for client 10.5.100.44 > 13/07/2011 11:18:31 Using image quality level 0 for client 10.5.100.44 > 13/07/2011 11:18:31 Enabling KeyboardLedState protocol extension for > client 10.5.100.44 > 13/07/2011 11:18:31 Enabling NewFBSize protocol extension for client > 10.5.100.44 > 13/07/2011 11:18:31 Enabling LastRect protocol extension for client > 10.5.100.44 > 13/07/2011 11:18:31 Enabling SupportedMessages protocol extension for > client 10.5.100.44 > 13/07/2011 11:18:31 Enabling SupportedEncodings protocol extension > for client 10.5.100.44 > 13/07/2011 11:18:31 Enabling ServerIdentity protocol extension for > client 10.5.100.44 > 13/07/2011 11:18:31 Using tight encoding for client 10.5.100.44 > Set framebuffer: buffer=80d20f000 w=720 h=400 bpp=32 > 13/07/2011 11:18:43 Sending rfbEncodingNewFBSize for resize to (720x400) > Set framebuffer: buffer=80dc04000 w=640 h=480 bpp=32 > 13/07/2011 11:18:43 Sending rfbEncodingNewFBSize for resize to (640x480) > Set framebuffer: buffer=807c0 w=1024 h=768 bpp=32 > 13/07/2011 11:19:23 Sending rfbEncodingNewFBSize for resize to (1024x768) > > !!Assertion Failed!! > Expression: RT_SUCCESS_NP(rc) > Location : > /tmp/ports/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.10_OSE/src/VBox/VMM/VMMR3/PGMSharedPage.cpp(207) > VBOXSTRICTRC pgmR3SharedModuleRegRendezvous(VM*, VMCPU*, void*) > VERR_PGM_PHYS_INVALID_PAGE_ID (-1637) - Trying to free a page with an > invalid Page ID. > Trace/BPT trap I just talked to the vbox developers and they told me this is a known problem that you should also see with other hosts but it's hard to reproduce. Do you have multiple VMs running with page fusion enabled when the error occurs? Please send the VBox.log (should be in $HOME/VirtualBox VMs//logs/VBox.log) of your failed session for further debugging. Thanks for your help! -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: vbox-4.0.8: are guests supposed to see USB devices?
On Fri, 27 May 2011 05:41:15 -0700, Yuri wrote: > Ubuntu guests don't see any USB devices on amd64 host. I know. The only guests where we have got a few success replies were with Windows XP. Mass-storage does not work yet. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VB 4.0.8 is working very well
On Mon, 23 May 2011 14:29:45 -0700, Kevin Oberman wrote: > I installed 4.0.8 this morning and it works very well. No problems at > all to this point using FreeBSD as the host and Windows7 as guest. I > may install Fedora a bit later. > > So far everything seems to be working very well. The issues I had with > 4.0.4 are gone and there is USB support. (I have yet to try it, though.) > > One thing I realized quickly is that I didn't have VNC support. A small > bit of looking made me realize that I needed to re-build with different > config options and it is rebuilding now. > > I would suggest that you look at adding a config section to the wiki. > While most options are pretty obvious, I had to look up VDE (don't need > it) and I still don't know what 'Webservice' covers. (Not knowing, I > didn't enable it.) It also does not even mention the virtualbox-ose-kmod > port. I know it will be installed as a dependency, but it could easily > be missed in an upgrade. Even in the handbook entry (which is looking a > bit stale) the only option mentioned is GuestAdditions. > > I'm willing to re-work the handbook entry and submit it to whoever is > appropriate and can add a 'config' section to the wiki if it's OK, once > I know what all the options really mean. How about fixing the option descriptions? I would be glad if some native speaker could come up with better descriptions that fit into the maximum length. For now I just try to describe what the options do: QT4 QT4 frontend DEBUG Additional logging and a lot of asserts DBUSDBUS+HAL and we need this for Host CD/DVD access PULSEAUDIO PulseAudio sound output X11 Provides an SDL frontend and is required for QT4 frontend VDE Virtual Distributed Ethernet driver (http://vde.sourceforge.net/) VNC VNC server support WEBSERVICE SOAP backend used by eg www/phpvirtualbox NLS NLS support for the QT4 frontend -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: R: Re: emulators/virtualbox-ose: error building package
On Mon, 23 May 2011 22:15:41 +0200 (CEST), Barbara wrote: >>On Sun, 22 May 2011 19:04:25 +0200 (CEST), Barbara wrote: >>> I had the following error while building a package for the new virtualbox: >>> >>> ===> Building package for virtualbox-ose-4.0.8 >>> tar: lib/virtualbox/VBoxDbg.so: Cannot stat: No such file or directory >>> tar: Error exit delayed from previous errors. >>> pkg_create: make_dist: tar command failed with code 256 >>> *** Error code 1 >> >>Could you please tell me the output of "make showconfig"? >> >>-- > > Sure! > > $ cd /usr/ports/emulators/virtualbox-ose && make showconfig > ===> The following configuration options are available for virtualbox-ose- > 4.0.8: > QT4=off "Build with QT4 Frontend" > DEBUG=off "Build with debugging symbols" > GUESTADDITIONS=on "Build with Guest Additions" > DBUS=on "Build with D-Bus and HAL support" > PULSEAUDIO=on "Build with PulseAudio" > X11=on "Build with X11 support" > VDE=off "Build with VDE support" > VNC=off "Build with VNC support" > WEBSERVICE=off "Build Webservice" > NLS=off "Native language support" > ===> Use 'make config' to modify these settings Thanks. I just committed a fix. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: emulators/virtualbox-ose: error building package
On Sun, 22 May 2011 19:04:25 +0200 (CEST), Barbara wrote: > I had the following error while building a package for the new virtualbox: > > ===> Building package for virtualbox-ose-4.0.8 > tar: lib/virtualbox/VBoxDbg.so: Cannot stat: No such file or directory > tar: Error exit delayed from previous errors. > pkg_create: make_dist: tar command failed with code 256 > *** Error code 1 Could you please tell me the output of "make showconfig"? -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Future direction of virtualbox-ose port on FreeBSD
On Tue, 17 May 2011 12:36:43 -0700, Cy Schubert wrote: > In message <4da6ad3d.7040...@mittelstaedt.us>, Ted Mittelstaedt writes: >> On 4/13/2011 4:38 AM, Bernhard Froehlich wrote: >> > Hi VirtualBox users. >> > >> > I'm sending this because there are a few problems in how we currently >> > maintain the emulators/virtualbox-ose ports on FreeBSD. I want to >> > outline my main concerns and propose a better way to solve that. >> > >> > The VirtualBox port is already very critical for many users and very >> > complex at the same time so it gets harder and harder to update the port >> > to new major versions without getting too much negative feedback from >> > users. In the past we did a call for testers when upstream released a >> > new major version (3.1.0, 3.2.0, 4.0.0) and got the update in the tree >> > after their first patch release (3.1.2, 3.2.2) but now for the 4.0 >> > release cycle we need at least to wait for 4.0.6 to get a useable state. >> > >> > Because of this long delay more and more people are using the cft and >> > our development ports. We do not want that average users use that ports >> > just to get to a newer version because they contain additional risks and >> > are usually unstable versions (no support, irregular updates, broken >> > ...). But we also do not want to make it harder for our testers to >> > provide feedback because your feedback is very valuable to us and we >> > need each tester we have. >> > >> > So we currently have these problems: >> > 1) we need a stable version around if you hit a problem at the new >> > version >> > 2) we need to get new major versions out earlier to testers >> > 3) we need to attract more testers >> > >> > >> > We could solve this problems with "unstable" ports and people can use >> > them if they care about it but we don't have that infrastructure in >> > FreeBSD yet. We could also create -devel ports but that only solves one >> > part of the problem and generates an huge amount of work on our side. >> > Our internal -devel ports are most of the time built with "trunk" code >> > so more or less alpha quality code. So that's not going to fly either. >> > >> > >> > Instead we came up with two improvements: >> > 1) Before a major version hits the tree we do a repocopy with the >> > current version. So in case you have a problem with the major version >> > you can fallback to the old version. It will be marked DEPRECATED with >> > the next major update and removed 2 months after that. Major updates for >> > vbox are 3.1.x, 3.2.x, 4.0.x >> > >> > 2) We provide binary packages and PBIs for virtualbox when we do a Call >> > for Testers and probably also on a regular basis to lower the burden to >> > test it. That only works for FreeBSD releases because the kernel module >> > needs to be build for a specific kernel. So if you use a STABLE kernel >> > you won't benefit from that. >> > >> > That means for us that we can bring in a new major version a bit >> > earlier than now but we will continue to do extensive testing first. So >> > you will still not see a .0 release in the ports. >> > >> > >> > What do you think about it? Any better ideas? >> > >> >> I vote for binary releases for the testers. From a test standpoint >> there is a huge benefit for you guys to have everyone running >> the same build, built the same way. Currently FreeBSD development >> snapshots are released binary, this isn't much different. >> >> Granted you may have some testers with weird systems setup that >> won't like it, but they can always keep the last RELEASE kernel around >> and boot their system on it temporarily for testing purposes only. >> >> Anyone running vbox in production is very likely NOT testing >> on their production servers. Ideally they are imaging their >> production boxes and booting the image on a spare box and testing >> on that - so worrying about fallback is kind of pointless - if the >> new version doesn't work, then they don't need to fall back >> to a prior one. > > Would it be possible install by default vbox 4.0.x into an alternate > LOCALBASE, allowing users to at least try the new vbox without having to > uninstall the old? No. You cannot load both kernel modules at the same time so installing both is a bad idea. Custom LOCALBASE should be possible (it works on PC-BSD after all) but it could cause some troubles because of their hardening (they check the path of the suid binaries). -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VBox 4.0.8 module dependencies
On Tue, 17 May 2011 11:31:15 -0400, Michael Butler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > There are two symbols referenced by the 4.0.8 vboxdrv which are not > built/linked in the current bluelife SVN revision (r1316). > > They produce the following messages .. > > kernel: link_elf: symbol RTStrCopy undefined > > .. then, when I get past that .. > > kernel: link_elf: symbol RTStrNCmp undefined > > Not being quite (yet) sure how to get a suitable patch into the build, I > thought I'd report it .. It's already fixed in r1319. http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1319 -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
On Mon, 09 May 2011 05:57:05 -0700, Yuri wrote: > I think 4.0.6 is quite stable now. Is it really less stable than the > current version in ports 3.2.12? There are a few regressions also in 4.0.6 but it's already a lot better than 4.0.4. We have already decided last week to update the ports to 4.0.6 soon (currently waiting for a repocopy). > Why don't you at least put them into ports/emulators repository with > -devel suffix like many other ports do? So that there is no need to go > through the third party repository. Throwing another -devel port in the won't solve anything! In fact it would even make the situation much worse because it trains people to use beta software which we strongly discourage and causes even more error reports and debugging headaches for another version that we would have to maintain. We have that 3rd party repository because it is our working repository. You should not use it at all if you don't want to be a beta tester and work with us to solve specific problems. If you use them for regular systems you are clearly doing something wrong except you have done a _lot_ of testing. We know that the situation is not perfect and we have already taken a few actions to improve it but if that is still not enough to you we need more people and a bigger team to test earlier, more and faster. Read here: http://lists.freebsd.org/pipermail/freebsd-emulation/2011-April/008633.html -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
On Sat, 07 May 2011 08:31:57 -0700, Yuri wrote:
> I had Ubuntu (64bit) VM with the snapshot, created under vbox-4.0.4.
> Now after upgrading to vbox-4.0.6 I restored this snapshot.
> But when trying to start the machine it fails with the message:
>
> Failed to open session for the virtual machine Ubuntu64.
> Failed to load unit 'HGCM' (VERR_INVALID_PARAMETER).
> Details
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: Console
> Interface: ICOnsole {}
>
> Not sure what to do with this machine now.
Looks like an upstream bug and it is not FreeBSD specific - See
http://www.virtualbox.org/ticket/6314 and
http://forums.virtualbox.org/viewtopic.php?f=6&t=28369
There is also an workaround how to recover from that error.
--
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
On Fri, 29 Apr 2011 23:13:04 +0300, Volodymyr Kostyrko wrote: > 22.04.2011 14:01, Bernhard Froehlich wrote: >> It's about two months since the last call for testers and a lot of >> bugfixing has happened since then. Not all of the reported problems were >> FreeBSD related which is a good indication that we're not too far behind >> the stability of the other hosts. So let's get it one once again. > > Some more questions. > > 1. Should any problems with guest systems be reported? Something like > "DragonflyBSD doesn't correctly detect CD-ROM"? Please verify first that it also happens with a supported host (Linux, Windows, Mac) and then report it upstream at VirtualBox or probalby in that case better DragonflyBSD. > 2. When I have stuck process (using 0% cpu / using 100% cpu) what is > a correct way to report it? ktrace(1)? gcore(1)? Those problems are hard to find and usually can only be fixed if a developer can reproduce it. I have also seen a 100% cpu problem recently but as a workaround it helped to pause the VM and resume it after restarting virtualbox. You could check VBox.log or any debug logfiles if they have reported anything abnormal. > 3. I see that my working machines after correct guest shutdown ends > up throwing 'Segmantation fault'. Should I report that too? During the call for testers we recommend to always build with DEBUG option enabled to spot all errors but in some cases that triggers assertions that are uncritical and sometimes even bugs in the debug code paths. So if you see a Segmentation fault please send us a stacktrace from the core file (already described somewhere in the thread how to get a core file and stacktrace) so that someone can check that. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
On Thu, 28 Apr 2011 11:17:10 +0200, Bernhard Froehlich wrote: > On Wed, 27 Apr 2011 23:28:19 +0300, Volodymyr Kostyrko wrote: >> 22.04.2011 14:01, Bernhard Froehlich wrote: >> >> As I understand reporting bugs is good? > > Yes, bugreports are important and good if you want that the bugs get > fixed. > >> uname -a >> FreeBSD flashk0.3501.lan 8.2-STABLE FreeBSD 8.2-STABLE #2: Mon Apr 25 >> 21:50:44 UTC 2011 arc...@flashk0.3501.lan:/usr/obj/usr/src/sys/MINIMAL >> amd64 >> >> Session transcript: >> >> VBoxManage createvm --name test --register >> >> VBoxManage modifyvm test --ostype Windows7_64 --memory 512 >> --pagefusion on --vram 32 --acpi on --ioapic on --pae on --hpet on >> --hwvirtex on --hwvirtexexcl on --nestedpaging on --largepages on >> --accelerate3d on --accelerate2dvideo on --chipset ich9 --nic1 nat >> --nictype1 Am79C970A --mouse usbtablet --keyboard usb --audio oss >> --audiocontroller hda --usb on --usbehci on >> >> VBoxManage storagectl test --add sata --name SATA >> >> VBoxManage storageattach test --storagectl SATA --port 1 --device 0 >> --type dvddrive --medium win7_7100_x64.iso >> >> # zfs create -s -o compression=on -V 20G flashk0/vbox_test >> >> VBoxManage internalcommands createrawvmdk -filename VirtualBox\ >> VMs/test/test.vmdk -rawdisk /dev/zvol/flashk0/vbox_test >> >> VBoxManage storageattach test --storagectl SATA --port 0 --device 0 >> --type hdd --medium VirtualBox\ VMs/test/test.vmdk >> >> VBoxHeadless -s test -n -m 18083 >> >> And it dumps core on signal 11. >> >> Full bt available at http://limbo.xim.bz/core.bt.full.xz >> >> What am I missing here? > > Thanks i've added it to our list and will report back when I have some > news. > > http://wiki.freebsd.org/VirtualBox/ToDo from Alexander Eichner: The problem is that the syscall to queue aio requests fails but no request has an error code. It could be possible that aio and zfs has some bug. As a workaround you can enable the host I/O cache of the storage controller for the VM or unload the aio kernel module on the host. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
On Wed, 27 Apr 2011 23:28:19 +0300, Volodymyr Kostyrko wrote: > 22.04.2011 14:01, Bernhard Froehlich wrote: > > As I understand reporting bugs is good? Yes, bugreports are important and good if you want that the bugs get fixed. > uname -a > FreeBSD flashk0.3501.lan 8.2-STABLE FreeBSD 8.2-STABLE #2: Mon Apr 25 > 21:50:44 UTC 2011 arc...@flashk0.3501.lan:/usr/obj/usr/src/sys/MINIMAL > amd64 > > Session transcript: > > VBoxManage createvm --name test --register > > VBoxManage modifyvm test --ostype Windows7_64 --memory 512 > --pagefusion on --vram 32 --acpi on --ioapic on --pae on --hpet on > --hwvirtex on --hwvirtexexcl on --nestedpaging on --largepages on > --accelerate3d on --accelerate2dvideo on --chipset ich9 --nic1 nat > --nictype1 Am79C970A --mouse usbtablet --keyboard usb --audio oss > --audiocontroller hda --usb on --usbehci on > > VBoxManage storagectl test --add sata --name SATA > > VBoxManage storageattach test --storagectl SATA --port 1 --device 0 > --type dvddrive --medium win7_7100_x64.iso > > # zfs create -s -o compression=on -V 20G flashk0/vbox_test > > VBoxManage internalcommands createrawvmdk -filename VirtualBox\ > VMs/test/test.vmdk -rawdisk /dev/zvol/flashk0/vbox_test > > VBoxManage storageattach test --storagectl SATA --port 0 --device 0 > --type hdd --medium VirtualBox\ VMs/test/test.vmdk > > VBoxHeadless -s test -n -m 18083 > > And it dumps core on signal 11. > > Full bt available at http://limbo.xim.bz/core.bt.full.xz > > What am I missing here? Thanks i've added it to our list and will report back when I have some news. http://wiki.freebsd.org/VirtualBox/ToDo -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Wed, 27 Apr 2011 15:28:11 -0400, Ryan Stone wrote:
> (Sorry for the noise earlier about the PBIs not working under PC-BSD;
> I'm not sure how I missed that had been already reported).
>
> I tried the new amd64 PBI and I am able to successfully start VMs now.
> I had one VM(running some relatively recent version of amd64 HEAD)
> boot up fine, but a second one (also running amd64 HEAD, but maybe a
> different svn revision) gets a Guru Meditation during startup. I'm
> not sure what is causing the crash. In their original configurations
> the working VM booted off of an emulated IDE disk while the broken VM
> booted of an emulated SATA disk, however I just tried changing the
> SATA disk to instead be an IDE disk and it doesn't seems to have
> resolved the problem.
>
> I'm not getting a corefile for the crash(or I'm unable to find it). I
> do have kern.sugid_coredump=1 and I'm running the PBI. Is this
> expected for a Guru Meditation, or should it be putting a core
> somewhere? I've put the VBox.log for the most recent crash here:
No, that looks fine.
> http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log
>
> This seems to be easy to reproduce so let me know if there's any more
> information that I can gather.
I've added it to the Todo list for 4.0.6 and will report it to the vbox
developers tomorrow. Sorry, don't have a clue what is going wrong there
- but i'm sure they know.
http://wiki.freebsd.org/VirtualBox/ToDo
> Also, the working VM was emulating uniprocessor machine. I tried
> adding a second CPU and that VM started crashing, too. I tried
> changing the broken VM to have only one core but it still crashes.
> I'm not sure if it's related to the first crash or not.
Look at the relevant parts of VBox.log and see if they look about the
same.
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current pointer
vs 84362000
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current VMCS version e
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Entered Cpu 3
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU0 Current Cpu 2
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current pointer
vs 84365000
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current VMCS version 0
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Entered Cpu 0
00:00:08.374 VERR_VMX_INVALID_VMCS_PTR: CPU1 Current Cpu 0
00:00:08.374
!!
00:00:08.374 !!
00:00:08.374 !! Guru Meditation -4001
(VERR_VMX_INVALID_VMCS_PTR)
00:00:08.374 !!
00:00:08.374 !!
00:00:08.374 !! {mappings, }
00:00:08.374 !!
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 - FreeBSD Guest Additions
On Wed, 27 Apr 2011 14:29:00 +0200, Bernhard Froehlich wrote: > On Wed, 27 Apr 2011 17:32:49 +0600, Rion wrote: >> 2011/4/27 Bernhard Froehlich : >>> On Wed, 27 Apr 2011 16:13:53 +0600, Rion wrote: >>>> 2011/4/27 Bernhard Froehlich : >>>>> On Wed, 27 Apr 2011 13:12:29 +0600, Rion wrote: >>>>>> Hi >>>>>> >>>>>> I just installed FreeBSD-8.2 as guest by this instruction >>>>>> http://wiki.freebsd.org/VirtualBox >>>>>> using blueports. >>>>>> >>>>>> * Mouse integration works well >>>>>> * Clipboard integration doesn't work >>>>>> * Auto guest screen resize on VB window resize doesn't work >>>>>> >>>>>> I'm absolutely new for FreeBSD and don't know what can be wrong. >>>>>> and here is my investigation. >>>>>> Xorg.0.log doesn't mention any issues >>>>>> I tried to manually start VBoxClient-all but it writes to stdout >>>>>> "Failed to connect to the VirtualBox kernel service" 4 times >>>>>> But if it's started by root(through sudo) nothing wrong happened >>>>>> and moreover clipboard and display integration starts working. >>>>>> I tried to set 0666 permissions to /dev/vboxguest* but this doesn't help. >>>>>> In any case it must be started as not-root user since its started by >>>>>> *.desktop file. >>>>>> >>>>>> from other things: >>>>>> * vboxguest kernel module loaded fine >>>>>> * VBoxService started and I see it in processes >>>>>> * nothing wrong in dmesg and syslog from first look. >>>>>> >>>>>> Not-mentioned in wiki things: >>>>>> * procfs must be mounted >>>>>> * xrandr must be installed >>>>> >>>>> Clipboard sharing used to work in virtualbox 3.2. but I also saw that >>>>> they do not work on 4.0. >>>>> >>>>> I also know that the virtualbox guest additions are generally in a very >>>>> bad shape. There are at least a few more bugs and features missing but >>>>> nobody had time yet to debug that and fix those problems. I spend some >>>>> time to integrate the additions better into the system (rc scripts, >>>>> autostart ...) during the 4.0 development phase but I guess we need a >>>>> few weeks of manpower to get the additions fully tested first, identify >>>>> the problems and implement the missing features. We actually already >>>>> started with the testing and identifying: >>>>> >>>>> http://wiki.freebsd.org/VirtualBox/ToDo >>>>> >>>>> If someone wants to contribute I think that is a very nice project. >>>>> >>>>> -- >>>>> Bernhard Fröhlich >>>>> http://www.bluelife.at/ >>>>> >>>> >>>> thanks for reply >>>> >>>> after all I found out that setting sticky bit on VBoxClient is enough to >>>> make >>>> clipboard/display integration and seamless mode working. >>>> I didn't try other stuff though. >>> >>> Please describe that in more details. What exactly have you done? Do >>> you mean the filesystem sticky bit? >>> >>> -- >>> Bernhard Fröhlich >>> http://www.bluelife.at/ >>> >> >> yep chmod +s /usr/local/bin/VBoxClient > > Thanks! I will try to verify that in the evening if nobody else > confirms that in the meantime. That would be a very easy fix for the > additions. Works fine for me. Change is committed in blueports. http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1297 -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Wed, 27 Apr 2011 09:07:16 -0400, Kris Moore wrote:
> On 04/26/2011 16:18, Bernhard Froehlich wrote:
>> On Tue, 26 Apr 2011 15:42:29 -0400, Ryan Stone wrote:
>>> On Sun, Apr 24, 2011 at 8:02 AM, Bernhard Froehlich
>>> wrote:
>>>> On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote:
>>>>> PBIs for PC-BSD are currently worked on and will hopefully be available
>>>>> in a few days.
>>>> Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts
>>>> to provide the PBIs!
>>>>
>>>> PC-BSD 8.x 32bit:
>>>> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi
>>>> ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi
>>>>
>>>> PC-BSD 8.x 64bit:
>>>> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi
>>>> ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi
>>>>
>>>>
>>>> Feedback (positive and negative) from PC-BSD users is very welcome!
>>>>
>>> I installed the 64-bit PBI on my PC-BSD 8.2 machine, but I am unable
>>> to start any virtual machines(both pre-existing VMs or a new VM that I
>>> tried to create). I get the following error dialog:
>>>
>>> Failed to open a session for the virtual machine RELENG_8_amd64.
>>>
>>> Failed to load VMMR0.r0
>>> (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
>>>
>>> Unknown error creating VM
>>> (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
>>>
>>> Details:
>>>
>>> Result Code:
>>> NS_ERROR_FAILURE (0x80004005)
>>> Component:
>>> Console
>>> Interface:
>>> IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
>> Yeah, thanks we already know. They added some strict hardening checks
>> in virtualbox 4.0 that fail on PC-BSD. Kris Moore is currently
>> rebuilding the PBIs with some modifications.
>>
>> That's exactly why we have call for testers so find such weird problems
>> that nobody could think of.
>>
>
> This bug has been fixed now for the 8.x / amd64 version of VirtualBox
> 4.0.6 PBI:
>
> ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi
>
> The 32bit version is still in the queue for rebuilding, but should be
> done in the next 24 hours or so.
Thanks a lot! Have you made any changes that we can include in the vbox
port or just the pbi packaging?
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 - FreeBSD Guest Additions
On Wed, 27 Apr 2011 17:32:49 +0600, Rion wrote: > 2011/4/27 Bernhard Froehlich : >> On Wed, 27 Apr 2011 16:13:53 +0600, Rion wrote: >>> 2011/4/27 Bernhard Froehlich : >>>> On Wed, 27 Apr 2011 13:12:29 +0600, Rion wrote: >>>>> Hi >>>>> >>>>> I just installed FreeBSD-8.2 as guest by this instruction >>>>> http://wiki.freebsd.org/VirtualBox >>>>> using blueports. >>>>> >>>>> * Mouse integration works well >>>>> * Clipboard integration doesn't work >>>>> * Auto guest screen resize on VB window resize doesn't work >>>>> >>>>> I'm absolutely new for FreeBSD and don't know what can be wrong. >>>>> and here is my investigation. >>>>> Xorg.0.log doesn't mention any issues >>>>> I tried to manually start VBoxClient-all but it writes to stdout >>>>> "Failed to connect to the VirtualBox kernel service" 4 times >>>>> But if it's started by root(through sudo) nothing wrong happened >>>>> and moreover clipboard and display integration starts working. >>>>> I tried to set 0666 permissions to /dev/vboxguest* but this doesn't help. >>>>> In any case it must be started as not-root user since its started by >>>>> *.desktop file. >>>>> >>>>> from other things: >>>>> * vboxguest kernel module loaded fine >>>>> * VBoxService started and I see it in processes >>>>> * nothing wrong in dmesg and syslog from first look. >>>>> >>>>> Not-mentioned in wiki things: >>>>> * procfs must be mounted >>>>> * xrandr must be installed >>>> >>>> Clipboard sharing used to work in virtualbox 3.2. but I also saw that >>>> they do not work on 4.0. >>>> >>>> I also know that the virtualbox guest additions are generally in a very >>>> bad shape. There are at least a few more bugs and features missing but >>>> nobody had time yet to debug that and fix those problems. I spend some >>>> time to integrate the additions better into the system (rc scripts, >>>> autostart ...) during the 4.0 development phase but I guess we need a >>>> few weeks of manpower to get the additions fully tested first, identify >>>> the problems and implement the missing features. We actually already >>>> started with the testing and identifying: >>>> >>>> http://wiki.freebsd.org/VirtualBox/ToDo >>>> >>>> If someone wants to contribute I think that is a very nice project. >>>> >>>> -- >>>> Bernhard Fröhlich >>>> http://www.bluelife.at/ >>>> >>> >>> thanks for reply >>> >>> after all I found out that setting sticky bit on VBoxClient is enough to >>> make >>> clipboard/display integration and seamless mode working. >>> I didn't try other stuff though. >> >> Please describe that in more details. What exactly have you done? Do >> you mean the filesystem sticky bit? >> >> -- >> Bernhard Fröhlich >> http://www.bluelife.at/ >> > > yep chmod +s /usr/local/bin/VBoxClient Thanks! I will try to verify that in the evening if nobody else confirms that in the meantime. That would be a very easy fix for the additions. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 - FreeBSD Guest Additions
On Wed, 27 Apr 2011 16:13:53 +0600, Rion wrote: > 2011/4/27 Bernhard Froehlich : >> On Wed, 27 Apr 2011 13:12:29 +0600, Rion wrote: >>> Hi >>> >>> I just installed FreeBSD-8.2 as guest by this instruction >>> http://wiki.freebsd.org/VirtualBox >>> using blueports. >>> >>> * Mouse integration works well >>> * Clipboard integration doesn't work >>> * Auto guest screen resize on VB window resize doesn't work >>> >>> I'm absolutely new for FreeBSD and don't know what can be wrong. >>> and here is my investigation. >>> Xorg.0.log doesn't mention any issues >>> I tried to manually start VBoxClient-all but it writes to stdout >>> "Failed to connect to the VirtualBox kernel service" 4 times >>> But if it's started by root(through sudo) nothing wrong happened >>> and moreover clipboard and display integration starts working. >>> I tried to set 0666 permissions to /dev/vboxguest* but this doesn't help. >>> In any case it must be started as not-root user since its started by >>> *.desktop file. >>> >>> from other things: >>> * vboxguest kernel module loaded fine >>> * VBoxService started and I see it in processes >>> * nothing wrong in dmesg and syslog from first look. >>> >>> Not-mentioned in wiki things: >>> * procfs must be mounted >>> * xrandr must be installed >> >> Clipboard sharing used to work in virtualbox 3.2. but I also saw that >> they do not work on 4.0. >> >> I also know that the virtualbox guest additions are generally in a very >> bad shape. There are at least a few more bugs and features missing but >> nobody had time yet to debug that and fix those problems. I spend some >> time to integrate the additions better into the system (rc scripts, >> autostart ...) during the 4.0 development phase but I guess we need a >> few weeks of manpower to get the additions fully tested first, identify >> the problems and implement the missing features. We actually already >> started with the testing and identifying: >> >> http://wiki.freebsd.org/VirtualBox/ToDo >> >> If someone wants to contribute I think that is a very nice project. >> >> -- >> Bernhard Fröhlich >> http://www.bluelife.at/ >> > > thanks for reply > > after all I found out that setting sticky bit on VBoxClient is enough to make > clipboard/display integration and seamless mode working. > I didn't try other stuff though. Please describe that in more details. What exactly have you done? Do you mean the filesystem sticky bit? -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
RE: Call for Testers: VirtualBox 4.0.6 - FreeBSD Guest Additions
On Wed, 27 Apr 2011 13:12:29 +0600, Rion wrote: > Hi > > I just installed FreeBSD-8.2 as guest by this instruction > http://wiki.freebsd.org/VirtualBox > using blueports. > > * Mouse integration works well > * Clipboard integration doesn't work > * Auto guest screen resize on VB window resize doesn't work > > I'm absolutely new for FreeBSD and don't know what can be wrong. > and here is my investigation. > Xorg.0.log doesn't mention any issues > I tried to manually start VBoxClient-all but it writes to stdout > "Failed to connect to the VirtualBox kernel service" 4 times > But if it's started by root(through sudo) nothing wrong happened > and moreover clipboard and display integration starts working. > I tried to set 0666 permissions to /dev/vboxguest* but this doesn't help. > In any case it must be started as not-root user since its started by > *.desktop file. > > from other things: > * vboxguest kernel module loaded fine > * VBoxService started and I see it in processes > * nothing wrong in dmesg and syslog from first look. > > Not-mentioned in wiki things: > * procfs must be mounted > * xrandr must be installed Clipboard sharing used to work in virtualbox 3.2. but I also saw that they do not work on 4.0. I also know that the virtualbox guest additions are generally in a very bad shape. There are at least a few more bugs and features missing but nobody had time yet to debug that and fix those problems. I spend some time to integrate the additions better into the system (rc scripts, autostart ...) during the 4.0 development phase but I guess we need a few weeks of manpower to get the additions fully tested first, identify the problems and implement the missing features. We actually already started with the testing and identifying: http://wiki.freebsd.org/VirtualBox/ToDo If someone wants to contribute I think that is a very nice project. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Tue, 26 Apr 2011 15:42:29 -0400, Ryan Stone wrote:
> On Sun, Apr 24, 2011 at 8:02 AM, Bernhard Froehlich
> wrote:
>> On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote:
>>> PBIs for PC-BSD are currently worked on and will hopefully be available
>>> in a few days.
>>
>> Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts
>> to provide the PBIs!
>>
>> PC-BSD 8.x 32bit:
>> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi
>> ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi
>>
>> PC-BSD 8.x 64bit:
>> http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi
>> ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi
>>
>>
>> Feedback (positive and negative) from PC-BSD users is very welcome!
>>
>
> I installed the 64-bit PBI on my PC-BSD 8.2 machine, but I am unable
> to start any virtual machines(both pre-existing VMs or a new VM that I
> tried to create). I get the following error dialog:
>
> Failed to open a session for the virtual machine RELENG_8_amd64.
>
> Failed to load VMMR0.r0
> (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
>
> Unknown error creating VM
> (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).
>
> Details:
>
> Result Code:
> NS_ERROR_FAILURE (0x80004005)
> Component:
> Console
> Interface:
> IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
Yeah, thanks we already know. They added some strict hardening checks
in virtualbox 4.0 that fail on PC-BSD. Kris Moore is currently
rebuilding the PBIs with some modifications.
That's exactly why we have call for testers so find such weird problems
that nobody could think of.
--
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: reproducible vbox crash
On Tue, 26 Apr 2011 11:14:12 +0200, Oliver Pinter wrote: > Only the VM terminates it - the system not paniced - , but no core > files, and no DDB in kernel. You need to have the DEBUG option enabled in the ports or use the binary packages and set sysctl kern.sugid_coredump=1 first to also get coredumps for suid binaries like VirtualBox is. Once you have a core file please run "gdb /usr/local/lib/virtualbox/VirtualBox your_corefile.core" and send me the output of "bt full". -- Bernhard Fröhlich http://www.bluelife.at/ > On 4/26/11, Bernhard Froehlich wrote: >> On Mon, 25 Apr 2011 20:00:54 +0200, Oliver Pinter wrote: >>> Hi all! >>> >>> I run in to reproducible vbox crash. I think it is releated to AIO >>> subsystem. The sceanrio how to reproduce: >>> >>> create vm: >>> --- >>> type: ubuntu 32bit >>> hdd: dynamic 20GB >>> ram: 1GB >>> os: ubuntu server 8.04.4 >>> >>> how to reproduce: >>> start vm >>> install ubuntu with default setting >>> wait... >>> on heavy disc load become a SIGSEGV >>> >>> --- >>> not depend to hw virt >>> >>> >>> >>> @pandora-dev ~> VBoxManage --version >>> 4.0.6_OSEr71344 >>> >>> >>> ktrace, kdump and some needed info: >>> http://oliverp.teteny.bme.hu/freebsd/vbox/vbox-scenario.tar.xz >>> >> >> Does the VM terminate or does it result in a kernel panic? Could you >> please provide a stacktrace? >> >> -- >> Bernhard Fröhlich >> http://www.bluelife.at/ >> > ___ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org" ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Sun, 24 Apr 2011 12:29:43 -0300, Sergio de Almeida Lenzi wrote: > For me it is working... > running windows XP dnd linux over an old(4.0.2) image it is ok... > very stable... > > Only a problem remains (that is not still fixed): > it is the problem with the vnc in VBoxHeadless > the cursor is not in sync (the vnc cursor) is not > in sync with the XP cursor.. although the sync > is better (compared with 4.0.2 but is still out of sync)... > How to reproduce: > VBoxHeadless --vnc --vncport 5901 --startvm XPimg > then goto another machine and execute: > vncviewer x.x.x.x:5901, the system opens works but the > mouse cursor is not in sync... > > Question: Will there be a fix??? Don't know if that is a bug or a problem of the implementation. I would recommend waiting for the VNC extpack. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: reproducible vbox crash
On Mon, 25 Apr 2011 20:00:54 +0200, Oliver Pinter wrote: > Hi all! > > I run in to reproducible vbox crash. I think it is releated to AIO > subsystem. The sceanrio how to reproduce: > > create vm: > --- > type: ubuntu 32bit > hdd: dynamic 20GB > ram: 1GB > os: ubuntu server 8.04.4 > > how to reproduce: > start vm > install ubuntu with default setting > wait... > on heavy disc load become a SIGSEGV > > --- > not depend to hw virt > > > > @pandora-dev ~> VBoxManage --version > 4.0.6_OSEr71344 > > > ktrace, kdump and some needed info: > http://oliverp.teteny.bme.hu/freebsd/vbox/vbox-scenario.tar.xz > Does the VM terminate or does it result in a kernel panic? Could you please provide a stacktrace? -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
On Sun, 24 Apr 2011 16:37:15 -0400, Jason Andresen wrote: > On Fri, 22 Apr 2011 13:01:40 +0200 > Bernhard Froehlich wrote: > >> It's about two months since the last call for testers and a lot of >> bugfixing has happened since then. Not all of the reported problems were >> FreeBSD related which is a good indication that we're not too far behind >> the stability of the other hosts. So let's get it one once again. >> >> Last time I asked for some help and Baptiste Daroussin (bapt@) made the >> classic mistake to respond. So all please welcome bapt to the FreeBSD >> Vbox Team! > > Good news and bad news. The good news is that it appears to be > stable with my WinXP Pro VM. Bad news is that enabling 3D > acceleration still causes the VM to immediately crash when I try to > start it. Please try to get a coredump and stacktrace. You need to have the DEBUG option enabled or use the binary packages and set sysctl kern.sugid_coredump=1 first to also get coredumps for suid binaries like VirtualBox is. Once you have a core file please run "gdb /usr/local/lib/virtualbox/VirtualBox your_corefile.core" and send me the output of "bt full". -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available)
On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote: > PBIs for PC-BSD are currently worked on and will hopefully be available > in a few days. Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts to provide the PBIs! PC-BSD 8.x 32bit: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-i386.pbi ftp://ftp.pcbsd.org/pub/pbioutgoing/i386/8/emulators/virtualbox-ose/virtualbox-4.0.6-i386.pbi PC-BSD 8.x 64bit: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/virtualbox-4.0.6-amd64.pbi ftp://ftp.pcbsd.org/pub/pbioutgoing/x64/8/emulators/virtualbox-ose/virtualbox-4.0.6-amd64.pbi Feedback (positive and negative) from PC-BSD users is very welcome! -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Call for Testers: VirtualBox 4.0.6
It's about two months since the last call for testers and a lot of bugfixing has happened since then. Not all of the reported problems were FreeBSD related which is a good indication that we're not too far behind the stability of the other hosts. So let's get it one once again. Last time I asked for some help and Baptiste Daroussin (bapt@) made the classic mistake to respond. So all please welcome bapt to the FreeBSD Vbox Team! This is also the first time that we provide FreeBSD binary packages. They are build for FreeBSD 7.4 and 8.2 on i386 and amd64 platform and have the DEBUG option enabled. If you use a STABLE kernel you can use the virtualbox-ose-4.0.6-*-RELEASE-*.tbz binary package but have to compile the kernel module port for your kernel yourself. (emulators/virtualbox-ose-kmod) PBIs for PC-BSD are currently worked on and will hopefully be available in a few days. What has happened since the last cft: - VirtualBox update to 4.0.6 - phpvirtualbox updated to 4.0-5 - VIMAGE support added - vboxheadless startscript added - vboxwebsrv rc startscript fixes - Build fixed with LOCALBASE != PREFIX - Documentation of USB configuration (see pkg-message or Wiki) Thanks to all people that have contributed to that release and also reported problems for the last cft. We really appreciate that! Changes in the port: http://svn.bluelife.at/index.cgi/blueports/log/emulators Changelog for 4.0.6: http://www.virtualbox.org/wiki/Changelog FreeBSD specific configuration: http://wiki.freebsd.org/VirtualBox Todo List: http://wiki.freebsd.org/VirtualBox/ToDo Ports: http://home.bluelife.at/ports/virtualbox-cft-20110421.tar.gz FreeBSD 8.2/amd64 packages: virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz FreeBSD 8.2/i386 packages: virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz FreeBSD 7.4/amd64 packages: virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz FreeBSD 7.4/i386 packages: virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz Checksums: SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-amd64.tbz) = d7bdad02d2a04dd9dc3f12cc3ee002ce3bfc196b SHA1 (phpvirtualbox-4.0.5-7.4-RELEASE-i386.tbz) = e3023f5117fd15e918cba749d1ace2b7366bdc88 SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-amd64.tbz) = bd2785ac54e8363d217e35433d942ccae8bb7ffd SHA1 (phpvirtualbox-4.0.5-8.2-RELEASE-i386.tbz) = f6c437febf60828218cb42d7bfab8b536ecb7301 SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-amd64.tbz) = 31bbe5ff1e8d9b14dbd64c5d1f964fb702efda9e SHA1 (virtualbox-ose-4.0.6-7.4-RELEASE-i386.tbz) = 019955d07293f25421a0ca49d67975c165ee3e85 SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-amd64.tbz) = e56736714e01dbe693515ed89e239337c7df77d3 SHA1 (virtualbox-ose-4.0.6-8.2-RELEASE-i386.tbz) = 8f59294036b2f1ef407849f874139a80b6aabbcb SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-amd64.tbz) = cc7e72fdcf0e2cd0bcd21bb152ffa8b1b1adcaae SHA1 (virtualbox-ose-additions-4.0.6-7.4-RELEASE-i386.tbz) = be14e942cd2b426007b2d9a395cc65843340970d SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-amd64.tbz) = d5be908e99f9dfc4f7a1efe1570b67ad2d6b8d27 SHA1 (virtualbox-ose-additions-4.0.6-8.2-RELEASE-i386.tbz) = 2627acdb5ea9008bfa6ac6c2f452d6b883cfa40e SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-amd64.tbz) = e846f4a94bf14d0a50d3deab0ae325da25e79448 SHA1 (virtualbox-ose-kmod-4.0.6-7.4-RELEASE-i386.tbz) = 68144054e11bebe21fcb2b19e99cb33cead6f25b SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-amd64.tbz) = 7f08351028f18a3d76ed8c57aba525b11b47ee9a SHA1 (virtualbox-ose-kmod-4.0.6-8.2-RELEASE-i386.tbz) = 6e9bbfe0a2b19985b556e739f02f02a86ef873dd Mirrors: http://disasterarea.chruetertee.ch/virtualbox/4.0.6/ (master) http://files.etoilebsd.net/vbox/4.0.6/ Thanks and good luck, Bernhard, on behalf of the FreeBSD Vbox Team -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: AW: rc.d script for running multiple VirtualBox VMs from /etc/rc.conf
On Mon, 18 Apr 2011 16:29:33 +0200, Bernhard Froehlich wrote: > On Wed, 13 Apr 2011 05:28:44 -0700, Tobias Oberstein wrote: >> Hi Bernhard, >> >>> > I wanted to configure multiple VirtualBox VMs to startup automatically >>> > at boot time and generally be a nice citizen to the FreeBSD way of >>> > starting up stuff. >>> > >>> > Using that rc.d script (see attached) you can configure starting up >>> > multiple VirtualBox VMs from /etc/rc.conf: >>> >>> Sorry it's probably my fault because you're the 3rd one who has written such >>> a script but we already have one for 4.0. >> >> Ah, ok;) >> >>> >>> http://svn.bluelife.at/index.cgi/blueports/view/emulators/virtualbox-ose- >>> devel/files/vboxheadless.in >>> >>> It is a bit less complicated and can also manage multiple VMs but it does >>> not >>> have separated flags per VM. >> >> Mine is more complicated, yes .. but it's more or less a direct >> adaption of the script for apache22. >> >> Also, I definitely need flags per VM, since we run each VM >> >> i) under a dedicated user >> ii) on a separate ZFS filesystem >> iii) with specific VNC port/password >> >> i+iii requires flags per VM. >> >> iii) is for obvious reasons .. need to connect to each VM on a distinct port. >> >> i) is for a) security and b) management of VMs by different "VM >> admins" which don't have to be root or have a user which would manage >> all VMs. >> >> == >> >> I there interest to consolidate our scripts? > > I've merged the features together and got the following: > > # vboxheadless_enable (bool): Set to "NO" by default. > # Set it to "YES" to enable > vboxheadless. > # vboxheadless_machines (str):Space separated list of machines > # vboxheadless_user (str):Default user account to run with > # vboxheadless__name (str): VBox machine name or UUID > # vboxheadless__user (str): User account to run with > # vboxheadless__flags (str): Custom flags for VBoxHeadless > > simple example: > > vboxheadless_enable="YES" > vboxheadless_machines="FreeBSD Ubuntu1 Machine3" > > > complex example: > vboxheadless_enable="YES" > vboxheadless_machines="vm1 vm2 Machine3" > vboxheadless_user="vboxuser" > > vboxheadless_vm1_name="FreeBSD" > vboxheadless_vm1_user="user1" > > vboxheadless_vm2_name="Ubuntu1" > vboxheadless_vm2_user="user2" > vboxheadless_vm2_flags="--vnc --vncport 4711 --vncpass " > > > I could not test it yet but will do that in the evening and commit the > new script to blueports. Done. http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1287 -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: AW: rc.d script for running multiple VirtualBox VMs from /etc/rc.conf
On Wed, 13 Apr 2011 05:28:44 -0700, Tobias Oberstein wrote: > Hi Bernhard, > >> > I wanted to configure multiple VirtualBox VMs to startup automatically >> > at boot time and generally be a nice citizen to the FreeBSD way of >> > starting up stuff. >> > >> > Using that rc.d script (see attached) you can configure starting up >> > multiple VirtualBox VMs from /etc/rc.conf: >> >> Sorry it's probably my fault because you're the 3rd one who has written such >> a script but we already have one for 4.0. > > Ah, ok;) > >> >> http://svn.bluelife.at/index.cgi/blueports/view/emulators/virtualbox-ose- >> devel/files/vboxheadless.in >> >> It is a bit less complicated and can also manage multiple VMs but it does not >> have separated flags per VM. > > Mine is more complicated, yes .. but it's more or less a direct > adaption of the script for apache22. > > Also, I definitely need flags per VM, since we run each VM > > i) under a dedicated user > ii) on a separate ZFS filesystem > iii) with specific VNC port/password > > i+iii requires flags per VM. > > iii) is for obvious reasons .. need to connect to each VM on a distinct port. > > i) is for a) security and b) management of VMs by different "VM > admins" which don't have to be root or have a user which would manage > all VMs. > > == > > I there interest to consolidate our scripts? I've merged the features together and got the following: # vboxheadless_enable (bool): Set to "NO" by default. # Set it to "YES" to enable vboxheadless. # vboxheadless_machines (str):Space separated list of machines # vboxheadless_user (str):Default user account to run with # vboxheadless__name (str): VBox machine name or UUID # vboxheadless__user (str): User account to run with # vboxheadless__flags (str): Custom flags for VBoxHeadless simple example: vboxheadless_enable="YES" vboxheadless_machines="FreeBSD Ubuntu1 Machine3" complex example: vboxheadless_enable="YES" vboxheadless_machines="vm1 vm2 Machine3" vboxheadless_user="vboxuser" vboxheadless_vm1_name="FreeBSD" vboxheadless_vm1_user="user1" vboxheadless_vm2_name="Ubuntu1" vboxheadless_vm2_user="user2" vboxheadless_vm2_flags="--vnc --vncport 4711 --vncpass " I could not test it yet but will do that in the evening and commit the new script to blueports. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: setting up a virtualbox 4.0.4 svn repository
On Wed, 13 Apr 2011 21:01:08 +, Michael D. Norwick wrote: > Good Day; > > I hope to test VirtualBox 4.0.4 on FreeBSD 8.2 amd64. I have > subversion 1.6 installed from ports. I have googled and scanned > svn.pdf but I require some help on importing virtualbox_4.0.4 source > or the virtualbox_4.0.4 port to my local repository. I appear to be > lacking the appropriate URL. Some basic steps on how to import this > source and the correct URL would be greatly appreciated. > > Also, I downloaded the source tar.gz from Oracle's web site and 'make > configure' halts because of the lack of the as86 assembler. I believe > it is required for i386 builds on linux but do not understand what > port or package provides this functionality on FreeBSD amd64. I > installed NASM from ports but that does not seem to be what the > VirtualBox configure script wants. Sorry, I don't understand what you want to do. Why don't you just take the 4.0.4 port? http://home.bluelife.at/ports/virtualbox-cft-20110218.tar.gz -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Future direction of virtualbox-ose port on FreeBSD
On Wed, 13 Apr 2011 13:24:09 +0100, Bob Bishop wrote: > Hi, > > On 13 Apr 2011, at 12:38, Bernhard Froehlich wrote: > >> Hi VirtualBox users. >> >> I'm sending this because there are a few problems in how we currently >> maintain the emulators/virtualbox-ose ports on FreeBSD. [etc] > > A question: woud there be any advantage in separating out the kernel > module from the rest of it? Just asking, because I have no idea about > the stability of the components and interfaces. You mean a separate port for the kernel module? Yes, emulators/virtualbox-ose-kmod is exactly that. Sorry if I was not clear enough but everyone will be able to use the binary packages but if he has a STABLE kernel he will have to compile the corresponding -kmod port nevertheless. Using old kernel modules with newer VirtualBox versions is not supported (especially not between major versions which we are talking about here). -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Future direction of virtualbox-ose port on FreeBSD
Hi VirtualBox users. I'm sending this because there are a few problems in how we currently maintain the emulators/virtualbox-ose ports on FreeBSD. I want to outline my main concerns and propose a better way to solve that. The VirtualBox port is already very critical for many users and very complex at the same time so it gets harder and harder to update the port to new major versions without getting too much negative feedback from users. In the past we did a call for testers when upstream released a new major version (3.1.0, 3.2.0, 4.0.0) and got the update in the tree after their first patch release (3.1.2, 3.2.2) but now for the 4.0 release cycle we need at least to wait for 4.0.6 to get a useable state. Because of this long delay more and more people are using the cft and our development ports. We do not want that average users use that ports just to get to a newer version because they contain additional risks and are usually unstable versions (no support, irregular updates, broken ...). But we also do not want to make it harder for our testers to provide feedback because your feedback is very valuable to us and we need each tester we have. So we currently have these problems: 1) we need a stable version around if you hit a problem at the new version 2) we need to get new major versions out earlier to testers 3) we need to attract more testers We could solve this problems with "unstable" ports and people can use them if they care about it but we don't have that infrastructure in FreeBSD yet. We could also create -devel ports but that only solves one part of the problem and generates an huge amount of work on our side. Our internal -devel ports are most of the time built with "trunk" code so more or less alpha quality code. So that's not going to fly either. Instead we came up with two improvements: 1) Before a major version hits the tree we do a repocopy with the current version. So in case you have a problem with the major version you can fallback to the old version. It will be marked DEPRECATED with the next major update and removed 2 months after that. Major updates for vbox are 3.1.x, 3.2.x, 4.0.x 2) We provide binary packages and PBIs for virtualbox when we do a Call for Testers and probably also on a regular basis to lower the burden to test it. That only works for FreeBSD releases because the kernel module needs to be build for a specific kernel. So if you use a STABLE kernel you won't benefit from that. That means for us that we can bring in a new major version a bit earlier than now but we will continue to do extensive testing first. So you will still not see a .0 release in the ports. What do you think about it? Any better ideas? Your VirtualBox on FreeBSD Team, decke@, bapt@, (i. a. beat@) -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: rc.d script for running multiple VirtualBox VMs from /etc/rc.conf
On Tue, 12 Apr 2011 12:15:37 -0700, Tobias Oberstein wrote: > I wanted to configure multiple VirtualBox VMs to startup > automatically at boot time and generally be a nice citizen to the > FreeBSD way of starting up stuff. > > Using that rc.d script (see attached) you can configure starting up > multiple VirtualBox VMs from /etc/rc.conf: Sorry it's probably my fault because you're the 3rd one who has written such a script but we already have one for 4.0. http://svn.bluelife.at/index.cgi/blueports/view/emulators/virtualbox-ose-devel/files/vboxheadless.in It is a bit less complicated and can also manage multiple VMs but it does not have separated flags per VM. # vboxheadless_enable (bool): Set to "NO" by default. # Set it to "YES" to enable vboxheadless. # vboxheadless_user (str): User account to run with # vboxheadless_list (str): Space Separated VBox Hostnames # vboxheadless_flags (str): Custom flags for VBoxHeadless -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: AW: VBox 4.0.4 testing : keyboard layout issue
On Sat, 9 Apr 2011 13:34:43 -0300, Mario Lobo wrote: > On Saturday 09 April 2011 12:56:40 Kevin Oberman wrote: >> > From: Tobias Oberstein >> > Date: Sat, 9 Apr 2011 06:10:46 -0700 >> > Sender: owner-freebsd-emulat...@freebsd.org >> > >> > Hello Bernhard, >> > >> > > No it should just work but I admit that i haven't tested it for quite a >> > > few months. Does it work fine in virtualbox 3.2.x ? Probably it's some >> > > upstream >> > >> > I did not test it with 3.x, because we need 4.x .. >> > >> > > bug because they changed quite a lot in that area and it's contributed >> > > code. >> > >> > ok. I see. >> > >> > Would you have time / be willing to accept a small sponsorship to fix >> > the issue - regardless if it's upstream or a port issue? If so, send >> > me a private mail .. would be cool;) >> >> I am not at all comfortable with 4.0.4 on the up-stream side. I have it >> installed on my personal Windows7 system (previously running 3.2.12 with >> an Ubuntu client and I a seeing the keyboard lock-ups there. >> >> I ma also having LOT of crashes of the VM. I just get a Win7 popup >> telling my that the VM has unexpectedly exited and do I want to report >> it to Microsoft. After the stability of the v3 B, this is very >> disappointing. >> >> I'll admit to being very nervous about 4.0.4. > > Man, besides a few resolved problems with previous nvidia drivers and vbox > 3.x, I am yet to see issues on VBox and FBSD amd64 host! It's great if it works for you but fact is that 4.0.4 has some regressions that make it unstable for a lot of users. Some of the problems seem to be FreeBSD specific but it does also not look great on other platforms. From what i've seen they are currently fixing lots of bugs upstream so I expect that the situation improves a lot with 4.0.6. See the Buglist on the bottom: http://wiki.freebsd.org/VirtualBox/ToDo -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: AW: VBox 4.0.4 testing : keyboard layout issue
On Sat, 9 Apr 2011 06:10:46 -0700, Tobias Oberstein wrote: > Hello Bernhard, > >> No it should just work but I admit that i haven't tested it for quite a few >> months. Does it work fine in virtualbox 3.2.x ? Probably it's some upstream > > I did not test it with 3.x, because we need 4.x .. > >> bug because they changed quite a lot in that area and it's contributed code. >> > > ok. I see. > > Would you have time / be willing to accept a small sponsorship to fix > the issue - regardless if it's upstream or a port issue? If so, send > me a private mail .. would be cool;) Sorry that won't help here at the moment. It would be better to find out if it is a client issue or a client configuration issue. If you are sure that you can reproduce the problem with different clients we can go on checking if it is a 4.0 regression or FreeBSD specific. It is a bit complicated to create a bugreport without that information and if it is FreeBSD specific we cannot create a bugreport at all so we need to find out first. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VBox 4.0.4 testing : keyboard layout issue
On Mon, 28 Mar 2011 16:46:23 -0700, Tobias Oberstein wrote:
> I am testing
>
> https://svn.bluelife.at/nightlies/virtualbox-port-r1273.tar.gz
>
> on FreeBSD 8.2 amd64.
>
> So far, both a Windows XP SP2 (vdi imported from other machine) and a
> Ubuntu 10.10 (fresh install) guest seems to work great. Both with VT
> etc enabled (the host is a Core7 Intel).
>
> I've built only headless (only VNC and VDE support in the ports
> config) and start stuff
>
> VBoxHeadless -n -s buildslave_winxp_vc2010
>
> and access from Windows with TightVNC or VNC Viewer (Real VNC).
>
> Problem is with keyboard map: it is weird .. I am using a german
> keyboard, y and z are swapped, but the real annoyance are "funny"
> chars like {/$- etc etc. (it's not like the "usual" mixup when running
> german kbd with US map .. )
Sounds a bit weird. We had some similar reports where VNC seems to
filter a few of the keys but nothing yet about mixing them up.
> I tried to config the port with NLS .. but it says that required Qt
> which I don't have/want on that machine.
I guess that won't help because NLS is for translations of the Qt GUI
only.
> Am I expected to do s.th. different or is there anything I can do/try?
No it should just work but I admit that i haven't tested it for quite a
few months. Does it work fine in virtualbox 3.2.x ? Probably it's some
upstream bug because they changed quite a lot in that area and it's
contributed code.
> Anyway .. really nice to have that port,
> Tobias
>
>
> libvncserver-0.9.7_2 Provide an easy API to write one's own vnc server
>
> vde2-2.3.1 User-mode virtual ethernet infrastructure
> virtualbox-ose-4.0.4 A general-purpose full virtualizer for x86 hardware
> virtualbox-ose-kmod-4.0.4 VirtualBox kernel module for FreeBSD
>
> sf0# uname -v
> FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011
> r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
--
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox 4.x
On Tue, 22 Mar 2011 15:30:02 -0500, Rusty Nejdl wrote: > Can I ask what we are waiting for to commit this to the ports > tree? This new version is a HUGE improvement, at least as I have seen. Because it's not stable enough yet. There have been some serious bugreports from the CFT and i've collected them on the wiki page: http://wiki.freebsd.org/VirtualBox/ToDo Once the major of them are fixed and 4.0.6 is released I will prepare another CFT to see if we can risk the update. -- Bernhard Froehlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox + VIMAGE
On Wed, 2 Mar 2011 15:09:21 -0600, Brandon Gooch wrote: > On Wed, Mar 2, 2011 at 2:52 PM, Bernhard Froehlich wrote: >> On Wed, 02 Mar 2011 21:31:45 +0100, Bernhard Froehlich wrote: >>> On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote: >>>> On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich >>>> wrote: >>>>> On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote: >>>>>> On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote: >>>>>> >>>>>> BF> Sounds like it's my turn now. Which FreeBSD version is required to >>>>>> be >>>>>> BF> able to use it? >>>>>> >>>>>> As Bjoern noted it is for __FreeBSD_version >= 800500. >>>>>> >>>>>> BF> Is VIMAGE enabled per default and what happens if VIMAGE is >>>>>> disabled - >>>>>> BF> does it at least build fine with that patch? >>>>>> >>>>>> We have VIMAGE disabled by default. >>>>>> >>>>>> I have added to src/VBox/HostDrivers/VBoxNetFlt/freebsd/Makefile: >>>>>> >>>>>> .if defined(VIMAGE) >>>>>> CFLAGS += -DVIMAGE >>>>>> .endif >>>>>> >>>>>> So to build the driver for VIMAGE enabled kernel one should run >>>>>> >>>>>> VIMAGE=1 make >>>>>> >>>>>> If VIMAGE variable is not defined the module for VIMAGE disabled kernel >>>>>> will >>>>>> be built. >>>>> >>>>> http://home.bluelife.at/patches/virtualbox-ose-kmod-devel-VIMAGE.diff >>>>> >>>>> I've integrated it a bit better into the VirtualBox build system, added >>>>> the ports stuff and updated the patch for VirtualBox 4.0.2. >>>>> >>>>> It is currently unclear to me why you add VIMAGE to CFLAGS but nowhere >>>>> check for VIMAGE in VBoxNetFlt-freebsd.c. Shouldn't we add a check for >>>>> VIMAGE in the #if defined line or is this already done somewhere deep in >>>>> the included headers? >>>>> >>>>> -- >>>>> Bernhard Froehlich >>>>> http://www.bluelife.at/ >>>> >>>> I managed to completely miss your patch posted this thread, so I just >>>> gave it a try on bluelife's virtualbox-ose-kmod svn r1239; it's >>>> working well. I've started each of my guests with bridged networking >>>> to be sure, and I see no panic (or any other anomaly) during boot or >>>> normal operation. >>>> >>>> Do you have plans on merging the patch soon? >>> >>> It's not committed because it doesn't work. What i have tested so far >>> is with stock 8.2-REL so without VIMAGE. >>> >>> enabled VIMAGE option on stock 8.2-REL: bridging works fine >>> disabled VIMAGE option on stock 8.2-REL: crashes vm with an assert >>> >>> Expression: !pPatchToGuestRec >>> Location : >>> /usr/home/decke/blueports/emulators/virtualbox-ose/work/VirtualBox-4.0.4_OSE/src/VBox/VMM/VMMR3/PATM.cpp(116 >>> 6) void patmr3AddP2GLookupRecord(VM*, _PATCHINFO*, uint8_t*, RTRCPTR, >>> PATM_LOOKUP_TYPE, bool) >> >> It looks like that assert is not related to the VIMAGE patch. Works >> fine now since half an hour. >> >>> Could someone with an VIMAGE kernel please test the patch? Just >>> configure a VM with bridging and let it transfer a few bytes. Once with >>> the option enabled and once disabled. > > I've had a machine running a linux guest for almost a day, bridging > with a VIMAGE kernel, while capturing traffic on the virtual interface > (and performing a few other tasks) -- so far, so good. No panics, and > no anomalies. > > I surely don't know what the above mentioned assert is about; I > haven't seen such a panic myself. Thanks to everyone involved! I have committed it now to our blueports repository and the patch will come together with the next major VirtualBox update to 4.0.x. http://svn.bluelife.at/index.cgi/blueports/revision/?rev=1264 It got also reviewed from upstream and it looks fine so far. Will hopefully be committed soon. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox + VIMAGE
On Wed, 02 Mar 2011 21:31:45 +0100, Bernhard Froehlich wrote: > On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote: >> On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich >> wrote: >>> On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote: >>>> On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote: >>>> >>>> BF> Sounds like it's my turn now. Which FreeBSD version is required to be >>>> BF> able to use it? >>>> >>>> As Bjoern noted it is for __FreeBSD_version >= 800500. >>>> >>>> BF> Is VIMAGE enabled per default and what happens if VIMAGE is disabled - >>>> BF> does it at least build fine with that patch? >>>> >>>> We have VIMAGE disabled by default. >>>> >>>> I have added to src/VBox/HostDrivers/VBoxNetFlt/freebsd/Makefile: >>>> >>>> .if defined(VIMAGE) >>>> CFLAGS += -DVIMAGE >>>> .endif >>>> >>>> So to build the driver for VIMAGE enabled kernel one should run >>>> >>>> VIMAGE=1 make >>>> >>>> If VIMAGE variable is not defined the module for VIMAGE disabled kernel >>>> will >>>> be built. >>> >>> http://home.bluelife.at/patches/virtualbox-ose-kmod-devel-VIMAGE.diff >>> >>> I've integrated it a bit better into the VirtualBox build system, added >>> the ports stuff and updated the patch for VirtualBox 4.0.2. >>> >>> It is currently unclear to me why you add VIMAGE to CFLAGS but nowhere >>> check for VIMAGE in VBoxNetFlt-freebsd.c. Shouldn't we add a check for >>> VIMAGE in the #if defined line or is this already done somewhere deep in >>> the included headers? >>> >>> -- >>> Bernhard Froehlich >>> http://www.bluelife.at/ >> >> I managed to completely miss your patch posted this thread, so I just >> gave it a try on bluelife's virtualbox-ose-kmod svn r1239; it's >> working well. I've started each of my guests with bridged networking >> to be sure, and I see no panic (or any other anomaly) during boot or >> normal operation. >> >> Do you have plans on merging the patch soon? > > It's not committed because it doesn't work. What i have tested so far > is with stock 8.2-REL so without VIMAGE. > > enabled VIMAGE option on stock 8.2-REL: bridging works fine > disabled VIMAGE option on stock 8.2-REL: crashes vm with an assert > > Expression: !pPatchToGuestRec > Location : > /usr/home/decke/blueports/emulators/virtualbox-ose/work/VirtualBox-4.0.4_OSE/src/VBox/VMM/VMMR3/PATM.cpp(116 > 6) void patmr3AddP2GLookupRecord(VM*, _PATCHINFO*, uint8_t*, RTRCPTR, > PATM_LOOKUP_TYPE, bool) It looks like that assert is not related to the VIMAGE patch. Works fine now since half an hour. > Could someone with an VIMAGE kernel please test the patch? Just > configure a VM with bridging and let it transfer a few bytes. Once with > the option enabled and once disabled. -- Bernhard Fröhlich http://www.bluelife.at/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
