Quantcast
Channel: Proxmox Support Forum
Viewing all 171654 articles
Browse latest View live
↧

Harddisk requirements

September 26, 2014, 6:46 pm
$
0
0
I'm trying to install PVE, but it keeps telling me the "harddisk" (more about that later) is too small. I tried 1GB, then 4GB (reported as 3GB for some reason). And all this *after* asking me for all other information. Why not right away when selecting the volume to install to? Why even *after* building the partition table? Why try installing when you [the installer] knows it's not going to work?

I'm trying to install PVE on a USB stick. I want internal SATA ports to be as available as possible, and I would guess that PVE by itself isn't very big. The download is only a few hundred MB, so I would never expect it to blow up to several GB. So i figured a 4GB USB stick would be plenty. Allthewhile, the requirements at the official website (listing recommended hardware, oddly enough?) doesn't say one word about minimum storage required.

@anyone: what's the actual minimum amount of storage required to install PVE?
@developers: please make the installer a little bit more intelligent about this. It's a bit frustrating, to be perfectly honest.
@webteam: please update the requirements page to show requirements, including everything the software requires. Recommended stuff are not requirements.

Thanks :)
↧
Search

Shellshock bash security update

September 26, 2014, 7:40 pm
$
0
0
Will the recently released bash update from Proxmox close the vulnerability recently found in bash?
↧
↧

import Hyper-V

September 27, 2014, 12:57 am
$
0
0
Hey!
Can I import från another virtual instans an Hyper-V VM machiner to Proxmox
Prehaps install Proxmox if that goes do that

Best Regards
↧

node instability - uncertain of cause

September 27, 2014, 9:11 am
$
0
0
I'm running a cluster at home. I know the recommended number is 3 nodes in a cluster, I'm running two. I simply am not able to afford a third at this time, so please overlook that fact.

I have two nodes, node 1 has been a fucking champ, node 2 has mucked up twice now. They are identical hardware, and are only about a year old.

About a month or two ago (forget the exact date/time), node2 buggered up real good (effectively the same how it is now) and started having kernel panics when I would try to migrate VMs, or do anything fairly intensive. At the time I performed rigorous CPU, RAM and other hardware stress testing to try to identify a potential cause, and I came up with no observable hardware failure. So what did I do? I removed the node from the cluster, re-installed Proxmox VE on the host, re-added it to the cluster, and it's been operating like a champ since... until today.

I am seeing the same effects today as previously. To add a bit more detail, sometimes I see a kernel panic, sometimes I see a hard-reset of node2. For the last month or two, I have been able to safely migrate VMs back and forth online (online seems to trigger the vomiting) ever since I fixed it last, ~1-2mo, and all other expected functionality has appeared to be just fine.

I looked at the logs, and I saw some oddities with the nightly backups from last night. I'm unsure if it's the cause, or if it's the canary. I woke up this morning to find 3 of my VMs stuck at grub, as if they had been hard-reset. Node2 was responding, and I thought this was odd. What I had assumed was perhaps a backup had failed part way through and it had reset the VM (less than ideal, but better than it could be). Then I began to interact with the VMs, and the kernel panics, and node2 hard-resets started happening.

I'm sure there's logs and stuff I can paste here, but I'm not certain which ones are desirable in this case.

I figure it would be prudent to try and find the cause of this so perhaps either I can fix it on my end, or a fix can be made, instead of simply nuking the node and re-installing it. Both nodes are fully updated as of this morning, and the effects persist.

Please advise.
↧

ubuntu 14.04 guest with qxl

September 27, 2014, 9:11 am
$
0
0
I can't seem to get this to work I have the xf86 qxl driver installed and I get the following error at boot. If I try to used the system through virt-viewer it crashes.

[drm:qxl_write_monitors_config_for_encoder] *ERROR* head number too large or missing monitors config: f38000, 0

I have windows guest working great and linux containers but I can't get a linux VM working with the qxl drivers. Probably just missed something but I need a little help.

Thanks!
↧
↧

DAB to be updated for squeeze-lts

September 27, 2014, 9:57 am
$
0
0
Please see if the following can be incorporated into the next DAB release:
Code:
--- /usr/share/perl5/PVE/DAB.pm    Sat Sep 27 22:17:19 2014
+++ /usr/share/perl5/PVE/DAB.pm    Sat Sep 27 22:20:45 2014
@@ -416,7 +416,9 @@
    if (!$config->{source}) {
    if ($suite eq 'etch' || $suite eq 'lenny' || $suite eq 'squeeze' || $suite eq 'wheezy' ) {
        push @{$config->{source}}, "http://ftp.debian.org/debian SUITE main contrib";
-        push @{$config->{source}}, "http://ftp.debian.org/debian SUITE-updates main contrib"
+        push @{$config->{source}}, "http://ftp.debian.org/debian SUITE-updates main contrib";
+        if ($suite eq 'squeeze');
+        push @{$config->{source}}, "http://ftp.debian.org/debian SUITE-lts main contrib";
        if ($suite eq 'squeeze' || $suite eq 'wheezy');
        push @{$config->{source}}, "http://security.debian.org SUITE/updates main contrib";
    } elsif ($suite eq 'hardy' || $suite eq 'intrepid' || $suite eq 'jaunty') {
Also the URLs for older debian packages should now be archive.debian.org

DAB126diff.txt Patch
Attached Files
↧

High I/O usage on Win2000 vm

September 27, 2014, 12:42 pm
$
0
0
hello

I did p2v on an old physical win2k server and put it as vm on a standalone proxmox node.
VM booted normally but I have very high i/o usage which makes things very difficult.
On same Proxmox nodeI have another vm with win2003 which also did p2v from another physical server.This vm runs as expected.Below I'm posting in case someone can give an idea:


vm config:
------------

Code:
acpi: 0
balloon: 1024
boot: ccn
bootdisk: ide0
cores: 1
ide0: local:101/vm-101-disk-1.qcow2,format=qcow2,size=65G
ide1: ssd-data:101/vm-101-disk-1.qcow2,format=qcow2,size=100G
ide2: none
memory: 4096
name: mainsrv
net0: e1000=6E:B8:ED:B8:93:76,bridge=vmbr0
ostype: w2k
smbios1: uuid=77dc2172-4804-4a24-8f29-a07186b254a0

sockets: 1




I have configured the vm with 2 ide disks which both reside on ssd disks.


Code:
pveperf
CPU BOGOMIPS:      29599.64
REGEX/SECOND:      2706175
HD SIZE:          14.60 GB (/dev/mapper/pve-root)
BUFFERED READS:    428.89 MB/sec
AVERAGE SEEK TIME: 0.06 ms
FSYNCS/SECOND:    212.79
DNS EXT:          171.22 ms


What I have tried:


1. Disabling ACPI and put 1 socket/ 1 cpu core -> Set Standard PC on Device Manager -> Computer type.
2. Enabling ACPI and put 1 socket/ 2 cpu cores -> Set ACPI Multiprocessor on Device Manager -> Computer type.
3. Tried to put Virtio but was difficult to find appropriate drivers for win2000 and finally after found and installed them, they appear with exclamation mark on device manager, so not working.
4. Tried only intel 1000 adapter for the moment and updated drivers from intel.


The strange thing is that inside vm by using process explorer everything looks normal but when I use iotop on proxmox host I can see that this particular vm has more than 50% i/o usage.
I am really out of ideas and would appreciate if anybody can suggest something else.



↧

Changing ip address for proxmox cluster

September 27, 2014, 1:22 pm
$
0
0
My current setup:
prox1 and prox2 with vmbr0 on 192.168.1.x subnet and DRAS interface (Fence Device) 192.168.1.x. My cluster is based on 192.168.1.x subnet.
I want to add vmbr1 for prox1 and prox2 for 10.1.1.x subnet and change the cluster to 10.1.1.x network which is connected to an isolated switch only allowing 10.1.1.x subnet. On the same switch, I am going to attach my ZFS storage also with ip range of 10.1.1.x . I want to also change my cluster.conf form 192.168.1.x to 10.1.1.x for the DRAS interfaces. Finally I want to add a 3rd node prox3 to the cluster with the same config setup.
Can someone tell me steps, I should take in order to achieve this?
Thanks in advance.
↧
Search

2-node cluster: How to allow VMs to automatically start w/o quorum?

September 27, 2014, 4:11 pm
$
0
0
One of my nodes will be going offline for about a week. I'd like to make sure the other (which is not the master) continues to function normally in the meantime. How can I do this?

Thanks.
↧
↧

Vm console has errors

September 27, 2014, 8:27 pm
$
0
0
Hello i am trying to access my virtual machines but when i open the console i get an error message i was wondering if anyone had the same issue i'm attaching a screen shot thanks for your help.

ERROR2.pngERROR1.png
Attached Images
↧

Unable to Open Proxmox GUI

September 27, 2014, 9:34 pm
$
0
0
Hi Proxmox Friends,
Here are my Proxmox details
Using -- Proxmox 3.3 and dont have any issues as of today.
But today i removed two packages related to iscsi manually by using the following command
apt-get --purge remove libiscsi4
apt-get --purge remove open-iscsi

But i am able to access proxmox box using putty.
I dont see any issues when using putty.

From then i am unable to access the console from laptop.
Any help is welcome.
Thanks for the help in advance.


Thanks
Persevere
↧

Install Procmox VE 3.3 on other device than /dev/sda

September 28, 2014, 7:07 am
$
0
0
Hi, I would like to test Proxmox VE to get rid of ESXi.
So I decided to add a new disk to my ESXi host and use it for a Proxmox test installation for performance tests.

The new disks are on an LSI RAID controller. I created 3 volumes. One for the Proxmox system another for the virtual machine storage and one to map directly into the virtual machine for the WEB server data.

The Proxmox installer allow you to choose the installation drive. In my case /dev/sdd. The install stopped when writing the boot loader to the disk, because it does it to "(hd0)" (hardcoded in the installer script, I guess). To solve this, I started the installer again with "debug ext4" (without the "). Doing so, I was able to enter a console to install grub manually by pressing abort, when the error occurred.

When the installer failed, it already did unmount the required paths for chroot.
So I added them again:
Code:
# mount -n /dev/sdd2 -o noatime,barrier=0 /target/boot
 # mount -n /dev/pve/data -o noatime,barrier=0 /target/var/lib/vz
 # mount -n -t tmpfs tmps /target/tmp
 # mount -n -t proc proc /target/proc
 # mount -n -t sysfs sysfs /target/sys
 # mount -n --bind /dev /target/dev
Now we can install grub:
Code:
# chroot /target /usr/sbin/grub-install --no-floppy /dev/sdd
 # chroot /target /usr/sbin/update-grub
Then I pressed "<control>-d" to finish the installer.

After rebooting, Proxmox was started, but the web interface was not running.
There is no /var/log/syslog and no /var/log/daemon.log to look further into this problem.
Any hints why they are not there?

Searching on the net brought me into the direction of "/etc/pve" (see: http://forum.proxmox.com/threads/141...g-in-Proxmox-3).
The directory was not mounted. I did this by "pmxcfs" (see: http://forum.proxmox.com/threads/752...-not-connected).
The directory /etc/pve/local was missing (symbolic link to /etc/pve/nodes/proxmox).

After a reboot the same problem happened again.

This might be caused by not installing to /dev/sda, but I can't change the RAID controller configuration, because I still need the ESXi installation.
Maybe someone can point me in the right direction.

Where can I find the installer script in the git repository. Maybe I can look there for installation issues, concerning a different disk.

BR
Jasmin
↧

qemu: could not load PC BIOS 'bios.bin'

September 28, 2014, 7:16 am
$
0
0
Hi,

After installing the proxmox on Debian Wheezy, I made the VM. I have such error on start

Code:
WARNING: failed to find acpi-dsdt.aml
qemu: could not load PC BIOS 'bios.bin'
TASK  ERROR: start failed: command '/usr/bin/kvm -id 101 -chardev  'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait' -mon  'chardev=qmp,mode=control' -vnc  unix:/var/run/qemu-server/101.vnc,x509,password -pidfile  /var/run/qemu-server/101.pid -daemonize -name Win2012 -smp  'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga std -no-hpet -cpu  'kvm64,hv_spinlocks=0xffff,hv_relaxed,+x2apic,+sep' -k en-us -m 512  -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2'  -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device  'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive  'file=/dev/cdrom,if=none,id=drive-ide2,media=cdrom,aio=native' -device  'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device  'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive  'file=/var/lib/vz/images/101/vm-101-disk-1.qcow2,if=none,id=drive-sata0,format=qcow2,aio=native,cache=none'  -device  'ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -netdev  'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge'  -device  'e1000,mac=BA:7D:2D:4C:C2:84,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'  -rtc 'driftfix=slew,base=localtime' -global  'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

# md5sum /usr/bin/kvm /usr/share/kvm/bios.bin /usr/share/kvm/acpi-dsdt.aml

abbca35bcaae484c7794af4f4bc28fd1 /usr/bin/kvm
45ed06bfc6c9ae6fcf256d4f1cbb6b09 /usr/share/kvm/bios.bin
c52da652d48d7092b65f151d58344256 /usr/share/kvm/acpi-dsdt.aml

# dpkg -L pve-qemu-kvm|grep acpi-dsdt
/usr/share/kvm/q35-acpi-dsdt.aml
/usr/share/kvm/acpi-dsdt.aml


What can I do?


Best regards
↧
↧

Huawei USB passtrough : not showing in the vm

September 28, 2014, 2:32 pm
$
0
0
Hello,

I am trying to pass a huawei 3g modem to a vm but i'm having difficulties. the usb in showing on the host, on the qm monitoring but not on the guest VM.

Quote:
root@proxmox:~# lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
|__ Port 4: Dev 5, If 0, Class=stor., Driver=usbfs, 480M
|__ Port 4: Dev 5, If 1, Class=stor., Driver=usbfs, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/2p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/2p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
I have added the following line in the vm conf file

Quote:
args: -device usb-host,hostbus=3,hostport=4
Quote:
qm> info usbhost
Bus 3, Addr 5, Port 4, Speed 480 Mb/s
Class 00: USB device 12d1:1446, HUAWEI Mobile
But then when i log in the VM and do an lsusb it's not showing

Quote:
jeedom@jeedom:~$ lsusb
Bus 001 Device 003: ID 0409:55aa NEC Corp. Hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Can someone help me ?
↧

Problem PCIe Passthrough M1015 XPEnology(Nanoboot) boot hang's up.

September 28, 2014, 11:12 pm
$
0
0
Hello.

I've got problems to passthrough my M1015 PCIe Controller, flashed to IT-mode.

I followd the instructions for intel at https://pve.proxmox.com/wiki/Pci_passthrough

Before i add the configuration option to the vm-file evetrything seems to be okay and i can bott my vm. If i sign the ocie to the vm, the vm stops at "Booting from Hard Disk". Even if i choose Boot menu and select the virtual disk i want to boot from nothing happens. booting from a live linux works with pcie passthroughed. i don't know what to do.

This is my .conf file at /etc/pve/qemu-server/100.conf
Code:
bootdisk: ide0
cores: 2
ide0: local:100/vm-100-disk-1.qcow2,format=qcow2,size=1G
memory: 512
name: DiskStation
net0: e1000=A6:AD:68:A2:1E:D4,bridge=vmbr0
ostype: l26
sata0: local:100/vm-100-disk-2.qcow2,size=10G
smbios1: uuid=7c7fa243-7797-46e7-9dbe-404bab88d449
sockets: 1
hostpci0: 06:00.0,pcie=1,driver=vfio
machine: q35
the adress from lspci | grep SCSI
Code:
06:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
and my versions:
Code:
root@proxmox:/etc/pve/qemu-server# pveversion -v
proxmox-ve-2.6.32: 3.2-136 (running kernel: 3.10.0-4-pve)
pve-manager: 3.3-1 (running version: 3.3-1/a06c9f73)
pve-kernel-3.10.0-4-pve: 3.10.0-17
pve-kernel-2.6.32-32-pve: 2.6.32-136
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.1-34
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-5
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
Hope somebody can help :)
qemu.jpg
Attached Images
↧
Search

[SOLVED] ERROR: Backup of VM 100 failed - command 'qm set 100 --lock backup' failed

September 29, 2014, 12:57 am
$
0
0
Hi,

By wanting to backup my virtual machine in a some cases I have "backup failed" in both versions of proxmox 2.2-24 and 3.1-21 :
and here is the error message:

Code:
INFO: starting new backup job: vzdump 100 --remove 0 --mode snapshot --compress lzo --storage Disque_Backups --node vm1
INFO: Starting Backup of VM 100 (qemu)
INFO: status = running
INFO: VM is locked (backup)
ERROR: Backup of VM 100 failed - command 'qm set 100 --lock backup' failed: exit code 25
INFO: Backup job finished with errors
TASK ERROR: job errors
What could be the cause of this error ?
I made several research but I have not found any on this error.
thank you for helping me

Best regards,
↧

VMs on Synology?

September 29, 2014, 1:16 am
$
0
0
In the book Mastering Proxmox, it talks about storing & running the VMs on a FreeNAS server.

Is it possible to use a Synology NAS server instead of FreeNAS?
↧
↧

Qemu Guest Agent Support ?

September 29, 2014, 3:16 am
$
0
0
Hi,

I would like to use qemu guest-agent and commands like guest-fsfreeze-freeze to get more consistant snapshot backups with proxmox.
What has to be done for guest agent support in proxmox ?

Thanks
↧

qcow2 file to big

September 29, 2014, 4:12 am
$
0
0
Hi,

root@proxmox2:/var/lib/vz/images/100# qemu-img info vm-100-disk-2.qcow2
image: vm-100-disk-2.qcow2
file format: qcow2
virtual size: 150G (161061273600 bytes)
disk size: 247G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false


you see the virtual size is aber 150G, but disk size is 247.. so realy to big and my bare metal disk is full ...

how can i shrink this?

Thx!

Erik
↧

ftp ist blocked

September 29, 2014, 4:44 am
$
0
0
hi,

i added ftp to the firewall. a client can connect to the server and is promted for user & pwd but then they get timeouts.
in the log i find that:
SRC=XXXXXXXXXX DST=XXXXXXXX LEN=60 TOS=0x00 PREC=0x00 TTL=120 ID=3786 DF PROTO=TCP SPT=51122 DPT=44499 SEQ=260317126 ACK=0 WINDOW=8192 SYN
is this because of passive ftp ?
how can i get this working with proxmox gui?
↧
Viewing all 171654 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>