P
prf
Guest
I think I have come across a small problem related to the updating of a KVM guest configuration file. The scenario is as follows:
I initially created a KVM guest and installed Windows 2008 R2 using a lvm logical volume created on an ISCSI volume. This guest has been running happily for some months now.
Today, I decided to change the guest system disc from IDE to VIRTIO using the signed Windows VIRTIO drivers on alt.fedoraproject.org.
I shutdown the KVM, mounted the VIRTIO iso image as a CD-ROM and added a small (1GB) hard disc of type VIRTIO.
I then rebooted the guest and successfully installed the VIRTIO driver for the 1GB disc from the VIRTIO CD-ROM.
I then shutdown the KVM, removed the 1GB disc and the removed then added the same main system disc volume, this time using VIRTIO type rather than IDE.
I rebooted the KVM but it stopped at the BIOS POST saying it could not boot.
I did some investigation and found that in the configuration file of the KVM guest (/etc/qemu-server/vmid.conf) that the bootdisk: directive was still referring to ide0. It had not been updated to refer to the virtual disc.
I manually edited this to reflect the correct virtio id and the system then booted correctly. The config did contain an entry for the virtio disc though ie virtio0: ... anthe ide0 entry had been removed correctly.
Not sure if this is due to a mistake I made or whether the config is not being updated correctly when a modification is made to the type of the boot drive.
I am running the following Proxmox version.
sur-vm-01:/etc/apt# pveversion -v
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.18-3-pve
proxmox-ve-2.6.18: 1.6-6
pve-kernel-2.6.18-3-pve: 2.6.18-6
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-18
pve-firmware: 1.0-8
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-6
Regards
Paul
I initially created a KVM guest and installed Windows 2008 R2 using a lvm logical volume created on an ISCSI volume. This guest has been running happily for some months now.
Today, I decided to change the guest system disc from IDE to VIRTIO using the signed Windows VIRTIO drivers on alt.fedoraproject.org.
I shutdown the KVM, mounted the VIRTIO iso image as a CD-ROM and added a small (1GB) hard disc of type VIRTIO.
I then rebooted the guest and successfully installed the VIRTIO driver for the 1GB disc from the VIRTIO CD-ROM.
I then shutdown the KVM, removed the 1GB disc and the removed then added the same main system disc volume, this time using VIRTIO type rather than IDE.
I rebooted the KVM but it stopped at the BIOS POST saying it could not boot.
I did some investigation and found that in the configuration file of the KVM guest (/etc/qemu-server/vmid.conf) that the bootdisk: directive was still referring to ide0. It had not been updated to refer to the virtual disc.
I manually edited this to reflect the correct virtio id and the system then booted correctly. The config did contain an entry for the virtio disc though ie virtio0: ... anthe ide0 entry had been removed correctly.
Not sure if this is due to a mistake I made or whether the config is not being updated correctly when a modification is made to the type of the boot drive.
I am running the following Proxmox version.
sur-vm-01:/etc/apt# pveversion -v
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.18-3-pve
proxmox-ve-2.6.18: 1.6-6
pve-kernel-2.6.18-3-pve: 2.6.18-6
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-18
pve-firmware: 1.0-8
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-6
Regards
Paul
