virtualbox.org

(Mod edit: Split from another user's topic)

Do the mods/Oracle have enough 6.1.3x logs yet?

AndyCot wrote:Do the mods/Oracle have enough 6.1.3x logs yet?

Although I'm no moderator and also not affiliated to Oracle or the VirtualBox development, I'll try to answer that from my POV. I've done my own investigations (see Re: Discuss the 6.1.32 release), and most VBox.log files reported by users match my findings. But a few reports deviate from that, and it's possible that I discover some additional details that may help.

Besides that, we generally try to advise VirtualBox users to disable Hyper-V if they don't need it, because VirtualBox VMs perform much better then, which holds true for any 6.1.x version.

I will try again:
Do end users of 6.1.32 still need to take the time and effort to supply log files if there have already been allot of log files supplied and it appeared that the issue has been potentially (hopefully) been identifies w.r.t. the conditions that cause the slowdown issues or apparent crashes as the guest is so slow the end user thinks the geuest has crashed?


Unfortunately Hyper-V is needed more and more in a MS dev environment now days and this has been known for a number of years now (at least 3 that I am aware) and as such should have given Oracle enough time to address s the Hyper-V issues like the other VM systems have done The other players in the commercial and OSS space have had Hyper-V working for at least a year.

Unfortunately I have not go into the low level VM "stuff" in then newer CPUs at the CPU ring level as I have not had to. Last time I looked at the x86 type CPU at this level was 15 years ago for trying to figure out about debugging a third party RTOS that ran on top of Windows for dev purposes instead of using real embedded H/W and OS/debugging that sucked compared to the windows environment. Now days I write the emulate the embedded H/W as a thread or sperate app on Windows and/or Linux and mod the app to run as as a Window and/or Linux app for dev purposes.

If you are reporting a problem, provide a zipped VM log file. If you don't think your report is needed then don't make one.

What!!

or as one of our red neck ozzie politicians say "please explain".

Typically, we need a log for every problem reported by a user who asks for help on any subject. If those logs end up showing a problem we already know how to fix easily, that is still a good thing.

Otherwise we would be guessing at the cause of the problem, and we might guess wrong (I've fallen into that trap).

So all new posters should be asked for a log, regardless of whether we are pretty certain or not what the cause of the issue is.

As Dr Thorndyke postulates, 'It is not before an investigation that we determine what information is necessary for the investigation, but afterwards.'

Besides:

fth0 wrote:most VBox.log files reported by users match my findings. But a few reports deviate from that

It looks like we're not entirely out of the woods yet.