ID ändern von Windows Server

[MartinSt]

Hi, ich habe ein Problem:

in Proxmox 6.0-11 habe ich einen Windows Server mit der ID 100 am laufen gehabt.
Da ich verschiedene Server betreibe überschneidet sich die ID von den anderen beim Backup.

Wie kann ich die ID + HDD-ID ändern.

Was ich gemacht habe:

1.) /etc/pve/nodes/virtfarm-03(/qemu-server/100.conf nach 100.conf.save kopiert
2.) 100.conf nach 124.conf kopiert
3.) scsi0: local-zfs:vm-100-disk-0,size=32G -> 100 auf 124 geändert
4.) Kontrolliert ob in der Proxmox Website alles stimmt
5.) mit zfs list meine zfs Platten aufgeslistet rpool/data/vm-100-disk-0 ist vorhanden
6.) mit zfs rename rpool/data/vm-100-disk-1 rpool/data/vm-125-disk-1 name geändert

Nun wollte ich das System starten und es geht nicht.
Was fehlt noch für eine Konfiguration?

Diese Fehlermeldung bekomme ich:
TASK ERROR: start failed: command '/usr/bin/kvm -id 125 -name SV11 -chardev 'socket,id=qmp,path=/var/run/qemu-server/125.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/125.pid -daemonize -smbios 'type=1,uuid=06cf9e80-ba2b-4a87-b353-387a3f421ed9' -smp '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/125.vnc,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,hv_ipi,enforce' -m 8192 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'vmgenid,guid=df18bc21-17a1-4d33-84e3-f4efecc93cac' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:425d679e3420' -drive 'file=/dev/zvol/rpool/data/vm-125-disk-0,if=none,id=drive-ide0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/dev/zvol/rpool/data/vm-125-disk-1,if=none,id=drive-ide1,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap125i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=8A:2C:5D:EC:F4:FB,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout

 

[Dominic]

3.) scsi0: local-zfs:vm-100-disk-0,size=32G -> 100 auf 124 geändert
(...)
6.) mit zfs rename rpool/data/vm-100-disk-1 rpool/data/vm-125-disk-1 name geändert

Typo?

Bitte poste

qm config 100
qm config 124
cat /etc/pve/storage.cfg
zfs list

Braucht zwar zwischendurch etwas Speicher, aber einen Klon der VM zu erstellen (VM anklicken, dann rechts oben More->Clone) könnte Nerven & Zeit sparen. Dabei kann man nämlich eine neue ID, die für VM und Disk verwendet wird, angeben.

 

[MartinSt]

sorry
Windows server ist id 125
---
root@virtfarm-03:~# qm config 125
bootdisk: ide0
cores: 2
ide0: local-zfs:vm-125-disk-0,size=32G
ide1: local-zfs:vm-125-disk-1,size=52G
ide2: none,media=cdrom
memory: 8192
name: SV11
net0: e1000=8A:2C:5D:EC:F4:FB,bridge=vmbr2,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=06cf9e80-ba2b-4a87-b353-387a3f421ed9
sockets: 2
vmgenid: df18bc21-17a1-4d33-84e3-f4efecc93cac
root@virtfarm-03:~#
---
root@virtfarm-03:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 52.2G 1.70T 96K /rpool
rpool/ROOT 11.4G 1.70T 96K /rpool/ROOT
rpool/ROOT/pve-1 11.4G 1.70T 11.4G /
rpool/data 40.7G 1.70T 96K /rpool/data
rpool/data/vm-102-disk-0 12.6G 1.70T 12.6G -
rpool/data/vm-124-disk-0 4.43G 1.70T 4.43G -
rpool/data/vm-125-disk-0 23.2G 1.70T 23.2G -
rpool/data/vm-125-disk-1 562M 1.70T 562M -
root@virtfarm-03:~#

 

[MartinSt]

cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso,backup,vztmpl

zfspool: local-zfs
pool rpool/data
content rootdir,images
sparse 1

 

[Dominic]

Eventuell:

• Storage neu anlegen
• qm rescan --vmid 125
• RAM-Menge verändern

Einfacher ist aber Klonen oder Backup & Restore.

 

[MartinSt]

1.) Rescan hat nix gebracht
qm rescan --vmid 125
rescan volumes...

2.) RAM-Menge verändert hat nix gebracht




TASK ERROR: start failed: command '/usr/bin/kvm -id 125 -name SV11 -chardev 'socket,id=qmp,path=/var/run/qemu-server/125.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/125.pid -daemonize -smbios 'type=1,uuid=06cf9e80-ba2b-4a87-b353-387a3f421ed9' -smp '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/125.vnc,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,hv_ipi,enforce' -m 4096 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'vmgenid,guid=df18bc21-17a1-4d33-84e3-f4efecc93cac' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:425d679e3420' -drive 'file=/dev/zvol/rpool/data/vm-125-disk-0,if=none,id=drive-ide0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/dev/zvol/rpool/data/vm-125-disk-1,if=none,id=drive-ide1,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=1,drive=drive-ide1,id=ide1' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap125i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=8A:2C:5D:EC:F4:FB,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout

3.) Clone erzeugt, selbe Fehlermeldung

 

[Dominic]

Startest du immer von der GUI?

 

[MartinSt]

JA

 

[Dominic]

Probiere es bitte mal vom CLI:

qm start 125 --timeout 120

 

[MartinSt]

qm start 125
start failed: command '/usr/bin/kvm -id 125 -name SV11 -chardev 'socket,id=qmp,path=/var/run/qemu-server/125.q mp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,re connect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/125.pid -daemonize -smbios 'typ e=1,uuid=06cf9e80-ba2b-4a87-b353-387a3f421ed9' -smp '4,sockets=2,cores=2,maxcpus=4' -nodefaults -boot 'menu=on ,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/12 5.vnc,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_t ime,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,hv_ipi,enforce' -m 4096 -device 'pci-bridge,i d=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -devi ce 'vmgenid,guid=df18bc21-17a1-4d33-84e3-f4efecc93cac' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-ball oon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:425d679e3420' -drive 'file=/dev/zvol/rpool/data/vm-125-disk-0,if=none,id=drive-ide0,format=raw,cache=none,aio=native,detect-zeroes= on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/dev/zvol/rpool/data /vm-125-disk-1,if=none,id=drive-ide1,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=id e.0,unit=1,drive=drive-ide1,id=ide1' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bu s=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap125i0,script=/var/l ib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=8A:2C:5D:EC:F4:FB ,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout


qm start 125 --timeout 120
Unknown option: timeout
400 unable to parse option
qm start <vmid> [OPTIONS]

 

[Dominic]

Ein Upgrade zu Proxmox VE 6.2 wäre gut. Damit sollte zumindest die timeout-Funktion verfügbar sein. Zwischenzeitlich sollte auch

qm showcmd 125 | bash

denselben Effekt haben.