thinkpol has quit [Remote host closed the connection]
thinkpol has joined #osdev
fedaykin has quit [Quit: leaving]
fedaykin has joined #osdev
netbsduser has quit [Ping timeout: 248 seconds]
bleb has quit [Ping timeout: 276 seconds]
bleb has joined #osdev
bleb has quit [Ping timeout: 252 seconds]
bleb has joined #osdev
bauen1 has quit [Ping timeout: 248 seconds]
edr has quit [Quit: Leaving]
slow99 has quit [Ping timeout: 260 seconds]
rorx has quit [Ping timeout: 252 seconds]
PublicWiFi has quit [Ping timeout: 276 seconds]
karenw has joined #osdev
xenos1984 has quit [Read error: Connection reset by peer]
karenw has quit [Read error: Connection reset by peer]
karenw has joined #osdev
PublicWiFi has joined #osdev
xenos1984 has joined #osdev
bliminse has quit [Quit: leaving]
bliminse has joined #osdev
rorx has joined #osdev
Lucretia has joined #osdev
PublicWiFi has quit [Ping timeout: 240 seconds]
PublicWiFi has joined #osdev
vdamewood has joined #osdev
goliath has joined #osdev
GeDaMo has joined #osdev
[Kalisto] has quit [Ping timeout: 240 seconds]
<ZetItUp>
so im back at the issue i had yesterday with my keyboard driver, seems like it's QEMU that's messing it up, anyone has any experience with that?
<ZetItUp>
im even adding the device in the Makefile with: qemu-system-i386 -monitor stdio -m 64M -machine pc -drive id=disk,file=build/diffos.img,if=ide,format=raw -device i8042
<ZetItUp>
it runs perfectly fine in VirtualBox after i tested it a few mins ago
<ZetItUp>
or can it be that im running QEMU inside WSL?
<ZetItUp>
current behaviour in QEMU is that i press a button and it just refuses to handle anymore IRQs on IRQ 1
zaquest has quit [Remote host closed the connection]
karenw has quit [Quit: Deep into that darkness peering...]
gildasio1 has joined #osdev
gildasio has quit [Ping timeout: 244 seconds]
[Kalisto] has joined #osdev
Gooberpatrol66 has quit [Ping timeout: 272 seconds]
Gooberpatrol66 has joined #osdev
duckworld has quit [Remote host closed the connection]
duckworld has joined #osdev
duckworld has quit [Remote host closed the connection]
duckworld has joined #osdev
Left_Turn has joined #osdev
Left_Turn has quit [Remote host closed the connection]
carbonfiber has joined #osdev
HumanG331 has joined #osdev
gildasio1 has quit [*.net *.split]
chiselfuse has quit [*.net *.split]
dude12312414 has quit [*.net *.split]
Yoofie6464463823 has quit [Ping timeout: 240 seconds]
bauen1 has joined #osdev
clever has quit [Ping timeout: 260 seconds]
chiselfuse has joined #osdev
gildasio has joined #osdev
clever has joined #osdev
<ZetItUp>
well after some trial and errors, the solution to the problem was, do not use newer versions of QEMU in WSL when you do osdev :P
<ZetItUp>
version 6 and 7 seems to work just fine
<nikolar>
here's a better solution, don't use windows to program :P
netbsduser has joined #osdev
<zid>
I hope that was without kvm
<zid>
because if you were using kvm, then I fully expect every problem
eck has quit [Quit: PIRCH98:WIN 95/98/WIN NT:1.0 (build 1.0.1.1190)]
vdamewood has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
eck has joined #osdev
xvmt has quit [Read error: Connection reset by peer]
xvmt has joined #osdev
<Ermine>
WSL 1 is half-assed
<Ermine>
WSL 2 is virtualization, but idk if they support nested virtualization
jcea has joined #osdev
<nikolar>
i think they do
<nikolar>
depending on your hardware :P
<nikolar>
zid complained that a win 10 update broke it for his ryzen cpu
carbonfiber has quit [Quit: Connection closed for inactivity]
<Ermine>
it's a property of engine
<nikolar>
what
<Ermine>
nested virt
<nikolar>
what's that got to do with what i said
<nikolar>
he said it worked and then an update broke it
<nikolar>
(on win 10)
<Ermine>
because he could use something other than hyper-v, but now everybody has to go through hyper-v and idk if hyper-v supports it
<nikolar>
you can't use wsl without hyperv
<nikolar>
that's kind of the whole thing
<Ermine>
is this what zid used when it got broken? I lack context
<nikolar>
yes, wsl
<nikolar>
you brought it up
<heat>
WSL 1 is not "half-assed"
<heat>
it's just remarkably hard to implement linux
<nikolar>
indeed
<heat>
even worse so on a !unixy kernel
<nikolar>
it's basically wine for linux
<nikolar>
and it works better than wsl2 for some stuff
<nikolar>
or so i hear
<heat>
i wouldn't know, i only use SUSE Linux Enterprise
<nikolar>
lies
<nikolar>
you use arch
<nikolar>
you lier
<nikolar>
liar
<nikolar>
dang it
<heat>
bozo typo
<heat>
lol
<nikolar>
lol
<Ermine>
heat: because there are subtle differences between windows and linux, so they couldn't reuse windows apis, as they initially planned
<nikolar>
that's not half-assed
<nikolar>
wine has the same issue, jsut in the other direction
<heat>
their whole idea is interesting
<heat>
but insanely ambitious
<nikolar>
which idea
<Ermine>
wsl1 is half-assed because they abandoned it basically
<Ermine>
so bunch of stuff doesn't work
<nikolar>
a bunch of stuff doesn't work on wine either
<heat>
nikolar: pico processes
<nikolar>
not sure what you're referring to
<Ermine>
much more stuff work on wine and wine is maintained
<Ermine>
works*
<heat>
> WSL's initial design (WSL 1) leveraged the NT kernel executive to serve Linux programs as special, isolated minimal processes (known as "pico processes") attached to kernel mode "pico providers" as dedicated system call and exception handlers distinct from that of a vanilla NT process, opting to reutilize existing NT implementations wherever possible
<nikolar>
i don't think they fully abandoned wsl1 but ok
<heat>
there's a whole vid about the internals of this stuff
<nikolar>
that's neat
<heat>
linux on a hypervisor is much less ambitious but much easier to do
<heat>
and even better performance because linux is not windows
<nikolar>
just implement some baloon drivers and fs proxies
<nikolar>
and you're golden
<nikolar>
heat: kek
<heat>
nothing pains me more than to see people doing threadripper benchmarks on windows
<heat>
like building chrome and saying it doesn't scale
<heat>
no, it DOES scale, just not on windows, hope that helps
<nikolar>
WINDOWS CRAPPER CONFIRMED??
<heat>
if you're buying a threadripper PLEASE don't use it on windows
<nikolar>
i'd buy a threadripper
<zid>
re earlier, kvm on wsl2 means nested virt under hyper-v
<nikolar>
even a first gen
* Ermine
plans to buy threadripper to use it on windows
<nikolar>
don't have where to put it though :(
<zid>
and I don't trust hyper-v as far as I can throw it
<heat>
windows is for LAPTOP SCALE CRAPPERS
<Ermine>
(jk)
<nikolar>
zid: i don't trust windows as far as I can throw it