Recent content by rgproxmox1

Thanks. I ended up installing a PMX 3.X server given your comments. Local VMs on a cluster node: - we use the local ones for DB servers sometimes. Better performance with the local drive. We also use other VMs that are not local, which allows us to take advantage of the cluster features.

Hi, I have a cluster running 3.4-6 with 3 members and I want to add a new member but that member is running 4.4-18. Can that be done? Will I be able to migrate VMs back and forth? (Maybe at first it would be OK if I can't migrate VMs). Can I keep the VM that I have created in the 4.4-18 server...

didn't want to do it, but I ended up having to do a physical reset of the host. reboot and "reboot -f" didn't do anything and I waited for about 15 mins.

by the way, the reason we're trying to kill that task is because the start process doesn't seem to be doing anything. VM still shows as "stopped" and even when I do a "qm list" it shows as "stopped".

I just upgraded to kernel 3.10.0-12-pve and have the latest set of updates in my Proxmox host. There's a VM that we tried to start and the "Start" task seems to be stuck: root 15338 1 0 08:50 ? 00:00:00 task UPID:allen-pmx3:00003BEA:0060E695:561BBABF:qmstart:104:<user_id>...

I found out that there have been 0x3b crashes in non-imported VMs (that is, VMs that were created from scratch in Proxmox). Management is putting a lot of pressure to get this fixed. Changing to SPICE drivers, the VGA adapter to standard, applying all the windows updates doesn't seem to make a...

After the host was reset, I went to the /var/logs directory and there's nothing there, but the boot messages (it stopped logging things at 3am of the day of the failure, when I'm going to assume the failure took place). The only messages are the boot messages when the host was rebooting after it...

I updated a cluster to the latest release (official, we have a license for PMX) and things have been running smoothly until one of the 3 hosts became unresponsive: SSH, Web and even console never come back - for SSH and console it asks for the login and it never comes back after that. I have...

Marco, Thanks again for taking the time to check things. Unfortunately, I've tried different things with most of those settings, EXCEPT the video driver. - memory. I've had machines with 4GB also crash - scsihw: machines were crashing with the default one (LSI 53C895A) - net0: e1000 with the...

Thanks for the info, Marco. That is interesting. Our configurations look very different. I hardly touch the .conf file itself and I let Proxmox enter the values. I don't know what the different values would be, as far as impact, but mine is: boot: cdn bootdisk: virtio0 cores: 1 ide1...

What is the recommended video driver configuration for W2003 VMs? How do people set up their VMs in that sense and have luck with them? That's one of the areas that keep showing up when Googling that error code. I've tried switching to different of the "standard VGA" types with no luck.

We just had today (that I've noticed) the first crash with the code 0x3b of a Windows Server 2003 that was not ported over from another Hypervisor. We're getting really frustrated here. We can't have production servers crashing like this! We applied all the recommended practices for W2003 that...

we've always used either: "shutdown -t 0 -r", or "shutdown -t 0 -s", which works for every non-Proxmox server. I've tried even the "/" version of them: "shutdown /t 0 /r" and same result. I know that all the VMs where it happens are Proxmox VMs that were installed from scratch and haven't seen...

I have several Windows 2003 servers that have been created from scratch (as opposed to other issues I'm having with VMs converted from Hyper-V) that have the same issue: When you try to shutdown / restart the VM from the command line, I get: "The computer is processing another action and thus...

We have a few Windows 2003 VMs that were ported over from Hyper-V and they keep crashing every once in a while with a code of 0x3b. We removed the Hyper-V guest tools software and disabled all the Hyper-V services that were not removed as part of the previous step. Yet, the crashes keep...