2024/freebsd-virtualization/20240129.freebsd-virtualization
Messages: 58, sorted by subject
|
Last update: Thu Nov 6 9:36:49 UTC 2025
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. Jan 24 bugzilla-noreply@freebsd.o [Bug 228907] VMCI driver: During datagram dispatch if there's no source context then use the current context. 2. Jan 27 bugzilla-noreply@freebsd.o [Bug 268653] /src/sys/dev/hyperv/input/hv_kbd.c error: use of undeclared identifier 'keycode' 3. 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 4. 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 5. 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 6. Jan 25 bugzilla-noreply@freebsd.o [Bug 275760] bhyve: xhci not working on linux guests 7. Jan 26 bugzilla-noreply@freebsd.o [Bug 275760] bhyve: xhci not working on linux guests 8. Jan 28 bugzilla-noreply@freebsd.o [Bug 275760] bhyve: xhci not working on linux guests 9. Jan 28 bugzilla-noreply@freebsd.o [Bug 275760] bhyve: xhci not working on linux guests 10. Jan 22 bugzilla-noreply@freebsd.o [Bug 275906] FreeBSD/amd64 main@51e7276365ba does not run on AWS 11. Jan 26 bugzilla-noreply@freebsd.o [Bug 276361] 14.0-Release iso boot challenges on virtualbox 12. Jan 26 bugzilla-noreply@freebsd.o [Bug 276361] 14.0-Release iso boot challenges on virtualbox 13. Jan 22 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 14. Jan 22 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 15. Jan 22 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 16. Jan 22 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 17. Jan 26 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 18. Jan 28 bugzilla-noreply@freebsd.o [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB 19. 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 20. 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
21. 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 22. 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 23. 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 24. Jan 22 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 25. Jan 22 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 26. Jan 22 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 27. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 28. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 29. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 30. Jan 26 bugzilla-noreply@freebsd.o [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 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 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead 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 24 bugzilla-noreply@freebsd.o [Bug 276575] Host can cause a crash in bhyve nvme emulation 44. Jan 24 bugzilla-noreply@freebsd.o [Bug 276575] Host can cause a crash in bhyve nvme emulation 45. Jan 26 bugzilla-noreply@freebsd.o [Bug 276575] Host can cause a crash in bhyve nvme emulation 46. Jan 22 Chuck Tuffli bhyve without UEFI questions 47. Jan 23 Peter Grehan Re: bhyve without UEFI questions 48. Jan 23 Henrik Gulbrandsen Re: bhyve without UEFI questions 49. Jan 23 Tomek CEDRO Re: bhyve without UEFI questions 50. Jan 28 bugzilla-noreply@FreeBSD.o Problem reports for virtualization@FreeBSD.org that need special attention 51. Jan 28 Jo Durchholz Vagrant images for KVM? 52. Jan 28 Miroslav Lachman Re: Vagrant images for KVM? 53. Jan 28 Jo Durchholz Re: Vagrant images for KVM? 54. Jan 28 Jo Durchholz Re: Vagrant images for KVM? 55. Jan 22 void vmm_load crashes to debugger early 56. Jan 22 Kyle Evans Re: vmm_load crashes to debugger early 57. Jan 23 void Re: vmm_load crashes to debugger early 58. Jan 27 void Re: vmm_load crashes to debugger early
home | up | archive sorted by: subject | author | date | reverse date