Search results

The funny thing is that it only happens with some disks above 500G, the others convert fine.

I was able to convert the Hyper-V VM to ESXi with vCenter Converted and it booted. The issue is converting it to Proxmox. I will now attempt to convert it from VMware to Proxmox. Regards, Dennis

For weeks I have been trying multiple methods to convert a Hyper-V VM to Proxmox without success. The issue is that in Proxmox, the machine reports: No bootable device. Here's a screenshot of the Hyper-V VM (Windows 2008 R2 Standard) disks: I export both disks and then do: qm importdisk...

No.

Yes it did.

I'm not 100% sure it does.I might have to try again to see if it does. I was able to coonvert the machine by manually creating the disk and using Clonezilla to remotely copy the disk from source. For the benefit of this argument, I will try the process again on a temp VM and post the results...

It errored out again. transferred 792.2 GiB of 800.0 GiB (99.02%) transferred 800.0 GiB of 800.0 GiB (100.00%) transferred 800.0 GiB of 800.0 GiB (100.00%) can't deactivate LV '/dev/IBM-SAS-900G-PROD-07/vm-1018-disk-0': Logical volume IBM-SAS-900G-PROD-07/vm-1018-disk-0 in use...

Ohhh, ok. Process is at 28% right now. I will keep you posted. Thank you, Dennis

Where can I find that log exactly?

Hi Dominic! Here it is: # cat /etc/pve/qemu-server/1018.conf agent: 1 boot: order=ide2;ide0 cores: 2 ide0: IBM-SAS-900G-PROD-07:vm-1018-disk-1,cache=writeback,size=100G ide2: ISOs:iso/virtio-win-0.1.190.iso,media=cdrom machine: pc-i440fx-5.2 memory: 16384 name: MTIPR-SQL net0...

I am converting a Hyper-V virtual machine into Proxmox. I exported the machine and copied the VHDX files (100G & 800G respectively) to a NFS volume in the Proxmox node. Did a: qm importdisk <vmid> FILE.VHDX LVM-STORAGE-VOLUME The first disk (100G) imported successfuly. The other one (800G)...

Hello all: I am trying a fresh install of Proxmox 6.4.1 on an IBM HS23 and the process gets stuck on Waiting or /dev/to be fully populated. I attempted to boot using nomodeset on linux grub and it continues but errors with: Installation aborted - unable to continue error. I tried installing...

Excellent. I already have a cluster connected to three 3TB FC-SAN LUNs. They're configured as LVM on Proxmox. What do you mean exactly that I need to create LVM VG slices for each cluster? Thanks for your help in advance. Dennis

Hello to all: Can I have two different Proxmox Clusters sharing the same FC Luns? Regards, Dennis

That post is from the same date this was, about two days ago. I joined the forums in July. Anyway, I have setup a two node cluster with LVM over FC, everything works great except I don't have snapshot support which is critical for our operation. We use snapshots when updating our different SaaS...

Thanks alexsusilk, I need a bit more info as to what options of storage, vm format, and so on should I use to achieve having snapshots and live migrations. I've been able to set it up using LVM, and I have live migrations but not snapshots. I need experience of others with similar hardware...

Hello LnxBil: I'm currently evaluating Proxmox as a replacement for one of my vSphere 6 clusters. My setup is: IBM Bladecenter H IBM HS22 Blades Qlogic HBA modules Dual FC San Switches IBM DS3525 Dual-controller SAN storage connected via Fibre Channel network Same as you, we have always...

I'm evaluating Proxmox as a replacement for one of our vSphere 6 clusters. Our hardware is: IBM Bladecenter H IBM HS22 Blades Qlogic HBA modules IBM DS3525 Dual-controller SAN storage connected via Fibre Channel network Since I'm new to Proxmox, I would like to know any recommendations from...

Finally solved the issue. The PVE node has a bonded interface and only one of the bond members had access to the VMs VLAN. Load balancing was sending traffic through the NIC that didn't had access to the VLAN causing the packet drop. Everything is good now. Working as expected. Thanks for the...

The second machine worked fine now with the VirtIO network driver. The issue appears to be machine-specific now. Regards, Dennis