Search results

yes, that's expected, as I wrote the script for my environment. Would be nice to automate the change, how can I know the storage path in use ? Should I read the value somewhere ?

Next step (atm I don't have time): add named arguments like `--uuid` `--host` and so on and not rely on arguments position

Try the v2 branch: https://github.com/guestisp/xen-to-pve Tested for about 4 VM transfers on my local server, all perfect. But I did some changes when publishing on github (just to remove hardcoded user/pass and so on) so please try it on a sandbox. Keep in mind that this will WRITE directly...

I did a (much) better version if you would like to try. It doesn't have to extract nothing, it dumps the full VM to the ZFS pool on PVE.

But one of the biggest issue is how to "merge" multiple disks in a bigger one. Some of my old VMs are made of 7-8 "small" 20-25GB disks, I would like to move on PVE with just one bigger disks, if possible

It' s a standard ZFS install made with the proxmox installer. I don't think it's thin provisoned by default

Ciao, this is the situation: multiple VMs migrated from XenServer to PVE, each one with their original disks (i've done an automated migration script that will move virtual disks from XS to PVE). Almost all of these server has multiple disks connected with A LOT of wasted space. In example...

O_o solved by removing "console=tty0 console=ttyS0,115200" from /etc/defaul/grub

I have some log made by iptables on one interface and i can see iptables loggin properly on console, but the boot process is still frozen

Hi. after a proxmox hard crash (still I don't know why) , all VMs are up and running properly except one (debian, like all others). Boot process is stuck at this: i've reboot the VM with a debian rescue disk, mounted everything, run fsck on everything and no errors were found. Also, from the...

reading an ovf file is much easier than the xva file. Do you know if i can export the VM metadata as OVF file ?

no help ?

Sorry for the OT but I don't know where to ask. I have to move a bounch of VMs from XenServer to Proxmox, to do so automatically with a script made by me, I need to know the exact disks lists and sizes attached to the XS server, via http call. Reading the OVA.xml file (i can export the VM...

Yes, I have another debian 5 VM , moved right now, in the same exact way, after installing linux-image-686-bigmem. Worked flawlessly at the first time

In every (linux) server I migrate from XenServer to PVE, i'll add virtio_blk and virtio_pci to initramfs and I'm using Virtio SCSI controller. For a very, very, very, very, very, very old server, (top performance is not a requirement) i have to migrate in the easiest way, so, if possible, to...

Worked with standard 686 kernel

Anyway, i'm trying with a standard 686 kernel image. let's see... maybe the xen kernel on lenny is not compatbile

Already done. (the kernel is compatible). As wrote, i did this procedure hundreds of time. This is the only one that doesn't work

I could try, but grub is already loaded and working. What's not working is the kernel. Grub is unable to load the kernel, but is able too see it ("ls" from grub rescue console, show all files)

agent: 1 boot: cdn bootdisk: virtio0 cores: 1 ide2: none,media=cdrom memory: 512 name: xxxxxxxxxxxxxxxxxxxx net0: virtio=0E:B1:42:0B:E9:A8,bridge=vmbr0,firewall=1 net1: virtio=0E:18:AB:4C:65:0D,bridge=vmbr1 numa: 0 ostype: l26 scsihw: virtio-scsi-pci serial0: socket smbios1...