OpenBSD Qemu

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

OpenBSD Qemu

abed
OpenBSD 6.7 version crashed on Qemu5.0.0. any idea?


Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD Qemu

abed
Even better. no hopefully I was able to press some keys but it crashing
randomly.

On 5/24/20 9:27 PM, Francois Pussault wrote:

> I failed to install it with Qemu because keyboard was "mad"
> ;)
>
>
>
>> ----------------------------------------
>> From: abed <[hidden email]>
>> Sent: Sun May 24 23:19:16 CEST 2020
>> To: <[hidden email]>
>> Cc: <[hidden email]>
>> Subject: OpenBSD Qemu
>>
>>
>> OpenBSD 6.7 version crashed on Qemu5.0.0. any idea?
>>
>>
>
> Cordialement
> Francois Pussault
> 10 chemin de négo saoumos
> apt 202 - bat 2
> 31300 Toulouse
> +33 6 17 230 820
> [hidden email]
>
Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD Qemu

Solene Rapenne
In reply to this post by abed
Le Sun, 24 May 2020 21:19:16 +0000,
abed <[hidden email]> a écrit :

> OpenBSD 6.7 version crashed on Qemu5.0.0. any idea?

I think you forgot to attach some information like the crash details.

Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD Qemu

abed
Sorry what kind of details you guess we need?

Host OS: FreeBSD 12.1

VMM: Qemu 5.0.0 (compiled from source)

Guest OS: OpenBSD 6.7

qemu-system-x86_64 -m 2048 \ -cdrom cd67.iso \ -drive
if=virtio,file=disk.qcow2,format=qcow2 \ -enable-kvm \ -netdev
user,id=mynet0,hostfwd=tcp:127.0.0.1:7922-:22 \ -device
virtio-net,netdev=mynet0 \ -smp 2

On 5/24/20 10:19 PM, Solene Rapenne wrote:
> Le Sun, 24 May 2020 21:19:16 +0000,
> abed <[hidden email]> a écrit :
>
>> OpenBSD 6.7 version crashed on Qemu5.0.0. any idea?
> I think you forgot to attach some information like the crash details.
>
>
Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD Qemu

abed
yeah that's right, for sure it's Qemu but you know I'm curious to find
the reason or any lead. OK, for now, I will test on earlier version.

On 5/25/20 3:48 AM, Aaron Mason wrote:

> On Mon, May 25, 2020 at 8:40 AM abed <[hidden email]> wrote:
>> Sorry what kind of details you guess we need?
>>
>> Host OS: FreeBSD 12.1
>>
>> VMM: Qemu 5.0.0 (compiled from source)
>>
>> Guest OS: OpenBSD 6.7
>>
>> qemu-system-x86_64 -m 2048 \ -cdrom cd67.iso \ -drive
>> if=virtio,file=disk.qcow2,format=qcow2 \ -enable-kvm \ -netdev
>> user,id=mynet0,hostfwd=tcp:127.0.0.1:7922-:22 \ -device
>> virtio-net,netdev=mynet0 \ -smp 2
>>
>> On 5/24/20 10:19 PM, Solene Rapenne wrote:
>>> Le Sun, 24 May 2020 21:19:16 +0000,
>>> abed <[hidden email]> a écrit :
>>>
>>>> OpenBSD 6.7 version crashed on Qemu5.0.0. any idea?
>>> I think you forgot to attach some information like the crash details.
>>>
>>>
> Maybe a description of what happens leading up to the crash? Logs? Screenshots?
>
> All being said, don't be too surprised if people aren't in a hurry to
> offer support.  The general consensus here is that if the OS works on
> real hardware but not an emulator, the problem is with the emulator,
> not the OS.
>
> I'd suggest trying an earlier version of QEMU, see if it breaks there as well.
>
Reply | Threaded
Open this post in threaded view
|

Re: OpenBSD Qemu

abed
In reply to this post by abed
maybe, but I'm trying to hook something to kernel somehow to remote
debugging the OpenBSD kernel, maybe we need some trap or something. at
least we need a core dump.
I'm sort of surprised by your quick response thanks.

On 5/25/20 4:14 AM, Stuart Longland wrote:

> On 25/5/20 8:34 am, abed wrote:
>> Sorry what kind of details you guess we need?
>>
>> Host OS: FreeBSD 12.1
>>
>> VMM: Qemu 5.0.0 (compiled from source)
>>
>> Guest OS: OpenBSD 6.7
>>
>> qemu-system-x86_64 -m 2048 \ -cdrom cd67.iso \ -drive
>> if=virtio,file=disk.qcow2,format=qcow2 \ -enable-kvm \ -netdev
>> user,id=mynet0,hostfwd=tcp:127.0.0.1:7922-:22 \ -device
>> virtio-net,netdev=mynet0 \ -smp 2
> Maybe direct a virtual serial port to a telnet port in QEMU, use
> `telnet` within `script` to log everything seen there and tell OpenBSD
> to use serial console on aforementioned serial port?
>
> That might give us a `dmesg` dump to work with at least.  If it really
> is interaction with the video console that causes it, maybe pressing
> some keys on said console will trigger it with the log messages going to
> the virtual serial port?