virtualization  

Messages by Thread

• • [Bug 277326] FreeBSD guest on QEMU with Hyper-V enlightenment on is no longer able to detect Hyper-V devices bugzilla-noreply
  • [Bug 277326] FreeBSD guest on QEMU with Hyper-V enlightenment on is no longer able to detect Hyper-V devices bugzilla-noreply
  • [Bug 277326] FreeBSD guest on QEMU with Hyper-V enlightenment on is no longer able to detect Hyper-V devices bugzilla-noreply
  • [Bug 277326] FreeBSD guest on QEMU with Hyper-V enlightenment on is no longer able to detect Hyper-V devices bugzilla-noreply
  • [Bug 277326] FreeBSD guest on QEMU with Hyper-V enlightenment on is no longer able to detect Hyper-V devices bugzilla-noreply
• drm-kmod-20220907_2 not supported for this configuration / NVIDIA : Failed to initialize the NVIDIA kernel module Mario Marietto
  • RE: drm-kmod-20220907_2 not supported for this configuration / NVIDIA : Failed to initialize the NVIDIA kernel module Simon Gusev
  • Re: drm-kmod-20220907_2 not supported for this configuration / NVIDIA : Failed to initialize the NVIDIA kernel module Mario Marietto
  • Re: drm-kmod-20220907_2 not supported for this configuration / NVIDIA : Failed to initialize the NVIDIA kernel module Mario Marietto
• Best way to have a FreeBSD VM for automated testing? Jo Durchholz
  • Re: Best way to have a FreeBSD VM for automated testing? Mario Marietto
  • Re: Best way to have a FreeBSD VM for automated testing? Jo Durchholz
  • Re: Best way to have a FreeBSD VM for automated testing? Mario Marietto
  • Re: Best way to have a FreeBSD VM for automated testing? Shane Ambler
  • Re: Best way to have a FreeBSD VM for automated testing? Mark Blackman
  • Re: Best way to have a FreeBSD VM for automated testing? Jo Durchholz
  • Re: Best way to have a FreeBSD VM for automated testing? Paul Vixie
  • Re: Best way to have a FreeBSD VM for automated testing? Jo Durchholz
  • Re: Best way to have a FreeBSD VM for automated testing? Shane Ambler
  • Re: Best way to have a FreeBSD VM for automated testing? John Nielsen
  • Re: Best way to have a FreeBSD VM for automated testing? Jo Durchholz
• problems booting netbsd guest on bhyve host void
• [Bug 277128] IPV6 public address lost after networking driver reload OR attaching a new network interface bugzilla-noreply
  • [Bug 277128] IPV6 public address lost after networking driver reload OR attaching a new network interface bugzilla-noreply
• How to send a bhyve vm totally in background,suppressing any message produced by the bhyve script that I use. Mario Marietto
  • Re: How to send a bhyve vm totally in background,suppressing any message produced by the bhyve script that I use. Aryeh Friedman
  • Re: How to send a bhyve vm totally in background,suppressing any message produced by the bhyve script that I use. Mario Marietto
  • Re: How to send a bhyve vm totally in background,suppressing any message produced by the bhyve script that I use. Mario Marietto
  • Re: How to send a bhyve vm totally in background,suppressing any message produced by the bhyve script that I use. Mario Marietto
• bhyve disk performance issue Matthew Grooms
  • Re: bhyve disk performance issue Chuck Tuffli
  • Re: bhyve disk performance issue Paul Procacci
  • Re: bhyve disk performance issue Chuck Tuffli
  • Re: bhyve disk performance issue Matthew Grooms
  • Re: bhyve disk performance issue Matthew Grooms
  • Re: bhyve disk performance issue Matthew Grooms
  • Re: bhyve disk performance issue Matthew Grooms
  • Re: bhyve disk performance issue Jason Tubnor
  • Re: bhyve disk performance issue Matthew Grooms
  • Re: bhyve disk performance issue Stephan Althaus
  • Re: bhyve disk performance issue Matthew Grooms
  • Re: bhyve disk performance issue Vitaliy Gusev
  • Re: bhyve disk performance issue Matthew Grooms
  • Re: bhyve disk performance issue Vitaliy Gusev
  • Re: bhyve disk performance issue Matthew Grooms
  • Re: bhyve disk performance issue Vitaliy Gusev
  • Re: bhyve disk performance issue Matthew Grooms
