Error Creating VM

[krzysiek2788]

Hi I was trying to use your script but I got this error below:

Any idea why?

@edit:

It looks like that thise line is causing an error:

[alesp24]

Hi, I've got a similar error too

could someone help me solve it? Thanks!

[Swell61]

I had the same issue trying to install hassos this evening, using this script. While I don't know what caused the problem, updating Proxmox and rebooting the host solved the issue. Here is where I found the soltuion (I have no other hasos installs and no issues with my Proxmox setup). The install went ahead flawlessly and I am now in the Home Assistant web UI.

[whiskerz007]

Is this still a problem?

[dmshimself]

I think it might still be an issue. I ran up a fresh proxmox install today, so the server has been rebooted. When using the script I get the following (data is zfs storage):

[INFO] Using 'data' for storage location. [INFO] Container ID is 104. Getting URL for latest Home Assistant disk image... Downloading disk image... Extracting disk image... Creating VM... [ERROR] 4@135 Unknown failure occured. #

If I use local-lvm, all is well

[whiskerz007]

@dmshimself I am unable to reproduce your results. Please run the following command in a Proxmox shell and post the entire output. bash -xc "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassos_install/raw/master/install.sh)"

[dmshimself]

Thanks for that and here is the output:

root@pve:~# bash -xc "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassos_install/raw/master/install.sh)"

