Warning about raw format with ZFS and KVM

[hakim]

Hi,

Each time I restore a KVM vm in my ZFS dataset filesystem, I get the following message :

WARNING: Image format was not specified for '/dev/zvol/proxmox/vm-100-disk-1' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly to remove the restrictions.

The type of my proxmox storage is : zfspool

I tried to set myself the raw format in the conf file, but whenever I do a backup / restore, same story.
The warning message states that not specifying the format "is dangerous for raw image".
But even when, I try to add new disks, I have no other choice than raw, but the format is not written in the conf file...

What could be wrong ?

Thanks,
Hakim

 

[dietmar]

What could be wrong ?

AFAIK this is already fixed in newer version. What version do you run exactly?

# pveversion -v

 

[hakim]

proxmox-ve: 4.1-41 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-22 (running version: 4.1-22/aca130cf)
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-36
qemu-server: 4.0-64
pve-firmware: 1.1-7
libpve-common-perl: 4.0-54
libpve-access-control: 4.0-13
libpve-storage-perl: 4.0-45
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-52
pve-firewall: 2.0-22
pve-ha-manager: 1.0-25
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie

I wanted to finish my tests before buying the subscription, but I am going to take it now.
Thanks Dietmar.

 

[dietmar]

OK, I can reproduce that. It is only a warning, so everything should work as expected.

Anyways, I filed a bug for this issue here: https://bugzilla.proxmox.com/show_bug.cgi?id=934

 

[gerfloim]

Same here:

 qm start 100
WARNING: Image format was not specified for '/dev/zvol/rz2pool/vm/vm-100-disk-1' and probing guessed raw.
         Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.

Im on 5.1-36:

proxmox-ve: 5.1-26 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.10.17-4-pve: 4.10.17-24
pve-kernel-4.10.17-2-pve: 4.10.17-20
pve-kernel-4.10.17-3-pve: 4.10.17-23
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: not correctly installed
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9
openvswitch-switch: 2.7.0-2

 

[fireon]

qm start 100 WARNING: Image format was not specified for '/dev/zvol/rz2pool/vm/vm-100-disk-1' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions.

I'am here on the same version. No such errormessage.

 

[fabian]

fixed in git already, next qemu-server update will contain the fix.