Search results

What is the reason you can't just use the kvm64 CPU?

I don't know your network configuration, but I've done this using a bridged network interface in the CT so it appears to the network like any other computer (and I set it with a static address too.) This skips anything the host might otherwise be doing to the network traffic.

Can you post the BSOD details? What CPU type do you have set for the VM? Have you tried different ones?

Hello. I'm installing Proxmox 3.1 (per the Wiki) and will update to pve-no-subscription later since this is for an open source project build system. I've done this a few times before on other systems with no problem, but this time, initial certificate generation is failing during configuration...

MS SQL databases also get corrupted! I have also discovered that the 2.6.32-37-pve kernel on the host causes databases in MS SQL running in Windows 2008 VMs to become corrupt no matter what the caching settings are. Reverting to 2.6.32-34-pve (and reinstalling the SQL databases) resolves the...

I tried reverting to the 2.6.32-34-pve kernel and that doesn't seem to have the problem. So what regressed in the new kernel?

Hello. Since installing the following updates on multiple of my ProxMox machines, all of my Debian OpenVZ containers running Web servers (Apache 2.2.22 + PHP5-FPM) now take between 3-7 seconds to respond when clients request pages that use PHP sessions. I normally just use file session storage...

The problem disappeared for me after one of the Proxmox updates awhile ago.

Hello again. Okay, it looks like using RAW format on the system drives has fixed all of my problems. (Some of my VMs continue to run fine with qcow2 system drives though. Until I upgraded the kernel, then they too were affected. Changing their system drives to RAW has fixed the problem there as...

That's what I'm trying now, on the system drive. (A machine that has been running fine with VirtIO everything just started acting up now too with the latest kernel.)

Sorry for the delay everyone. Thanks for your patience. This is the one that still occasionally freezes (about every two days): boot: cdn bootdisk: ide0 cores: 1 ide0: vms2-drbd:143/vm-143-disk-1.qcow2,format=qcow2,size=22G ide2: none,media=cdrom memory: 2048 name: FileData1 net0...

Okay people. The VM in question has had IDE disk, e1000 NIC and LSI controller for the past two days and it STILL hung just a half hour ago! Again, nothing is logged in Windows' system log. What do you suggest at this point?

And now one VM on the host running the previous kernel also just hung! It is using IDE disks but VirtIO NIC and has been fine for 5 days. WHAT. THE. HELL?! How can I roll back the qemu package? I've had about enough of this.

This same VM (running on the latest 2.6 PVE kernel) hung AGAIN using no VirtIO anything! (The Baloon driver still loads (so I can see the actual memory usage) but the VM is set to a fixed size.)

Seems like Christophe and I are seeing the exact same problem. Another data point: my one problem VM on the host running the latest 2.3.32-33-pve kernel just hung while using IDE disks. It was using VirtIO NIC which I am now going to change and see if it helps.)

Thank you very much for this additional information, Christophe! If the problem is with the storage driver, I would expect we can still use VirtIO for the NIC. I wonder if using a SCSI vdisk is any better performance than the IDE one? Good find, Mir. Is there a way to disable PCI...

So even on the host running the slightly older kernel, I just had two of the same VMs block. (One let me try to log in but got stuck at "Waiting for User Profile Service" remotely and "Welcome" on the console. Still had to Stop the VM.) I just switched the disks to IDE and the storage...

And this was the problem: I booted one of my hosts on the 'Linux ClientVMs2 2.6.32-32-pve #1 SMP Thu Aug 21 08:50:19 CEST 2014 x86_64 GNU/Linux' kernel and the problem goes away, regardless of VM hardware settings. The VM I moved to the other host that is running the latest...

Okay, I'll try that tonight, but it won't be easy because Windows has a fit when you change the boot device. (And will make me reconfigure the NIC.) Host RAM: 32GB # VMs: 3 on each right now, one also has a VZ container. Only three of the 6 VMs are exhibiting the problem and it doesn't matter...

It was just a port naming issue. The port trunks are correct, so that's not it.