this post was submitted on 11 Jul 2023
4 points (100.0% liked)

chat

234 readers
4 users here now

founded 1 year ago
MODERATORS
 

Soo.. Apologies if this is in the wrong place. Still new and unfamiliar to Lemmy. ๐Ÿ˜Š I could not find a specific vm community, so chat is hopefully ok? Posting this with Jerboa on iusearchlinux.fyi (hopefully?)

I have an issue with booting a windows vm from a physical drive and I hope this community might be able to help.

I run arch on my desktop where I have 2 nvme drives. One with Linux and the other with win10. This us the first time I am using systemd-boot for dual boot setup. I normally use grub but this I went with systemd. Possibly a mistake...

I have used these drives and the win10 install with several Linux installs over the years on this motherboard. Both as a dual boot, but also for vfio virtual machine. This works like a charm. But not this time... Dual boot works great, but the vm boot is not working atm.

I normally pass the entire windows drive to qemu, pass the spare Nvidia card and if we go. Usually controlled with looking-glass. It's sweet and work like a charm.

But for some reason I cannot boot the windows drive like this anymore. I suspect systemd-boot does something but I am not familiar enough to tell for sure.

Anyone with a similar setup with a success story to share? Is this possible with systemd? Or is my best bet to go back to grub?

Cheers all!

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 1 year ago

Yay! Glad to see the issue's solved. You actually reminded me - yeah, Windows and I believe macOS too will just leech off whatever EFI partition it can find. I've had EFI partitions on data drives for whatever reason that they'll just use. Part of why when I'll install an OS on bare metal, I'll disable everything but the drive being used (granted that's probably harder on some motherboards).