• set -o errexit
• set -o errtrace
• set -o nounset
• set -o pipefail
• shopt -s expand_aliases
• alias 'die=EXIT=$? LINE=$LINENO error_exit'
• trap die ERR
• trap cleanup EXIT ++ mktemp -d
• TEMP_DIR=/tmp/tmp.geHgA51VP1
• pushd /tmp/tmp.geHgA51VP1
• read -r line ++ awk 'NR>1' ++ pvesm status -content images ++ echo data zfspool active 2828009172 1752654260 1075354912 61.97% ++ awk '{print $1}'
• TAG=data ++ echo data zfspool active 2828009172 1752654260 1075354912 61.97% ++ awk '{printf "%-10s", $2}'
• TYPE='zfspool ' ++ echo data zfspool active 2828009172 1752654260 1075354912 61.97% ++ numfmt --field 4-6 --from-unit=K --to=iec --format %.2f ++ awk '{printf( "%9sB", $6)}'
• FREE=' 1001.51GB'
• ITEM=' Type: zfspool Free: 1001.51GB '
• OFFSET=2
• [[ 38 -gt '' ]]
• MSG_MAX_LENGTH=38
• STORAGE_MENU+=("$TAG" "$ITEM" "OFF")
• read -r line ++ echo local-lvm lvmthin active 1797799936 9887899 1787912036 0.55% ++ awk '{print $1}'
• TAG=local-lvm ++ echo local-lvm lvmthin active 1797799936 9887899 1787912036 0.55% ++ awk '{printf "%-10s", $2}'
• TYPE='lvmthin ' ++ awk '{printf( "%9sB", $6)}' ++ numfmt --field 4-6 --from-unit=K --to=iec --format %.2f ++ echo local-lvm lvmthin active 1797799936 9887899 1787912036 0.55%
• FREE=' 1.63TB'
• ITEM=' Type: lvmthin Free: 1.63TB '
• OFFSET=2
• [[ 38 -gt 38 ]]
• STORAGE_MENU+=("$TAG" "$ITEM" "OFF")
• read -r line
• '[' 2 -eq 0 ']'
• '[' 2 -eq 1 ']'
• '[' -z '' ']' ++ whiptail --title 'Storage Pools' --radiolist 'Which storage pool you would like to use for the container?\n\n' 16 61 6 data ' Type: zfspool Free: 1001.51GB ' OFF local-lvm ' Type: lvmthin Free: 1.63TB ' OFF
• STORAGE=data
• '[' -z x ']'
• info 'Using '\''data'\'' for storage location.'
• local 'REASON=Using '\''data'\'' for storage location.'
• local 'FLAG=\e[36m[INFO]\e[39m'
• msg '\e[36m[INFO]\e[39m Using '\''data'\'' for storage location.'
• local 'TEXT=\e[36m[INFO]\e[39m Using '\''data'\'' for storage location.'
• echo -e '\e[36m[INFO]\e[39m Using '\''data'\'' for storage location.' [INFO] Using 'data' for storage location. ++ pvesh get /cluster/nextid
• VMID=100
• info 'Container ID is 100.'
• local 'REASON=Container ID is 100.'
• local 'FLAG=\e[36m[INFO]\e[39m'
• msg '\e[36m[INFO]\e[39m Container ID is 100.'
• local 'TEXT=\e[36m[INFO]\e[39m Container ID is 100.'
• echo -e '\e[36m[INFO]\e[39m Container ID is 100.' [INFO] Container ID is 100.
• msg 'Getting URL for latest Home Assistant disk image...'
• local 'TEXT=Getting URL for latest Home Assistant disk image...'
• echo -e 'Getting URL for latest Home Assistant disk image...' Getting URL for latest Home Assistant disk image...
• RELEASE_EXT=vmdk.gz ++ cat ++ python3
• URL=https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vmdk.gz
• '[' -z https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vmdk.gz ']'
• msg 'Downloading disk image...'
• local 'TEXT=Downloading disk image...'
• echo -e 'Downloading disk image...' Downloading disk image...
• wget -q --show-progress https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vmdk.gz hassos_ova-4.11.vmdk.gz 100%[================================================================>] 237.69M 1.36MB/s in 3m 38s ++ basename https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vmdk.gz
• FILE=hassos_ova-4.11.vmdk.gz
• msg 'Extracting disk image...'
• local 'TEXT=Extracting disk image...'
• echo -e 'Extracting disk image...' Extracting disk image...
• gunzip -f hassos_ova-4.11.vmdk.gz ++ pvesm status -storage data ++ awk 'NR>1 {print $2}'
• STORAGE_TYPE=zfspool
• '[' zfspool = dir ']'
• for i in {0,1}
• disk=DISK0
• eval DISK0=vm-100-disk-0 ++ DISK0=vm-100-disk-0
• eval DISK0_REF=data:vm-100-disk-0 ++ DISK0_REF=data:vm-100-disk-0
• for i in {0,1}
• disk=DISK1
• eval DISK1=vm-100-disk-1 ++ DISK1=vm-100-disk-1
• eval DISK1_REF=data:vm-100-disk-1 ++ DISK1_REF=data:vm-100-disk-1
• msg 'Creating VM...'
• local 'TEXT=Creating VM...'
• echo -e 'Creating VM...' Creating VM... ++ sed -e 's/_//g' -e s/.vmdk.gz//
• VM_NAME=hassosova-4.11
• qm create 100 -agent 1 -bios ovmf -name hassosova-4.11 -net0 virtio,bridge=vmbr0 -onboot 1 -ostype l26 -scsihw virtio-scsi-pci
• pvesm alloc data 100 vm-100-disk-0 128 ++ EXIT=4 ++ LINE=135 ++ error_exit ++ trap - ERR ++ local 'DEFAULT=Unknown failure occured.' ++ local 'REASON=\e[97mUnknown failure occured.\e[39m' ++ local 'FLAG=\e[91m[ERROR] \e[93m4@135' ++ msg '\e[91m[ERROR] \e[93m4@135 \e[97mUnknown failure occured.\e[39m' ++ local 'TEXT=\e[91m[ERROR] \e[93m4@135 \e[97mUnknown failure occured.\e[39m' ++ echo -e '\e[91m[ERROR] \e[93m4@135 \e[97mUnknown failure occured.\e[39m' [ERROR] 4@135 Unknown failure occured. ++ '[' '!' -z 100 ']' ++ cleanup_vmid +++ qm status 100 +++ awk '{print $2}' +++ qm status 100 ++ '[' stopped == running ']' ++ qm destroy 100 ++ exit 4
• cleanup
• popd
• rm -rf /tmp/tmp.geHgA51VP1 root@pve:~#

