0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 11 months agoIt happens 🤷sh.itjust.worksimagemessage-square197fedilinkarrow-up1667arrow-down137
arrow-up1630arrow-down1imageIt happens 🤷sh.itjust.works0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 11 months agomessage-square197fedilink
minus-squarecyanarchy@sh.itjust.workslinkfedilinkEnglisharrow-up7·11 months agoNot on bare metal, for this reason
minus-square0x4E4F@sh.itjust.worksOPlinkfedilinkEnglisharrow-up2·11 months agoNeed for interacting with hardware, so yeah, have it on bare metal, plus in a VM.
minus-squareherrvogel@lemmy.worldlinkfedilinkarrow-up1·11 months agoAny reason you can’t just pass the hardware through to the vm?
minus-square0x4E4F@sh.itjust.worksOPlinkfedilinkEnglisharrow-up1·edit-211 months agoBecause it needs SATA emulation (needs to communicate natively with SATA devices), and that’s still not a thing in KVMs as far as I know.
minus-squareacockworkorange@mander.xyzlinkfedilinkarrow-up2·11 months agoAlways use a condom to interface your bare metal and windows.
Not on bare metal, for this reason
Need for interacting with hardware, so yeah, have it on bare metal, plus in a VM.
Any reason you can’t just pass the hardware through to the vm?
Because it needs SATA emulation (needs to communicate natively with SATA devices), and that’s still not a thing in KVMs as far as I know.
Always use a condom to interface your bare metal and windows.