(looks like list archive is down - 403/404) Following a short chat with some good folks in the #IRC channel, indications are that it could relate to permissions.
I've done most/all of my testing as oneadmin on localhost, to keep it relative consistent with some of the docs/guides. For `grep "oneadmin" /etc/group` (keep in mind this is still default from guides) CentOS: oneadmin:x:9869: Ubuntu: oneadmin:x:9869: kvm:x:111:oneadmin libvirtd:x:112:$me,oneadmin What I've found out through trial&error/process-of-elimination: * can create an instance if I don't attach any media to it (i.e. CD & HDD), but netboot only. (both hosts) * can create an instance if I attach up uploaded ubuntu-14.04-desktop-amd64.iso live-boot image, but it fails to boot with VNC: "Boot failed: Could not boot from CDROM (code 0004)" (both hosts) * I've imported ttylinux - kvm (ID#4fc76a938fb81d3517000003) from the store to localhost & created template around it, but it fails to instantiate on Ubuntu - not seeing anything in an empty $VMID.log (CentOS only). Both are fresh boxed (new host OS installations from scratch) running Ubuntu 14.04 LTS & CentOS 7, so there could be slight differences in their respective implementations that I'm missing. This *could* suggest to me that it could have something to do with image integrity, or the data is unreadable/unwritable? What bugs me is why the market images work on the CentOS box, but not the ISO's, or market images or ISO's on the Ubuntu counterpart - same user, same auth, same back-end subsystems. Almost identical hosts & scenario's. Was hoping that I could simply grab the /var/lib/one//datastores/0/$VMID/deployment.0 for a failing provisioning/instantiation & test/deploy it manually using lower-level KVM/libwirt CLI, but it looks like the OpenNebula implementation differs somewhat from the stock I'm used to. Any help to drill down in this issue & find the underlying cause would be appreciated. Cheers - J On Tue, Oct 21, 2014 at 12:50 PM, BakGat Net <[email protected]> wrote: > I tried a next step by provisioning my own VM's from ISO. > I'm following this handy webcast ( > https://www.youtube.com/watch?v=fQP4NQQ9NSI) & it gells mostly with my > understanding & experience with such systems, but the errors I indicated > before has presented again (doing this all now via SunStone GUI - testing) > for an Ubuntu mini instance I'm trying to fire up. > > This seems to be a fairly generic error with no real indicator as to where > what's failing: > > Tue Oct 21 12:39:29 2014 [Z0][DiM][I]: New VM state is ACTIVE. > Tue Oct 21 12:39:29 2014 [Z0][LCM][I]: New VM state is PROLOG. > Tue Oct 21 12:39:30 2014 [Z0][LCM][I]: New VM state is BOOT > Tue Oct 21 12:39:30 2014 [Z0][VMM][I]: Generating deployment file: > /var/lib/one/vms/20/deployment.0 > Tue Oct 21 12:39:31 2014 [Z0][VMM][I]: ExitCode: 0 > Tue Oct 21 12:39:31 2014 [Z0][VMM][I]: Successfully execute network driver > operation: pre. > Tue Oct 21 12:39:31 2014 [Z0][VMM][I]: Command execution fail: cat << EOT > | /var/tmp/one/vmm/kvm/deploy '/var/lib/one//datastores/0/20/deployment.0' > 'localhost' 20 localhost > Tue Oct 21 12:39:31 2014 [Z0][VMM][I]: error: Failed to create domain from > /var/lib/one//datastores/0/20/deployment.0 > Tue Oct 21 12:39:31 2014 [Z0][VMM][I]: error: Failed to open file > '/var/lib/one//datastores/0/20/disk.0': No such file or directory > Tue Oct 21 12:39:31 2014 [Z0][VMM][E]: Could not create domain from > /var/lib/one//datastores/0/20/deployment.0 > Tue Oct 21 12:39:31 2014 [Z0][VMM][I]: ExitCode: 255 > Tue Oct 21 12:39:31 2014 [Z0][VMM][I]: Failed to execute virtualization > driver operation: deploy. > Tue Oct 21 12:39:31 2014 [Z0][VMM][E]: Error deploying virtual machine: > Could not create domain from /var/lib/one//datastores/0/20/deployment.0 > Tue Oct 21 12:39:31 2014 [Z0][DiM][I]: New VM state is FAILED > > "/var/lib/one//datastores/0/20/deployment.0" exists as an XML file, but: > "Failed to open file '/var/lib/one//datastores/0/20/disk.0': No such file > or directory". > > This stack is still relatively new to me, so I still need to get up to > speed re methods & understanding relative logs. > > There seems to be something wrong with the mailinglist: getting a 403/404 > for http://lists.opennebula.org/pipermail/users-opennebula.org/, so I > can't even look up any previous resolutions. > > Any good resources I could/should look at in trying to decypher the above? > I've gone into the respective configs hinted at there, and nothing stands > out as immediately wrong >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
