Discuss the 5.0.6 release

[johnlee]

Is there any planned release and timeline available for issuing bug fix?

No. Might be good to know why this problem is more important than all the rest.

Because it stops our programs with avx instructions in working on some platforms and seems like a rather significant restriction, so +1 to fix it asap. Is it difficult problem to fix? j

[loukingjr]

I believe michaln's question was rhetorical. Everyone's "problem" is important to fix and I assume they are done in the order of Oracle's paying customers needs.

[johnlee]

I believe michaln's question was rhetorical. Everyone's "problem" is important to fix and I assume they are done in the order of Oracle's paying customers needs.

Can't see anything suggesting it was rhetorical - he asked for info, and I supplied some and added a +1 to the original, so can't see why you are bothering to send this email, which doesn't really add much. j

[loukingjr]

He didn't ask why your problem was important. He asked why your problem was more important than any others. But no matter.

[Thomas Greif]

Hello,

i have Problems to get the Serial-Port working in Windows7

Guest: Windows7 x86

Host: Windows7 x64

VBoxManager 5.06


The SerialPort was working with Manager 5.04.
After upgrade to 5.06 the DeviceManager tells me: The Driver cannot be started

The Guest Additions from 5.06 were installed.

After this i reinstalled the Manager 5.04 and it works again (with the Guest Additions from 5.06)


Do you know about this Problem?

[mpack]

Do you know about this Problem?

Please search for previous answers before posting.

Problem with Serial Port on XP Guest on Win 7 Host.
Bug ticket: 14659.

[Thomas Greif]

Sorry for the Post. I searched the Forum but i didn't find anything about Com-Port.

It's good to know that the Problem is being fixed with the next Version.


Thanks

Thomas

[johnlee]

Re 5.0.7 103382, latest test build, can't see whether it has latest dnd changes 58212 included.

The help does not mention it but I'd assumed that 'latest test build' was exactly that ie had the latest changes in it.

john

[edstevens]

I just installed 5.0.6 on my Win7 Home Premium laptop, replacing several iterations of 4.x. I immediately noticed a difference in the ip address of the hostonly adapter installed on the host OS. All previous versions had used 192.168.56.1, but I now it is created at 169.254.225.182. Just seems like a rather odd change.



Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5450cdcb:e1b6%36
Autoconfiguration IPv4 Address. . : 169.254.225.182
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

[Legorol]

I just installed 5.0.6 on my Win7 Home Premium laptop, replacing several iterations of 4.x. I immediately noticed a difference in the ip address of the hostonly adapter installed on the host OS. All previous versions had used 192.168.56.1, but I now it is created at 169.254.225.182. Just seems like a rather odd change.

169.254.225.182 is an auto-configured link-local IP address (see https://en.wikipedia.org/wiki/IP_addres ... figuration), not assigned by VirtualBox. Having such an address means something has gone wrong with VirtualBox assigning an IP address to the host-only adapter. You may have to reinstall VirtualBox.

[edstevens]

169.254.225.182 is an auto-configured link-local IP address (see https://en.wikipedia.org/wiki/IP_addres ... figuration), not assigned by VirtualBox. Having such an address means something has gone wrong with VirtualBox assigning an IP address to the host-only adapter. You may have to reinstall VirtualBox.

Reinstalling AFTER rebooting (de-install, reboot, install) did the trick. This time it installed with 192.168.56.1. I guess I should have mentioned that I was able to reconfigure the first install to use the correct address (preferences .. network .. configure) but I was curious about a possible reason for the change.

Thanks for the lead.