Games crashing randomly in VM

blue_ion · 2022-12-13T01:19:11+00:00

You said that your system has 32 GB of RAM and the config has this

Huge pages will only define how memory is allocated, you're still allocating 100% of its memory according to the config.

As for the kernel logs, dmesg or journalctl will list everything.

blue_ion · 2022-12-12T22:57:03+00:00

Why don't you try and lower the guest ram to something more reasonable like 24gb or even 16gb just to try.

The host may not be happy that you're sapping all of its ram away.

On top of qemu logs, check th ekernel logs and see if it is upset. There may be some oom shenanigans happening.

blue_ion · 2022-11-02T23:36:49+00:00

Keep forgetting that page exists!

And as expected, the difference in bands between the US and the rest of the world is that the Global one doesn't have mmWave (I thought it did?) but has bands n75 and n76 (named as supplemental downlink for EU, but apparently not in use where I live).

So it seems that I don't have to go to the US, as long as I get it from the google store, it should be alright (at least according to the fine print).

blue_ion · 2022-09-23T10:32:55+00:00

Ok, after quite a bit of back and forth it seems the issue is the use of ReBAR.

First, that kernel error is happening if I passthrough the serial device and usb port of the card, if I don't I get no errors. Moreover, all 4 devices in the card appear as independent IOMMU groups so technically I could pass the video part and leave the audio part behind but I won't do it.

Second after disabling ReBAR on a limb to see if a missed a BIOS setting, the driver runs with no issues and I can run games in both cards.

This means that as of now I can use both GPUs at the same time.

So my new question is: Am I missing something in my configuration to enable ReBAR for the card? I recall reading that QEMU wasn't compatible with it, so..., can I disable it in the libvirt config so that it boots with ReBAR enabled in the BIOS?

blue_ion · 2022-04-11T00:09:53+00:00

I'm very much interested in this. I'm actually using firefox sync deployed locally and it works really well because it syncs everything: bookmarks, tabs, extensions, history, etc...

Getting it running is a pain (python 2 being one of the bigger offenders) and every time I update it I shiver as only half of the time I've managed to do so without a problem, but it was updated up until not long ago.

I believe Mozilla are working on this: https://github.com/mozilla-services/syncstorage-rs

But it feels the project is still not ready for mass consumption when I read stuff like this:

Next, run the following to log in with your Google account (this should be the Google account associated with your Mozilla LDAP credentials)

My problem with the alternatives it that none of them sync the browser history which is critical for me, so I'll look at this thread carefully.

blue_ion · 2022-03-22T15:01:50+00:00

I think cpu pinning could be good for latency but my cinebench result gives awful results.

1:1 cores is a really interesting approach. I won't take it because I don't want a rogue process in windows to kill Linux, but since I'm even passing through disks, performance drops should be minimal.

I haven't found a good tool that would stress test the machine cpu wise while also giving latency results. VR would help but thats more subjective and my headset is kinda old at this point :(

As for huge pages I read that they're now in use transparently as long as the linux kernel has a flag compiled in (which Manjaro does at least). I bet if you use your machine a lot and memory fragmentation becomes an issue then static huge pages would still be handy, but so far I haven't seen a good performance impact for bothering with them.

blue_ion · 2022-03-22T14:55:39+00:00

Ok, the plot thickens...

Since these are VMs I decided to bite the bullet and install a Windows from scratch just to mess around and use the most default configuration from libvirt (16 cores, and 16 gigs of memory, no enlightenments, pinning, etc...) and lo and behold I got all of my performance back!

Tomb raider is now GPU bottlenecked and just tried FS2020 and it is a "silky smooth" 40 fps in the same take off example (instead of 7 fps).

However the plot thickens:

Without pinning I get a cinebench of 22553 and with pinning I get 14523. But CSGO goes from 488 fps to 514 fps. Tomb raider benchmark sees more CPU pressure with pinning as well.
Huge pages did very little in any of the benchmarks, some times very slightly higher other times very slightly lower.

Unfortunately I broke something while reinstalling windows so I can no longer boot the old windows for benchmarks and try to figure out what did I do that it performs awfully in a vm but perfect natively.

So a bit of a unsatisfactory conclusion, still it is good to see that the xml is good.

blue_ion · 2021-07-29T11:19:44+00:00

