since Haiku is an GUI only OS and currently VMM doesn't suppot framebuffer or VNC/RDP (and perhaps will never support?) getting Haiku running on VMM is quite hard to get useful. this might can fixed with a pre-installed haiku image with VNC enabled on boot using qemu. there are some packages on HaikuPorts for basic VNC server, i didn't checked them yet. however, here are logs Haiku i386: Connected to /dev/ttyp5 (speed 115200) Boot failed: not a bootable disk ....................... Welcome to kernel debugger output! Haiku revision: hrev55181+51, debug level: 1 CPU: no microcode provided reserve_io_interrupt_vectors: reserved 2 vectors starting from 98 CPU 0: type 0 family 6 extended_family 0 model 13 extended_model 2 stepping 7, s tring 'GenuineIntel' CPU 0: vendor 'Intel' model name 'Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz' No CPU topology information available. CPU 0: apic id 0, package 0, core 0, smt 0 CPU 0: features: fpu vme de pse tsc msr pae cx8 sep pge cmov pat pse36 clfsh mmx fxsr sse sse2 sse3 pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx hype rvisor syscall nx pdpe1gb long CPU 0: patch_level 0 reserve_io_interrupt_vectors: reserved 16 vectors starting from 0 using PAE paging mark_page_range_in_use(0x0, 0x100): start page is before free list mark_page_range_in_use(0x0, 0xa0): start page is before free list PANIC: did not find any boot partitions! Welcome to Kernel Debugging Land... Thread 14 "main2" running on CPU 0 stack trace for thread 14 "main2" kernel stack: 0x8260f000 to 0x82613000 frame caller :function + offset 0 826129a8 (+ 32) 80148aa2 arch_debug_stack_trace() + 0x12 1 826129c8 (+ 16) 800a6f33 stack_trace_trampoline__FPv() + 0x0b 2 826129d8 (+ 12) 8013a3b6 arch_debug_call_with_fault_handler() + 0x1b 3 826129e4 (+ 48) 800a89d7 debug_call_with_fault_handler() + 0x 57 4 82612a14 (+ 64) 800a713f kernel_debugger_loop__FPCcT0Pcl() + 0x207 5 82612a54 (+ 48) 800a74e3 kernel_debugger_internal__FPCcT0Pcl( ) + 0x77 6 82612a84 (+ 48) 800a8d4a panic() + 0x3a 7 82612ab4 (+1200) 80103af4 vfs_mount_boot_file_system() + 0x80 8 82612f64 (+ 80) 80067cb1 main2__FPv() + 0xad 9 82612fb4 (+ 48) 80088d2e common_thread_entry__FPv() + 0x3a initial commands: syslog | tail 15 ata 0 error: target device not present ata 0 error: target device not present ata 0 error: invalid target device Last message repeated 12 times. ata 1: controller doesn't support DMA, disabling ata 1: _DevicePresent: device selection failed for device 0 ata 1: _DevicePresent: device 1, presence 0 ata 1: deviceMask 0 ata 1: ignoring device 0 ata 1: ignoring device 1 ata 1 error: target device not present ata 1 error: target device not present ata 1 error: invalid target device Last message repeated 12 times. KDiskDeviceManager::InitialDeviceScan() returned error: No such file or director y kdebug> Haiku amd64: Connected to /dev/ttyp5 (speed 115200) Boot failed: not a bootable disk ....................... Welcome to kernel debugger output! Haiku revision: hrev55181+51, debug level: 1 CPU: no microcode provided CPU 0: type 0 family 6 extended_family 0 model 13 extended_model 2 stepping 7, string 'GenuineIntel' CPU 0: vendor 'Intel' model name 'Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz' No CPU topology information available. CPU 0: apic id 0, package 0, core 0, smt 0 CPU 0: features: fpu vme de pse tsc msr pae cx8 sep pge cmov pat pse36 clfsh mmx fxsr sse sse2 sse3 pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx hypervisor syscall nx pdpe1gb long CPU 0: patch_level 0 reserve_io_interrupt_vectors: reserved 16 vectors starting from 0 mark_page_range_in_use(0x0, 0x100): start page is before free list mark_page_range_in_use(0x0, 0xa0): start page is before free list PANIC: did not find any boot partitions! Welcome to Kernel Debugging Land... Thread 14 "main2" running on CPU 0 stack trace for thread 14 "main2" kernel stack: 0xffffffff81e7f000 to 0xffffffff81e84000 frame caller :function + offset 0 ffffffff81e83928 (+ 24) ffffffff8014510c arch_debug_call_with_fault_handler() + 0x16 1 ffffffff81e83940 (+ 80) ffffffff800a9108 debug_call_with_fault_handler() + 0x88 2 ffffffff81e83990 (+ 96) ffffffff800aaa91 _ZL20kernel_debugger_loopPKcS0_P13__va_list_tagi() + 0xf1 3 ffffffff81e839f0 (+ 80) ffffffff800aad8e _ZL24kernel_debugger_internalPKcS0_P13__va_list_tagi() + 0x6e 4 ffffffff81e83a40 (+ 240) ffffffff800ab0f7 panic() + 0xb7 5 ffffffff81e83b30 (+1072) ffffffff8010bd0e vfs_mount_boot_file_system() + 0x3ae 6 ffffffff81e83f60 (+ 80) ffffffff80062799 _ZL5main2Pv() + 0x99 7 ffffffff81e83fb0 (+ 32) ffffffff8008b5b6 _ZL19common_thread_entryPv() + 0x36 8 ffffffff81e83fd0 (+2115485744) ffffffff81e83fe0 initial commands: syslog | tail 15 file system: file_systems/packagefs/v1 KDiskDeviceManager::_AddDiskSystem(file_systems/packagefs/v1) KDiskDeviceManager::_AddDiskSystem() done: No error file system: file_systems/iso9660/v1 KDiskDeviceManager::_AddDiskSystem(file_systems/iso9660/v1) KDiskDeviceManager::_AddDiskSystem() done: No error file system: file_systems/write_overlay/v1 KDiskDeviceManager::_AddDiskSystem(file_systems/write_overlay/v1) KDiskDeviceManager::_AddDiskSystem() done: No error file system: file_systems/bfs/v1 KDiskDeviceManager::_AddDiskSystem(file_systems/bfs/v1) KDiskDeviceManager::_AddDiskSystem() done: No error number of disk systems: 10 KDiskDeviceManager::_Scan(/dev/disk) KDiskDeviceManager::InitialDeviceScan() returned error: No such file or directory kdebug>