Search results

I was talking about the "snapshot" link in git.proxmox.com where you can download tarred source package. And how can I tell the correct point for enterprise package x.y-z? "bump" commit seems to be logical choice but I want confirmation on that. Exactly and that is where proxmox staff needs to...

I guess nobody is denying Proxmox is free. Biggest problem here is the new model where people don't know what the new non-enterprise repo is like. People are happily running promox and suddenly, without warning they are forced to make a decision between paying for support or using possibly...

Let's say I have version 3.1-2 running and after 6 months I want to have the source. Do I get snapshot of that "bump" or the version before next version increase commit? Aren't all git snapshots at version 3.1-2 between commits 3.1-2 and 3.1-3 (or 3.2 or whatever the next version is)?

I'd also would like to know how can I get a specific version out of git? Since there are no src packages, checking out from git is the only option. If I buy subscription how can I get source of the exact version of a package? Naturally thats what I want, not a master version which already has...

I'd like to bring up an old issue regarding lvm striping. It's been discussed about in this thread. http://forum.proxmox.com/threads/6981-PVE-LVM-striping-on-iSCSI-storage-%28with-multipath%29 I've been experimenting with drbd a bit and got interesting results. I have two servers with two 1TB...

Don't tell that to my router :) I've been running openvpn with a tap device (actually 3 of them) for few years now. Not exactly Proxmox vm but KVM vm using my own startup script.

Old thread but I haven't seen anything regarding adding CPU and RAM to a pool. IMO it would make sense to prevent certain pool users/admins to use up all RAM and CPU resources on the server. It would be nice to be able to say "You guys have 4 GB RAM and 2 CPU cores. You them anyway you like"...

The page I linked has installation instructions. They are better than what I could come up with :) Maybe proxmox devs could include this in the kernel? Those AR81xx chips seem to be pretty common nowadays.

NIC is not supported by proxmox kernel. You can get the driver here: http://www.linuxfoundation.org/collaborate/workgroups/networking/alx

Right. Actually I'm using 1.1 and it is still there and never had any problems. But apparently there are some issues.

I guess it is regarded as stable. Works for me (TM). I'm talking about simple "migrate -b" monitor command. From "help" monitor command migrate [-d] [-b] [-i] uri -- migrate to URI (using -d to not wait for completion) -b for migration without shared storage with full copy of disk...

Just for the record, KVM itself supports live block migration and it works well. Sure it takes a while to migrate a large disk but IMO it's better than nothing. Then there is also incremental block migration which uses same base image on both nodes and block migrates only the COW image...

What if you want the host to have an IP in the same VLAN?

How about implementing block migration (-b parameter to migration command)?

Try 'blockio --setra 8192 /dev/vda' in the guest. Replace /dev/vda with correct disk of course.

Any chance to get feature like this? I find it quite difficult to track backups with current naming convention after few virtual machines have been created/destroyed. Would it be possible to append vm name to backup name? Notes/comments would be nice also.

Just for the record, I tested live migration on the same hardware using my own script, stock debian 2.6.32 kernel and qemu-kvm-1.0 and have not had s single failed migration. Shared storage, incremental block and full block migration work ok.

Any plans to upgrade qemu-kvm to 1.0?

I would also like to see that the UI would use names to reference virtual machines. Names are easier to remember than numbers. Off the top of my head: 1) All the VM and container lists in the main window. 2) Console window - Now I need to check from the main window which VM this console...

Try '192.168.1.101 mini1' instead of 127.0.1.1 in /etc/hosts