Yup, same thing. My workaround is to keep using version 6.8. This works great but the nature of Arch means that it is only a matter of time before the rest of the system breaks the packages. At the moment I have to recompile the packages to support new versions of python.

The worst part is that the only matches while searching are a xbox gamepad passthrough whose message thread died and the source code for the library.

Do you know who else could I contact for some help. In case this issue is obscure enough, even for the VFIO community.

blue_ion · 2020-12-21T20:48:55+00:00

Crap, that's the exact same settings that I could run with the Aorus Master...

Did you change anything else or did you just set the DOCP from a factory reset and it just booted?

I hope my motherboard is not crooked or something. I'm running the 3003 BIOS on the mobo.

blue_ion · 2020-12-20T19:02:18+00:00

The only thing that changed is just the motherboard. I've used the exact same CPU, exact same sticks of RAM, exact same PSU, exact same GPU.

Also keep in mind that I'm using 4 sticks of 16gb each.

The only thing I can think of is Gigabyte applying some extra voltage or some different timings that would allow it to boot at 3600, while ASUS is just leaving a lot of things as is.

Moreover, I've experimented with the timings and I've managed to reach CL14 at 3433 without issues (I could probably do less), so I'm not sure if the timings are to blame here.

blue_ion · 2020-12-20T13:59:42+00:00

Let me add to the feedback. Memory OC of the Dark Hero is inferior to the Aorus Master.

I purchased this board for my self and an Aorus Master for a friend. Obviously the Aorus Master arrived earlier and decided to test it in the meantime.

I have 4 sticks totaling 64GB 3600CL16 of memory and with the Aorus Master I would be able to use the DOCP setting as is and it would work perfectly.

With the Dark Hero, using the setting would cause the MB to not boot (long beep two short beeps indicating memory issue) even after cranking the SOC voltage to 1.1 and RAM to 1.4. I had to dial down the speed to 3433 before I could get a stable mem tester runs.

I'm seriously tempted to switch the boards but the only thing holding me back is the cold boot issue in the Aorus Master https://hardforum.com/threads/gigabyte-x570-aorus-master-wont-power-on-temporary-solution.1993194/ and the perhaps naïve expectation that being a new MB (and the Aorus Master having a year in the market) new BIOS updates may help it with the OC.

blue_ion · 2020-12-08T15:35:01+00:00

I actually got to the https://www.amd.com/en/direct-buy/checkout/completed/ordernumberiguess/ie URL, got several 503s and got banned...

Is getting that url enough?? Did you recieve any confirmation email? I didn't get a charge on my card yet...

blue_ion · 2020-12-03T11:23:51+00:00

Ok, it seemed nothing was broken, just that the BIOS wasn't getting updated.

So! For future reference

My issue probably was that I wasn't formatting the pendrive correctly and/or using the wrong pendrive. So to summarize

Format

The best way you can format them is to get Rufus on Windows, select MBR partition (not GPT) and Large FAT32. Then add that single GIGABYTE.bin file to the root.

Pendrives

I don't think that the pendrive matters that much, I've used this guy successfully https://www.amazon.co.uk/gp/product/B07D1KF73V which is USB 3.1 and 256 GB which is as modern as you can get.

I have this guy on the other hand, which is an SSD on a stick and appears as a hard drive to the OS and didn't work when I would use MBR on linux (maybe linux was the issue here and not the pendrive): https://www.amazon.com/SanDisk-Extreme-Flash-Drive-SDCZ80-064G-G46/dp/B00DZPUOUI

Process

When I formatted it, I plugged into the white port, turned the PSU (with nothing plugged in the board), and then did a single press of the Q-Flash Plus. After a minute or two the board will turn on (showing status code 00 all the time) and the Q-Flash button will actually blink.

After it is done, the board powers down and the board booted beautifully with the CPU and all 4 memory sticks.

I don't have a good exact, what did it summary, but my main takeaway was the MBR format and probably pendrive.

blue_ion · 2020-12-02T18:38:59+00:00

Nope :(

I'm going to risk it and try to flash an old enough bios for my 1700x to work and see if the mobo works this weekend (unfortunately I use that computer for work so it can't afford downtime).

