Posted by jpluimers on 2018/01/12
This is not what you like when you reboot a VM in Proxmox:
Booting from Hard disk...
Missing operating system

Booting from Hard disk… Missing operating system
This case was a Windows 7 UK Professional x64 SP1 virtual machine.
Luckily the ISO is at https://archive.org/download/en_windows_7_professional_with_sp1_x64_dvd_u_676939_201606/en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso via https://archive.org/details/en_windows_7_professional_with_sp1_x64_dvd_u_676939_201606 (later I found out I had the image in my backup vault as well).
I put that one in /var/lib/vz/template/iso so proxmox will automagically provide it in the local storage of iso images.
Now for some screenshots some based on what I learned at [Archive.is] How to use System Recovery Options for repairing Windows Vista or 7 installations:
Read the rest of this entry »
Posted in Power User, Proxmox, Virtualization, Windows, Windows 7 | Leave a Comment »
Posted by jpluimers on 2016/10/24
Gut feeling indicates I need these someday:
From VHD to Proxmox you need to convert to RAW not IMG:
# qemu-img convert -f vpc -O raw PATH/to/DISK.vhd PATH/to/DISK.raw
–jeroen
Posted in Power User, Proxmox, Virtualization | Leave a Comment »
Posted by jpluimers on 2016/10/21
Not sure why yet, but on a gigabit network between a Windows 2008 R2 Server and a Proxmox KVM machine, WinSCP gets around 10 megabit/second and FileZilla > 30 megabit/second.
Others seem to agree that filezilla faster than winscp.
–jeroen
Posted in Communications Development, Development, Internet protocol suite, Power User, Proxmox, SSH, TCP, Virtualization, VMware, Windows, Windows Server 2008, Windows Server 2008 R2 | 1 Comment »
Posted by jpluimers on 2016/09/20
In the 2009 past, sdelete used the -c parameter to zero wipe clean a hard drive and -z would clean it with a random pattern.
That has changed. Somewhere along the lines, -c and -z has swapped meaning which I didn’t notice.
This resulted in many of my virtual machines image backups were a lot larger than they needed to be.
The reason is that now:
-c does a clean free space with a random DoD conformant pattern (which does not compress well)
-z writes zeros in the free space
Incidently, -c is a lot slower than -z as well.
TL;DR: use this command
sdelete -z C:
Where C: is the drive to zero clean the free space.
–jeroen
Posted in Batch-Files, Development, Fusion, Hyper-V, Power User, Proxmox, Scripting, sdelete, Software Development, SysInternals, View, VirtualBox, Virtualization, VMware, VMware ESXi, VMware Workstation, Windows | Leave a Comment »