[opensuse-factory] Milestone 1 in Virtualbox
Hello, is 11.2 Milestone 1 supposed to work in Virtualbox? When rebooting the installed system, I get a Kernel panic. (I do not know how to copy the error messages from the Virtualbox screen, so before trying, I would first like to know whether it is not a known bug.) Regards, Marc -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 25 April 2009 08:30:46 am Marc Ensenbach wrote:
Hello,
is 11.2 Milestone 1 supposed to work in Virtualbox?
When rebooting the installed system, I get a Kernel panic. (I do not know how to copy the error messages from the Virtualbox screen, so before trying, I would first like to know whether it is not a known bug.)
Hi Marc, Thank you for the time to test openSUSE 11.2. The VirtualBox screen is just another window and I use PrtScr in KDE to call KSnapshot. After that I can limit area to one window and take new snapshot with more details, save it and upload to some of places that let us temporary store images, like http://picpaste.com . If the bug is well known, it should be listed on: http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.2_dev This is place where either: - Novell/SUSE developers, - BugBusters, or ( http://en.opensuse.org/BugBusters ) - Testing Team ( http://en.opensuse.org/Testing_Team ) should list them. The Testing Team and BugBusters are currently work in a first phase of planning and discussions, but few workarounds already exist. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schrieb:
The VirtualBox screen is just another window and I use PrtScr in KDE to call KSnapshot.
Thanks for this hint. Since I did not find any reports related to this issue, I created https://bugzilla.novell.com/show_bug.cgi?id=498301 including the screenshot. Regards, Marc -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le April 25, 2009 11:04:23 am Marc Ensenbach, vous avez écrit :
Rajko M. schrieb:
The VirtualBox screen is just another window and I use PrtScr in KDE to call KSnapshot.
Thanks for this hint. Since I did not find any reports related to this issue, I created https://bugzilla.novell.com/show_bug.cgi?id=498301 including the screenshot.
Regards,
Marc
I have it working well under VirtualBox. Installed the internet version. Andre. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 25 April 2009 10:04:23 am Marc Ensenbach wrote:
Rajko M. schrieb:
The VirtualBox screen is just another window and I use PrtScr in KDE to call KSnapshot.
Thanks for this hint. Since I did not find any reports related to this issue, I created https://bugzilla.novell.com/show_bug.cgi?id=498301 including the screenshot.
Marc, did you try to let computer go past this error. I had something like that, but computer (VirtualBox) boots anyway. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. schrieb:
did you try to let computer go past this error. I had something like that, but computer (VirtualBox) boots anyway.
The boot process stopped directly after this message. Going past this error was not possible. Regards, Marc -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Marc Ensenbach wrote:
Hello,
is 11.2 Milestone 1 supposed to work in Virtualbox?
When rebooting the installed system, I get a Kernel panic. (I do not know how to copy the error messages from the Virtualbox screen, so before trying, I would first like to know whether it is not a known bug.)
Regards,
Marc
I get no kernel panic, but I got this message while starting it as user both locally and over ssh. As per my other posts, it works as root over ssh, but not locally.
VirtualBox /usr/bin/VirtualBox: line 72: /usr/lib/virtualbox/VirtualBox: Permission denied /usr/bin/VirtualBox: line 72: exec: /usr/lib/virtualbox/VirtualBox: cannot execute: Success
Doing "chmod a+rx /usr/lib/virtualbox/VirtualBox" it now works as user. Original permissions were rws-r-x---. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 25 April 2009 01:53:42 pm Sid Boyce wrote: ...
/usr/bin/VirtualBox: line 72: /usr/lib/virtualbox/VirtualBox: Permission denied /usr/bin/VirtualBox: line 72: exec: /usr/lib/virtualbox/VirtualBox: cannot execute: Success
Doing "chmod a+rx /usr/lib/virtualbox/VirtualBox" it now works as user. Original permissions were rws-r-x---.
Hi Sid, The VirtualBox can be started without change in permissions if you add user that will use it to vboxusers group and then log out and then log in, so the change is effective. -- Regards, Rajko http://news.opensuse.org/category/people-of-opensuse/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Rajko M. wrote:
On Saturday 25 April 2009 01:53:42 pm Sid Boyce wrote: ...
/usr/bin/VirtualBox: line 72: /usr/lib/virtualbox/VirtualBox: Permission denied /usr/bin/VirtualBox: line 72: exec: /usr/lib/virtualbox/VirtualBox: cannot execute: Success
Doing "chmod a+rx /usr/lib/virtualbox/VirtualBox" it now works as user. Original permissions were rws-r-x---.
Hi Sid,
The VirtualBox can be started without change in permissions if you add user that will use it to vboxusers group and then log out and then log in, so the change is effective.
Thanks, that's a change in behaviour, perhaps a tightening of security. I am sure permissions on the file were always the same as I checked when I encountered the FUTEX_WAIT_PRIVATE problems as root. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Andre Malin -
Marc Ensenbach -
Rajko M. -
Sid Boyce