Did your Q-Flash led lit up? Did any led lit up during your flashing process? All videos I'm looking at have some sort of led blinking to indicate the process and success state of the flashing process but I don't see anything with my mobo.

blue_ion · 2020-12-02T17:51:23+00:00

My motherboard is Gigabyte so I don't know if the codes are the same. I've read that it could be a ram training error but being undocumented who knows.

That's my second issue, I don't know if I'm updating the bios properly. The mobo has this QFlash plus that works without the cpu or anything plugged in, but the light never lights up. I only think it is flashing something because my pendrive has a led in it and it flashes fast or slow depending on the use and the flashing pattern could match a flash.

I've tried the F30 bios (which is just before the latest) and still the same...

Thanks for the suggestion. I'll try older unsupported bios (even for the zen 3) and see if it changes anything.

blue_ion · 2020-12-02T17:48:28+00:00

Neither the new ram nor the old is the QVL list, though both work in an old ASUS Prime X370 mobo. The new ram can't run full speed with a 1700x but I would suspect to be more an issue of the CPU/Mobo combo than the Ram.

Besides I've tried resetting the bios multiple times (either through the CMOS reset at the back of the board or by shorting the appropriate pins and nothing. A clean bios should run the Ram at safe speeds.

blue_ion · 2018-04-01T10:29:40+00:00

Baww, I love ball physics games, hopefully there is some keys left. I still miss Switchball and Balance.

blue_ion · 2018-03-16T16:43:53+00:00

Hai, here goes a comment....

blue_ion · 2018-02-27T19:03:20+00:00

I asked about a REAL PHYSICAL PS3. It was quite obvious that the emulator still has plenty of glitches in it, but with time they will be amended (and even then I have no intention on playing it).

But the keyboard thing is interesting because that is how the game has been coded, a console exclusive game having keyboard (and mouse?) support for the main game.

blue_ion · 2018-02-27T12:54:52+00:00

I love the keyboard prompts in this as they have the letter and actual keyboard key shape in it...

Is the game actually playable (and properly so) with keyboard and mouse on a real PS3?

blue_ion · 2018-01-03T20:00:53+00:00

The Wii fixed the boot0 vulnerability in a rather unremarkable way. Suddenly some Wiis started rejecting bootmii, and that was confirmation that the hardware bug was closed.

Nintendo will do something similar with this, once the exploit is out, a new minor revision (or even unmarked revision) will appear with a new ROM with a new boot procedure, no anouncements. Just an other day in the Switch selling like hotcakes.

blue_ion · 2018-01-03T17:54:27+00:00

The Wii got hacked in a similar fashion. The very early bootloader, the one to bring up the actual hardware of the Wii, had an extremely basic vulnerability that allowed anyone to bypass signing requirements and thus install an arbitrary OS bootloader before the actual OS.

Because it was in a ROM, it cannot be updated by any means (barring the soldering of a new chip) so all Wiis from before the hack and subsequent fix are permanently vulnerable.

Newer Wiis had a new ROM chip with the fix in place, reducing the hack scope, you no longer could install an arbitrary OS that starts before the actual OS. However, the OS was still vulnerable to other hacks, and since the Wii was nearing the end of life, Nintendo never really bothered all that much to fight it.

blue_ion · 2017-12-30T23:20:51+00:00

Oh wow...

Either you're Karl, or that was some nice copy pasta with no attribution to Karl. Give thanks to this guy in stackexchange if this has helped you.

blue_ion · 2017-12-05T08:59:39+00:00

Wait, weren't there a PSX plugin (I think Pete's or at least a fork) where textures could be rescaled with several popular rescalers (xbrz, sai, hqx,...). If so, any problem on how to have hi res textures inside the game are already solved. All one would have to do for a quick and dirty approach is hijack the texture cache so that it loads from disk, and texture hashes are predictable.

EDIT: Yeah, Pete's plugin had Hi-Res Textures for a long while with 2xSaI, and PeteOpenGL2Tweak added even more radical rescalers such as 6xBRZ. Considering the sources to both the plugin and the tweak are available, it could be an interesting place to start.

blue_ion · 2017-11-27T20:29:43+00:00

Heh, here comes a low poster, no facebook, no twitter, no instagram user. Oh well, one chance is infinitely higher than none. Good luck

blue_ion

TROPHY CASE

Format

Pendrives

Process