Discuss the 5.2.0 release

This is for discussing general topics about how to use VirtualBox.

Re: VM settings is unresponsive

Postby clloyd » 27. Oct 2017, 05:35

michaln wrote:Does that happen with every host OS VirtualBox supports, or just the one you tried? If the latter, would you mind mentioning which one it was?


Forgot to mention I'm using Ubuntu 17.04. Somehow it's fine the next day though, including the Manager's preference.

Is that an OS 5.1.8 is expected to recognize?


I might have misinterpreted the error message.
Code: Select all   Expand viewCollapse view
Error reading OVA (VERR_TAR_UNEXPECTED_EOS), Result Code VBOX_E_IPRT_ERROR (OX80BB0005), Component: ApplianceWrap, Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}

Some googling suggests it might be due to corrupted file. But I was able to export the same VM (guest OS is XP 32-bit) using 5.1.28 with the same external HDD, to be imported by 5.1.8.
This time with 5.2, I had to export .vdi instead, create new VM in the destination and point to the vdi.
clloyd
 
Posts: 4
Joined: 26. Oct 2017, 02:33

Re: Discuss the 5.2.0 release

Postby mpack » 27. Oct 2017, 08:44

UNEXPECTED_EOS means unexpected End Of Stream, a.k.a. unexpected end of file a.k.a. truncated OVA.

Nothing to do with recognizing the OS, which VirtualBox doesn't need to do anyway.
mpack
Site Moderator
 
Posts: 25501
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Discuss the 5.2.0 release

Postby klaus » 27. Oct 2017, 12:16

If you have an appliance which can't be imported we can only investigate the cause (especially if it isn't truncated in reality, which can be e.g. established by comparing some checksum, length and so on). We'll investigate any such case, no matter who/what created the OVA appliance which doesn't work, with extra motivation if VirtualBox can't import something created by an older or newer version of VirtualBox.
klaus
Oracle Corporation
 
Posts: 537
Joined: 10. May 2007, 14:57

Re: Discuss the 5.2.0 release

Postby Air Force One » 1. Nov 2017, 02:02

Sorry to tell this, but I still have some problems with sound, as described here. I tested with current development version (118869) and 118425 before. And I saw some tickets about this issue already opened in bug tracker.

I think that the problem is a new asynchronous HDA emulation. So it really asynchronous to the sound in the VM, which one can see by watching some video and hearing the lag. Another issue is that there is some kind of buffer, which is also has some problems with asynchronous execution, so I have some distortion at the end or beginning of the playback and then periodically after some time. The stammer of playback on pausing it has probably also something to do with buffer and asynchronous emulation: emulation can’t be completely paused and plays the last sound over and over again.

I hope that developer would fix this in the near future. These issues aren’t big ones, but somehow disturbing. The new audio switches are really nice and it would be such a pity to lose them. Otherwise, it’s better to go back to the old but functioning emulation, the same thing which happened last summer after the new sound implementation couldn’t be corrected for some months.
Air Force One
 
Posts: 12
Joined: 6. Oct 2017, 16:54

Unable to import appliance

Postby clloyd » 2. Nov 2017, 06:29

klaus wrote:If you have an appliance which can't be imported we can only investigate the cause (especially if it isn't truncated in reality, which can be e.g. established by comparing some checksum, length and so on). We'll investigate any such case, no matter who/what created the OVA appliance which doesn't work, with extra motivation if VirtualBox can't import something created by an older or newer version of VirtualBox.


I just tried exporting the same VM using 5.2 and 5.1.30 (OVF 2.0 with manifest in a .OVA file on both versions). Both versions yield similar size but different checksum. I can import the VM on 5.1.8 created by 5.1.30 but not 5.2 (same error message).
clloyd
 
Posts: 4
Joined: 26. Oct 2017, 02:33

Re: Unable to import appliance

Postby michaln » 2. Nov 2017, 12:43

clloyd wrote:I can import the VM on 5.1.8 created by 5.1.30 but not 5.2 (same error message).

Can you import the VM created by 5.2 into 5.1.30? 5.1.8 is long outdated and may well have bugs related to import.
michaln
Oracle Corporation
 
Posts: 2841
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Any and all

Re: Discuss the 5.2.0 release

Postby mpack » 5. Nov 2017, 17:44

Prabh wrote:can i install and run ESXi in a Virtualbox VM?

Only if it can run without VT-x: a question for VMWare to answer.
mpack
Site Moderator
 
Posts: 25501
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Discuss the 5.2.0 release

Postby SgtSaltNPeppr » 6. Nov 2017, 16:04

I had to back out 5.2, also. Most of my Linux VMs which used KVM as the virtualizer gave repeated problems starting. Many with kernel timing problems. Going back to 5.13
SgtSaltNPeppr
 
