-
Notifications
You must be signed in to change notification settings - Fork 6
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
not bootable disk #1
Comments
https://github.com/OpenNebula/addon-lxdone/blob/master/image-handling/build-img.sh is intended for creating a base image from scratch, if you have an existing LXC container read https://github.com/OpenNebula/addon-lxdone/blob/master/Image.md there are instructions for that case. Also mount the image created and list the contents inside it |
I tried both ways - none works No errors on every step from tutorial I am using latest clone from github below image from ONE NAME : lxdone PERMISSIONS IMAGE TEMPLATE also ONE template ID : 7 PERMISSIONS TEMPLATE CONTENTS |
Let's inspect the contents of the image you created. Try
If there were no errors during the execution of build-img.sh I'd expect the image is fine. The below commands are supposed to do that. Also give me the screenshot of the VNC error. I suspect your host is using KVM because that particular output
I've seen it when using virt-manager |
yes of course drwx------ 2 root root 16K Apr 3 19:39 lost+found |
Try |
/mnt: /mnt/rootfs/: /mnt/templates/: |
Read and follow carefully https://github.com/OpenNebula/addon-lxdone/blob/master/Setup.md#42-virtualization-node seems you made some mistake there |
Thanks for your suggestions. I wonder is it normal behaviour and I must create network config manually in every lxd VM? |
The VMs were initialized in that host because the Opennebula scheduler's decision. You must specify an LXD host (or a cluster) within it's template to avoid such behavior. We remove eth0 from the default profile because we want to, inside the containers, only interfaces that we attached from it's template. If you skip that step, containers will have an interface that was not declared inside Opennebula. Contextualization, for example, will not work. |
if you leave eth0 in the default lxd profile that network interface won't be controlled by OpenNebula, and that's not what we aim. |
I follow tutorial
https://github.com/OpenNebula/addon-lxdone/blob/master/Setup.md
unfortunately after creating VM with no errors
i get in VNC message
Booting from Hard Disk
Boot failed: not a bootable disk
I tried images create from exported existing LXC container and also
build-img.sh script provided from addon-lxdone
https://github.com/OpenNebula/addon-lxdone/blob/master/image-handling/build-img.sh
what am i forgot?
regards
The text was updated successfully, but these errors were encountered: