[Bug 260192] Re: Ubuntu 8.04.1 Sun VirtualBox Incompatibility
The closed source version of VirtualBox isn't supported by Ubuntu. ** Changed in: virtualbox-ose (Ubuntu) Status: New = Invalid -- Ubuntu 8.04.1 Sun VirtualBox Incompatibility https://bugs.launchpad.net/bugs/260192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 260192] Re: Ubuntu 8.04.1 Sun VirtualBox Incompatibility
I make no claim as to my qualifications, but I downloaded the 8.04.1 version of Ubuntu, then used a report elsewhere as to how to enable USB support in it by removing some comments in one of the script files. That enabled USB support, but with some noted issues. I didn't have to report it I guess, but it seemed appropriate in case others encountered the same problems of the supporters needed to know the effects involved. The thing abut 8,04,1 is that you may gain something, but it looks like you give up something as well. So I am sticking with 8.04 for the present. ---Original Message--- From: Xavier Poinsard Date: 12/17/2008 08:43:00 AM To: oldef...@cox.net Subject: [Bug 260192] Re: Ubuntu 8.04.1 Sun VirtualBox Incompatibility Since you mention USB, I assume you are using the closed source version of virtualbox, isnt'it ? If Yes, you bug is incorrectly filed against the ubuntu package (which is based on open source version and without USB support). -- Ubuntu 8.04.1 Sun VirtualBox Incompatibility https://bugs.launchpad.net/bugs/260192 You received this bug notification because you are a direct subscriber of the bug. No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.18/1851 - Release Date: 12/16/2008 8:53 AM ** Attachment added: unnamed http://launchpadlibrarian.net/20509327/unnamed ** Attachment added: unnamed http://launchpadlibrarian.net/20509328/unnamed ** Attachment added: unnamed http://launchpadlibrarian.net/20509329/unnamed -- Ubuntu 8.04.1 Sun VirtualBox Incompatibility https://bugs.launchpad.net/bugs/260192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 260192] Re: Ubuntu 8.04.1 Sun VirtualBox Incompatibility
Since you mention USB, I assume you are using the closed source version of virtualbox, isnt'it ? If Yes, you bug is incorrectly filed against the ubuntu package (which is based on open source version and without USB support). -- Ubuntu 8.04.1 Sun VirtualBox Incompatibility https://bugs.launchpad.net/bugs/260192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 260192] Re: Ubuntu 8.04.1 Sun VirtualBox Incompatibility
** Changed in: virtualbox-ose (Ubuntu) Sourcepackagename: None = virtualbox-ose -- Ubuntu 8.04.1 Sun VirtualBox Incompatibility https://bugs.launchpad.net/bugs/260192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 260192] Re: Ubuntu 8.04.1 Sun VirtualBox Incompatibility
I managed to resolve this problem. Doing online research, I first added the entry specified for OpenSuse not supporting USB that is mentioned in the VirtualBox FAQ. This entry goes in /etc/fstab, and is for device none usb. This caused my external usb hard drive to mount on startup automatically. I also added subfolders to /media for each drive that was not being mounted at startup. After I had reverting to the prefinal setup method, and did all updates, the ntfs partitions mounted on startup, but the ext3 partitions did not. I added entries to /etc/fstab for each unmounted drive, and changed the properties for the ext3 partitions from defaults to defaults,auto in the same table. That still did not mount them. So I edited /etc/init.d/mountall.sh and added ,ext3 to each of the two mount commands located there, and this finally worked after perfroming /etc/init.d/mountall.sh start (or following a reboot).. . I still had a problem with accessing the external usb hard drive in the guest OS, but finally realized that I had enabled support through /etc/fstab, but still had a USB filter in place for it in VirtualBox. So I removed the USB filter, and set the external drive up via shared folders. This worked. I had to change the properties on the none usb entry in /etc/fstab from =0664 to -0666 to enable write access to this drive. And that is it. It even works better than my original efforts, since if the external hard drive is added or removed at any time, I get no errors from either the host or guest OS. I also found that if I wanted, I could add the subfolders to /mnt instead of to /media, in which case you can still access the drives, but they will not automatically appear as icons on the desktop. You just have to show the designated mountpoint as the second field in each entry in /etc/fstab. I also noted that /etc/mtab shows the drives that will be normally mounted if these changes are not made, but that this table apparently cannot be directly edited, as the system will crash if you try. It apparently will only accept a reboot command if that happens. And you can use the blkid command to see all the known partitions on your system. However, this does not show the block size used, and this may be a required entry at some point, so you can use the dumpfs [driveid] command for that information, but redirect it () to a text file so that you can see the pertinent information near the top of the list, as it is a verbose report and you will see it scroll off the top of the screen if you use the dumpfs [driveid] command by itself. I hope that is enough information to help someone else overcome the same problems. -- Ubuntu 8.04.1 Sun VirtualBox Incompatibility https://bugs.launchpad.net/bugs/260192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 260192] Re: Ubuntu 8.04.1 Sun VirtualBox Incompatibility
** Description changed: Moving to fuse has caused severe compatibility problems with VirtualBox. Even going through and mounting all Windows drives beforehand, and trying to access them as shared folders in VirtualBox does not work. The drives appear to show up, but are void. Cannot access external USB drive via VirtualBox either, does not show up at all. Attempting to add drives to fstab manually as done in 8.04 appears to corrupt the mount process so that the drive cannot be mounted at all. Putting the fstab back as it was did not fix this problem - had to restore image from backup. Fuse mounts the drives with generic names if no label was assigned. Unable to change names through Properties. Was able to rename from terminal after installing ntfsprogs and using ntsflabel for ntfs volumes and e2label for ext3 volumes. No option to set name during install of Ubuntu. Instructions should indicate the use of double quotes around new name as means of setting case and adding special characters like (). Should be option to keep matters as they were under 8.04. The use of uuid in fstab is counter-productive. If you install a second or third instance of Linux, the drive's uuids will change, and grub will be unable to boot to all instances if the uuid does not match up with that found in the host boot process (/boot/grub/menu.lst). You should permit generic boot order using /dev entries.. + + UPDATE: Reinstalled Ubuntu 8.04 using prefinal image (before install + process finalized), which had drives on desktop (before fuse), Then I + used update process to bring that installl up to current levels. Sun + VirtualBox was able to set these up as shared folders for guest OS + Windows XP Pro, which could not access them previously as per above + report. However, something has changed because Windows 2000 Pro will + not install as a guest now, keeps recycling when trying to set up + Network.. And as reported above, even though USB Host Proxy has been + enabled, and users enabled in groups vboxusers and vboxdrv, unable to + access external hard drive although USB and USB 2.0 support enabled in + VirtualBox and a mass storage device, external hard drive, and USB + connected printer are passed through. Of these, only the printer can be + accessed within the guest OS. + + Before changes to version 8.04, culminating in 8.04.1, the combination + of Ubuntu and VirtualBox was almost flowless. Now something is + seriously broken, and I am just trying to hekp point out where the + change occurred. -- Ubuntu 8.04.1 Sun VirtualBox Incompatibility https://bugs.launchpad.net/bugs/260192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