Posts: 1
Joined: 6. Nov 2017, 16:02

Re: Discuss the 5.2.0 release

Postby michaln » 7. Nov 2017, 13:20

SgtSaltNPeppr wrote:I had to back out 5.2, also. Most of my Linux VMs which used KVM as the virtualizer gave repeated problems starting. Many with kernel timing problems. Going back to 5.13

You're welcome to downgrade, but bugs that are not reported are not going to magically fix themselves (and this was definitely not a bug report).
michaln
Oracle Corporation
 
Posts: 2841
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Any and all

Re: Unable to import appliance

Postby clloyd » 10. Nov 2017, 10:57

michaln wrote:Can you import the VM created by 5.2 into 5.1.30?


Yes, I can import into 5.1.30. Issue resolved.
clloyd
 
Posts: 4
Joined: 26. Oct 2017, 02:33

Re: Discuss the 5.2.0 release

Postby 007-theguru » 11. Nov 2017, 04:13

michaln wrote:
SgtSaltNPeppr wrote:I had to back out 5.2, also. Most of my Linux VMs which used KVM as the virtualizer gave repeated problems starting. Many with kernel timing problems. Going back to 5.13

You're welcome to downgrade, but bugs that are not reported are not going to magically fix themselves (and this was definitely not a bug report).


can please kindly fix the sound lag issue when playing games installed on latest vm 5.2 ? as only 5.2 works with creators fall update 1709 but has sound lag issue for games. have to use previous creators update 1703 to use vm 5.1 for games (as 5.1 does not work with fall creators update 1709) which works perfect with no lag in sound when playing games.
007-theguru
 
Posts: 4
Joined: 18. Oct 2017, 21:42

Windows XP Guest - no more 3d acceleration

Postby Ethancarter » 18. Nov 2017, 23:30

Hello,

I use Virtualbox on Windows 10 Host (fall update). My Guest is Windows XP.

Since I upgrade to Virtualbox 5.2, 3d acceleration (Direct 3D) is no more working.

Every 3d app crashes, even dxdiag. When I stop the guest, I have a "Wine3D fake windows" (????) that prevent Windows shutdown....

I'm on a new installation of Windows XP (x86) + SP3 + all updates of Windows Updates.

I installed Virtualbox addition in safe mode and 3D acceleration is enabled.

I already had the same issue, fixed by reinstalling Nvidia Drivers (on the host)
But I update my drivers with the latest driver (on the host) but 3D crashes on the host again.

Thanks !

Attachment : vbox.log
Attachments
XP-2017-11-18-22-23-49.zip
(34.52 KiB) Not downloaded yet
Last edited by Ethancarter on 19. Nov 2017, 13:20, edited 2 times in total.
Ethancarter
 
Posts: 7
Joined: 16. Oct 2017, 18:44

Re: Discuss the 5.2.0 release

Postby mpack » 19. Nov 2017, 10:11

I moved your post to the 5.2.0 feedback topic where it belongs.

As to the problem, I found something similar, except that DxDiag hung, it did not crash. I have not had time to investigate further.
mpack
Site Moderator
 
Posts: 25501
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Discuss the 5.2.0 release

Postby Ethancarter » 19. Nov 2017, 13:16

mpack wrote:I moved your post to the 5.2.0 feedback topic where it belongs.

As to the problem, I found something similar, except that DxDiag hung, it did not crash. I have not had time to investigate further.


Sorry. I didn't read your post, so I post again my topic (you can delete it)
However, Markie has the same issue (viewtopic.php?f=2&t=85509) on XP Guest.
And yes, dxdiag don't crashes, it hungs (my english is too bad, I didn't choose the good word).
Markie explained the issue better.
Ethancarter
 
Posts: 7
Joined: 16. Oct 2017, 18:44

Kernel 4.14.0 breaks VB 5.20 on Linux Mint Host

Postby mingle » 20. Nov 2017, 04:46

Hi guys,

Just ran into a show-stopper on my Linux Mint 18.2 64-bit xfce host system.

Running kernel 4.13.2 all was fine with VB 5.20.

Then I upgraded the Linux kernel to 4.14.0, after than VB fails to start, see the attached screen-shot.

Reverted to kernel 4.13.2 and worked okay.

I tried running /sbin/vboxconfig, but it fails with multiple error when trying to build the modules - I can't included the log file, as it was 12.3MB in size.

I also tried re-installing the DEB package, but that made no difference.

Cheers,

Mike.
Attachments
Screenshot_2017-11-20_12-38-37.jpg
Screenshot_2017-11-20_12-38-37.jpg (107.05 KiB) Viewed 160 times
mingle
 
Posts: 28
Joined: 6. Jun 2015, 07:55

PreviousNext

Return to Using VirtualBox

Who is online

Users browsing this forum: No registered users and 9 guests