Greg Treantos

I have a Proxmox server setup with a quad port Intel i350 adapter where I have two ports using sr-iov, each port has 7 ViFs. I usually P2V my work laptop and run the image as a guest on a hypervisor, which is currently Proxmox. What I found is Clonezilla 2.7 -> 3.0 does not like going through a ViF. When I clone it is very slow. I decided to run iperf3 on Clonezilla and it proves this out. Throughput is in the k range over a 1gb lan. When I boot the Windows 10 guest I cloned using the ViF inter I...

It turned out I had Pi console configured. I had to remove console=serial0,115200 console=tty1 from cmdline.txt and that fixed all my issues with minicom and screen.. I also disabled bluetooth in the pi which can conflict with my setup. Thanks for the reply. On Tue, Mar 9, 2021 at 9:26 AM Steven Shiau steven_shiau@users.sourceforge.net wrote: Maybe it's easier to use screen for this purpose, instead of minicom. E.g., sudo screen /dev/ttyUSB0 115200 Ref: https://wiki.archlinux.org/index.php/working_with_the_serial_console#Screen...

I would like to setup a Pi Zero W serial connection on a system to run Clonezilla. I have the boot parms setup and it works in putty but minicom fails to render. While I know this isn't a Clonezilla issue per se I was wondering if anyone has thoughts on getting minicom to render properly. Nothing I have searched for seems to work. I also tried screen which also fails.

Never mind. It turned out I had to select the right partition in the bios after clonning....

I tried to do a disk to disk clone of a freeBSD 10.3 system and it failed. Should...