[whiskerz007]

Please run the following and post the output.

pvesm alloc data 100 vm-100-disk-0 128; echo $?

[dmshimself]

A colleague re-installedanother fresh install, so the sorage usage changed. However I re-ran the first script and this second one, so the results are still consistent.

root@pve:~# bash -xc "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassos_install/raw/master/install.sh)"

• set -o errexit
• set -o errtrace
• set -o nounset
• set -o pipefail
• shopt -s expand_aliases
• alias 'die=EXIT=$? LINE=$LINENO error_exit'
• trap die ERR
• trap cleanup EXIT ++ mktemp -d
• TEMP_DIR=/tmp/tmp.bLk8dSvpK5
• pushd /tmp/tmp.bLk8dSvpK5
• read -r line ++ awk 'NR>1' ++ pvesm status -content images ++ echo local-zfs zfspool active 1735983332 15113492 1720869840 0.87% ++ awk '{print $1}'
• TAG=local-zfs ++ echo local-zfs zfspool active 1735983332 15113492 1720869840 0.87% ++ awk '{printf "%-10s", $2}'
• TYPE='zfspool ' ++ echo local-zfs zfspool active 1735983332 15113492 1720869840 0.87% ++ awk '{printf( "%9sB", $6)}' ++ numfmt --field 4-6 --from-unit=K --to=iec --format %.2f
• FREE=' 1.57TB'+ ITEM=' Type: zfspool Free: 1.57TB '
• OFFSET=2
• [[ 38 -gt '' ]]
• MSG_MAX_LENGTH=38
• STORAGE_MENU+=("$TAG" "$ITEM" "OFF")
• read -r line
• '[' 1 -eq 0 ']'
• '[' 1 -eq 1 ']'
• STORAGE=local-zfs
• info 'Using '\''local-zfs'\'' for storage location.'
• local 'REASON=Using '\''local-zfs'\'' for storage location.'
• local 'FLAG=\e[36m[INFO]\e[39m'
• msg '\e[36m[INFO]\e[39m Using '\''local-zfs'\'' for storage location.'
• local 'TEXT=\e[36m[INFO]\e[39m Using '\''local-zfs'\'' for storage location.'
• echo -e '\e[36m[INFO]\e[39m Using '\''local-zfs'\'' for storage location.' [INFO] Using 'local-zfs' for storage location. ++ pvesh get /cluster/nextid
• VMID=102
• info 'Container ID is 102.'
• local 'REASON=Container ID is 102.'
• local 'FLAG=\e[36m[INFO]\e[39m'
• msg '\e[36m[INFO]\e[39m Container ID is 102.'
• local 'TEXT=\e[36m[INFO]\e[39m Container ID is 102.'
• echo -e '\e[36m[INFO]\e[39m Container ID is 102.' [INFO] Container ID is 102.
• msg 'Getting URL for latest Home Assistant disk image...'
• local 'TEXT=Getting URL for latest Home Assistant disk image...'
• echo -e 'Getting URL for latest Home Assistant disk image...' Getting URL for latest Home Assistant disk image...
• RELEASE_EXT=vmdk.gz ++ python3 ++ cat
• URL=https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vmdk.gz
• '[' -z https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vmdk.gz ']'
• msg 'Downloading disk image...'
• local 'TEXT=Downloading disk image...'
• echo -e 'Downloading disk image...' Downloading disk image...
• wget -q --show-progress https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_ova-4.11.vmdk.gz hassos_ova-4.11.vmdk. 100%[=======================>] 237.69M 215KB/s in 11m 43s ++ basename https://github.com/home-assistant/operating-system/releases/download/4.11/ hassos_ova-4.11.vmdk.gz
• FILE=hassos_ova-4.11.vmdk.gz
• msg 'Extracting disk image...'
• local 'TEXT=Extracting disk image...'
• echo -e 'Extracting disk image...' Extracting disk image...
• gunzip -f hassos_ova-4.11.vmdk.gz ++ awk 'NR>1 {print $2}' ++ pvesm status -storage local-zfs
• STORAGE_TYPE=zfspool
• '[' zfspool = dir ']'
• for i in {0,1}
• disk=DISK0
• eval DISK0=vm-102-disk-0 ++ DISK0=vm-102-disk-0
• eval DISK0_REF=local-zfs:vm-102-disk-0 ++ DISK0_REF=local-zfs:vm-102-disk-0
• for i in {0,1}
• disk=DISK1
• eval DISK1=vm-102-disk-1 ++ DISK1=vm-102-disk-1
• eval DISK1_REF=local-zfs:vm-102-disk-1 ++ DISK1_REF=local-zfs:vm-102-disk-1
• msg 'Creating VM...'
• local 'TEXT=Creating VM...'
• echo -e 'Creating VM...' Creating VM... ++ sed -e 's/_//g' -e s/.vmdk.gz//
• VM_NAME=hassosova-4.11
• qm create 102 -agent 1 -bios ovmf -name hassosova-4.11 -net0 virtio,bridge=vmbr0 -onboot 1 -ostype l26 -scsihw virtio-scsi-pci
• pvesm alloc local-zfs 102 vm-102-disk-0 128 ++ EXIT=4 ++ LINE=135 ++ error_exit ++ trap - ERR ++ local 'DEFAULT=Unknown failure occured.' ++ local 'REASON=\e[97mUnknown failure occured.\e[39m' ++ local 'FLAG=\e[91m[ERROR] \e[93m4@135' ++ msg '\e[91m[ERROR] \e[93m4@135 \e[97mUnknown failure occured.\e[39m' ++ local 'TEXT=\e[91m[ERROR] \e[93m4@135 \e[97mUnknown failure occured.\e[39m' ++ echo -e '\e[91m[ERROR] \e[93m4@135 \e[97mUnknown failure occured.\e[39m' [ERROR] 4@135 Unknown failure occured. ++ '[' '!' -z 102 ']' ++ cleanup_vmid +++ qm status 102 +++ qm status 102 +++ awk '{print $2}' ++ '[' stopped == running ']' ++ qm destroy 102 ++ exit 4
• cleanup
• popd
• rm -rf /tmp/tmp.bLk8dSvpK5

