End user forums for VirtualBox
https://forums.virtualbox.org/
I'm guessing that they either aren't done yet or they haven't finished uploading them to the server.sawka wrote:I see that new packages are available but i can't download .deb for wheezy. Server responses with: "Not Found. The requested object does not exist on this server.". Can u fix it?
Uhh, yes. It is possible. I see now that not only wheezy packages are unavailable. Previously i tried a few links and all of the are downloable so i wrote this post. So let's wait.I'm guessing that they either aren't done yet or they haven't finished uploading them to the server.
Is there any change in the source code to fix this problem? I see you have redone the binary release more than once but the source package stays the same. Unfortunately I have to compile from source because I need to apply a patch, otherwise VirtualBox does not work on my system.Frank Mehnert wrote:Actually we found the problem. Very nasty, will require to redo the 4.3.10 release :-/
But thank you for the report!
Got it, thanks.Frank Mehnert wrote:Actually we found the problem. Very nasty, will require to redo the 4.3.10 release :-/
But thank you for the report!
The initial release was "4.3.10 r92957", the new release is "4.3.10 r93012".poncho524 wrote:You shouldn't release a changed application under the same version number.
This is very confusing and problematic.
You should release the regression fix as 4.3.10.1 or something.
Please Please Please, dont release two different versions under the same name in the future.
Ok, So there was no application change... just packaging fix... got it.smithlar wrote:The initial release was "4.3.10 r92957", the new release is "4.3.10 r93012".
These complete Version ID's are displayed in the VMM GuI Help/About box,
and are part of the installer/rpm/deb file names.
When built from source the new release is still r92957. This is misleading.smithlar wrote:poncho524 wrote:...
The initial release was "4.3.10 r92957", the new release is "4.3.10 r93012".
These complete Version ID's are displayed in the VMM GuI Help/About box,
...
This is still broken. Running Ubuntu 12.04 LTS host. Installed "virtualbox-4.3_4.3.10-93012~Ubuntu~precise_amd64.deb" via apt, then upgraded guest additions on 2 guests (also 12.04) using "./VBoxLinuxAdditions.run --nox11". Now neither guest can boot. Guest console hangs on "EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro".Frank Mehnert wrote:The upload of the fixed 4.3.10 packages is now complete. The old packages had the revision 92957 while the fixed packages have the revision 93012. I guess it will take some time until the deb/rpm repositories are refreshed on the download servers though.
Apologizes,
Frank
This is a different problem. Please open a new ticket in the bug tracker.thump wrote:This is still broken. Running Ubuntu 12.04 LTS host. Installed "virtualbox-4.3_4.3.10-93012~Ubuntu~precise_amd64.deb" via apt, then upgraded guest additions on 2 guests (also 12.04) using "./VBoxLinuxAdditions.run --nox11". Now neither guest can boot. Guest console hangs on "EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro".Frank Mehnert wrote:The upload of the fixed 4.3.10 packages is now complete. The old packages had the revision 92957 while the fixed packages have the revision 93012. I guess it will take some time until the deb/rpm repositories are refreshed on the download servers though.
Apologizes,
Frank
Guests are both Ubutnu 12.04 LTS x64 installs running on VDI disks with Bridged networking to separate physical nics. Guest root partitions are LVM2 with ext4. Both use shared folders (mounted via /etc/fstab on guests, not using host automount option).
VBoxSVC Log shows:
VirtualBox XPCOM Server 4.3.10 r93012 linux.amd64 (Mar 26 2014 20:12:06) release log
00:00:00.000525 main Log opened 2014-03-27T02:28:17.237682000Z
00:00:00.000528 main Build Type: release
00:00:00.000534 main OS Product: Linux
00:00:00.000536 main OS Release: 3.2.0-60-generic
00:00:00.000538 main OS Version: #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014
00:00:00.000572 main DMI Product Name: RS100-E5/PI2
00:00:00.000588 main DMI Product Version: 1.XX
00:00:00.000698 main Host RAM: 7986MB total, 6622MB available
00:00:00.000706 main Executable: /usr/lib/virtualbox/VBoxSVC
00:00:00.000707 main Process ID: 15344
00:00:00.000708 main Package type: LINUX_64BITS_UBUNTU_12_04
00:00:00.106859 nspr-2 Loading settings file "/home/vboxuser/.VirtualBox/VirtualBox.xml" with version "1.14-linux"
00:00:00.203942 nspr-2 Successfully initialised host USB using sysfs
00:00:00.211266 nspr-2 HostDnsMonitorProxy: Host's DNS information updated:
00:00:00.211284 nspr-2 DNS server 1: 127.0.0.1
00:00:00.211294 nspr-2 DNS domain: <redacted>
00:00:00.217485 nspr-2 NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link status for vboxnet0: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:00.218117 nspr-2 VDInit finished
00:00:00.229050 nspr-2 Loading settings file "/mnt/local/vboxes/<redacted>.vbox" with version "1.14-linux"
00:00:00.230466 nspr-2 Loading settings file "/mnt/local/vboxes/<redacted>.vbox" with version "1.14-linux"
00:04:51.120193 nspr-2 NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link status for vboxnet0: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:04:58.421052 nspr-4 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={c20238e4-3221-4d3f-8891-81ce92d9f913} aComponent={ProgressProxy} aText={Error info is not available, operation is still in progress}, preserve=false
**** UPDATE: Downgrade to 4.3.8 does not fix this issue. Install of 4.3.10-93012 Guest Additions seems to have borked both upgraded guests. Moving to backups. ****
**** UPDATE2: Downgrade to 4.3.8 plus restore of last night's guest VDI backups solved it for now. ****
Thanks but we didn't change anything in the Linux installer for many releases. So it must be either a problem with your setup or the problem exists in the installer for a long time ...robatino wrote:I can verify that after updating from 92957 to 93012, my VM now boots. However, immediately after update, "dkms status" on the host showed no modules, so I manually did "dkms install vboxhost/4.3.10 -k 3.13.6-200.fc20.x86_64" to create them, and installed the new Extension Pack, before attempting to run the VM.
My setup is pretty clean, so the latter is definitely possible.Frank Mehnert wrote:Thanks but we didn't change anything in the Linux installer for many releases. So it must be either a problem with your setup or the problem exists in the installer for a long time ...robatino wrote:I can verify that after updating from 92957 to 93012, my VM now boots. However, immediately after update, "dkms status" on the host showed no modules, so I manually did "dkms install vboxhost/4.3.10 -k 3.13.6-200.fc20.x86_64" to create them, and installed the new Extension Pack, before attempting to run the VM.