cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce vnc unix:/var/run/qemu-server/102.vnc,x509,password boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,file=/dev/zvol/nvme/vm-102-disk-2' drive 'if=pflash,unit=0,format=raw,readonly,file=/usr/share/pve-edk2-firmware//OVMF_CODE.fd' chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' device scsi-hd,bus=virtioscsi2.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi2,id=scsi2ĭoes anyone has an idea on what's going on ? device virtio-scsi-pci,id=virtioscsi2,bus=pci.3,addr=0x3 -drive file=/dev/zvol/zfs-sas/vm-72102-disk-3,if=none,id=drive-scsi2,format=raw,cache=none,aio=native,detect-zeroes=on device scsi-hd,bus=virtioscsi1.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1 device virtio-scsi-pci,id=virtioscsi1,bus=pci.3,addr=0x2 -drive file=/dev/zvol/zfs-sas/vm-72102-disk-1,if=none,id=drive-scsi1,format=raw,cache=none,aio=native,detect-zeroes=on device scsi-hd,bus=virtioscsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=200 device virtio-scsi-pci,id=virtioscsi0,bus=pci.3,addr=0x1 -drive file=/dev/zvol/zfs-sas/vm-72102-disk-2,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=100 drive if=none,id=drive-ide2,media=cdrom,aio=threads Smbios1: uuid=e960e799-74ea-4c0f-84a4-fadf865d53b3Īdding io-thread or changing virtio-scsi-single to virtio-scsi doesn't help.Īrguments passed to KVM for disk look ok: I have downgraded packages to previous version : pve-qemu-kvm to 2.11.1-5 and pve-edk2-firmware to 1.20180316-1 with no effect (I even try a last buit of edk2: on /repos/jenkins/edk2/edk2.git-ovmf-圆.rpm )Įfidisk0: zfs-sas:vm-72102-disk-4,size=128K
#Systemrescuecd uefi create plus
It is the same version as what is in portage (5.01), so the fact that the binary compiled by me hangs means something is wrong with the compilation.Ģ) sys-apps/memtest86 (without the plus at the end) does not work at all - it shows some garbled characters after booting.I just upgraded my server from 5.1 to 5.2 but i have most of my VM booting with only the first drive: /dev/sda which has only the UEFI boot partition in FAT32.Īs a result grub complain of not finding the OS disk (UUID) (and it always been that way, I used memtest before - always wondered why is it linux16)ġ) The memtest binary from sysrescuecd works with grub (booted in BIOS i386-pc mode). I do not get the "linux16" either, it is just what /etc/grub.d/39_memtest86 produces. Do not know the reason.įwiw, for legacy (BIOS) booting, systemrescuecd uses syslinux, not grub. You have to boot the usb stick in legacy (BIOS) mode, then the option for memtest shows up. Thank you, actually memtest from systemrescuecd works. To make an error is human, letting it be is the error. Life is a fog where some thinks to know where to go
#Systemrescuecd uefi create install
Have you tried to ask this question in a more apropriate forum?Įither way, how did an install of memtest go without a + as an emerge requrement?įinally, there might be corrupt writes to the memory modules not showing up when just doing reads.
How you can have those mems in a 16-bit mode and at the same time have UEFI-board. Last edited by apurkrt on Wed 6:58 pm edited 1 time in totalĭid you try systemrescuecd? there is your memtest86 present and working i guess.įlux & Contemplation - Portrait of an Artist in Isolation
So anybody knows of a good alternative to memtest86+ working well with UEFI? When I boot with linux16 from x86_64-efi grub with linux16, I see nothing, just hear the beeps (probably because memtest run in text mode, and uefi boots in graphical mode). And it starts the test, but it hangs after a short while. I copied memtest.bin to /run/media/foo/bar/boot/, added an entry for it in grub.cfgīooted in i386-pc legacy mode. Grub-install -target=i386-pc -boot-directory=/run/media/foo/bar/boot/ /dev/sdX I created usb stick in grub i386-pc legacy mode - the usb was created with I tried sys-apps/memtest86+-5.01-r4, but it hangs after 5 seconds (and the memories are 100% ok, I have no problems whatsoever with the system, no crashes, no hangups) Hi, is there something like memtest86+ working well with UEFI? Posted: Wed 3:48 pm Post subject: memtest for UEFI 64bit Gentoo Forums Forum Index Portage & Programming Gentoo Forums :: View topic - memtest for UEFI 64bit
0 kommentar(er)