pvesm alloc local-zfs 100 vm-100-disk-0 128; echo $? successfully created 'local-zfs:vm-100-disk-0' 0

[HorstBoy]

I'm seeing same problem, but only when I have multiple VMs running that utilize same ZFS backed datastore. It seems that others having same problem are also using ZFS and some have eventually succeeded after tricks like reboots or retrying several times.

My theory is that everyone experiencing this problem is using ZFS for datastore and have either slow disk subsystem or enough load on disks causing "pvesm alloc" call to fail during "zfs create" step. Proxmox enforces 5 second timeout for zfs create which is simply too low for some of us.

After removing /dev/null redirection of pvesm output I get following error message: "command 'zfs create -s -V 1024k rpool/data/vm-119-disk-0' failed: got timeout"

Trying to run "zfs create -s -V 1024k rpool/data/vm-119-disk-0" manually fails as volume is actually created just fine, simply not fast enough for pvesm to be happy.

Extending timeout from 5 seconds to 15 seconds by patching Proxmox code makes this work (for me) but is obviously not a good solution as it will be overwritten by Proxmox updates. Waiting fix from Proxmox might take awhile as this problem was first reported over 5 years ago.

If Whiskerz is willing to maintain workaround for Proxmox side bug this could be solved as part of install.sh. If "pvesm alloc" returns error code 4 then enter loop that sleeps for couple seconds, check if new volume was created successfully despite pvesm error, repeat for n times if necessary and only if it still doesn't exist then bail out with error. Otherwise continue to next step of install.

