I've just spent 4 days figuring out why there is no transfer of data on hetzener vswitch between multiple proxmox machines...
The problem was mtu.. which has to be set on the actual interface and not the bridge. Now the problem remaining is that the Proxmox doesn't set the mtu of the LXC...
I don't know why, but after the upgrade from beta to stable I have weird time jumps on my server and also the CPU usage and server load graphs don't show anything. their start and end time are both showing 1970-01-01 01:00:00. also If I by any chance manage to login into the UI, then after the...
I'm trying to build a network between different machines connected to Hetzner vswitch but I'd like to have two things. I know how to do this with two network interfaces inside a LXC, but I'd really like to only have one.
* network traffic of all LXCs on server X must be NATted out via the...
This did help however I'm finding this to be a regression since this worked just fine with proxmox 4.4 and LXC 2.0
Also this is annoying especially if you connect directly to the proxmox and then each of the hosts individually to do some maintenance.
I've updated (well created a new one and restored container from backup) one machine to 5.2 from 4.4 and it seems that with new lxc the mc is not working properly.
Steps to reproduce:
Install ubuntu 16.04 as a container
now connect to the host proxmox machine with putty
This one is happening to us also and only on some machines. I've updated the quemu agent and there is no change.
The mos annying thig with that is. that this is going on for an hour.. Can proxmox catch this and cancel the backup of that particular VM and then retires at the end, or it tries it...
This is the same problem I reported after the 4.2 was announced (in anouncment thread). However I'm using Windows.
P.S. The only message in console is "unreachable code after return statement[Learn More]ext-all.js:22:344134"
I've just updated to Px 4.2 an it seems that this version doesn't work in firefox 46, I've issued a forced refresh and also tried incognito mode but to no avail. It seems that the clicks as not registered
We were using .24 for the past 18 months and with .32 crashing I went back to it and .24 is working just fine with 1.8.
We have a development environment built with standard PC components: Phenom 2 x6 and Proxmox 1.8 with .32 kernel are working without a hitch.
But somewhat .32 doesn't like HP...
This is the other part as the forum didn't like the length of a post.
This is the one I got after I decided it's best to restart and boot back to .24 kernel:
Apr 23 00:42:10 master kernel: BUG: unable to handle kernel paging request at 00000000dead111c
Apr 23 00:42:10 master kernel: IP...
I tried to upgrade our server from 1.5 and .24 kernel to 1.8 and .32 kernel.
The proxmox upgrade went well but we are having a problem with .32 kernel.
The 1st crash is in vzwdog module:
Apr 23 00:30:00 master kernel: disk_io: 104 0 cciss/c0d0 1877 409 56530 8272 111 126 1896 192 0 6088...