Agreed. Use case has a LOT do with things. It's unfortunate that so many have come to depend on OpenVZ ... I've been tracking them for years and have always noticed quite a lot of instability in how that teams works. They haven't been and still are not responsive to the needs of their users...
Tom hits the nail on the head here so to speak.
The biggest reason that other corporations have to support for 5 years or more is exactly as he mentions...no clean upgrade path which means it's a migration which means major planning. Being that Proxmox has such an AWESOME track record of...
Yes, I'm experiencing the same thing for one of our nodes. If I go to the GUI of that node there's no problem but when accessing the cluster GUI from another node that's when I see that error exactly as you noted.
I'd love to hear of an answer from someone in the know as well.
Thanks in...
Cool, I get it. Anyway, I'll leave the hosts file alone and leave everything IPv4 until a patch is released to address the migration issue.
Thanks again
Great! I'm glad it's so simple to adjust to work properly .... I'm sure that can be patched within a short time, no?
Also, I noticed for IPv6 to work in the cluster you need to add the proper address entry to the /etc/hosts file as follows
At the end of the IPv6 section put...
I've found that with IPv6 enabled in Proxmox 4.1 I can no longer migrate VMs within the cluster
Jan 27 11:37:51 starting migration of VM 103 to node 'PMX-node-I' (2607:xxxx:xxxx:x::35)
Jan 27 11:37:51 copying disk images
ssh: connect to host 2607 port 22: Invalid argument
rsync: connection...
I found the same thing. We have a four node cluster and 3 out of the 4 machines are upgraded to Proxmox 3.0. I was seeing the same thing, snapshotting was not available on VMs that are in QCOW2 format. I finally realized though that I was looking at the cluster through the one Proxmox 2.3 node...
I should have said this last year, I know. I apologize. Thank you Tom for spending the time to attack this issue and verify that it HAS been fixed as of that kernel version.
Proxmox is an awesome product. Keep up the great work.
I've tried pretty much everything. The only thing I hadn't tried that has been talked about in this forum is changing the kernel to an older kernel. I've changed network card back and forth between virtio and Intel e1000. I've change video card type. I've changed the hard drive between virtio...
This is an update to the problem. I've verified that Word starts fine when the Windows 2003 Server VM is started in safe mode. This clearly indicates a virtual "piece of hardware" that is the offender here. I'm still banging my head against the wall here to figure this out. Any help? Please...
I couldn't find anything similar in the forums for this. We are converting XenServer vms over to Proxmox 2.0. After converting a couple of customers, we got a complaint that they couldn't open MS Word to be able to paste into it. We checked into it and sure enough if you launched MS Word 2003...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.