As said this is actually old and known bug: https://forum.proxmox.com/threads/zfs-plugin-timeouts.18882/#post-110786

https://github.com/proxmox/pve-storage/blob/74b724a6993fbe859a76d46dd5f2f9be395a2002/PVE/Storage/ZFSPoolPlugin.pm#L311 https://github.com/proxmox/pve-storage/blob/74b724a6993fbe859a76d46dd5f2f9be395a2002/PVE/Storage/ZFSPoolPlugin.pm#L168

zfs_create_zvol doesn't specify timeout when calling zfs_request which causes timeout to be 5 seconds. It's not enough in all cases which triggers timeout.

[dmshimself]

Very useful information - many thanks

[whiskerz007]

Try running the following and compare to the original script. Please report your findings.

bash -c "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassos_install/raw/patch-slow-zfs/install.sh)"

[dmshimself]

It worked perfectly. I put the server under as much load as I could. Lots of IO on the same zfs pool, lots of CPU use and it sales through. Specifically I got:

Getting URL for latest Home Assistant disk image... Downloading disk image... Extracting disk image... Creating VM... Adding serial port and configuring console... Installing 'kpartx'... [INFO] Completed Successfully! New VM ID is 120.

[HorstBoy]

Unfortunately that doesn't solve problem since both "pvesm alloc" and "qm importdisk" call "zfs create" with same 5 second timeout.

One can simulate how script behaves with slow zfs disk subsystem by playing with timeout setting on ZFSPoolPlugin.pm and setting it to something really low such as 100ms.

--- /usr/share/perl5/PVE/Storage/ZFSPoolPlugin.pm.orig  2020-07-14 14:58:24.000000000 +0300
+++ /usr/share/perl5/PVE/Storage/ZFSPoolPlugin.pm       2020-08-24 21:46:18.028085724 +0300
@@ -173,7 +173,7 @@
     my $msg = '';
     my $output = sub { $msg .= "$_[0]\n" };

-    $timeout = PVE::RPCEnvironment->is_worker() ? 60*60 : 5 if !$timeout;
+    $timeout = PVE::RPCEnvironment->is_worker() ? 60*60 : 0.1 if !$timeout;

     run_command($cmd, errmsg => "zfs error", outfunc => $output, timeout => $timeout);

[Psychoses]

hi,

same problem here some time on a zfs install.

i have try : bash -c "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassos_install/raw/patch-slow-zfs/install.sh)" but without success.

Finally, i got a successfull install with a simple sleep 15 between qm create and pvesm alloc

[mmychu]

Hello, same problem on my zfs with running another VM

Did like below: wget https://github.com/whiskerz007/proxmox_hassos_install/raw/master/install.sh to download script

firstly I got an error: Unable to handle file extension 'zip', so I did:

apt install unzip sed '/*"gz") gunzip -f $FILE;;/a\ \ *"zip") unzip -o $FILE;;' install.sh > temp.sh mv temp.sh install.sh chmod 755 install.sh

Later I added sleep 30 between qm create and pvesm alloc

type nano install.sh and add sleep 30 between qm create and pvesm alloc in "VM Create" section run script ./install.sh

My output: Before script modification:

root@proxmox:~# bash -c "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassos_install/raw/patch-slow-zfs/install.sh)" [INFO] Using 'local-zfs' for storage location. [INFO] Container ID is 103. Getting URL for latest Home Assistant disk image... Downloading disk image... Extracting disk image... Creating VM... [ERROR] 4@138 Unknown failure occured.

After script modification:

root@proxmox:~# nano install.sh root@proxmox:~# ./install.sh [INFO] Using 'local-zfs' for storage location. [INFO] Container ID is 103. Getting URL for latest Home Assistant disk image... Downloading disk image... Extracting disk image... Archive: haos_ova-6.2.vmdk.zip inflating: haos_ova-6.2.vmdk
Creating VM... Adding serial port and configuring console... Installing 'kpartx'... [INFO] Completed Successfully! New VM ID is 103.