• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "VirtualBox on Ubuntu"

Collapse

  • suityou01
    replied
    Originally posted by CalmEddie View Post
    Good job you found the fix. For future ref though, as a workaround it's much safer to crack the app and user folders wide open with chmod -R 777 than to run an app as root. Would achieve the same thing.
    Darmstadt

    Do not worship other idols

    Seriously though, well chuffed. Thanks for your help too CE.

    Leave a comment:


  • CalmEddie
    replied
    Originally posted by suityou01 View Post
    this is running as SUDO I may add root to that group to see if this fixes it.
    Good job you found the fix. For future ref though, as a workaround it's much safer to crack the app and user folders wide open with chmod -R 777 than to run an app as root. Would achieve the same thing.

    Leave a comment:


  • suityou01
    replied
    Originally posted by darmstadt View Post
    I had exactly the same problem with VB under Debian (upon which Ubuntu is based) and IIRC it had to do with something like not having created the vboxusers group and then adding my user to it. There might have been a permissions problem in there somewhere as well...
    Er, yep, that'll be it then.

    Darmstadt you are nothing but a god to me.

    Leave a comment:


  • suityou01
    replied
    Originally posted by darmstadt View Post
    I had exactly the same problem with VB under Debian (upon which Ubuntu is based) and IIRC it had to do with something like not having created the vboxusers group and then adding my user to it. There might have been a permissions problem in there somewhere as well...
    It created that group as part of the install. My user is a member, root is not. Seeing as this is running as SUDO I may add root to that group to see if this fixes it. Thanks for the feedback.

    Leave a comment:


  • darmstadt
    replied
    I had exactly the same problem with VB under Debian (upon which Ubuntu is based) and IIRC it had to do with something like not having created the vboxusers group and then adding my user to it. There might have been a permissions problem in there somewhere as well...

    Leave a comment:


  • suityou01
    replied
    Virtual Box running on Ubuntu machine is blocking the SIP port.
    Virtual Box running on Vista machine is NOT blocking the SIP port.

    The Ubuntu box is not running a software firewall. Both are on the same subnet.

    Wtf would it block the SIP port?

    Leave a comment:


  • suityou01
    replied
    Originally posted by CalmEddie View Post
    That's not how Ubuntu rolls. The latest LTS release is 8.04, which is the most stable version.

    I can confirm that VB runs perfectly fine on 8.04 64 bit, and VB3+ runs multiple cores (VMware doesn't unless you pay). I've since reinstalled using 9.10 and the same virtual machines work just fine. Seriously - Don't upgrade from 8 to 9. Re-install. Do it as a side-by-side dual boot if you want to be sure.

    Your softphone problems will very likely be to do with the bridge the virtual machine makes with the host.

    I prefer VB to VMware, it's a lot more stable. And you can convert VMware VMs to work with virtualbox.

    The errors you're getting, is this with a new VM, or an existing one?
    Both VB and VM Vms are new today.

    I have VB working now. Did nothing different. Installed as logged in user, but need to launch as sudo otherwise I get the stupid com error. Permissions wrong somewhere, but I'm fine running as sudo for now.

    Leave a comment:


  • CalmEddie
    replied
    Originally posted by Ardesco View Post
    Ubuntu is on 9.10 now, Ubuntu 8 is 2007?
    That's not how Ubuntu rolls. The latest LTS release is 8.04, which is the most stable version.

    I can confirm that VB runs perfectly fine on 8.04 64 bit, and VB3+ runs multiple cores (VMware doesn't unless you pay). I've since reinstalled using 9.10 and the same virtual machines work just fine. Seriously - Don't upgrade from 8 to 9. Re-install. Do it as a side-by-side dual boot if you want to be sure.

    Your softphone problems will very likely be to do with the bridge the virtual machine makes with the host.

    I prefer VB to VMware, it's a lot more stable. And you can convert VMware VMs to work with virtualbox.

    The errors you're getting, is this with a new VM, or an existing one?

    Leave a comment:


  • VectraMan
    replied
    Originally posted by MarillionFan View Post
    BTW. How does VB compare in performance to VMWare Workstation? I had some real performance issues with VB.
    There is, or was a real problem with the dual core support on VirtualBox, or rather the problem was with IO-APIC which the dual core support turned on. Made the guest OS run dog slow.

    I use it all the time, and it's okay. I think VMWare is generally better though, and the general configuration and management of VMs and snapshots is better in VMWare. However, VirtualBox is considerably cheaper.

    I had it running okay on Ubuntu 9.

    Leave a comment:


  • suityou01
    replied
    Cannot be arsed upgrading the whole of ubuntu. That will cause more problems than it fixes

    I have VMware installed and working on Ubunutu so I decided to use this.

    I have installed asterix, done my screen grabs all going well. Buuuuut.

    I cannot connect my softphone to the VMware PBX. Wireshark shows "destination port unreachable" for the SIP connection.

    Why? The host has no software firewall, so VMWare must be blocking the port. But I am using bridged networking? Anyone come across VMware doing this?

    Lot of unecessary ball ache going on here.

    Leave a comment:


  • Ardesco
    replied
    Ubuntu is on 9.10 now, Ubuntu 8 is 2007?

    Virtualbox in 2007 was not a good bit of software, are the repositories using a 2007 version of the package (something like 1.4 - 1.5).

    If so look for an updated version, virtualbox is on 3.1.x now. Of course there is always the possibility that a two year old version of ubuntu is missing some of the requirements for a working up to date virtualbox install. I would suggest updating Ubuntu as well.

    Leave a comment:


  • Cliphead
    replied
    I prefer Mint 8 which in my opinion is what Ubuntu should have been. No problems with VB on that.

    Leave a comment:


  • suityou01
    replied
    Originally posted by MarillionFan View Post
    Nope. I had enough problems trying to get it to share folders with using Windows!

    BTW. How does VB compare in performance to VMWare Workstation? I had some real performance issues with VB.
    Only had it running on my Vista laptop. It dragged the whole machine down quite a bit and made it run hot. Another reason for wanting it on my ubuntu host.

    Leave a comment:


  • MarillionFan
    replied
    Nope. I had enough problems trying to get it to share folders with using Windows!

    BTW. How does VB compare in performance to VMWare Workstation? I had some real performance issues with VB.

    Leave a comment:


  • suityou01
    started a topic VirtualBox on Ubuntu

    VirtualBox on Ubuntu

    In an effort to document the steps I took for the linux pbx I have been working on I decided to rebuild the pbx from scratch so I could take screen shots for the how to.

    I installed VirtualBox on my ubuntu machine. When I try and launch I get the following error

    Failed to create VirtualBox com object

    I've tried searching the interweb for a solution, everyone just says to reinstall and it will be fine. Not so.

    I am using Ubuntu 8 (Amd64) and the appropriate deb package from http://www.virtualbox.org/wiki/Linux_Downloads

    Anyone seen this before and can give a steer?

    Can't believe all the annoying hurdles that are getting in my way.

Working...
X