2024/freebsd-virtualization/20240129.freebsd-virtualization
Messages: 58, old messages first
|
Last update: Mon Jan 29 0:07:02 2024
|
|
home | archive sorted by: subject | author | date | reverse date
1. Jan 22 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 2. Jan 22 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 3. Jan 22 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 4. Jan 22 bugzilla-noreply@freebsd.o [Bug 275906] FreeBSD/amd64 main@51e7276365ba does not run on AWS 5. Jan 22 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 6. Jan 22 bugzilla-noreply@freebsd.o [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators 7. Jan 22 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 8. Jan 22 void vmm_load crashes to debugger early 9. Jan 22 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 10. Jan 22 bugzilla-noreply@freebsd.o [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators 11. Jan 22 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 12. Jan 22 Kyle Evans Re: vmm_load crashes to debugger early 13. Jan 22 bugzilla-noreply@freebsd.o [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators 14. Jan 22 Chuck Tuffli bhyve without UEFI questions 15. Jan 23 Peter Grehan Re: bhyve without UEFI questions 16. Jan 23 Henrik Gulbrandsen Re: bhyve without UEFI questions 17. Jan 23 Tomek CEDRO Re: bhyve without UEFI questions 18. Jan 23 void Re: vmm_load crashes to debugger early 19. Jan 24 bugzilla-noreply@freebsd.o [Bug 276575] Host can cause a crash in bhyve nvme emulation 20. Jan 24 bugzilla-noreply@freebsd.o [Bug 276575] Host can cause a crash in bhyve nvme emulation
21. Jan 24 bugzilla-noreply@freebsd.o [Bug 228907] VMCI driver: During datagram dispatch if there's no source context then use the current context. 22. Jan 25 bugzilla-noreply@freebsd.o [Bug 275760] bhyve: xhci not working on linux guests 23. Jan 25 bugzilla-noreply@freebsd.o [Bug 273555] GPT table lost or filesystem became invalid for new disk hot added on an existing LSILogic/LSILogicSAS controller in VM with gues 24. Jan 25 bugzilla-noreply@freebsd.o [Bug 273555] GPT table lost or filesystem became invalid for new disk hot added on an existing LSILogic/LSILogicSAS controller in VM with gues 25. Jan 25 bugzilla-noreply@freebsd.o [Bug 273555] GPT table lost or filesystem became invalid for new disk hot added on an existing LSILogic/LSILogicSAS controller in VM with gues 26. Jan 26 bugzilla-noreply@freebsd.o [Bug 275760] bhyve: xhci not working on linux guests 27. Jan 26 bugzilla-noreply@freebsd.o [Bug 276575] Host can cause a crash in bhyve nvme emulation 28. Jan 26 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 29. Jan 26 bugzilla-noreply@freebsd.o [Bug 276361] 14.0-Release iso boot challenges on virtualbox 30. Jan 26 bugzilla-noreply@freebsd.o [Bug 276361] 14.0-Release iso boot challenges on virtualbox 31. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 32. Jan 26 bugzilla-noreply@freebsd.o [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators 33. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 34. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 35. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 36. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 37. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 38. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 39. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 40. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead
41. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 42. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 43. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 44. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 45. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 46. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 47. Jan 26 bugzilla-noreply@freebsd.o [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators 48. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 49. Jan 27 void Re: vmm_load crashes to debugger early 50. Jan 27 bugzilla-noreply@freebsd.o [Bug 268653] /src/sys/dev/hyperv/input/hv_kbd.c error: use of undeclared identifier 'keycode' 51. Jan 28 bugzilla-noreply@freebsd.o [Bug 275760] bhyve: xhci not working on linux guests 52. Jan 28 bugzilla-noreply@freebsd.o [Bug 275760] bhyve: xhci not working on linux guests 53. Jan 28 Jo Durchholz Vagrant images for KVM? 54. Jan 28 Miroslav Lachman Re: Vagrant images for KVM? 55. Jan 28 Jo Durchholz Re: Vagrant images for KVM? 56. Jan 28 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 57. Jan 28 Jo Durchholz Re: Vagrant images for KVM? 58. Jan 28 bugzilla-noreply@FreeBSD.o Problem reports for virtualization@FreeBSD.org that need special attention
home | archive sorted by: subject | author | date | reverse date