[Bug 1923693] [NEW] Lack of architecture in gdbstub makes debugging confusing

2021-04-13 Thread kallisti5
Public bug reported: I spent some quality time debugging GEF and came to a conclusion here: https://github.com/hugsy/gef/issues/598#issuecomment-819174169 tldr; * gdb_arch_name was undefined on riscv * this bug was fixed recently via https://github.com/qemu/qemu/commit/edf647864bdab84ed4b1a4f47

[Bug 1715203] Re: Maintain Haiku support

2020-09-06 Thread kallisti5
A patch for this work has been posted to the qemu-dev ML. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1715203 Title: Maintain Haiku support Status in QEMU: Confirmed Bug description: It was

[Bug 1715203] Re: Maintain Haiku support

2020-09-05 Thread kallisti5
and away we go.. ./haiku.x86_64 --image /tmp/haiku.img --build-qemu /home/kallisti5/Code/qemu Submodule 'dtc' (https://git.qemu.org/git/dtc.git) registered for path 'dtc' Submodule 'slirp' (https://git.qemu.org/git/libslirp.git) registered for path 'slirp

[Bug 1715203] Re: Maintain Haiku support

2020-09-05 Thread kallisti5
$ ./haiku.x86_64 --verbose --image /tmp/haiku.img uname Haiku ./haiku.x86_64 --verbose --image /tmp/haiku.img "gcc -v" Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/8.3.0/lto-wrapper Target: x86_64-unknown-haiku Configured

[Bug 1715203] Re: Maintain Haiku support

2020-09-05 Thread kallisti5
ok.. a Haiku vm for QEMU is WIP here: https://github.com/kallisti5/qemu/tree/haiku-test-vm ``` $ ./haiku.x86_64 --build-image --image /tmp/haiku.img ### Downloading disk image ... ### Preparing disk image ... ./box.img 100% repochecksum-1 [65 bytes] Validating checksum for Haiku...done. 100

[Bug 1715203] Re: Maintain Haiku support

2020-09-05 Thread kallisti5
Hi! Sorry, I forgot about this one. Haiku has a lot of options.. we can setup a vm image if needed to move this along. Haiku is graphical, but has ssh and all the standard tools. Vagrant also supports Haiku and provides some automation around it. https://app.vagrantup.com/boxes/search?utf8=%E2%

[Qemu-devel] [Bug 1715203] Re: Maintain Haiku support

2017-09-07 Thread kallisti5
We're purchasing some new hardware, once we get it set up we'll setup a x86_64 Haiku machine to build qemu. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1715203 Title: Maintain Haiku support Stat

[Qemu-devel] [Bug 1715203] Re: Maintain Haiku support

2017-09-05 Thread kallisti5
Contacting our board of directors to see if I can get a VM deployed at Vultr. I'll keep this ticket updated. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1715203 Title: Maintain Haiku support Sta

[Qemu-devel] [Bug 1715203] Re: Maintain Haiku support

2017-09-05 Thread kallisti5
Haiku recently got a virtio driver, so running a Haiku system in cloud infrastructure seems possible now. (I've personally run it on vultr.com) Does QEMU have some infrastructure available so we can stand up a x86_64 system? -- You received this bug notification because you are a member of qemu-

[Qemu-devel] [Bug 1715203] [NEW] Maintain Haiku support

2017-09-05 Thread kallisti5
Public bug reported: It was pointed out that the 2.10 release notes are pushing to drop Haiku support. The qemu port is currently working as-is under Haiku. Was there a reason this was recommended? Is there anything Haiku can do to keep it from being dropped? We're working on a docker container