xxxx.conf

N

nbhanji

Renowned Member
Nov 30, 2010
16
0
66
USA, FL
Can you please tell me whether this is new feature or something missed.

Prior to pve 2.3 -- when you listed the contents of vm's conf file, you did not see other vm's disk images. Now you can.

9503.conf
unused0: local:9502/vm-9502-disk-1.qcow2virtio0: local:9503/vm-9503-disk-1.qcow2,size=32G


9502.conf
unused0: local:9503/vm-9503-disk-1.qcow2
virtio0: local:9502/vm-9502-disk-1.qcow2,size=64G


Thanks for your help

pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-93
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
 
No, I had one vm 9502, I created another one - 9503. But I had not started it because I was going to copy a .qed image to it.
While waiting for it to finish copying on temp dir, I was working on adding USB port to 9502. That's when I noticed the 9305's image entry in 9502.conf file

Now it is showing up on web page of hardware status of vm
 
Is there a way to resolve this. I edited the 9502.conf and added usb0: xxxx:xxxx, but that images were showing before that. So is there a way to solve the issue of not propagating images to the conf files? I may not be the only one doing manual configuration if needed. How can i fix it

Thanks in advance
 
You must log in or register to reply here.
Top Bottom