Page 2 of 2
Re: Discuss the 4.0.10 Release
Posted: 29. Jun 2011, 19:30
by Virtual_WA
Hello,
Or, more simply, that fix is not considered as much worthy/important/urgent as others, thus becoming part of the considerable array of tickets which remain "open" for a... very long time.
Could be - but the whole "AMD-350" platform is affected - Windows and Linux host. Nobody on this platform can run 64Bit guests. I'm not sure whether the developers are aware of this fact.
There's no right of "complaining" about the developers' decisions, especially if using this useful program free of charge.
I'm with You that the program is free of charge for private use. So no one has the "right to complain". Nevertheless I think it is ok to state that "I'm sad because this nasty bug was not fixed."
BR
Werner
Re: Discuss the 4.0.10 Release
Posted: 29. Jun 2011, 21:42
by mschwartz
See attached. The first part I highlighted seems a bogus error message.
The second part I highlighted is something I haven't seen before.
Re: Discuss the 4.0.10 Release
Posted: 29. Jun 2011, 23:06
by Perryg
@mschwartz,
The first error is in fact valid. VBox sees your current kernel and headers do not match. Check and make sure that the headers and kernel are the same.
Second message you highlighted has been around for a while, but I am not sure exactly when it started being logged.
Re: Discuss the 4.0.10 Release
Posted: 30. Jun 2011, 08:34
by marco
Virtual_WA wrote:...I think it is ok to state that "I'm sad because this nasty bug was not fixed."...
I also think it is OK.
Moreover, I think it is perfectly rightful and also useful.
Actually this is one way (maybe the main one) in which we, private users, are "paying" for the software: finding out and reporting bugs or possible enhancements.
Sadly, we also have no certainty at all about "if" or "when" our reports will be taken into account.
That's another way.
Re: Discuss the 4.0.10 Release
Posted: 30. Jun 2011, 18:51
by johnelee
Guess not very 4.0.10 specific, but I've noticed a lot of people re 4.0.10 are having trouble running snow leopard & other apple OSs on 4.0.10 as a VM on non Apple hardware - this appears to be prohibited by vbox because of Apple's licencing. This seems bizarre - I can't see why vbox gets involved - or to put it more crudely what the **** has it got to do with vbox? eg vbox doesn't, for example, stop people running unlicenced or hacked windows software as a VM...
No doubt the vbox supporters club will trot out the vbox line here & ban this email, as they seem to want to do aboiut the oter recent vbox criticisms on this forum... but why oh why is vbox being the nanny?
John
Re: Discuss the 4.0.10 Release
Posted: 30. Jun 2011, 19:59
by ingo2
I now did test 4.0.10 for 2 days and finally had to downgrade to 4.0.4 again
The problems with mouse hanging/unresponsive in the guest (OS/2 4.5), when host (Debian-Squeeze) is suspended and resumed while VM is up and running. See my post here:
http://forums.virtualbox.org/viewtopic. ... 53#p191853.
Interesting is that only mouse clicks are "swallowed" while the pointer movement still works. Can easily be observed i.e. in a card game which uses a lot of mouse clicks to play.
With 4.0.4 all is fine again, so there definitely must have been a major/basic change in VBox since 4.0.4.
With best regards,
Ingo
P.S.: Please update the "host operating system" drop down list where you edit your profile. You only have the choice Debian-Lenny and Debian-other, however Squeeze ist current stable.
Re: Discuss the 4.0.10 Release
Posted: 7. Jul 2011, 13:38
by peo61
Hi, I installed the 4.0.10 version today and now I can't get any guest to start because the network adapter is failing.
Before the upgrade it was working ok.
The error message is as follows:
Failed to open/create the internal network 'HostInterfaceNetWorking-Broadcom NetXtreme 57xx Gigabit Controller'
(VERR_SUPDRV_COMPONENT_NOT_FOUND)
Resultatkod:
E_FAIL (0x80004005)
Komponent:
Console
Gränssnitt:
IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
I suspect that the virtual network adapter was uninstalled when installing 4.0.10, and when I check the network adapters installed, the virtualbox network adapter is nonexistent.
Running on 32bit Windows 7.
Also I tried to uninstall the 4.0.10 version and reinstall the previously working 4.0.8 version but had no luck with reinstalling the network adapter.
Is there any way to get the virtual network adapter installed again?
Best Regards,
Peo
Re: Discuss the 4.0.10 Release
Posted: 7. Jul 2011, 14:52
by mediaf
Hi everybody,
I have a similar problem as "peo61" : since I upgraded to the last Vbox release, I can't start any guest ( I have a debian 5.08 and a Windows Seven )
I get an error message : Failed to open a session for the virtual machine
Nonexistent host networking interface
Unknown error creating VM
I have VBox Installed on a notebook with Windows XP Sp3.
I have an ethernet card ( Intel(R) 82577LC Gigabit Network Connection ) a wireless card (Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC ) and the virtual VirtualBox Host-Only Ethernet Adapter.
When using the host Windows XP, I don't have any problem with the two physical networks, but Vbox seems to not detect my ethernet card : in the dropdown menu used to choose the network card when configuring a guest, only my wireless card appears, so if the Wifi isn't activated the guests with bridged mode network refuse to start throwing "Nonexistent host networking interface"
Re: Discuss the 4.0.10 Release
Posted: 8. Jul 2011, 23:39
by Sasquatch
johnelee wrote:Guess not very 4.0.10 specific, but I've noticed a lot of people re 4.0.10 are having trouble running snow leopard & other apple OSs on 4.0.10 as a VM on non Apple hardware - this appears to be prohibited by vbox because of Apple's licencing. This seems bizarre - I can't see why vbox gets involved - or to put it more crudely what the **** has it got to do with vbox? eg vbox doesn't, for example, stop people running unlicenced or hacked windows software as a VM...
No doubt the vbox supporters club will trot out the vbox line here & ban this email, as they seem to want to do aboiut the oter recent vbox criticisms on this forum... but why oh why is vbox being the nanny?
John
Maybe because Windows is licensed by MS to run on just about any PC hardware, as opposed to Mac OSX. The latter is only available on Apple hardware and only licensed for that hardware. If people have difficulties running any version of OSX on non-Apple hardware, good for them. They shouldn't run it in the first place. If you want to run OSX, get a Mac or keep your mouth shut. Want to run Windows, visit your local computer shop and buy a copy. It's that simple. If you don't want to pay for a license for an OS that requires one, you have no right to use VB IMO. In fact, I don't even think you should use a computer at all. Would you drive a car like it's your own without paying the manufacturer? Would you get your groceries without paying for it?
Re: Discuss the 4.0.10 Release
Posted: 13. Jul 2011, 15:15
by mschwartz
I've been seeing "hardware" errors on /dev/sda1 in my Ubuntu guest (Windows 7 x64 host). They occur after the VM has been running for a long time, certainly > 24 hours. I have to hard reset the VM, because the guest won't shut down due to the errors.
Re: Discuss the 4.0.10 Release
Posted: 13. Jul 2011, 15:42
by mschwartz
Perryg wrote:@mschwartz,
The first error is in fact valid. VBox sees your current kernel and headers do not match. Check and make sure that the headers and kernel are the same.
Second message you highlighted has been around for a while, but I am not sure exactly when it started being logged.