Re: [Users] [Engine-devel] Autorecovery feature plan for review
On 02/14/2012 08:57 AM, Livnat Peer wrote: On 14/02/12 05:56, Itamar Heim wrote: On 02/13/2012 12:32 PM, Laszlo Hornyak wrote: Hi, Please review the plan document for autorecovery. http://www.ovirt.org/wiki/Features/Autorecovery why would we disable auto recovery by default? it sounds like the preferred behavior? I think that by default Laszlo meant in the upgrade process to maintain current behavior. I agree that for new entities the default should be true. i think the only combination which will allow this is for db to default to false and code to default to true for this property? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Engine-devel] Autorecovery feature plan for review
On 14/02/12 05:56, Itamar Heim wrote: > On 02/13/2012 12:32 PM, Laszlo Hornyak wrote: >> Hi, >> >> Please review the plan document for autorecovery. >> http://www.ovirt.org/wiki/Features/Autorecovery > > why would we disable auto recovery by default? it sounds like the > preferred behavior? > I think that by default Laszlo meant in the upgrade process to maintain current behavior. I agree that for new entities the default should be true. > ___ > Engine-devel mailing list > engine-de...@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt VM start fails - Perm Denied error
On 02/13/2012 08:10 PM, Dan Kenigsberg wrote: On Mon, Feb 13, 2012 at 08:57:23AM -0500, Keith Robertson wrote: On 02/13/2012 08:33 AM, Deepak C Shetty wrote: On 02/13/2012 03:16 PM, Dan Kenigsberg wrote: On Sun, Feb 12, 2012 at 11:58:05PM +0530, Deepak C Shetty wrote: Hi, I have tried this multiple times and i hit the same error. I have 3 storage domains created (iso, data and export) all connected to the DC with DC status as Up and 1 host with status as Up and the same (only) host acting as SPM. I used the engine-iso-uploader utility to upload my .iso to the iso domain. Created a new VM and attached a vdisk of type sparse (thin-prov) and click on "Run Once", where i select "Attach CD" and select my .iso, and change boot order to boot from CD, then disk. But i get this error... VM first-ovirt-vm is down. Exit message internal error process exited while connecting to monitor: qemu-kvm: -drive file=/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw: could not open disk image /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso: Permission denied . I am unable to figure out why.. bcos the user.group perms for the .iso are fine. In fact i logged into the system serving the nfs share and added 0777 perms still i get the same error. Here is the snip of how the perms for .iso look like... ll /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso -rwxr-xr-x. 1 vdsm kvm 3757047808 Feb 13 04:24 /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso would you try `ls -lZ` ? Does your /var/log/audit/audit.log shows an selinux problem? What's `getenforce`? And `getsebool virt_use_nfs`? What is `groups qemu`? Does su - qemu -s /bin/bash -c 'strings your.iso' work for you? Regards, Dan. Hello Dan, Here is the output you requested... [root@llm56 ~]# ls -lZ /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso -rwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0 /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso [root@llm56 ~]# getenforce Enforcing [root@llm56 ~]# getsebool virt_use_nfs virt_use_nfs --> off Vdsm SHOULD configure this to "on" when it first starts, by running /usr/sbin/semanage boolean -m -S targeted -F /dev/stdin<< _EOF virt_use_nfs=1 _EOF This hangs... tho' i see the below msgs in /var/log/messages... Feb 14 17:39:58 llm56 dbus[1170]: avc: received policyload notice (seqno=5) Feb 14 17:39:58 llm56 setsebool: The virt_use_nfs policy boolean was changed to 1 by root Feb 14 17:39:58 llm56 dbus[1170]: [system] Reloaded configuration Feb 14 17:39:58 llm56 dbus-daemon[1170]: dbus[1170]: avc: received policyload notice (seqno=5) Feb 14 17:39:58 llm56 dbus-daemon[1170]: dbus[1170]: [system] Reloaded configuration I had to kill this from anotehr session, but using setsebool virt_use_nfs 1 worked for me. /usr/sbin/setsebool virt_use_nfs on Please try running this as root to understand why it failed. qemu cannot use NFS when this is off and selinux is enforcing ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt VM start fails - Perm Denied error
On 02/13/2012 03:16 PM, Dan Kenigsberg wrote: On Sun, Feb 12, 2012 at 11:58:05PM +0530, Deepak C Shetty wrote: Hi, I have tried this multiple times and i hit the same error. I have 3 storage domains created (iso, data and export) all connected to the DC with DC status as Up and 1 host with status as Up and the same (only) host acting as SPM. I used the engine-iso-uploader utility to upload my .iso to the iso domain. Created a new VM and attached a vdisk of type sparse (thin-prov) and click on "Run Once", where i select "Attach CD" and select my .iso, and change boot order to boot from CD, then disk. But i get this error... VM first-ovirt-vm is down. Exit message internal error process exited while connecting to monitor: qemu-kvm: -drive file=/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw: could not open disk image /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso: Permission denied . I am unable to figure out why.. bcos the user.group perms for the .iso are fine. In fact i logged into the system serving the nfs share and added 0777 perms still i get the same error. Here is the snip of how the perms for .iso look like... ll /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso -rwxr-xr-x. 1 vdsm kvm 3757047808 Feb 13 04:24 /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso would you try `ls -lZ` ? Does your /var/log/audit/audit.log shows an selinux problem? What's `getenforce`? And `getsebool virt_use_nfs`? Hi Dan, Thanks for the hint, after setting virt_use_nfs, it worked for me. Strangely VDSM should have set it, not sure why it didn't. What is `groups qemu`? Does su - qemu -s /bin/bash -c 'strings your.iso' work for you? Regards, Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Hey using NFS as my main datastore
On 02/10/2012 03:28 AM, Douglas Landgraf wrote: Hi Dominic, On 02/09/2012 01:49 PM, Dominic Kaiser wrote: So I have fixed it! Thanks Itamar! It was chown -R 36:36 /path to my shared folder. I should have looked at the ovirt wiki also: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues. So all NFS shares up and my virtual servers are starting. Hi Dominic, I had the same "perm denied" issue even after having all the user.group stuff right. It ended up as VDSM not setting the selinux policy. It went away for me after running `setsebool virt_use_nfs 1` Strangely, this is not mentioned in the above troubleshooting guide/link, let me see if i can add it. Nice! Next time something similar happens, you might want to try nfs-check script: http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=commitdiff;h=578cfe90239d5c3f6f11f1fc063c148606e991dc Thanks! Hi Doug, I saw the script, it just gives a hint to check selinux booleans, but doesn't go into specific as to which booleans need to be set. Is there any other place in the ovirt wiki where the selinux booleans are mentioned so that users can map it to their setup and make changes accordingly to match it as mentioned in the wiki ? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Engine-devel] Autorecovery feature plan for review
On 02/13/2012 12:32 PM, Laszlo Hornyak wrote: Hi, Please review the plan document for autorecovery. http://www.ovirt.org/wiki/Features/Autorecovery why would we disable auto recovery by default? it sounds like the preferred behavior? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Pxeboot - pwd/login issue
On Mon, 2012-02-13 at 11:13 -0800, Li, David wrote: > Mike, > > Root pwd worked. Ssh is still broken. Haven't looked at ssh yet, but I will. > > su - admin produced an error message - too fast to be caputured with my eyes. > It seemed simiar to the one before. > ssh admin@ip also failed: > > ssh admin@192.168.36.114 > The authenticity of host '192.168.36.114 (192.168.36.114)' can't be > established. > RSA key fingerprint is 0b:e5:90:dd:68:15:e5:f4:d5:3c:34:83:b8:77:f4:a3. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '192.168.36.114' (RSA) to the list of known hosts. > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). Take your current git repository, and run: git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/80/1880/1 && git cherry-pick FETCH_HEAD That will get you a fix for the TUI to work in stateless. Mike > > > > - David > > From: Mike Burns [mbu...@redhat.com] > Sent: Monday, February 13, 2012 5:55 AM > To: Li, David > Cc: users@ovirt.org > Subject: RE: [Users] Pxeboot - pwd/login issue > > On Sat, 2012-02-11 at 07:39 -0800, Li, David wrote: > > Mike, > > > > Tried the new ssh patch and the problem still there. Both options were used > > BOOTIF and ssh_pwauth > > > > When I logged in first time and changed pwd, any subsequent logins were > > rejected. Again I couldn't capture the error message. > > > > Tried to ssh into the node, but was rejected too: > > > > [xxx oVirtNode]# ssh admin@192.168.36.114 > > The authenticity of host '192.168.36.114 (192.168.36.114)' can't be > > established. > > RSA key fingerprint is 23:6f:98:80:80:ec:d7:bb:e5:2a:02:59:93:85:38:39. > > Are you sure you want to continue connecting (yes/no)? yes > > Warning: Permanently added '192.168.36.114' (RSA) to the list of known > > hosts. > > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > > Hmm, looks like something isn't right with ssh_pwauth then. I'll look > into that, but for now, try using rootpw instead of adminpw. Then login > as root. Once you're in as root, you can su - admin to go the the TUI > (or in this case, get the stack trace for why the TUI is failing). > > Mike > > > > > > > - David > > > > From: Mike Burns [mbu...@redhat.com] > > Sent: Friday, February 10, 2012 11:34 AM > > To: Li, David > > Cc: users@ovirt.org > > Subject: RE: [Users] Pxeboot - pwd/login issue > > > > On Fri, 2012-02-10 at 11:22 -0800, Li, David wrote: > > > ok, I have already patched like this. Hope this is ok: > > > > > > [lid@FC16-1 ovirt-node]$ git fetch http://gerrit.ovirt.org/p/ovirt-node > > > refs/changes/07/1807/1 && git checkout FETCH_HEAD > > > remote: Counting objects: 57, done > > > remote: Finding sources: 100% (39/39) > > > remote: Total 39 (delta 28), reused 39 (delta 28) > > > Unpacking objects: 100% (39/39), done. > > > From http://gerrit.ovirt.org/p/ovirt-node > > > * branchrefs/changes/07/1807/1 -> FETCH_HEAD > > > Warning: you are leaving 1 commit behind, not connected to > > > any of your branches: > > > > > > 07d8a0f Add archipel option with stateless boot > > > > > > If you want to keep them by creating a new branch, this may be a good time > > > to do so with: > > > > > > git branch new_branch_name 07d8a0fc5007c5f74f9421b7a565cd2db2d9e772 > > > > > > HEAD is now at a94c33c... fix ssh_pwauth handling in autoinstall > > > [lid@FC16-1 ovirt-node]$ git fetch http://gerrit.ovirt.org/p/ovirt-node > > > refs/changes/08/1808/1 && git checkout FETCH_HEAD > > > remote: Counting objects: 62, done > > > remote: Finding sources: 100% (44/44) > > > remote: Total 44 (delta 32), reused 44 (delta 32) > > > Unpacking objects: 100% (44/44), done. > > > From http://gerrit.ovirt.org/p/ovirt-node > > > * branchrefs/changes/08/1808/1 -> FETCH_HEAD > > > Warning: you are leaving 5 commits behind, not connected to > > > any of your branches: > > > > > > a94c33c fix ssh_pwauth handling in autoinstall > > > 893a095 Add archipel option with stateless boot > > > a1053cb regenerate repos.ks when building iso > > > 237870c Add network configure before dropping into emergency shell > > > 5bb3613 add error handling to recent rhn.py commit > > > > > > If you want to keep them by creating a new branch, this may be a good time > > > to do so with: > > > > > > git branch new_branch_name a94c33c6d0957391a48ab0cd2e78e4a15e5ad80e > > > > > > HEAD is now at 3daa6d3... when stateless, don't execute store_config and > > > remove_config > > > [lid@FC16-1 ovirt-node]$ > > > > I *think* you're ok, because I pushed the commits such that this last > > command should get both. The way to check is to run > > > > $ git log > > > > and look at the commits in the log. You should see both the commits > > "fix ssh_pwauth handling..." and "when stateless..." commits at the top > > of the log. > > > > > > > > > > > ONE MORE QUESTION: do I need to run
Re: [Users] Pxeboot - pwd/login issue
Mike, Root pwd worked. Ssh is still broken. su - admin produced an error message - too fast to be caputured with my eyes. It seemed simiar to the one before. ssh admin@ip also failed: ssh admin@192.168.36.114 The authenticity of host '192.168.36.114 (192.168.36.114)' can't be established. RSA key fingerprint is 0b:e5:90:dd:68:15:e5:f4:d5:3c:34:83:b8:77:f4:a3. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.36.114' (RSA) to the list of known hosts. Permission denied (publickey,gssapi-keyex,gssapi-with-mic). - David From: Mike Burns [mbu...@redhat.com] Sent: Monday, February 13, 2012 5:55 AM To: Li, David Cc: users@ovirt.org Subject: RE: [Users] Pxeboot - pwd/login issue On Sat, 2012-02-11 at 07:39 -0800, Li, David wrote: > Mike, > > Tried the new ssh patch and the problem still there. Both options were used > BOOTIF and ssh_pwauth > > When I logged in first time and changed pwd, any subsequent logins were > rejected. Again I couldn't capture the error message. > > Tried to ssh into the node, but was rejected too: > > [xxx oVirtNode]# ssh admin@192.168.36.114 > The authenticity of host '192.168.36.114 (192.168.36.114)' can't be > established. > RSA key fingerprint is 23:6f:98:80:80:ec:d7:bb:e5:2a:02:59:93:85:38:39. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '192.168.36.114' (RSA) to the list of known hosts. > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). Hmm, looks like something isn't right with ssh_pwauth then. I'll look into that, but for now, try using rootpw instead of adminpw. Then login as root. Once you're in as root, you can su - admin to go the the TUI (or in this case, get the stack trace for why the TUI is failing). Mike > > > - David > > From: Mike Burns [mbu...@redhat.com] > Sent: Friday, February 10, 2012 11:34 AM > To: Li, David > Cc: users@ovirt.org > Subject: RE: [Users] Pxeboot - pwd/login issue > > On Fri, 2012-02-10 at 11:22 -0800, Li, David wrote: > > ok, I have already patched like this. Hope this is ok: > > > > [lid@FC16-1 ovirt-node]$ git fetch http://gerrit.ovirt.org/p/ovirt-node > > refs/changes/07/1807/1 && git checkout FETCH_HEAD > > remote: Counting objects: 57, done > > remote: Finding sources: 100% (39/39) > > remote: Total 39 (delta 28), reused 39 (delta 28) > > Unpacking objects: 100% (39/39), done. > > From http://gerrit.ovirt.org/p/ovirt-node > > * branchrefs/changes/07/1807/1 -> FETCH_HEAD > > Warning: you are leaving 1 commit behind, not connected to > > any of your branches: > > > > 07d8a0f Add archipel option with stateless boot > > > > If you want to keep them by creating a new branch, this may be a good time > > to do so with: > > > > git branch new_branch_name 07d8a0fc5007c5f74f9421b7a565cd2db2d9e772 > > > > HEAD is now at a94c33c... fix ssh_pwauth handling in autoinstall > > [lid@FC16-1 ovirt-node]$ git fetch http://gerrit.ovirt.org/p/ovirt-node > > refs/changes/08/1808/1 && git checkout FETCH_HEAD > > remote: Counting objects: 62, done > > remote: Finding sources: 100% (44/44) > > remote: Total 44 (delta 32), reused 44 (delta 32) > > Unpacking objects: 100% (44/44), done. > > From http://gerrit.ovirt.org/p/ovirt-node > > * branchrefs/changes/08/1808/1 -> FETCH_HEAD > > Warning: you are leaving 5 commits behind, not connected to > > any of your branches: > > > > a94c33c fix ssh_pwauth handling in autoinstall > > 893a095 Add archipel option with stateless boot > > a1053cb regenerate repos.ks when building iso > > 237870c Add network configure before dropping into emergency shell > > 5bb3613 add error handling to recent rhn.py commit > > > > If you want to keep them by creating a new branch, this may be a good time > > to do so with: > > > > git branch new_branch_name a94c33c6d0957391a48ab0cd2e78e4a15e5ad80e > > > > HEAD is now at 3daa6d3... when stateless, don't execute store_config and > > remove_config > > [lid@FC16-1 ovirt-node]$ > > I *think* you're ok, because I pushed the commits such that this last > command should get both. The way to check is to run > > $ git log > > and look at the commits in the log. You should see both the commits > "fix ssh_pwauth handling..." and "when stateless..." commits at the top > of the log. > > > > > > > ONE MORE QUESTION: do I need to run 'make publish' before make iso? > > Yes, always rerun make publish. In general, I'd say rerun the > autogen.sh too, but in this case you're fine. > > Mike > > > > - David > > > > From: Mike Burns [mbu...@redhat.com] > > Sent: Friday, February 10, 2012 11:19 AM > > To: Li, David > > Cc: users@ovirt.org > > Subject: Re: [Users] Pxeboot - pwd/login issue > > > > On Fri, 2012-02-10 at 11:09 -0800, Li, David wrote: > > > Ok, what's the right cmd to get both? Do I have to start from scratch? > > > > No need to
Re: [Users] Difference between RHEV and ovirt
- Original Message - > From: "patrick" > To: users@ovirt.org > Sent: Monday, February 13, 2012 12:14:00 PM > Subject: [Users] Difference between RHEV and ovirt > > Hello all, > > In our company we want to use either RHEV or oVirt in a production > environment. After testing RHEV for 30 days we are happy with the > stability and features. Can someone explain the difference between > RHEV and oVirt? Are there maybe some features just available in RHEV > like Windows guest drivers or someting like that? > I'm not sure if I get this right, but as oVirt is the upstream of > RHEV > does this means that new features like hot add nic etc. are first > available in oVirt and afterwards in RHEV. Does oVirt has any > drawbacks compared to RHEV other than support? > A good comparison would be Fedora and RHEL. All the development work happens upstream in oVirt, so new features appear in and are developed in oVirt. At some regular interval RHEV will be built from a snapshot of oVirt. It's not as simple as just taking the code as of Feb 13th and search/replace oVirt->RHEV there's stabilization, testing, certification (Microsoft SVVP, WHQL), etc. Then on top of that there's support, patches, security hotfixes, backports ... oVirt will always be a leading edge platform ahead of RHEV (and anyone else who decides to do a downstream distribution) so expect in most cases the oVirt release to be ahead of RHEV but given the fast release cadence for the next couple of years I don't think the feature gap will be significant. > Thanks in advance > Patrick van der Wiel > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt VM start fails - Perm Denied error
On 02/13/2012 08:57 AM, Keith Robertson wrote: On 02/13/2012 08:33 AM, Deepak C Shetty wrote: On 02/13/2012 03:16 PM, Dan Kenigsberg wrote: On Sun, Feb 12, 2012 at 11:58:05PM +0530, Deepak C Shetty wrote: Hi, I have tried this multiple times and i hit the same error. I have 3 storage domains created (iso, data and export) all connected to the DC with DC status as Up and 1 host with status as Up and the same (only) host acting as SPM. I used the engine-iso-uploader utility to upload my .iso to the iso domain. Created a new VM and attached a vdisk of type sparse (thin-prov) and click on "Run Once", where i select "Attach CD" and select my .iso, and change boot order to boot from CD, then disk. But i get this error... VM first-ovirt-vm is down. Exit message internal error process exited while connecting to monitor: qemu-kvm: -drive file=/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw: could not open disk image /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso: Permission denied . I am unable to figure out why.. bcos the user.group perms for the .iso are fine. In fact i logged into the system serving the nfs share and added 0777 perms still i get the same error. Here is the snip of how the perms for .iso look like... ll /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso -rwxr-xr-x. 1 vdsm kvm 3757047808 Feb 13 04:24 /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso would you try `ls -lZ` ? Does your /var/log/audit/audit.log shows an selinux problem? What's `getenforce`? And `getsebool virt_use_nfs`? What is `groups qemu`? Does su - qemu -s /bin/bash -c 'strings your.iso' work for you? Regards, Dan. Hello Dan, Here is the output you requested... [root@llm56 ~]# ls -lZ /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso -rwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0 /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso [root@llm56 ~]# getenforce Enforcing [root@llm56 ~]# getsebool virt_use_nfs virt_use_nfs --> off [root@llm56 ~]# groups qemu qemu : qemu kvm Also `su - qemu -s /bin/bash -c 'strings your.iso'` worked for me.. dumped loads of strings on the screen. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Perhaps I missed that snippet of logs, but is llm56 the hyper-visor? Also, here is another litmus test to help shake out some common NFS issues. Do the following from the hyper-visor: 1. temporarily give user vdsm in /etc/passwd a login shell (e.g. /bin/bash) 2. mkdir /mnt/testmount 3. mount :/path/to/iso/storage/domain /mnt/testmount 4. su - vdsm <-- Really important. 5. cd 35f880f8-bd0c-4063-b171-2ddaa59e1212/images/---- 6. touch test.txt 7. strings Fedora-16-x86_64-DVD.iso 8. reset vdsm in /etc/passwd to nologin Do 6 and 7 work? Cheers, Keith Here another suggestion, a tool, nfs-check: http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob_plain;f=contrib/nfs-check.py;h=1b763c66e053eae2c273048879aa98e634b04d7f;hb=578cfe90239d5c3f6f11f1fc063c148606e991dc -- Cheers Douglas ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Pxeboot - pwd/login issue
Mike, Ran into a problem at make ovirt-node-image.iso: ) ./node-creator ovirt-node-image.ks Traceback (most recent call last): File "/usr/bin/livecd-creator", line 210, in sys.exit(main()) File "/usr/bin/livecd-creator", line 167, in main ks = imgcreate.read_kickstart(options.kscfg) File "/usr/lib/python2.7/site-packages/imgcreate/kickstart.py", line 61, in read_kickstart e.args[0])) imgcreate.errors.KickstartError: Failed to read kickstart file '/mnt/storage/home/lid/ovirt-cache/node-creator-x86_64-tmp/ovirt-node-image.ks' : Local file does not exist: /mnt/storage/home/lid/ovirt-cache/node-creator-x86_64-tmp/ovirt-node-image.ks mv ovirt-node-image.iso ovirt-node-image-2.2.3-0.1.fc16.gitd7dbc01.iso mv: cannot stat `ovirt-node-image.iso': No such file or directory make: *** [ovirt-node-image.iso] Error 1 I checked but the file is there: [lid@fc16-lid recipe]$ ls -al /mnt/storage/home/lid/ovirt-cache/node-creator-x86_64-tmp/ovirt-node-image.ks -rw-r--r--. 1 lid Engineering 29910 Feb 13 09:13 /mnt/storage/home/lid/ovirt-cache/node-creator-x86_64-tmp/ovirt-node-image.ks Any clue? - David From: Mike Burns [mbu...@redhat.com] Sent: Monday, February 13, 2012 7:28 AM To: Li, David Cc: users@ovirt.org Subject: RE: [Users] Pxeboot - pwd/login issue On Mon, 2012-02-13 at 07:20 -0800, Li, David wrote: > Hi Mike, > > I will also double check my side starting from a new clone. To get all the > patches you 've put in for stateless, are these the steps I need to take? > > git clone http://gerrit.ovirt.org/p/ovirt-node.git > cd ovirt-node > git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/38/1738/3 don't need this one ^^. It's already in master. > git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/07/1807/1 && git > cherry-pick FETCH_HEAD > git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/08/1808/1 && git > cherry-pick FETCH_HEAD > > > David > > > >-Original Message- > >From: Mike Burns [mailto:mbu...@redhat.com] > >Sent: Monday, February 13, 2012 5:56 AM > >To: Li, David > >Cc: users@ovirt.org > >Subject: RE: [Users] Pxeboot - pwd/login issue > > > >On Sat, 2012-02-11 at 07:39 -0800, Li, David wrote: > >> Mike, > >> > >> Tried the new ssh patch and the problem still there. Both options were > >> used BOOTIF and ssh_pwauth > >> > >> When I logged in first time and changed pwd, any subsequent logins were > >rejected. Again I couldn't capture the error message. > >> > >> Tried to ssh into the node, but was rejected too: > >> > >> [xxx oVirtNode]# ssh admin@192.168.36.114 The authenticity of host > >> '192.168.36.114 (192.168.36.114)' can't be established. > >> RSA key fingerprint is 23:6f:98:80:80:ec:d7:bb:e5:2a:02:59:93:85:38:39. > >> Are you sure you want to continue connecting (yes/no)? yes > >> Warning: Permanently added '192.168.36.114' (RSA) to the list of known > >hosts. > >> Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > > > >Hmm, looks like something isn't right with ssh_pwauth then. I'll look into > >that, > >but for now, try using rootpw instead of adminpw. Then login as root. Once > >you're in as root, you can su - admin to go the the TUI (or in this case, > >get the > >stack trace for why the TUI is failing). > > > >Mike > > > >> > >> > >> - David > >> > >> From: Mike Burns [mbu...@redhat.com] > >> Sent: Friday, February 10, 2012 11:34 AM > >> To: Li, David > >> Cc: users@ovirt.org > >> Subject: RE: [Users] Pxeboot - pwd/login issue > >> > >> On Fri, 2012-02-10 at 11:22 -0800, Li, David wrote: > >> > ok, I have already patched like this. Hope this is ok: > >> > > >> > [lid@FC16-1 ovirt-node]$ git fetch > >> > http://gerrit.ovirt.org/p/ovirt-node refs/changes/07/1807/1 && git > >> > checkout FETCH_HEAD > >> > remote: Counting objects: 57, done > >> > remote: Finding sources: 100% (39/39) > >> > remote: Total 39 (delta 28), reused 39 (delta 28) Unpacking objects: > >> > 100% (39/39), done. > >> > From http://gerrit.ovirt.org/p/ovirt-node > >> > * branchrefs/changes/07/1807/1 -> FETCH_HEAD > >> > Warning: you are leaving 1 commit behind, not connected to any of > >> > your branches: > >> > > >> > 07d8a0f Add archipel option with stateless boot > >> > > >> > If you want to keep them by creating a new branch, this may be a > >> > good time to do so with: > >> > > >> > git branch new_branch_name > >07d8a0fc5007c5f74f9421b7a565cd2db2d9e772 > >> > > >> > HEAD is now at a94c33c... fix ssh_pwauth handling in autoinstall > >> > [lid@FC16-1 ovirt-node]$ git fetch > >> > http://gerrit.ovirt.org/p/ovirt-node refs/changes/08/1808/1 && git > >> > checkout FETCH_HEAD > >> > remote: Counting objects: 62, done > >> > remote: Finding sources: 100% (44/44) > >> > remote: Total 44 (delta 32), reused 44 (delta 32) Unpacking objects: > >> > 100% (44/44), done. > >> > From http://gerrit.ovirt.org/p/ovirt-node > >> > * branchrefs/c
[Users] Difference between RHEV and ovirt
Hello all, In our company we want to use either RHEV or oVirt in a production environment. After testing RHEV for 30 days we are happy with the stability and features. Can someone explain the difference between RHEV and oVirt? Are there maybe some features just available in RHEV like Windows guest drivers or someting like that? I'm not sure if I get this right, but as oVirt is the upstream of RHEV does this means that new features like hot add nic etc. are first available in oVirt and afterwards in RHEV. Does oVirt has any drawbacks compared to RHEV other than support? Thanks in advance Patrick van der Wiel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt VM start fails - Perm Denied error
- Original Message - > From: "Jason Brooks" > To: users@ovirt.org > Sent: Monday, February 13, 2012 11:21:00 AM > Subject: Re: [Users] ovirt VM start fails - Perm Denied error > > On 02/12/2012 10:28 AM, Deepak C Shetty wrote: > > Hi, > >I have tried this multiple times and i hit the same error. > > > > I have 3 storage domains created (iso, data and export) all > > connected > > to the DC with DC status as Up and > > 1 host with status as Up and the same (only) host acting as SPM. > > > > I used the engine-iso-uploader utility to upload my .iso to the iso > > domain. > > Created a new VM and attached a vdisk of type sparse (thin-prov) > > and > > click on "Run Once", > > where i select "Attach CD" and select my .iso, and change boot > > order to > > boot from CD, then disk. > > > > But i get this error... > > > > VM first-ovirt-vm is down. Exit message internal error process > > exited > > while connecting to monitor: qemu-kvm: -drive > > file=/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw: > > could not open disk image > > /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso: > > Permission denied . > > I hit this same issue last week, on an ovirt-engine that I'd updated > from nightly to stable. In order to get around the issue, I > completely > uninstalled ovirt and removed the /rhev/datacenter directory, which > wasn't removed automatically when I uninstalled ovirt. Once I did > that, > I was able to proceed normally. > /rhev/* Is there BZ to change this to ovirt? > Jason > > > > > > I am unable to figure out why.. bcos the user.group perms for the > > .iso > > are fine. > > In fact i logged into the system serving the nfs share and added > > 0777 perms > > still i get the same error. Here is the snip of how the perms for > > .iso > > look like... > > > > ll > > /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso > > > > -rwxr-xr-x. 1 vdsm kvm 3757047808 Feb 13 04:24 > > /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso > > > > > > Here are some of the imp. logs from the engine.log... note that i > > tried > > multiple times, so there are multiple > > entries of ERRORs for each of those tries... > > > > 2012-02-13 05:10:04,563 INFO > > [org.ovirt.engine.core.vdsbroker.UpdateVdsDynamicDataVDSCommand] > > (pool-5-thread-47) FINISH, UpdateVdsDynamicDataVDSCommand, log id: > > 549dfc2f > > 2012-02-13 05:10:04,612 INFO > > [org.ovirt.engine.core.bll.RunVmOnceCommand] (pool-5-thread-47) > > Running > > command: RunVmOnceCommand internal: false. Entities affected : ID: > > c587bc8e-f800-4ce4-a35e-1dd43480cb58 Type: VM > > 2012-02-13 05:10:04,617 ERROR > > [org.ovirt.engine.core.bll.RunVmCommand] > > (pool-5-thread-47) Cant find VDS to run the VM > > c587bc8e-f800-4ce4-a35e-1dd43480cb58 on, so this VM will not be > > run. > > 2012-02-13 05:10:04,622 ERROR > > [org.ovirt.engine.core.bll.RunVmOnceCommand] (pool-5-thread-47) > > Transaction rolled-back for command: > > org.ovirt.engine.core.bll.RunVmOnceCommand. > > 2012-02-13 05:11:25,735 INFO > > [org.ovirt.engine.core.bll.DbUserCacheManager] > > (QuartzScheduler_Worker-10) > > DbUserCacheManager::refreshAllUserData() - > > entered > > 2012-02-13 05:11:52,648 WARN > > [org.ovirt.engine.core.bll.GetConfigurationValueQuery] > > (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null > > version, using default general for version > > 2012-02-13 05:11:52,791 WARN > > [org.ovirt.engine.core.bll.GetConfigurationValueQuery] > > (http--0.0.0.0-8080-2) calling GetConfigurationValueQuery with null > > version, using default general for version > > 2012-02-13 05:11:55,828 WARN > > [org.ovirt.engine.core.bll.GetConfigurationValueQuery] > > (http--0.0.0.0-8080-8) calling GetConfigurationValueQuery with null > > version, using default general for version > > 2012-02-13 05:11:56,917 WARN > > [org.ovirt.engine.core.bll.GetConfigurationValueQuery] > > (http--0.0.0.0-8080-2) calling GetConfigurationValueQuery with null > > version, using default general for version > > 2012-02-13 05:12:11,611 INFO > > [org.ovirt.engine.core.bll.UpdateVmCommand] (http--0.0.0.0-8080-10) > > Running command: UpdateVmCommand internal: false. Entities affected > > : > > ID: c587bc8e-f800-4ce4-a35e-1dd43480cb58 Type: VM > > 2012-02-13 05:12:11,617 INFO > > [org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand] > > (http--0.0.0.0-8080-10) START, IsValidVDSCommand(storagePoolId = > > 4087fea7-b54a-4318-8d5c-828eff8846f4, ignoreFailoverLimit = false, > > compatabilityVersion = null), log id: 247cacfc > > 2012-02-13 05:12:11,619 IN
Re: [Users] ovirt VM start fails - Perm Denied error
On 02/12/2012 10:28 AM, Deepak C Shetty wrote: > Hi, >I have tried this multiple times and i hit the same error. > > I have 3 storage domains created (iso, data and export) all connected > to the DC with DC status as Up and > 1 host with status as Up and the same (only) host acting as SPM. > > I used the engine-iso-uploader utility to upload my .iso to the iso domain. > Created a new VM and attached a vdisk of type sparse (thin-prov) and > click on "Run Once", > where i select "Attach CD" and select my .iso, and change boot order to > boot from CD, then disk. > > But i get this error... > > VM first-ovirt-vm is down. Exit message internal error process exited > while connecting to monitor: qemu-kvm: -drive > file=/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw: > could not open disk image > /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso: > Permission denied . I hit this same issue last week, on an ovirt-engine that I'd updated from nightly to stable. In order to get around the issue, I completely uninstalled ovirt and removed the /rhev/datacenter directory, which wasn't removed automatically when I uninstalled ovirt. Once I did that, I was able to proceed normally. Jason > > I am unable to figure out why.. bcos the user.group perms for the .iso > are fine. > In fact i logged into the system serving the nfs share and added 0777 perms > still i get the same error. Here is the snip of how the perms for .iso > look like... > > ll > /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso > > -rwxr-xr-x. 1 vdsm kvm 3757047808 Feb 13 04:24 > /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso > > > Here are some of the imp. logs from the engine.log... note that i tried > multiple times, so there are multiple > entries of ERRORs for each of those tries... > > 2012-02-13 05:10:04,563 INFO > [org.ovirt.engine.core.vdsbroker.UpdateVdsDynamicDataVDSCommand] > (pool-5-thread-47) FINISH, UpdateVdsDynamicDataVDSCommand, log id: 549dfc2f > 2012-02-13 05:10:04,612 INFO > [org.ovirt.engine.core.bll.RunVmOnceCommand] (pool-5-thread-47) Running > command: RunVmOnceCommand internal: false. Entities affected : ID: > c587bc8e-f800-4ce4-a35e-1dd43480cb58 Type: VM > 2012-02-13 05:10:04,617 ERROR [org.ovirt.engine.core.bll.RunVmCommand] > (pool-5-thread-47) Cant find VDS to run the VM > c587bc8e-f800-4ce4-a35e-1dd43480cb58 on, so this VM will not be run. > 2012-02-13 05:10:04,622 ERROR > [org.ovirt.engine.core.bll.RunVmOnceCommand] (pool-5-thread-47) > Transaction rolled-back for command: > org.ovirt.engine.core.bll.RunVmOnceCommand. > 2012-02-13 05:11:25,735 INFO > [org.ovirt.engine.core.bll.DbUserCacheManager] > (QuartzScheduler_Worker-10) DbUserCacheManager::refreshAllUserData() - > entered > 2012-02-13 05:11:52,648 WARN > [org.ovirt.engine.core.bll.GetConfigurationValueQuery] > (http--0.0.0.0-8080-1) calling GetConfigurationValueQuery with null > version, using default general for version > 2012-02-13 05:11:52,791 WARN > [org.ovirt.engine.core.bll.GetConfigurationValueQuery] > (http--0.0.0.0-8080-2) calling GetConfigurationValueQuery with null > version, using default general for version > 2012-02-13 05:11:55,828 WARN > [org.ovirt.engine.core.bll.GetConfigurationValueQuery] > (http--0.0.0.0-8080-8) calling GetConfigurationValueQuery with null > version, using default general for version > 2012-02-13 05:11:56,917 WARN > [org.ovirt.engine.core.bll.GetConfigurationValueQuery] > (http--0.0.0.0-8080-2) calling GetConfigurationValueQuery with null > version, using default general for version > 2012-02-13 05:12:11,611 INFO > [org.ovirt.engine.core.bll.UpdateVmCommand] (http--0.0.0.0-8080-10) > Running command: UpdateVmCommand internal: false. Entities affected : > ID: c587bc8e-f800-4ce4-a35e-1dd43480cb58 Type: VM > 2012-02-13 05:12:11,617 INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand] > (http--0.0.0.0-8080-10) START, IsValidVDSCommand(storagePoolId = > 4087fea7-b54a-4318-8d5c-828eff8846f4, ignoreFailoverLimit = false, > compatabilityVersion = null), log id: 247cacfc > 2012-02-13 05:12:11,619 INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand] > (http--0.0.0.0-8080-10) FINISH, IsValidVDSCommand, return: true, log id: > 247cacfc > 2012-02-13 05:12:11,632 INFO > [org.ovirt.engine.core.vdsbroker.irsbroker.UpdateVMVDSCommand] > (http--0.0.0.0-8080-10) START, UpdateVMVDSCommand(storagePoolId = > 4087fea7-b54a-4318-8d5c-828eff8846f4, ignoreFailoverLimit = false, > compatabilityVersion = null, storageDomainId = > ----, info
Re: [Users] Pxeboot - pwd/login issue
On Mon, 2012-02-13 at 07:20 -0800, Li, David wrote: > Hi Mike, > > I will also double check my side starting from a new clone. To get all the > patches you 've put in for stateless, are these the steps I need to take? > > git clone http://gerrit.ovirt.org/p/ovirt-node.git > cd ovirt-node > git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/38/1738/3 don't need this one ^^. It's already in master. > git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/07/1807/1 && git > cherry-pick FETCH_HEAD > git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/08/1808/1 && git > cherry-pick FETCH_HEAD > > > David > > > >-Original Message- > >From: Mike Burns [mailto:mbu...@redhat.com] > >Sent: Monday, February 13, 2012 5:56 AM > >To: Li, David > >Cc: users@ovirt.org > >Subject: RE: [Users] Pxeboot - pwd/login issue > > > >On Sat, 2012-02-11 at 07:39 -0800, Li, David wrote: > >> Mike, > >> > >> Tried the new ssh patch and the problem still there. Both options were > >> used BOOTIF and ssh_pwauth > >> > >> When I logged in first time and changed pwd, any subsequent logins were > >rejected. Again I couldn't capture the error message. > >> > >> Tried to ssh into the node, but was rejected too: > >> > >> [xxx oVirtNode]# ssh admin@192.168.36.114 The authenticity of host > >> '192.168.36.114 (192.168.36.114)' can't be established. > >> RSA key fingerprint is 23:6f:98:80:80:ec:d7:bb:e5:2a:02:59:93:85:38:39. > >> Are you sure you want to continue connecting (yes/no)? yes > >> Warning: Permanently added '192.168.36.114' (RSA) to the list of known > >hosts. > >> Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > > > >Hmm, looks like something isn't right with ssh_pwauth then. I'll look into > >that, > >but for now, try using rootpw instead of adminpw. Then login as root. Once > >you're in as root, you can su - admin to go the the TUI (or in this case, > >get the > >stack trace for why the TUI is failing). > > > >Mike > > > >> > >> > >> - David > >> > >> From: Mike Burns [mbu...@redhat.com] > >> Sent: Friday, February 10, 2012 11:34 AM > >> To: Li, David > >> Cc: users@ovirt.org > >> Subject: RE: [Users] Pxeboot - pwd/login issue > >> > >> On Fri, 2012-02-10 at 11:22 -0800, Li, David wrote: > >> > ok, I have already patched like this. Hope this is ok: > >> > > >> > [lid@FC16-1 ovirt-node]$ git fetch > >> > http://gerrit.ovirt.org/p/ovirt-node refs/changes/07/1807/1 && git > >> > checkout FETCH_HEAD > >> > remote: Counting objects: 57, done > >> > remote: Finding sources: 100% (39/39) > >> > remote: Total 39 (delta 28), reused 39 (delta 28) Unpacking objects: > >> > 100% (39/39), done. > >> > From http://gerrit.ovirt.org/p/ovirt-node > >> > * branchrefs/changes/07/1807/1 -> FETCH_HEAD > >> > Warning: you are leaving 1 commit behind, not connected to any of > >> > your branches: > >> > > >> > 07d8a0f Add archipel option with stateless boot > >> > > >> > If you want to keep them by creating a new branch, this may be a > >> > good time to do so with: > >> > > >> > git branch new_branch_name > >07d8a0fc5007c5f74f9421b7a565cd2db2d9e772 > >> > > >> > HEAD is now at a94c33c... fix ssh_pwauth handling in autoinstall > >> > [lid@FC16-1 ovirt-node]$ git fetch > >> > http://gerrit.ovirt.org/p/ovirt-node refs/changes/08/1808/1 && git > >> > checkout FETCH_HEAD > >> > remote: Counting objects: 62, done > >> > remote: Finding sources: 100% (44/44) > >> > remote: Total 44 (delta 32), reused 44 (delta 32) Unpacking objects: > >> > 100% (44/44), done. > >> > From http://gerrit.ovirt.org/p/ovirt-node > >> > * branchrefs/changes/08/1808/1 -> FETCH_HEAD > >> > Warning: you are leaving 5 commits behind, not connected to any of > >> > your branches: > >> > > >> > a94c33c fix ssh_pwauth handling in autoinstall > >> > 893a095 Add archipel option with stateless boot > >> > a1053cb regenerate repos.ks when building iso > >> > 237870c Add network configure before dropping into emergency shell > >> > 5bb3613 add error handling to recent rhn.py commit > >> > > >> > If you want to keep them by creating a new branch, this may be a > >> > good time to do so with: > >> > > >> > git branch new_branch_name > >a94c33c6d0957391a48ab0cd2e78e4a15e5ad80e > >> > > >> > HEAD is now at 3daa6d3... when stateless, don't execute store_config > >> > and remove_config > >> > [lid@FC16-1 ovirt-node]$ > >> > >> I *think* you're ok, because I pushed the commits such that this last > >> command should get both. The way to check is to run > >> > >> $ git log > >> > >> and look at the commits in the log. You should see both the commits > >> "fix ssh_pwauth handling..." and "when stateless..." commits at the > >> top of the log. > >> > >> > > >> > > >> > ONE MORE QUESTION: do I need to run 'make publish' before make iso? > >> > >> Yes, always rerun make publish. In general, I'd say rerun the > >> autogen.sh too, but in this case you're fine. >
Re: [Users] Pxeboot - pwd/login issue
Hi Mike, I will also double check my side starting from a new clone. To get all the patches you 've put in for stateless, are these the steps I need to take? git clone http://gerrit.ovirt.org/p/ovirt-node.git cd ovirt-node git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/38/1738/3 git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/07/1807/1 && git cherry-pick FETCH_HEAD git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/08/1808/1 && git cherry-pick FETCH_HEAD David >-Original Message- >From: Mike Burns [mailto:mbu...@redhat.com] >Sent: Monday, February 13, 2012 5:56 AM >To: Li, David >Cc: users@ovirt.org >Subject: RE: [Users] Pxeboot - pwd/login issue > >On Sat, 2012-02-11 at 07:39 -0800, Li, David wrote: >> Mike, >> >> Tried the new ssh patch and the problem still there. Both options were >> used BOOTIF and ssh_pwauth >> >> When I logged in first time and changed pwd, any subsequent logins were >rejected. Again I couldn't capture the error message. >> >> Tried to ssh into the node, but was rejected too: >> >> [xxx oVirtNode]# ssh admin@192.168.36.114 The authenticity of host >> '192.168.36.114 (192.168.36.114)' can't be established. >> RSA key fingerprint is 23:6f:98:80:80:ec:d7:bb:e5:2a:02:59:93:85:38:39. >> Are you sure you want to continue connecting (yes/no)? yes >> Warning: Permanently added '192.168.36.114' (RSA) to the list of known >hosts. >> Permission denied (publickey,gssapi-keyex,gssapi-with-mic). > >Hmm, looks like something isn't right with ssh_pwauth then. I'll look into >that, >but for now, try using rootpw instead of adminpw. Then login as root. Once >you're in as root, you can su - admin to go the the TUI (or in this case, get >the >stack trace for why the TUI is failing). > >Mike > >> >> >> - David >> >> From: Mike Burns [mbu...@redhat.com] >> Sent: Friday, February 10, 2012 11:34 AM >> To: Li, David >> Cc: users@ovirt.org >> Subject: RE: [Users] Pxeboot - pwd/login issue >> >> On Fri, 2012-02-10 at 11:22 -0800, Li, David wrote: >> > ok, I have already patched like this. Hope this is ok: >> > >> > [lid@FC16-1 ovirt-node]$ git fetch >> > http://gerrit.ovirt.org/p/ovirt-node refs/changes/07/1807/1 && git >> > checkout FETCH_HEAD >> > remote: Counting objects: 57, done >> > remote: Finding sources: 100% (39/39) >> > remote: Total 39 (delta 28), reused 39 (delta 28) Unpacking objects: >> > 100% (39/39), done. >> > From http://gerrit.ovirt.org/p/ovirt-node >> > * branchrefs/changes/07/1807/1 -> FETCH_HEAD >> > Warning: you are leaving 1 commit behind, not connected to any of >> > your branches: >> > >> > 07d8a0f Add archipel option with stateless boot >> > >> > If you want to keep them by creating a new branch, this may be a >> > good time to do so with: >> > >> > git branch new_branch_name >07d8a0fc5007c5f74f9421b7a565cd2db2d9e772 >> > >> > HEAD is now at a94c33c... fix ssh_pwauth handling in autoinstall >> > [lid@FC16-1 ovirt-node]$ git fetch >> > http://gerrit.ovirt.org/p/ovirt-node refs/changes/08/1808/1 && git >> > checkout FETCH_HEAD >> > remote: Counting objects: 62, done >> > remote: Finding sources: 100% (44/44) >> > remote: Total 44 (delta 32), reused 44 (delta 32) Unpacking objects: >> > 100% (44/44), done. >> > From http://gerrit.ovirt.org/p/ovirt-node >> > * branchrefs/changes/08/1808/1 -> FETCH_HEAD >> > Warning: you are leaving 5 commits behind, not connected to any of >> > your branches: >> > >> > a94c33c fix ssh_pwauth handling in autoinstall >> > 893a095 Add archipel option with stateless boot >> > a1053cb regenerate repos.ks when building iso >> > 237870c Add network configure before dropping into emergency shell >> > 5bb3613 add error handling to recent rhn.py commit >> > >> > If you want to keep them by creating a new branch, this may be a >> > good time to do so with: >> > >> > git branch new_branch_name >a94c33c6d0957391a48ab0cd2e78e4a15e5ad80e >> > >> > HEAD is now at 3daa6d3... when stateless, don't execute store_config >> > and remove_config >> > [lid@FC16-1 ovirt-node]$ >> >> I *think* you're ok, because I pushed the commits such that this last >> command should get both. The way to check is to run >> >> $ git log >> >> and look at the commits in the log. You should see both the commits >> "fix ssh_pwauth handling..." and "when stateless..." commits at the >> top of the log. >> >> > >> > >> > ONE MORE QUESTION: do I need to run 'make publish' before make iso? >> >> Yes, always rerun make publish. In general, I'd say rerun the >> autogen.sh too, but in this case you're fine. >> >> Mike >> > >> > - David >> > >> > From: Mike Burns [mbu...@redhat.com] >> > Sent: Friday, February 10, 2012 11:19 AM >> > To: Li, David >> > Cc: users@ovirt.org >> > Subject: Re: [Users] Pxeboot - pwd/login issue >> > >> > On Fri, 2012-02-10 at 11:09 -0800, Li, David wrote: >> > > Ok, what's the right cmd to get both?
Re: [Users] ovirt VM start fails - Perm Denied error
On Mon, Feb 13, 2012 at 08:57:23AM -0500, Keith Robertson wrote: > On 02/13/2012 08:33 AM, Deepak C Shetty wrote: > >On 02/13/2012 03:16 PM, Dan Kenigsberg wrote: > >>On Sun, Feb 12, 2012 at 11:58:05PM +0530, Deepak C Shetty wrote: > >>>Hi, > >>>I have tried this multiple times and i hit the same error. > >>> > >>>I have 3 storage domains created (iso, data and export) all > >>>connected to the DC with DC status as Up and > >>>1 host with status as Up and the same (only) host acting as SPM. > >>> > >>>I used the engine-iso-uploader utility to upload my .iso to > >>>the iso domain. > >>>Created a new VM and attached a vdisk of type sparse (thin-prov) and > >>>click on "Run Once", > >>>where i select "Attach CD" and select my .iso, and change boot order > >>>to boot from CD, then disk. > >>> > >>>But i get this error... > >>> > >>>VM first-ovirt-vm is down. Exit message internal error process > >>>exited while connecting to monitor: qemu-kvm: -drive > >>>file=/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw: > >>>could not open disk image > >>>/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso: > >>>Permission denied . > >>> > >>>I am unable to figure out why.. bcos the user.group perms for the > >>>.iso are fine. > >>>In fact i logged into the system serving the nfs share and > >>>added 0777 perms > >>>still i get the same error. Here is the snip of how the perms for > >>>.iso look like... > >>> > >>>ll > >>>/tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso > >>>-rwxr-xr-x. 1 vdsm kvm 3757047808 Feb 13 04:24 > >>>/tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso > >>would you try `ls -lZ` ? Does your /var/log/audit/audit.log shows an > >>selinux problem? What's `getenforce`? And `getsebool virt_use_nfs`? > >> > >>What is `groups qemu`? > >>Does > >>su - qemu -s /bin/bash -c 'strings your.iso' > >>work for you? > >> > >>Regards, > >>Dan. > >> > >> > > > >Hello Dan, > >Here is the output you requested... > > > >[root@llm56 ~]# ls -lZ > >/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso > >-rwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0 > >/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso > > > >[root@llm56 ~]# getenforce > >Enforcing > > > >[root@llm56 ~]# getsebool virt_use_nfs > >virt_use_nfs --> off Vdsm SHOULD configure this to "on" when it first starts, by running /usr/sbin/semanage boolean -m -S targeted -F /dev/stdin << _EOF virt_use_nfs=1 _EOF /usr/sbin/setsebool virt_use_nfs on Please try running this as root to understand why it failed. qemu cannot use NFS when this is off and selinux is enforcing. > > > >[root@llm56 ~]# groups qemu > >qemu : qemu kvm > > > >Also `su - qemu -s /bin/bash -c 'strings your.iso'` > > > >worked for me.. dumped loads of strings on the screen. > > > >___ > >Users mailing list > >Users@ovirt.org > >http://lists.ovirt.org/mailman/listinfo/users > Perhaps I missed that snippet of logs, but is llm56 the hyper-visor? > > Also, here is another litmus test to help shake out some common NFS > issues. Do the following from the hyper-visor: > 1. temporarily give user vdsm in /etc/passwd a login shell (e.g. /bin/bash) > 2. mkdir /mnt/testmount > 3. mount :/path/to/iso/storage/domain /mnt/testmount > 4. su - vdsm <-- Really important. unrelated comment: if you add '-s /bin/bash' you can avoid steps 1 and 8. > 5. cd > 35f880f8-bd0c-4063-b171-2ddaa59e1212/images/---- > 6. touch test.txt > 7. strings Fedora-16-x86_64-DVD.iso > 8. reset vdsm in /etc/passwd to nologin > > Do 6 and 7 work? > > Cheers, > Keith ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problem with required packages when installingovirt-engine
>> The problem is that you are installing fedora packages into SL. They were >> really built for Fedora. They may actually work, but I believe that their >> are some packages missing from base repos for RHEL, SL, and CentOS. On >> RHEL, you would get those packages when you added RHEV. I don't think they >> exist for SL or CentOS. Look through the January messages on this board. >> SOmeone was doing the install on one of the EL clones and you may find more >> info there. Otherwise you could try using Fedora. > Thank you. Yes, I naively assumed that this would install on any > reasonablly current RPM-based system, since I didn't see (and still > don't see) any system requirements anywhere in any docs that suggest > otherwise. All I see says "point to our yum repo and install it". When > I saw the failed dependencies when I tries to install the engine, I > started to suspect that this was based on a far "newer" system than I > had. > I have now installed Fedora 16, and will try again. > ___ I am somewhat surprised this is not supported for SL or CentOS considering the main target audience would presumably be Admins with many critical VM's to manage. Fedora being generally considered not really suitable in Production. Maybe I'm missing something here. ** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. ** Consumer Testing Laboratories, Inc., Confidential ** ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt VM start fails - Perm Denied error
On 02/13/2012 08:33 AM, Deepak C Shetty wrote: On 02/13/2012 03:16 PM, Dan Kenigsberg wrote: On Sun, Feb 12, 2012 at 11:58:05PM +0530, Deepak C Shetty wrote: Hi, I have tried this multiple times and i hit the same error. I have 3 storage domains created (iso, data and export) all connected to the DC with DC status as Up and 1 host with status as Up and the same (only) host acting as SPM. I used the engine-iso-uploader utility to upload my .iso to the iso domain. Created a new VM and attached a vdisk of type sparse (thin-prov) and click on "Run Once", where i select "Attach CD" and select my .iso, and change boot order to boot from CD, then disk. But i get this error... VM first-ovirt-vm is down. Exit message internal error process exited while connecting to monitor: qemu-kvm: -drive file=/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw: could not open disk image /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso: Permission denied . I am unable to figure out why.. bcos the user.group perms for the .iso are fine. In fact i logged into the system serving the nfs share and added 0777 perms still i get the same error. Here is the snip of how the perms for .iso look like... ll /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso -rwxr-xr-x. 1 vdsm kvm 3757047808 Feb 13 04:24 /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso would you try `ls -lZ` ? Does your /var/log/audit/audit.log shows an selinux problem? What's `getenforce`? And `getsebool virt_use_nfs`? What is `groups qemu`? Does su - qemu -s /bin/bash -c 'strings your.iso' work for you? Regards, Dan. Hello Dan, Here is the output you requested... [root@llm56 ~]# ls -lZ /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso -rwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0 /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso [root@llm56 ~]# getenforce Enforcing [root@llm56 ~]# getsebool virt_use_nfs virt_use_nfs --> off [root@llm56 ~]# groups qemu qemu : qemu kvm Also `su - qemu -s /bin/bash -c 'strings your.iso'` worked for me.. dumped loads of strings on the screen. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Perhaps I missed that snippet of logs, but is llm56 the hyper-visor? Also, here is another litmus test to help shake out some common NFS issues. Do the following from the hyper-visor: 1. temporarily give user vdsm in /etc/passwd a login shell (e.g. /bin/bash) 2. mkdir /mnt/testmount 3. mount :/path/to/iso/storage/domain /mnt/testmount 4. su - vdsm <-- Really important. 5. cd 35f880f8-bd0c-4063-b171-2ddaa59e1212/images/---- 6. touch test.txt 7. strings Fedora-16-x86_64-DVD.iso 8. reset vdsm in /etc/passwd to nologin Do 6 and 7 work? Cheers, Keith ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Pxeboot - pwd/login issue
On Sat, 2012-02-11 at 07:39 -0800, Li, David wrote: > Mike, > > Tried the new ssh patch and the problem still there. Both options were used > BOOTIF and ssh_pwauth > > When I logged in first time and changed pwd, any subsequent logins were > rejected. Again I couldn't capture the error message. > > Tried to ssh into the node, but was rejected too: > > [xxx oVirtNode]# ssh admin@192.168.36.114 > The authenticity of host '192.168.36.114 (192.168.36.114)' can't be > established. > RSA key fingerprint is 23:6f:98:80:80:ec:d7:bb:e5:2a:02:59:93:85:38:39. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '192.168.36.114' (RSA) to the list of known hosts. > Permission denied (publickey,gssapi-keyex,gssapi-with-mic). Hmm, looks like something isn't right with ssh_pwauth then. I'll look into that, but for now, try using rootpw instead of adminpw. Then login as root. Once you're in as root, you can su - admin to go the the TUI (or in this case, get the stack trace for why the TUI is failing). Mike > > > - David > > From: Mike Burns [mbu...@redhat.com] > Sent: Friday, February 10, 2012 11:34 AM > To: Li, David > Cc: users@ovirt.org > Subject: RE: [Users] Pxeboot - pwd/login issue > > On Fri, 2012-02-10 at 11:22 -0800, Li, David wrote: > > ok, I have already patched like this. Hope this is ok: > > > > [lid@FC16-1 ovirt-node]$ git fetch http://gerrit.ovirt.org/p/ovirt-node > > refs/changes/07/1807/1 && git checkout FETCH_HEAD > > remote: Counting objects: 57, done > > remote: Finding sources: 100% (39/39) > > remote: Total 39 (delta 28), reused 39 (delta 28) > > Unpacking objects: 100% (39/39), done. > > From http://gerrit.ovirt.org/p/ovirt-node > > * branchrefs/changes/07/1807/1 -> FETCH_HEAD > > Warning: you are leaving 1 commit behind, not connected to > > any of your branches: > > > > 07d8a0f Add archipel option with stateless boot > > > > If you want to keep them by creating a new branch, this may be a good time > > to do so with: > > > > git branch new_branch_name 07d8a0fc5007c5f74f9421b7a565cd2db2d9e772 > > > > HEAD is now at a94c33c... fix ssh_pwauth handling in autoinstall > > [lid@FC16-1 ovirt-node]$ git fetch http://gerrit.ovirt.org/p/ovirt-node > > refs/changes/08/1808/1 && git checkout FETCH_HEAD > > remote: Counting objects: 62, done > > remote: Finding sources: 100% (44/44) > > remote: Total 44 (delta 32), reused 44 (delta 32) > > Unpacking objects: 100% (44/44), done. > > From http://gerrit.ovirt.org/p/ovirt-node > > * branchrefs/changes/08/1808/1 -> FETCH_HEAD > > Warning: you are leaving 5 commits behind, not connected to > > any of your branches: > > > > a94c33c fix ssh_pwauth handling in autoinstall > > 893a095 Add archipel option with stateless boot > > a1053cb regenerate repos.ks when building iso > > 237870c Add network configure before dropping into emergency shell > > 5bb3613 add error handling to recent rhn.py commit > > > > If you want to keep them by creating a new branch, this may be a good time > > to do so with: > > > > git branch new_branch_name a94c33c6d0957391a48ab0cd2e78e4a15e5ad80e > > > > HEAD is now at 3daa6d3... when stateless, don't execute store_config and > > remove_config > > [lid@FC16-1 ovirt-node]$ > > I *think* you're ok, because I pushed the commits such that this last > command should get both. The way to check is to run > > $ git log > > and look at the commits in the log. You should see both the commits > "fix ssh_pwauth handling..." and "when stateless..." commits at the top > of the log. > > > > > > > ONE MORE QUESTION: do I need to run 'make publish' before make iso? > > Yes, always rerun make publish. In general, I'd say rerun the > autogen.sh too, but in this case you're fine. > > Mike > > > > - David > > > > From: Mike Burns [mbu...@redhat.com] > > Sent: Friday, February 10, 2012 11:19 AM > > To: Li, David > > Cc: users@ovirt.org > > Subject: Re: [Users] Pxeboot - pwd/login issue > > > > On Fri, 2012-02-10 at 11:09 -0800, Li, David wrote: > > > Ok, what's the right cmd to get both? Do I have to start from scratch? > > > > No need to start from scratch. > > > > First, figure out the name of the remote. > > $ git remote show > > It will most likely return just one entry, and it's probably named > > origin. If it's something other than origin, then just substitute in > > the following commands: > > > > $ git fetch origin > > $ git reset --hard origin/master > > $ git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/07/1807/1 && > > git cherry-pick FETCH_HEAD > > $ git fetch http://gerrit.ovirt.org/p/ovirt-node refs/changes/08/1808/1 && > > git cherry-pick FETCH_HEAD > > > > $ git status # should show something like: > > # On branch master > > # Your branch is ahead of 'origin/master' by 2 commits. > > > > Now you should be good to build. > > > > Mike > > > > > > >-Ori
Re: [Users] ovirt VM start fails - Perm Denied error
On 02/13/2012 03:16 PM, Dan Kenigsberg wrote: On Sun, Feb 12, 2012 at 11:58:05PM +0530, Deepak C Shetty wrote: Hi, I have tried this multiple times and i hit the same error. I have 3 storage domains created (iso, data and export) all connected to the DC with DC status as Up and 1 host with status as Up and the same (only) host acting as SPM. I used the engine-iso-uploader utility to upload my .iso to the iso domain. Created a new VM and attached a vdisk of type sparse (thin-prov) and click on "Run Once", where i select "Attach CD" and select my .iso, and change boot order to boot from CD, then disk. But i get this error... VM first-ovirt-vm is down. Exit message internal error process exited while connecting to monitor: qemu-kvm: -drive file=/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw: could not open disk image /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso: Permission denied . I am unable to figure out why.. bcos the user.group perms for the .iso are fine. In fact i logged into the system serving the nfs share and added 0777 perms still i get the same error. Here is the snip of how the perms for .iso look like... ll /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso -rwxr-xr-x. 1 vdsm kvm 3757047808 Feb 13 04:24 /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso would you try `ls -lZ` ? Does your /var/log/audit/audit.log shows an selinux problem? What's `getenforce`? And `getsebool virt_use_nfs`? What is `groups qemu`? Does su - qemu -s /bin/bash -c 'strings your.iso' work for you? Regards, Dan. Hello Dan, Here is the output you requested... [root@llm56 ~]# ls -lZ /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso -rwxr-xr-x. vdsm kvm system_u:object_r:nfs_t:s0 /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso [root@llm56 ~]# getenforce Enforcing [root@llm56 ~]# getsebool virt_use_nfs virt_use_nfs --> off [root@llm56 ~]# groups qemu qemu : qemu kvm Also `su - qemu -s /bin/bash -c 'strings your.iso'` worked for me.. dumped loads of strings on the screen. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Autorecovery feature plan for review
On 02/13/2012 01:31 PM, Oved Ourfalli wrote: > Some comments: > 1. I think the amount of time between tests should be configurable. > 2. I guess some of the actions done by the autorecovery process should be > monitored, so take a look at > "http://www.ovirt.org/wiki/Features/TaskManagerDetailed#Job_for_System_Monitors"; > in order to monitor this action. We plan to insert monitoring at phase2. > > Oved > > - Original Message - >> From: "Laszlo Hornyak" >> To: "engine-devel" , users@ovirt.org >> Sent: Monday, February 13, 2012 12:32:34 PM >> Subject: [Users] Autorecovery feature plan for review >> >> Hi, >> >> Please review the plan document for autorecovery. >> http://www.ovirt.org/wiki/Features/Autorecovery >> >> Thank you, >> Laszlo >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Autorecovery feature plan for review
Some comments: 1. I think the amount of time between tests should be configurable. 2. I guess some of the actions done by the autorecovery process should be monitored, so take a look at "http://www.ovirt.org/wiki/Features/TaskManagerDetailed#Job_for_System_Monitors"; in order to monitor this action. Oved - Original Message - > From: "Laszlo Hornyak" > To: "engine-devel" , users@ovirt.org > Sent: Monday, February 13, 2012 12:32:34 PM > Subject: [Users] Autorecovery feature plan for review > > Hi, > > Please review the plan document for autorecovery. > http://www.ovirt.org/wiki/Features/Autorecovery > > Thank you, > Laszlo > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Autorecovery feature plan for review
Hi, Please review the plan document for autorecovery. http://www.ovirt.org/wiki/Features/Autorecovery Thank you, Laszlo ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] ovirt VM start fails - Perm Denied error
On Sun, Feb 12, 2012 at 11:58:05PM +0530, Deepak C Shetty wrote: > Hi, >I have tried this multiple times and i hit the same error. > > I have 3 storage domains created (iso, data and export) all > connected to the DC with DC status as Up and > 1 host with status as Up and the same (only) host acting as SPM. > > I used the engine-iso-uploader utility to upload my .iso to the iso domain. > Created a new VM and attached a vdisk of type sparse (thin-prov) and > click on "Run Once", > where i select "Attach CD" and select my .iso, and change boot order > to boot from CD, then disk. > > But i get this error... > > VM first-ovirt-vm is down. Exit message internal error process > exited while connecting to monitor: qemu-kvm: -drive > file=/rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw: > could not open disk image > /rhev/data-center/4087fea7-b54a-4318-8d5c-828eff8846f4/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso: > Permission denied . > > I am unable to figure out why.. bcos the user.group perms for the > .iso are fine. > In fact i logged into the system serving the nfs share and added 0777 perms > still i get the same error. Here is the snip of how the perms for > .iso look like... > > ll > /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso > -rwxr-xr-x. 1 vdsm kvm 3757047808 Feb 13 04:24 > /tmp/iso1-domain/35f880f8-bd0c-4063-b171-2ddaa59e1212/images/----/Fedora-16-x86_64-DVD.iso would you try `ls -lZ` ? Does your /var/log/audit/audit.log shows an selinux problem? What's `getenforce`? And `getsebool virt_use_nfs`? What is `groups qemu`? Does su - qemu -s /bin/bash -c 'strings your.iso' work for you? Regards, Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
