Search results

I'd like to see that too - while I do actually have it working on 1.9, it seems many people want to know how to do this. That said, I think this topic would be best left until 2.0 is actually released ;) I actually was going to say the same thing. Running a "normalize" on the audio might help...

There will be. It's mentioned in a few places. If it was me making the decision, I'd be going with 1.9 and waiting for 2.0 to be ready.

OK. Fair enough. I guess I'll set up the external drive for Proxmox snapshots for now and start on convincing them to buy the NAS :p

Long story short - a client is now running Proxmox with a Win2K8 guest. They need to run Windows backup on this, and would like to use multiple USB hard disks in rotation. What is the current best method to get the USB disks to show in Windows in such a way that they can plug and unplug them...

The filename doesn't matter at all. All the files in modprobe.d are loaded one by one and treated as if they were in modprobe.conf. I usually name the file with something that makes it stand out that I created it. That way I can spot ones I made easily, and also avoid the chance of it being...

I ended up doing what it said and passing the "allow_unsafe_assigned_interrupts=1" option to the kvm module (create a new file in /etc/modprobe.d/ and add "options kvm allow_unsafe_assigned_interrupts=1" to it. I've had no issues with it at all since doing that with 2.6.32-6. The VM has been...

I've got "amd_iommu=on iommu=pt iommu=1", but now getting a message telling me I need to "allow_unsafe_assigned_interrupts=1" in the kvm module options... Does anyone know exactly what that option does? The vague info I found suggests it's to stop malicious acts on guests reaching the host, but...

Well, to be honest, I'm not sure. I just know when I boot the newer kernel, I get no IOMMU (or AMD-Vi) info in the kernel output, and the VM using it won't start. I'm on an AMD system if that helps - maybe it's there for Intel but not AMD. I haven't had time to look at the kernel configs to try...

I'm running 2.6.32-4-pve. I tried 2.6.32-6-pve, but it doesn't seem to have the IOMMU support required for the passthrough. I'm pretty sure the PCI Stub stuff I mentioned is required. I made a script and stuck it at /etc/rc2.d/S19dahdi-card-to-pci-stub Having it in there makes it boot up and...

It's currently working fine as far as I can tell, aside from still causing that CPU lockup issue on the host when shutting down the guest. However, this seems to only be happening some of the time. Haven't had the time or guts to fully work out what triggers it, but I THINK it might only be...

Oh cool - and it's a long weekend this weekend here... ;) I shall be finding a spare machine to do some testing on too...

Just tried the 2.6.32-6-pve that pvetest seems to have put on - didn't even want to boot up properly. Got a kernel error of some sort (couldn't see - ran off the page and froze up). I'm suspecting the "netjet" ISDN module may be involved - this doesn't load on the -4 kernel, but does on the -6...

I'm using 2.6.32-4-pve Do you know whether the passthrough works significantly better in the newer kernel?

Ah - I did look in the syslog section. Didn't think to look in the tasks log. Good to know you plan to improve things in that regard though... It's not the best feeling when something doesn't work and you don't even know where to start. :-)

If an ISO image is deleted but a KVM machine still refers to it, the KVM machine will refuse to start with no errors reported. To reproduce: Create KVM refering to ISO image (don't start VM) Delete ISO Attempt to start KVM guest I had this just happen with a fairly important KVM guest. It was...

Chipset, CPU and BIOS all have to support hardware I/O virtualization. "Intel VT-d" is what to look for in Intel stuff. AMD call it "AMD-vi" and also sometimes "AMD I/O virtualisation". The generic name is IOMMU. Watch out when buying if you're getting consumer desktop grade gear - there's...

I just attempted to reboot the VM again, only this time after running "device_del mydevice".... Same result. The kernel on the host is spewing out the following (CPU involved changes though), if it means anything to anyone: Sep 10 11:37:10 kernel BUG: soft lockup - CPU#7 stuck for...

Oh dear... Yes... My brain fails maths... How embarrassing :P Lucky my job doesn't involve schedules...

Wow - 5 days into Q3 and people already want it. Settle down people.... The quarter goes for another 2 months and 25ish days. :p\ I want it too - mostly for the ACL stuff - but when it's done, not when it's rushed out the door full of bugs like a certain large OS vendor likes to do.

OK, I think I have it working now... For both my own reference and anyone else who comes across this, here's what I've done. First, I enabled "DMA Virtualisation" in the BIOS. This seems to be what Dell have labelled IOMMU. Next, as documented in this page, I ran (though with the corrected PCI...