• VNC Viewer on Windows: Unable to access VMs GUI Odhiambo Washington
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Mario Marietto
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Odhiambo Washington
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Odhiambo Washington
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Mario Marietto
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Odhiambo Washington
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Mario Marietto
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Mario Marietto
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Odhiambo Washington
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Mario Marietto
  • Re: VNC Viewer on Windows: Unable to access VMs GUI Corvin Köhne
• 14R bhyve RHEL9+NVME Matthew Grooms
  • Re: 14R bhyve RHEL9+NVME Jason Tubnor
  • Re: 14R bhyve RHEL9+NVME Chuck Tuffli
  • Re: 14R bhyve RHEL9+NVME Matthew Grooms
• OpenBSD vm troubles Odhiambo Washington
  • Re: OpenBSD vm troubles Shane Ambler
  • Re: OpenBSD vm troubles Mario Marietto
• [Bug 276815] loader.efi: failure to load a module causes general protection fault bugzilla-noreply
  • [Bug 276815] loader.efi: failure to load a module causes general protection fault bugzilla-noreply
  • [Bug 276815] loader.efi: failure to load a module causes general protection fault bugzilla-noreply
• if_ixl: Admin Queue memory allocation issue hangs the server Antranig Vartanian
  • Re: if_ixl: Admin Queue memory allocation issue hangs the server Loren M. Lang
• If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Alejandro Imass
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Odhiambo Washington
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Mario Marietto
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Alejandro Imass
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Patrick M. Hausen
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Alejandro Imass
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Sam W
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Mario Marietto
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Alejandro Imass
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Paul Vixie
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Mario Marietto
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Alejandro Imass
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Mario Marietto
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Alejandro Imass
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Mario Marietto
  • Re: If we are so opposed to Docker and Kubernetes, what is the real alternative on BSD? Alejandro Imass
• [Bug 276734] bhyve gets stuck during VM boot bugzilla-noreply
  • [Bug 276734] bhyve gets stuck during VM boot bugzilla-noreply
  • [Bug 276734] bhyve gets stuck during VM boot bugzilla-noreply
• Contributing the build of a KVM image Jo Durchholz
  • Re: Contributing the build of a KVM image Pete Wright
  • Re: Contributing the build of a KVM image Jo Durchholz
  • Re: Contributing the build of a KVM image Jo Durchholz
  • Won't contribute KVM build :-( (was: Contributing the build of a KVM image) Jo Durchholz
• [Bug 276720] AMIs fail to boot in AWS EC2 bugzilla-noreply
  • [Bug 276720] AMIs fail to boot in AWS EC2 bugzilla-noreply
  • [Bug 276720] AMIs fail to boot in AWS EC2 bugzilla-noreply
  • [Bug 276720] AMIs fail to boot in AWS EC2 bugzilla-noreply
  • [Bug 276720] AMIs fail to boot in AWS EC2 bugzilla-noreply
  • [Bug 276720] AMIs fail to boot in AWS EC2 bugzilla-noreply
  • [Bug 276720] AMIs fail to boot in AWS EC2 bugzilla-noreply
  • [Bug 276720] AMIs fail to boot in AWS EC2 bugzilla-noreply
  • [Bug 276720] AMIs fail to boot in AWS EC2 bugzilla-noreply
• Vagrant images for KVM? Jo Durchholz
  • Re: Vagrant images for KVM? Miroslav Lachman
  • Re: Vagrant images for KVM? Jo Durchholz
  • Re: Vagrant images for KVM? Jo Durchholz
• [Bug 228907] VMCI driver: During datagram dispatch if there's no source context then use the current context. bugzilla-noreply
• [Bug 276575] Host can cause a crash in bhyve nvme emulation bugzilla-noreply
  • [Bug 276575] Host can cause a crash in bhyve nvme emulation bugzilla-noreply
  • [Bug 276575] Host can cause a crash in bhyve nvme emulation bugzilla-noreply
  • [Bug 276575] Host can cause a crash in bhyve nvme emulation bugzilla-noreply
• bhyve without UEFI questions Chuck Tuffli
  • Re: bhyve without UEFI questions Peter Grehan
  • Re: bhyve without UEFI questions Henrik Gulbrandsen
  • Re: bhyve without UEFI questions Tomek CEDRO
