diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/output/hypervisor/1798057 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/1798057')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/output/hypervisor/1798057 | 29 |
1 files changed, 0 insertions, 29 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/1798057 b/results/classifier/deepseek-2-tmp/output/hypervisor/1798057 deleted file mode 100644 index 799b561ef..000000000 --- a/results/classifier/deepseek-2-tmp/output/hypervisor/1798057 +++ /dev/null @@ -1,29 +0,0 @@ - -Not able to start instances larger than 1 TB - -Specs: - -CPU: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz -OS: Ubuntu 18.04 AMD64 -QEMU: 1:2.11+dfsg-1ubuntu7.6 (Ubuntu Bionic Package) -Openstack: Openstack Queens (Ubuntu Bionic Package) -Libvirt-daemon: 4.0.0-1ubuntu8.5 -Seabios: 1.10.2-1ubuntu1 - - -The Problem: -We are not able to start instances, which have a memory size over 1 TB. -After starting the instance, they shortly lock up. Starting guests with a lower amount of RAM works -perfectly. We dealt with the same problem in the past with an older Qemu Version (2.5) by patching some source files according to this patch: - -https://git.centos.org/blob/rpms!!qemu-kvm.git/34b32196890e2c41b0aee042e600ba422f29db17/SOURCES!kvm-fix-guest-physical-bits-to-match-host-to-go-beyond-1.patch - - -I think we now have somewhat the same problem here, however the source base changed and I'am not able to find the corresponding snippet to patch this. - -Also, guests show a wrong physical address size which is probably the cause of the lock ups on high memory guests: -root@debug:~# grep physical /proc/cpuinfo -physical id : 0 -address sizes : 40 bits physical, 48 bits virtual - -Any way to fix this? \ No newline at end of file |