KVM + physical device

Hi Tom,

sorry but bevor i posted, i have read the manuel for qm but found anything about physical harddrive device.

Regards, Valle
 
Thanks Tom,
i have this (ide:1 /dev/sda) insertet bevor i post. Looks like this is a qemu bug.

Become the message "unable to parse volume ID /dev/sda"

Regards and a nice weekend,

Valle
 
valshare said:
Thanks Tom,
i have this (ide:1 /dev/sda) insertet bevor i post. Looks like this is a qemu bug.

Become the message "unable to parse volume ID /dev/sda"

Regards and a nice weekend,

Valle
Click to expand...

see my config file (not ide:1 - you need ide1:)

Code: 
name: winxp-sp3
ide2: none,media=cdrom
vlan0: rtl8139=DA:B4:B7:B5:12:25
bootdisk: ide0
ostype: wxp
ide0: LVM-on-iscsi2:vm-103-disk-1
ide1: /dev/sde
memory: 512
sockets: 1
 
Last edited:
Hi Tom,

sorry for the example. I mean ide1: i have make a mistake.

Here is my qm conf

ide2: local:iso/openfiler-2.3-x86-disc1.iso,media=cdrom
vlan0: e1000=FA:4B:2A:A1:9F:86
bootdisk: ide0
ostype: other
ide0: local:113/vm-113-disk-1.raw
memory: 512
sockets: 1
ide1: /dev/sdb


qm start 113 gives me:

proxmox-testserver:~# qm start 113
unable to parse volume ID '/dev/sdb'

Its a Samsung HDD.

Regards, Valle
 
valshare said:
Hi Tom,

sorry for the example. I mean ide1: i have make a mistake.

Here is my qm conf

ide2: local:iso/openfiler-2.3-x86-disc1.iso,media=cdrom
vlan0: e1000=FA:4B:2A:A1:9F:86
bootdisk: ide0
ostype: other
ide0: local:113/vm-113-disk-1.raw
memory: 512
sockets: 1
ide1: /dev/sdb


qm start 113 gives me:

proxmox-testserver:~# qm start 113
unable to parse volume ID '/dev/sdb'

Its a Samsung HDD.

Regards, Valle
Click to expand...

and the samsung HDD is on /dev/sdb (on the Proxmox VE host)?

And you use the latest version of 1.4 - run apt-get update and apt-get upgrade to make sure and test again.
 
Hi Tom,

yes the Samsung HDD is on /dev/sdb. Latest Update

proxmox-testserver:~# pveversion -v
pve-manager: 1.4-7 (pve-manager/1.4/4366)
qemu-server: 1.1-5
pve-kernel: 2.6.24-16
pve-qemu-kvm: 0.11.0-2
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-2
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
proxmox-testserver:~
 
In theory, it's also possible to add a drive to a running system ("drive_add" in KVM monitor).

Unfortunately, I was not able to add a drive (with "drive_add") so that it's visible in the guest.
 
I am having this same exact issue with all nodes in my cluster after running:

apt-get update && apt-get dist-upgrade -y
pveam update

I use ghost to provision KVM so mounting a preexisting hdd with Ghost files is essential. I cannot provision untill this is fixed which is a big issue.



###############################

qm set 200 -ide1 /dev/sdc1
unable to parse volume ID '/dev/sdc1'

###############################

fdisk -l

Device Boot Start End Blocks Id System
/dev/sdc1 1 60802 488384536 7 HPFS/NTFS


###############################

pveversion -v


pve-manager: 2.1-12 (pve-manager/2.1/be112d89)
running kernel: 2.6.32-13-pve
proxmox-ve-2.6.32: 2.1-72
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-13-pve: 2.6.32-72
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-45
pve-firmware: 1.0-17
libpve-common-perl: 1.0-28
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-27
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-6
ksm-control-daemon: 1.1-1


This was all working perfectly before i ran the upgrade, so there must be an issue with the latest version.
 
you are in the wrong forum (1.x)!
 
as workaround, add it manually in the VMID.conf file.
 
You must log in or register to reply here.
Top Bottom