• vmm_load crashes to debugger early void
  • Re: vmm_load crashes to debugger early Kyle Evans
  • Re: vmm_load crashes to debugger early void
  • Re: vmm_load crashes to debugger early void
• [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
  • [Bug 276524] Setting LUN block size in ctl.conf to 512 will use volblocksize instead bugzilla-noreply
• [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
  • [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators bugzilla-noreply
• Move VMs from vmswitch to vether0? Mark
• [Bug 276463] Linux guest uses only 503G of memory when using UEFI loader bugzilla-noreply
  • [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB bugzilla-noreply
  • [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB bugzilla-noreply
  • [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB bugzilla-noreply
  • [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB bugzilla-noreply
  • [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB bugzilla-noreply
  • [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB bugzilla-noreply
  • [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB bugzilla-noreply
  • Re: [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB Rodney W. Grimes
  • [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB bugzilla-noreply
  • [Bug 276463] UEFI-booted VM limited to 503GB RAM rather than requested 1.5TB bugzilla-noreply
• [Bug 205549] bhyve pci passthru stops working after guest is restarted bugzilla-noreply
  • [Bug 205549] bhyve pci passthru stops working after guest is restarted bugzilla-noreply
  • [Bug 205549] bhyve pci passthru stops working after guest is restarted bugzilla-noreply
  • [Bug 205549] bhyve pci passthru stops working after guest is restarted bugzilla-noreply
  • [Bug 205549] bhyve pci passthru stops working after guest is restarted bugzilla-noreply
• [Bug 276421] Commit b0165dc4539fdfc84351a719b58850e4e7a6cbb6 inhibits initialization of Xen front and backends bugzilla-noreply
  • [Bug 276421] Commit b0165dc4539fdfc84351a719b58850e4e7a6cbb6 inhibits initialization of Xen front and backends bugzilla-noreply
• [Bug 268653] /src/sys/dev/hyperv/input/hv_kbd.c error: use of undeclared identifier 'keycode' bugzilla-noreply
  • [Bug 268653] /src/sys/dev/hyperv/input/hv_kbd.c error: use of undeclared identifier 'keycode' bugzilla-noreply
  • [Bug 268653] /src/sys/dev/hyperv/input/hv_kbd.c error: use of undeclared identifier 'keycode' bugzilla-noreply
• bhyve intel 530 integrated graphics error Michael Sløgedal
  • Re: bhyve intel 530 integrated graphics error Corvin Köhne
  • RE: bhyve intel 530 integrated graphics error Michael Sløgedal
  • RE: bhyve intel 530 integrated graphics error Michael Sløgedal
• [Bug 276361] 14.0-Release iso boot challenges on virtualbox bugzilla-noreply
  • [Bug 276361] 14.0-Release iso boot challenges on virtualbox bugzilla-noreply
  • [Bug 276361] 14.0-Release iso boot challenges on virtualbox bugzilla-noreply
  • [Bug 276361] 14.0-Release iso boot challenges on virtualbox bugzilla-noreply
  • [Bug 276361] 14.0-Release iso boot challenges on virtualbox bugzilla-noreply
• (vm-)bhyve stopped working recently on 13.2 Tomek CEDRO
  • Re: (vm-)bhyve stopped working recently on 13.2 Mario Marietto
  • Re: (vm-)bhyve stopped working recently on 13.2 Michael Gmelin
  • Re: (vm-)bhyve stopped working recently on 13.2 Tomek CEDRO
  • Re: (vm-)bhyve stopped working recently on 13.2 Michael Gmelin
  • Re: (vm-)bhyve stopped working recently on 13.2 Tomek CEDRO
  • Re: (vm-)bhyve stopped working recently on 13.2 Michael Gmelin
  • Re: (vm-)bhyve stopped working recently on 13.2 Michael Gmelin
  • Re: (vm-)bhyve stopped working recently on 13.2 Tomek CEDRO
  • Re: (vm-)bhyve stopped working recently on 13.2 Bakul Shah
• Unknown option "XENHVM" for Arm 32 and for arm 64 ; missing code detected. Mario Marietto
• Dockerfile to Bastille interpreter/translator Alejandro Imass
  • Re: Dockerfile to Bastille interpreter/translator Zhenlei Huang
  • Re: Dockerfile to Bastille interpreter/translator Alejandro Imass

• Earlier messages
• Later messages