Search results

  1. S

    USB Passthrough: identical ID

    See: http://pve.proxmox.com/wiki/USB_physical_port_mapping
  2. S

    KVM vs Hyper-v 2012 Performances

    host: install with default settings, hardware raid 10 4x sas 10k rpm. guest: 2cores/1socket, 2GB ram, 32GB (pve: virtio lvm, hyper-v: default ide). no big gap between pve and ms.
  3. S

    Fencing with ILO question

    Try to manually add ip's / hosts names in /etc/hosts file ...but i'm not sure if this is needed. https://alteeve.ca/w/Configuring_HP_iLO_2_on_EL5
  4. S

    Proxmox Ve 2.3 high load on host

    You can reduce idle CPU usage (and context switches) by disabling "Use Tablet for pointer". http://pve.proxmox.com/wiki/Performance_Tweaks
  5. S

    [Proxmox : Console] Can't access to to console from proxmox

    Try with different web browser. failed: exit code 1
  6. S

    Win 2012 on HP Proliant DL360 G4 results in 'Your PC needs to restart' error message.

    Re: Win 2012 on HP Proliant DL360 G4 results in 'Your PC needs to restart' error mess Ok, i just ran quick test with "No-Execute Memory Protection" Disabled and i get exactly the same error. When No-Execute Memory Protection is Enabled installation finishes without any problems. So i'm not...
  7. S

    Win 2012 on HP Proliant DL360 G4 results in 'Your PC needs to restart' error message.

    Re: Win 2012 on HP Proliant DL360 G4 results in 'Your PC needs to restart' error mess Try to reinstall VM. http://www.wintips.org/how-to-solve-error-0x0000006-when-installing-windows-8/
  8. S

    Win 2012 on HP Proliant DL360 G4 results in 'Your PC needs to restart' error message.

    Re: Win 2012 on HP Proliant DL360 G4 results in 'Your PC needs to restart' error mess I have this on G5 (BIOS P56 07/10/2009): System Options → Power Regulator for ProLiant → HP Static High Performance Mode ... Advanced Options → MPS Table Mode → Full Table APIC → ROM Selection...
  9. S

    kvm guest won't shutdown

    Run sudo apt-get install acpid inside VM.
  10. S

    Proxmox virtualized Pfsense with one public IP

    pfsense needs to hold both bridges: vmbr0 & vmbr1. I would leave the default vmbr0 as it is and use vmbr1 for WAN.
  11. S

    PVE 2.3 Backup in Snapshot Mode starts an stopped VM

    What happens if you choose RAW as disk format and not qcow2?
  12. S

    Proxmox Security Setup for SSH

    I guess you could solve this problem by binding the services to specific IP...and use of IPsec VPN tunnel between you and PVE host would solve a lot of security issues.
  13. S

    2.3 Installation on a DELL server with existing Windows Server 2008

    Did you try with Microsoft Diagnostics and Recovery Toolset?
  14. S

    PVE 2.3 - help on understanding the memory usage and CPU/core usage

    1GB RAM is ok for testing. I would suggest at least 4GB or more RAM. See this document for more information (Best practices for KVM): http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaat/liaatbestpractices_pdf.pdf It's more effective when the VM's are the same.
  15. S

    Firewall advice

    auto vmbr1 iface vmbr1 inet static bridge_ports eth1 bridge_stp off bridge_fd 0 auto vmbr1 iface vmbr1 inet static # address 192.168.0.254 # netmask 255.255.255.0 #network 192.168.0.0 #broadcast 192.168.0.255 #gateway 192.168.0.1...
  16. S

    Sas hdd's issue

    Is RAID controller with or without BBU (battery)? Can you run test with pveperf and post output here?
  17. S

    proxmox 2.3 Windows 2012 not booting reliably

    AFAIK you'll need to install ssh server on windows machine in to get access from cli: http://www.windowsnetworking.com/articles-tutorials/windows-server-2008/install-SSH-Server-Windows-Server-2008.html See also: http://pve.proxmox.com/wiki/Performance_Tweaks
  18. S

    [Firmware Bug]: The BIOS Has Corrupted Hw-PMU Resources

    Strange, in my case this message appears (after few minutes): edit: i was using corrupted CD image that is why installation failed.
  19. S

    [Firmware Bug]: The BIOS Has Corrupted Hw-PMU Resources

    Same here on DL380 G5. However the installer won't start when using latest iso (2.3). You have to use 2.2 ISO and then upgrade it to the latest version.