Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mount warning and VM not Start #125

Open
hellresistor opened this issue Dec 8, 2021 · 2 comments
Open

Mount warning and VM not Start #125

hellresistor opened this issue Dec 8, 2021 · 2 comments

Comments

@hellresistor
Copy link

hellresistor commented Dec 8, 2021

# bash -c "$(wget -qLO - https://github.com/whiskerz007/proxmox_hassos_install/raw/master/install.sh)"
[INFO] Using 'local' for storage location.
[INFO] Container ID is 100.
Getting URL for latest Home Assistant disk image...
Downloading disk image...
Extracting disk image...
Creating VM...
Adding serial port and configuring console...
mount: /tmp/tmp.OUTPOb4HdB/mnt: /dev/mapper is not a block device.
[WARNING] Unable to configure serial port. VM is still functional.
loop deleted : /dev/loop0
[INFO] Completed Successfully! New VM ID is 100.

Unable to Start VM

()
kvm: device requires 67108864 bytes, block backend provides 131072 bytes
TASK ERROR: start failed: QEMU exited with code 1

prox1
prox2

Have tried resize disk
# qm resize 100 efidisk0 +256M

But keeps the same message

kvm: device requires 67108864 bytes, block backend provides 268566528 bytes
TASK ERROR: start failed: QEMU exited with code 1
@hellresistor hellresistor changed the title Mount warning? Mount warning and VM not Start Dec 8, 2021
@hellresistor
Copy link
Author

after a little change on script replacing Variable 'vmdk' to 'qcow2'
and execute a more precise EFIdisk space 'qm resize 100 efidisk0 +65408K'
I am able start the VM, BUT stays here :|

proxhanotboot

@meichthys
Copy link

meichthys commented Dec 23, 2021

I get this often. Not sure why.
To get things going you can try this from the host machine:

# Make sure VM is disabled:
ha-manager set vm:<VMID> --state disabled
# Open GDISK to modify disk partition map
gdisk /dev/zvol/rpool/vm-<VMID>-disk-<DISK#>
# Once GDISK opens, then just use the W command to re-write the partiion map
# Re-enable (start) VM to verify the VM boots using the disk
ha-manager set vm:<VMID> --state enabled

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants