Recent content by bohansen

Ended up renaming existing volumes on destination and doing a new replication before migrating. Everything went fine after renaming volumes and rescheduling replication (gui) and then doing migration also from the gui. However, I might have stumbled upon unexpected behaviour when PVE...

Hi, I recently reinstalled to PVE 5.1 and have been using a desktop as backup when doing changes to the server. Migrating between the two has worked flawlessly (2-cluster with zfs), but for some reason the replication decided to send a full image while it already exists on the other side...

Before putting it into any production system I would wait for the proxmox team to update the vzctl release for proxmox. That said you can build the debian package yourself by following this guide: https://git.proxmox.com/?p=pve-common.git;a=blob_plain;f=README.dev;hb=HEAD When you get to step 3...

It's not necessary to install upstart. There's a fix in vzctl 3.2 which is easily backported to current proxmox vzctl. See https://bugzilla.proxmox.com/show_bug.cgi?id=210

Seems like DRBD ressources are started later than qemu-server. Try changing the startup order. E.g. like this moving drbd to startup order 23 (qemu-server is 24 here): update-rc.d -f drbd remove update-rc.d drbd start 23 2 3 4 5 . stop 08 0 1 6 . Best regards, Bo

1. Yes, provided you use shared storage you only need to make sure you rsync configuration files to a backup directory on the other server. So a little manual work is needed in case of hw breakdown on the primary node. However normal maintenance you should be able to live migrate most machines...

Fine, thanks - just wanted to mention it ;-)

Hi, We had a breakdown of a server last friday due to a missing NFS share for backup. It's a rather big logfile, but it seems the lost connection to an NFS server has something to do with it. I noticed this is similar to this thread...

Current proxmox 1.7 allows creation of OpenVZs with ID's less than 100. When running vzdump on a VM created with ID 15 I get the following error: "ERROR: got reserved VM ID 15". Best regards, Bo

Output from route -n: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.16.32.0 0.0.0.0 255.255.255.0 U 0 0 0 eth7 172.16.31.0 0.0.0.0 255.255.255.0 U 0 0 0 eth6 192.168.0.0...

Nice spotted :), but unfortunately just a copy/paste error :(

Hi, I have a bunch of NICs in my server and want to distribute the VMs to different NICs. However all the VMs are on the same subnet and it seems to give me some trouble when routing. The general subnet is 255.255.224.0. If I add a machine to vmbr1 with e.g. 192.168.31.230 I am not able to ping...