<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div dir="auto">Kinda orthogonal to the original problem, but if you want to run KVM VMs on a remote headless machine, I quite strongly recommend using a canned system for doing that such as ProxmoxVE (PVE) or similar, and not relying on the traditional libvirt
CLI tooling. If you don't like PVE, there are quite a few other projects that accomplish much the same ends.</div>
<div dir="auto">-Adam</div>
<div style=""><br>
</div>
<div dir="auto" style="" id="ms-outlook-mobile-signature">Get <a href="https://aka.ms/AAb9ysg">
Outlook for Android</a></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Roundtable <roundtable-bounces@muug.ca> on behalf of Scott Toderash <scott@100percenthelpdesk.com><br>
<b>Sent:</b> Sunday, February 5, 2023 6:44:17 AM<br>
<b>To:</b> Continuation of Round Table discussion <roundtable@muug.ca><br>
<b>Subject:</b> Re: [RndTbl] libvirt, vmware, and Windows 2000</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">I had done steps very similar to yours.<br>
<br>
qemu-img convert -O raw S1\ -\ Production-0.vmdk <br>
/dev/vg_vmhost9/kvm140_img<br>
<br>
virt-install --name kvm140 --memory 4096 --vcpus 2 --disk <br>
/dev/vg_vmhost9/kvm140_img,bus=ide --import --network default <br>
--os-variant win2k<br>
<br>
Initially I had tried using bus=sata and that was not bootable. IDE made <br>
the C: accessible but I wonder if I need more parameters to map out the <br>
other drives.<br>
<br>
The virt-install was helpful to help me generate a decent XML file and <br>
then I tweaked it a bit from there.<br>
<br>
On first boot it went through the old "Windows found new hardware" <br>
thing, which I had completely forgot about. It couldn't find any drivers <br>
of course, so oh well. It's possible that without having installed <br>
virtio drivers before I got my snapshot it isn't going to work but I"m <br>
not sure about that.<br>
<br>
Then I thought I should be able to fire up vmware player and boot the <br>
vmdk image. Then I discovered that running player on a remote headless <br>
machine is a real hassle. It seems possible but I haven't actually got <br>
it working yet.<br>
<br>
<br>
<br>
<br>
On 2023-02-04 11:36, Chris Audet wrote:<br>
> @Scott Haven't worked much with Win 2000, thankfully.<br>
> <br>
> Tried to reproduce your problem in my lab by installing Win 2000<br>
> Professional on ESXI, adding a bunch of virtual HDDs using FAT or NTFS<br>
> with basic or dynamic disks (trying to see if some combination caused<br>
> it to fail), downloading the VMDK files, converting to qcow2, and<br>
> importing into Proxmox.<br>
> <br>
> However wasn't able to make it past the converting VMDK to qcow2 step.<br>
> I must've messed up somewhere because after importing the disks into<br>
> Proxmox I just get a Windows "boot drive inaccessible" error.<br>
> <br>
> Sadly I didn't take many notes while experimenting with all this, but<br>
> if you end up finding a solution I'd be very curious to learn it.<br>
> <br>
> The only part that stuck out to me while doing this is that when<br>
> initializing new disks on Win 2000 it seemed to default to dynamic<br>
> disks, and was trying to build a software raid by default. I'm not<br>
> sure if this would be a factor with your disk conversion - but I can<br>
> see how if the disks are configured as a raid but "qemu-img convert"<br>
> is handling the disks one at a time it could have strange results.<br>
> <br>
> bash-5.1$ qemu-img convert -p -f vmdk -O qcow2 Chris_Win2000.vmdk<br>
> Chris_Win2000.qcow2<br>
> (100.00/100%)<br>
> bash-5.1$ qemu-img convert -p -f vmdk -O qcow2 Chris_Win2000_1.vmdk<br>
> Chris_Win2000_1.qcow2<br>
> (100.00/100%)<br>
> bash-5.1$ qemu-img convert -p -f vmdk -O qcow2 Chris_Win2000_2.vmdk<br>
> Chris_Win2000_2.qcow2<br>
> (100.00/100%)<br>
> bash-5.1$ qemu-img convert -p -f vmdk -O qcow2 Chris_Win2000_3.vmdk<br>
> Chris_Win2000_3.qcow2<br>
> (100.00/100%)<br>
> root@MGV7091:~# qm importdisk 102 Chris_Win2000.qcow2 local-lvm<br>
> root@MGV7091:~# qm importdisk 102 Chris_Win2000_1.qcow2 local-lvm<br>
> root@MGV7091:~# qm importdisk 102 Chris_Win2000_2.qcow2 local-lvm<br>
> root@MGV7091:~# qm importdisk 102 Chris_Win2000_3.qcow2 local-lvm<br>
> <a href="https://ostechnix.com/import-qcow2-into-proxmox/">https://ostechnix.com/import-qcow2-into-proxmox/</a><br>
> <a href="https://docs.openstack.org/image-guide/convert-images.html">https://docs.openstack.org/image-guide/convert-images.html</a><br>
> <br>
> On Tue, Jan 31, 2023 at 12:47 PM Scott Toderash<br>
> <scott@100percenthelpdesk.com> wrote:<br>
> <br>
>> If the subject line doesn't scare you then maybe you can help me out<br>
>> <br>
>> with this one. Windows 2000 is its own punishment at this point, but<br>
>> <br>
>> it's part of the mission in this case.<br>
>> <br>
>> I have a working Windows 2000 server running on VMWare esxi. I<br>
>> downloaded the image as a vmdk file and attempted to import it into<br>
>> my<br>
>> Linux system as a KVM image. It mostly works.<br>
>> <br>
>> I did this successfully with 2 other machines that were Windows<br>
>> 2012R2<br>
>> from the same source and same destination. Those work.<br>
>> <br>
>> W2k is having issues because it has C: E: and F: but only C: is<br>
>> recognized when I boot it up in the new environment. It shows that<br>
>> E:<br>
>> exists but it believes that it is corrupted.<br>
>> <br>
>> There are probably some parameters that I don't know about that I<br>
>> need<br>
>> to pass in order to make this work.<br>
>> <br>
>> The general process was download the vmdk image, use "qemu-img<br>
>> convert"<br>
>> to make a raw file and then try to boot that. I tried using<br>
>> virt-install<br>
>> and I tried some other manual config methods but this is as far as I<br>
>> <br>
>> have been able to get.<br>
>> <br>
>> Does anyone here have experience with this sort of scenario?<br>
>> <br>
>> _______________________________________________<br>
>> Roundtable mailing list<br>
>> Roundtable@muug.ca<br>
>> <a href="https://muug.ca/mailman/listinfo/roundtable">https://muug.ca/mailman/listinfo/roundtable</a><br>
> _______________________________________________<br>
> Roundtable mailing list<br>
> Roundtable@muug.ca<br>
> <a href="https://muug.ca/mailman/listinfo/roundtable">https://muug.ca/mailman/listinfo/roundtable</a><br>
_______________________________________________<br>
Roundtable mailing list<br>
Roundtable@muug.ca<br>
<a href="https://muug.ca/mailman/listinfo/roundtable">https://muug.ca/mailman/listinfo/roundtable</a><br>
</div>
</span></font></div>
</body>
</html>