Search results

Another note, when you install the service, don't install from the cd. Copy from the cd to your vm, then install. When you install the service it will link/install from the directory its located in. So if you install from the cd, remove the cd, then the service will not start. There may be a...

Sorry, I hijacked this tread. Was just brainstorming. It would seem that if you configured the VM with fixed memory it would disable it anyway, but it does not.

been messing with this, drivers (inf) appear to have windows 2000 info... still not able to deal with the balloon service. This machine has been running but trendco post has me looking at it again...

Well I have an old 2000 still running too. Taking a look. I see the VirIO Balloon devices, but no drivers. So they they are not working, yellow !, but I did not add any special config as you have stated. To be honest, if I noticed it was when I imaged the machine from physical to vm. And...

So here I am, 3 weeks out and crash.

Just curious, nic/bond config on storage interfaces? I have pretty much the same hardware and issue and have been free of it now for 2 weeks, I disabled LACP on the bonded nics to my SAN. Nothing in my logs yet, just checked. But I don't consider this fixed yet as it has at times plagued me...

My logic was heading for LACP and bonding on the storage interfaces (with some iscsi in the mix). FYI. Have been dealing with this quite randomly on 4 different servers. Thats why I asked about the nic/bonding. I have since config my storage net with no LACP. Some research indicated this did...

Guess that throws out my theory, at least for the time being.. Good luck

Just curious, any bonded interfaces? If so bond type and switch?

Re: Host don´t boot afer setting autostart-option in guest I have a 4 nodes in a cluster and have seen this when quorum is not successful Wed Jan 14 08:12:36 2015: Waiting for quorum... [ OK ] bootlog might be of some help.

Using chrome as well, I get this in the logs when it happens.. pveproxy[425359]: connect to '127.0.0.1:5900' failed: Connection refused at /usr/share/perl5/PVE/HTTPServer.pm line 415

No one has replied yet? I got the book, lot of good stuff here. Found it well worth $$. I have worked aound Prox for a 2-3 years and have worked IT in some form longer than I will say or remember? Its not just about HA as it title suggest, but covers some of the requirements and steps to...

Keep in mind as well that a VM might have to be completely shutdown (stopped) to see any changes made in the proxmox gui.. not just a simple VM reboot..

Just something to check... at the time (not sure it has changed) it would let you enable HA while the VM was running.. Which I later found out it not the right way...In my case I would start the VM thinking it was down and start getting warnings about the disk within them being corrupted. Kind...

Has HA been configured and enabled anywhere in this cluster? Reason I ask is I got stung once by enabling HA on running VMs, and it was kinda the way you describe. I showed the machines down but they were still running somewhat invisible to the GUI...

Not a fault or bug but just something to look for... ( at least I don't think so.. maybe info indicating why the failure in someway?) I had a VM migration that kept saying it was failing because of a missing iso for the cdrom.. GUI indicated that no iso or hardware was to be used.. argh...

I too have seen this over the past few months. But I'm thinking maybe the nodes are out of time sync. I only say this because I had a similar issue with my san cluster of 8 nodes that were all synced to an external time server. Time would get off and nodes would fall offline (giving some type...

Notice this as well over the past couple of days... but then way beyond that I have had issues with data between nodes being synced and going into panic during ssh communications between them. I'm just wondering if the cause might be openssh and openssl, since ours appear to be somewhat...

The VM conf file might have the info, maybe the VM disk is on a local share and not a network share. That would contain the path where the disk image is. done that by accident when in a hurry.

I have ran into migration issues whenever there was a backup or snapshot attached to the VM.. Some VM would migrate other not.. various errors ,this is what I found in my case. Once removed it migrated ok.. YMMV