Search results

  1. J

    Windoze 2008 R2 SP1 Bluescreen on Install (-cpu host)

    Hello, While attempting to install windoze 2k8r2 it bluescreens right after the 'loading windoze' part. I have tracked the error down to using '-cpu host'. It seems to function while using qemu64. The stop message is something like "STOP 0x000007A" Anyone seen this/figured a way around it...
  2. J

    Proxmox 2.0 with One-Time-Passwords?

    Hello, Been experimenting with some OTP solutions (pam-oath, pam-obc). Anyone used/experimented with them on the Proxmox web gui? I'm thinking pam-obc would be the better course of action. It delivers it out-of-band via email, sms, aim, etc, whatever. Modifying proxmox wouldn't be necessary...
  3. J

    Upgraded, storage not showing for backup

    Hi, I had an issue with users not being able to change passwords, I installed the update and now they can. Only problem is, we cant see the storage for backups. I added a test storage, backups only, group permission, made sure user permissions are correct (PVEVMUser), set it shared. Still...
  4. J

    users cant change own passwords

    hello, i was doing some testing and a customer notified me they were unable to change their own password, which is strange because i manually tested it and it worked before, it doesnt now. the error thats thrown is "Permission check failed (/access/realm/pve, Realm.AllocateUser) (403)" Im...
  5. J

    Tab in VNC console

    Hi,Im using 2.0 and I cant seem to get Tab to work in the console. It just activates the menu bar and the SendKey option does not have tab.Any workarounds/fixes?
  6. J

    Upgrade 1.9->2.0 -- already running Debian 6

    Hello,We run Proxmox 1.9 on Debian 6 and i'd desperately love to try v2.0 (been waiting for it to come out of beta for a while) However, we already run Debian 6 on the server. Would it cause a cataclysmic failure to run the upgrade script as it is? Normal logic would predict that it would...