Search results

Virtual Balloon device. To disable this device add to VM.conf file: balloon: 0 More here: http://forum.proxmox.com/threads/13174-proxmox-2-3-win2003-server-vm-cannot-be-started-BSOD-caused-by-virtio-balloon-pci

Probably you are using two gateways and if you trace-route 192.168.1.x it will try to find this IP through router/gateway 10.18.66.1. So i guess you need to add permanent route and remove gateway setting from second NIC: route add -p destination mask subnetmask gateway

http://forum.proxmox.com/threads/9627-Using-unicast-instead-of-multicast-%28for-Proxmox-VE-2-x-Cluster%29

Did you try to create and start VM with a single core?

Or this:

VirtIO Controller driver can be updated. I'm not sure about disk drive driver - i guess is the same for all 2008 versions? edit:install iso that i use (trial version _x86): http://www.microsoft.com/en-us/download/details.aspx?id=8371

You can Start/Stop/Migrate/Shutdown/Reboot/SSH VM by clicking the right button on the mouse.

Post output of pveversion -v. vz.conf is located in /etc/vz/ folder. ls -l /etc/vz/vz.conf

http://forum.proxmox.com/threads/12273-Problem-with-CPU-Units Maybe this will solve your problem?

I guess you can ignore this message. Check this link: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03265132

Sorry, i can't tell you nothing about swatch.

Try this (copy/pasted from man qm):

For example: See : http://pve.proxmox.com/wiki/Quick_installation

See: man qm -usb[n] host=HOSTUSBDEVICE Configure an USB device (n is 0 to 4). This can be used to pass-through usb devices to the guest. HOSTUSBDEVICE syntax is: 'bus-port' (decimal numbers) or...

I'm using ossec for those kinds of things. example email warning: OSSEC HIDS Notification. 2012 Dec 20 11:22:58 Received From: (PVE-1) 10.16.1.1->/var/log/syslog Rule: 800022 fired (level 5) -> "pve success login" Portion of the log(s): Dec 20 11:22:58 proxmox pvedaemon[445357]...

Try: http://web.archiveorange.com/archive/v/iXUGhHytzr23Cqk2QxxM

I tought you needed vmbr0 for managment and vmbr1 for VMs...:/ This scenario does work somehow, but only in direction vmbr1 -> vmbr0. Maybe ARP related problem because there is IP on vmbr0. If you add new eth3 and vmbr2 without IP i guess you should be ok.

Easy way: 1. Assign additional IP address on your router (or firewall): 10.3.4.1/24. 2. Connect eth1/vmbr1 to router (or firewall). 3. Boot VM and set the IP address: 10.3.4.100 and gateway 10.3.4.1 4. Enable port forwarding on your router (or firewall) for IP 10.3.4.100

Is this what you're looking for?

Can you post VM config?