Search results

I always use the command below to create VMs but today on latest Proxmox server I got error below: /usr/sbin/qm create 10410 --cdrom local:iso/CentOS-5.4-i386-bin-DVD.iso --name srv15822 --net1 rtl8139,bridge=vmbr0 --bootdisk ide0 --ostype other --ide0 local:100,format=raw --memory 2048...

It's 2.6.32-279.5.1.el6.x86_64 #1 SMP Tue Aug 14 23:54:45 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

I've a CentOS x64 KVM guest which it's time goes back about 3 hours every day and some times on reboot I didn't install or configure any time server and the hardware time and system time zone are fine Any one familiar with this issue?

As in Proxmox 2.3 the qcow2 is default HDD format, I need to now how can I copy it, With the raw format I simply use the cp command to copy the HDD drive perfectly and sime times when the file was on bad sector the dd command worked well Is it still possible to use cp and dd with qcow2 commands...

I've installed the e1000 driver on Windows 2003 VMs, the Windows 2008 has built in driver for e1000, The link is: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18719&lang=eng

It worked for me, But it's necessary for Proxmox to fix such critical bug.

I want to make new scripting system to selftest every disk of my servers 3 times a week, ( one longtest and two shorttest ) My question is if it make some pressure on HDD drives? Anyone has experience using smart to test drives periodically ?

cp can't be used in such scenario because when cp hits the first badsector it will show an I/O error and abort the process of copying the file, while dd will continue and ignores the badblock

Anyone else facing the same issue?

I don't know if block size is important in such scenario, but two disks has the same block size.

Sometimes when I can't copy a KVM based VM's raw file ( because of badsectors ) I use the below dd command to copy raw file to new drive and also ignore the bad blocks. dd if=/var/lib/vz/images/100/100.raw of=/newdisk/100/100.raw bs=4k conv=noerror,syncUsing the `ls -hs` on original raw file...

Yes the hostname is exactly the same, But it's also necessary to copy below files: /var/lib/pve-cluster/config.db /var/lib/pve-cluster/config.db-shm /var/lib/pve-cluster/config.db-wal coping all these 3 files it got working and `qm list` shows all VMs,

I've copied the /var/lib/pve-cluster/config.db to new installed server but even after reboot the `qm list` command shows no vm also /etc/pve/qemu-servers is empty

Is it possible to use this file on newly installed server? ( just copying to new server's /var/lib/pve-cluster/config.db )

I've a crushed server which I want to recover it's important data only but in a systemrescue live cd environmental how can I read /etc/pve data ?

I'm not using virtio, simple configuration of a vm bootdisk: ide0 cores: 1 ide0: local:7673/vm-7673-disk-1.raw,size=25G memory: 256 name: stest net1: rtl8139=F2:74:4A:37:8A:A4,bridge=vmbr1 onboot: 0 ostype: other

I've this issue on all Windows Guests from pve 2.2-32 on another new server too Anyone has the same experience?

I need to account traffic usage of each VM with out changing the gateway, Also I want to ignore some subnets so it seems that the ipt_accounting module to iptables is a good choice Any one has experience with using it on Proxmox? Is this setup guide applicable for Proxmox...

Today I see this messages in syslog after a server down, Any one know what does it mean? Dec 30 02:59:19 c72 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 154 Dec 30 02:59:19 c72 kernel: Raw EDID: Dec 30 02:59:19 c72 kernel: 9a 00 00 00 00 00 00 00 00 00...