I haven't thought about ISDN in ages. IIRC I had to get a serial expansion card with a faster UART to get the benefit, which was...eh, dubious. Twice nothing is still nothing LMAO.
First word: Oh
Second word: no
Third word: not
Fourth word: again
Actually I've had a pretty good day. Woke up early, made a mocha latte, got caught up for work, and now I've spent all afternoon getting high and playing video games.
Went camping with some friends. We were all underage. Guy at the 7-11 sold us wine coolers. I vividly remember dude saying "You men have a good evening." 😆
Experience was...ok? Drank just enough to get a slight buzz.
Forgot to include the boot/system volume. It's a lovely time waster when you're dealing with disk images that are hundreds of gigabytes in size that have to be copied over the network. 😆
I'll add Disk2hvd screenshots when I get a sec.
Situation gets slightly more complicated if you had multiple drives in your system when you installed Windows, of course. Installer might put system volume on a different drive, so you'd have to image more than one drive to get a working system. Might get a little confusing as to which volumes should go in which image. There's a tool called GWMI that might help with that since afaik the volume guids don't show up in the Windows Disk Management snap-in.
Edit: The promised screenshot. In my case, I knew the volume labelled SYSTEM resided on the same disk as my C: drive. Probably don't have to include the recovery partition, strictly speaking, but I did.
Well before today, I'd never heard of virtio-win, and I'd never used KVM/QEMU for virtualization on Linux, and despite an error on my part I had a running VM by close of business. Thanks for stopping by.
Good idea. Weirdly no errors in /var/log/libvirt/qemu/
<box>
.log or in journalctl for libvirtd. Maybe devs can advise on other places to look.