- Users - oVirt List Archives

[Users] Still unable to boot in system with UEFI
by Federico Alberto Sayd 15 Feb '12

15 Feb '12

Hello: Recently I downloaded the ovirt stable node image. According to releases notes since 2.2.2 UEFI installation bug has been fixed, but I still can't boot from my server with UEFI. Ovirt installs without problem, but when the system reboots nothing happens, the system don't boot. Then I try to boot with super grub disk 2 live cd, it detects ovirt installation and boots the system. I think that still there is a problem with UEFI in certain hardware: Mi system is a IBM blade center HS22 7870 Can anyone confirm problems with UEFI in 2.2.2 version? Thanks Federico

2 4

Re: [Users] Possible to migrate from an existing KVM/Libvirt VM (installed in an LVM) ?
by Richard W.M. Jones 14 Feb '12

14 Feb '12

From: Morgan Cox <morgancoxuk(a)gmail.com> > Can an existing KVM/Libvirt VM (installed in an LVM) ever be migrated to > an Ovirt node (offline migration is ok.) ? [Sorry this isn't threaded -- I wasn't subscribed to the list until now] The answer is that virt-v2v ought to work with oVirt. It was developed originally against RHEV-M 2.2 and, later, 3.0. Of course KVM guest images should require only minimal changes, since they should already support virtio etc., certainly for Linux guests. So in many cases virt-v2v would be a no-op, and simply copying the disk image may work. Matt ...? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

2 1

[Users] Autorecovery feature plan for review
by Laszlo Hornyak 14 Feb '12

14 Feb '12

Hi, Please review the plan document for autorecovery. http://www.ovirt.org/wiki/Features/Autorecovery Thank you, Laszlo

6 6

[Users] Hey using NFS as my main datastore
by Dominic Kaiser 14 Feb '12

14 Feb '12

I am using NFS share on an Openfile server as my main datastore went to fire up a virtual instance this is the error I get: VM Building_Automation is down. Exit message internal error process exited while connecting to monitor: qemu-kvm: -drive file=/rhev/data-center/c10c25e0-526a-11e1-a5e4-87fa674ffb5d/340dad49-2ec7-475e-b6c6-668504bdb5b1/images/da582689-2248-4d0e-a017-b09f8cfa9410/78340ab7-b1f5-4fad-9150-437e7ff9d14c,if=none,id=drive-virtio-disk0,format=raw,serial=0e-a017-b09f8cfa9410,cache=none,werror=stop,rerror=stop,aio=threads: could not open disk image /rhev/data-center/c10c25e0-526a-11e1-a5e4-87fa674ffb5d/340dad49-2ec7-475e-b6c6-668504bdb5b1/images/da582689-2248-4d0e-a017-b09f8cfa9410/78340ab7-b1f5-4fad-9150-437e7ff9d14c: Permission denied . Does vdsm have to be installed on the server that shares the main datastore? Export and ISO are fine no problems. -- Dominic Kaiser Greater Boston Vineyard Director of Operations cell: 617-230-1412 fax: 617-252-0238 email: dominic(a)bostonvineyard.org

5 5

Re: [Users] Pxeboot - pwd/login issue
by Li, David 13 Feb '12

13 Feb '12

Hi Mike, I ran into the login/pwd problem again with this new build. Kernel option adminpw worked but only for a short time. I was asked to change pwd immediately after login but then rejected again after I did that. There was an short-lived error message on the screen but I wasn't able to capture it. I tried the latest from archipel source and it worked without password issue. I pulled it from: git clone https://github.com/primalmotion/Archipel.git There might be a few updates right after you pulled it last time. Would you mind merge the new updates into ovirt node again? Thanks. David >-----Original Message----- >From: Mike Burns [mailto:mburns@redhat.com] >Sent: Thursday, February 09, 2012 5:10 PM >To: Li, David >Cc: Perry Myers; users(a)ovirt.org >Subject: Re: [Users] Pxeboot > >On Thu, 2012-02-09 at 17:05 -0800, Li, David wrote: >> Mike, >> Built it finally! >> Thanks a lot! > >Woot! > >> >> >-----Original Message----- >> >From: Mike Burns [mailto:mburns@redhat.com] >> >Sent: Thursday, February 09, 2012 4:18 PM >> >To: Li, David >> >Cc: Perry Myers; users(a)ovirt.org >> >Subject: Re: [Users] Pxeboot >> > >> >On Thu, 2012-02-09 at 15:50 -0800, Li, David wrote: >> >> MIke, >> >> >> >> Got something new this time in make publish: >> >> >> >> /bin/sh: -c: line 36: syntax error near unexpected token `)' >> >> /bin/sh: -c: line 36: `)' >> >> make[1]: *** [repos.ks] Error 1 >> >> make[1]: Leaving directory >> >> `/home/lid/workspace/ovirt/node-archipel- >> >2.2.2/ovirt-node/recipe' >> >> make: *** [distdir] Error 1 >> >> >> >> [lid@FC16-1 ovirt-node]$ echo $OVIRT_CACHE_DIR >$OVIRT_LOCAL_REPO >> >> /home/lid/ovirt-cache file:///home/lid/ovirt-cache/ovirt >> >> [lid@FC16-1 ovirt-node]$ >> > >> >Oops, bad merge on my part. >> > >> >$ git reset --hard origin/master #sets you back to head of the >> >master branch $ git fetch http://gerrit.ovirt.org/p/ovirt-node >> >refs/changes/38/1738/3 && git cherry-pick FETCH_HEAD # checks out the >new version of the patch set. >> > >> >Mike >> > >> >> >> >> >> >> - David >> >> ________________________________________ >> >> From: Mike Burns [mburns(a)redhat.com] >> >> Sent: Thursday, February 09, 2012 2:12 PM >> >> To: Li, David >> >> Cc: Perry Myers; users(a)ovirt.org >> >> Subject: Re: [Users] Pxeboot >> >> >> >> On Thu, 2012-02-09 at 13:34 -0800, Li, David wrote: >> >> > Mike, >> >> > >> >> > It seems it needs couple vdsm pkgs: >> >> > >> >> > ./node-creator ovirt-node-image.ks Error creating Live CD : >> >> > Failed to find package 'vdsm-cli' : No >> >> > package(s) available to install mv ovirt-node-image.iso >> >> > ovirt-node-image-2.2.3-0.1fc16.git16688ea.iso >> >> > mv: cannot stat `ovirt-node-image.iso': No such file or directory >> >> > make: *** [ovirt-node-image.iso] Error 1 >> >> > >> >> > >> >> > can I remove them from ks files? >> >> >> >> Not if you want to use ovirt-node with ovirt-engine. There was a >> >> bug in that patch set that is fixed in patch set 2 (along with the >> >> bad ===== package). I hadn't pulled the patch set together and >> >> uploaded to gerrit yet, but it's there now. >> >> >> >> git fetch http://gerrit.ovirt.org/p/ovirt-node >> >> refs/changes/38/1738/2 && git checkout FETCH_HEAD >> >> >> >> This should fix the problem. >> >> >> >> Mike >> >> >> >> > >> >> > - David >> >> > ________________________________________ >> >> > From: Mike Burns [mburns(a)redhat.com] >> >> > Sent: Thursday, February 09, 2012 12:07 PM >> >> > To: Li, David >> >> > Cc: Perry Myers; users(a)ovirt.org >> >> > Subject: Re: [Users] Pxeboot >> >> > >> >> > On Thu, 2012-02-09 at 11:52 -0800, Li, David wrote: >> >> > > It's still the same error: >> >> > > >> >> > > [lid@FC16-1 ovirt-node]$ cd recipe/ >> >> > > [lid@FC16-1 recipe]$ make ovirt-node-image.iso ( \ >> >> > > echo "PRODUCT='"oVirt Node Hypervisor"'" ;\ >> >> > > echo "PRODUCT_SHORT='"oVirt Node Hypervisor"'" ;\ >> >> > > echo "PACKAGE=ovirt-node-image" ;\ >> >> > > echo "VERSION=2.2.3" ;\ >> >> > > echo "RELEASE=0.1fc16.git16688ea" ;\ >> >> > > ) > version.ks >> >> > > ./node-creator ovirt-node-image.ks Error creating Live CD : >> >> > > Failed to find package '=======' : No package(s) available to >> >> > > install mv ovirt-node-image.iso >> >> > > ovirt-node-image-2.2.3-0.1fc16.git16688ea.iso >> >> > > mv: cannot stat `ovirt-node-image.iso': No such file or >> >> > > directory >> >> > > make: *** [ovirt-node-image.iso] Error 1 >> >> > > [lid@FC16-1 recipe]$ echo $OVIRT_LOCAL_REPO >> >> > > file:///home/lid/ovirt-cache/ovirt >> >> > > [lid@FC16-1 recipe]$ ll /home/lid/ovirt-cache/ovirt/ total 12 >> >> > > drwxr-xr-x. 2 lid lid 4096 Feb 9 11:10 noarch drwxrwxr-x. 2 >> >> > > lid lid 4096 Feb 9 11:10 repodata drwxrwxr-x. 2 lid lid 4096 >> >> > > Feb 9 >> >> > > 11:10 src >> >> > >> >> > That's a bug in the patch. edit recipe/common-pkgs.ks and remove >> >> > the last line which is "=======" >> >> > >> >> > Mike >> >> > > >> >> > > >> >> > > Did make publish store the rpms in $OVIRT_LOCAL_REPO? >> >> > > >> >> > > - David >> >> > > ________________________________________ >> >> > > From: Mike Burns [mburns(a)redhat.com] >> >> > > Sent: Thursday, February 09, 2012 11:44 AM >> >> > > To: Li, David >> >> > > Cc: Perry Myers; users(a)ovirt.org >> >> > > Subject: RE: [Users] Pxeboot >> >> > > >> >> > > On Thu, 2012-02-09 at 11:40 -0800, Li, David wrote: >> >> > > > The error seems a little stubborn. >> >> > > > >> >> > > > [lid@FC16-1 recipe]$ echo $OVIRT_LOCAL_REPO >> >> > > > file://home/lid/ovirt-cache/ovirt >> >> > > >> >> > > You need 3 slashes. file:///home/lid/ovirt-cache/ovirt >> >> > > >> >> > > > [lid@FC16-1 recipe]$ make ovirt-node-image.iso ( \ >> >> > > > echo "PRODUCT='"oVirt Node Hypervisor"'" ;\ >> >> > > > echo "PRODUCT_SHORT='"oVirt Node Hypervisor"'" ;\ >> >> > > > echo "PACKAGE=ovirt-node-image" ;\ >> >> > > > echo "VERSION=2.2.3" ;\ >> >> > > > echo "RELEASE=0.1fc16.git16688ea" ;\ >> >> > > > ) > version.ks >> >> > > > ./node-creator ovirt-node-image.ks Error creating Live CD : >> >> > > > Unable to download from repo : Cannot retrieve repository >> >> > > > metadata (repomd.xml) for repository: local. Please verify >> >> > > > its path and try again mv ovirt-node-image.iso >> >> > > > ovirt-node-image-2.2.3-0.1fc16.git16688ea.iso >> >> > > > mv: cannot stat `ovirt-node-image.iso': No such file or >> >> > > > directory >> >> > > > make: *** [ovirt-node-image.iso] Error 1 >> >> > > > >> >> > > > There is also a pop-up window: Unable to open a folder for >> >> > > > _ovirt-node-imag >> >> > > > >> >> > > > maybe it's looking at the wrong place? >> >> > > > >> >> > > > >> >> > > > - David >> >> > > > ________________________________________ >> >> > > > From: Mike Burns [mburns(a)redhat.com] >> >> > > > Sent: Thursday, February 09, 2012 11:15 AM >> >> > > > To: Li, David >> >> > > > Cc: Perry Myers; users(a)ovirt.org >> >> > > > Subject: RE: [Users] Pxeboot >> >> > > > >> >> > > > On Thu, 2012-02-09 at 10:57 -0800, Li, David wrote: >> >> > > > > ok, that's my bad:) >> >> > > > > >> >> > > > > Ran into error at the last iso build step: >> >> > > > > >> >> > > > > Start building ISO image.... >> >> > > > > ( \ >> >> > > > > echo "PRODUCT='"oVirt Node Hypervisor"'" ;\ >> >> > > > > echo "PRODUCT_SHORT='"oVirt Node Hypervisor"'" ;\ >> >> > > > > echo "PACKAGE=ovirt-node-image" ;\ >> >> > > > > echo "VERSION=2.2.3" ;\ >> >> > > > > echo "RELEASE=0.1.fc16.git16688ea" ;\ >> >> > > > > ) > version.ks >> >> > > > > ./node-creator ovirt-node-image.ks Error creating Live CD : >> >> > > > > Unable to download from repo : Cannot retrieve repository >> >> > > > > metadata (repomd.xml) for repository: local. Please verify >> >> > > > > its path and try again mv ovirt-node-image.iso >> >> > > > > ovirt-node-image-2.2.3-0.1.fc16.git16688ea.iso >> >> > > > > mv: cannot stat `ovirt-node-image.iso': No such file or >> >> > > > > directory >> >> > > > > make: *** [ovirt-node-image.iso] Error 1 >> >> > > > >> >> > > > IIRC, this is usually because you have OVIRT_LOCAL_REPO >> >> > > > defined, but not correctly. It needs to be like this: >> >> > > > file:///home/mburns/rpmbuild/RPMS >> >> > > > >> >> > > > Ok, I just looked at the Node Building page, and it needs some >updates. >> >> > > > Try this from the base directory of the git repo >> >> > > > >> >> > > > $ export OVIRT_CACHE_DIR=${HOME}/ovirt-cache >> >> > > > $ export OVIRT_LOCAL_REPO=file://${OVIRT_CACHE_DIR}/ovirt >> >> > > > $ ./autogen.sh --with-image-minimizer $ make publish #this >> >> > > > builds the rpms and puts them in ${OVIRT_CACHE_DIR} $ cd >> >> > > > recipe $ make ovirt-node-image.iso >> >> > > > >> >> > > > Mike >> >> > > > > >> >> > > > > >> >> > > > > >> >> > > > > I wonder which repo my machine is lacking? >> >> > > > > >> >> > > > > - David >> >> > > > > ________________________________________ >> >> > > > > From: Mike Burns [mburns(a)redhat.com] >> >> > > > > Sent: Thursday, February 09, 2012 10:02 AM >> >> > > > > To: Li, David >> >> > > > > Cc: Perry Myers; users(a)ovirt.org >> >> > > > > Subject: Re: [Users] Pxeboot >> >> > > > > >> >> > > > > On Thu, 2012-02-09 at 09:47 -0800, Li, David wrote: >> >> > > > > > Got an error: >> >> > > > > > [lid@FC16-1 ovirt-node]$ git fetch >> >> > > > > > http://gerrit.ovirt.org/ refs/changes/38/1738/1&&git >> >> > > > > > cherry-pick FETCH_HEAD >> >> > > > > > fatal: http://gerrit.ovirt.org/info/refs not found: did >> >> > > > > > you run git >> >update-server-info on the server? >> >> > > > > >> >> > > > > Bad copy/paste: >> >> > > > > >> >> > > > > git fetch http://gerrit.ovirt.org/p/ovirt-node >> >> > > > > refs/changes/38/1738/1 && git cherry-pick FETCH_HEAD >> >> > > > > > >> >> > > > > > any ideas? >> >> > > > > > >> >> > > > > > - David >> >> > > > > > ________________________________________ >> >> > > > > > From: Mike Burns [mburns(a)redhat.com] >> >> > > > > > Sent: Thursday, February 09, 2012 8:37 AM >> >> > > > > > To: Li, David >> >> > > > > > Cc: Perry Myers; users(a)ovirt.org >> >> > > > > > Subject: Re: [Users] Pxeboot >> >> > > > > > >> >> > > > > > On Thu, 2012-02-09 at 08:30 -0800, Li, David wrote: >> >> > > > > > > Mike, >> >> > > > > > > >> >> > > > > > > Two quick questions before I kick off a build: >> >> > > > > > > >> >> > > > > > > 1. Git errors. Do they matter? >> >> > > > > > > >> >> > > > > > > >> >> > > > > > > [lid@FC16-1 node-archipel-2.2.2]$ git clone >> >> > > > > > > http://gerrit.ovirt.org/p/ovirt-node.git >> >refs/changes/38/1738/1&&git checkout FETCH_HEAD Cloning into >> >refs/changes/38/1738/1... >> >> > > > > > > remote: Counting objects: 14791, done >> >> > > > > > > remote: Finding sources: 100% (14791/14791) >> >> > > > > > > remote: Total 14791 (delta 10855), reused 14778 (delta >> >> > > > > > > 10855) Receiving objects: 100% (14791/14791), 16.92 MiB >> >> > > > > > > | 154 >> >KiB/s, done. >> >> > > > > > > Resolving deltas: 100% (10855/10855), done. >> >> > > > > > > fatal: Not a git repository (or any of the parent >> >> > > > > > > directories): .git >> >> > > > > > >> >> > > > > > try this instead: >> >> > > > > > >> >> > > > > > 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/1 && git cherry-pick FETCH_HEAD >> >> > > > > > >> >> > > > > > > >> >> > > > > > > >> >> > > > > > > 2. Build machine. >> >> > > > > > > >> >> > > > > > > I am using a x86_64 FC16 VM as the build machine. My >> >> > > > > > > target is >> >x86_64 Intel board. Is this ok? >> >> > > > > > >> >> > > > > > Should be fine. >> >> > > > > > >> >> > > > > > Mike >> >> > > > > > > >> >> > > > > > > >> >> > > > > > > >> >> > > > > > > - David >> >> > > > > > > ________________________________________ >> >> > > > > > > From: Mike Burns [mburns(a)redhat.com] >> >> > > > > > > Sent: Thursday, February 09, 2012 8:16 AM >> >> > > > > > > To: Li, David >> >> > > > > > > Cc: Perry Myers; users(a)ovirt.org >> >> > > > > > > Subject: RE: [Users] Pxeboot >> >> > > > > > > >> >> > > > > > > On Thu, 2012-02-09 at 08:10 -0800, Li, David wrote: >> >> > > > > > > > Not sure where the boot log is since I can't login. >> >> > > > > > > > >> >> > > > > > > > I got the source from >> >> > > > > > > > https://github.com/primalmotion/archipel-node and >> >> > > > > > > > followed the build instructions in >> >> > > > > > > > http://ovirt.org/wiki/Node_Building >> >> > > > > > > > >> >> > > > > > > > maybe I should rebuild the iso from the ovirt node >> >> > > > > > > > source tree >> >as you have pulled in archipel changes yesterday. How do I do that? >> >> > > > > > > >> >> > > > > > > git fetch http://gerrit.ovirt.org/p/ovirt-node >> >> > > > > > > refs/changes/38/1738/1 && git checkout FETCH_HEAD >> >> > > > > > > >> >> > > > > > > That command will checkout the current version of the >> >> > > > > > > archipel-node changes. Then you can just follow the >> >> > > > > > > Node_Building process. Note that the changes aren't >> >> > > > > > > merged into master yet. I'm still in the process of reviewing >them. >> >> > > > > > > >> >> > > > > > > Mike >> >> > > > > > > > >> >> > > > > > > > - David >> >> > > > > > > > >> >> > > > > > > > >> >> > > > > > > > >-----Original Message----- >> >> > > > > > > > >From: Mike Burns [mailto:mburns@redhat.com] >> >> > > > > > > > >Sent: Thursday, February 09, 2012 7:22 AM >> >> > > > > > > > >To: Li, David >> >> > > > > > > > >Cc: Perry Myers; users(a)ovirt.org >> >> > > > > > > > >Subject: Re: [Users] Pxeboot >> >> > > > > > > > > >> >> > > > > > > > >On Thu, 2012-02-09 at 07:06 -0800, Li, David wrote: >> >> > > > > > > > >> Mike, >> >> > > > > > > > >> >> >> > > > > > > > >> I added adminpw as a kernel option. After boot, I >> >> > > > > > > > >> tried >> >"admin/abc123" >> >> > > > > > > > >> and "root/abc123" but not able to login. >> >> > > > > > > > >> Any idea? >> >> > > > > > > > >> >> >> > > > > > > > > >> >> > > > > > > > >Are there any errors in your build or boot logs? >> >> > > > > > > > > >> >> > > > > > > > >Mike >> >> > > > > > > > > >> >> > > > > > > > >> David >> >> > > > > > > > >> >> >> > > > > > > > >> >> >> > > > > > > > >> >-----Original Message----- >> >> > > > > > > > >> >From: Mike Burns [mailto:mburns@redhat.com] >> >> > > > > > > > >> >Sent: Wednesday, February 08, 2012 6:53 PM >> >> > > > > > > > >> >To: Li, David >> >> > > > > > > > >> >Cc: Perry Myers; users(a)ovirt.org >> >> > > > > > > > >> >Subject: Re: [Users] Pxeboot >> >> > > > > > > > >> > >> >> > > > > > > > >> >On Wed, 2012-02-08 at 17:11 -0800, Li, David wrote: >> >> > > > > > > > >> >> Ok, I built an iso out of archipel and >> >> > > > > > > > >> >> pxebooted it with stateless option. Now >> >> > > > > > > > >> >I got a "localhost" login prompt. Any idea what >> >> > > > > > > > >> >should I put >> >in as user/pwd? >> >> > > > > > > > >> >> David >> >> > > > > > > > >> > >> >> > > > > > > > >> >You will need to pass a password in on the >> >> > > > > > > > >> >command line as well >> >> > > > > > > > >> > >> >> > > > > > > > >> >adminpw=<hashed_password> >> >> > > > > > > > >> > >> >> > > > > > > > >> >You can generate the hashed password using: >> >> > > > > > > > >> > >> >> > > > > > > > >> >$ openssl passwd >> >> > > > > > > > >> > >> >> > > > > > > > >> >Assuming the password was abc123 >> >> > > > > > > > >> > >> >> > > > > > > > >> >$ openssl passwd abc123 >> >> > > > > > > > >> >tKrQfufCbosr6 >> >> > > > > > > > >> > >> >> > > > > > > > >> >adminpw=tKrQfufCbosr6 >> >> > > > > > > > >> > >> >> > > > > > > > >> >Mike >> >> > > > > > > > >> > >> >> > > > > > > > >> >> >> >> > > > > > > > >> >> >-----Original Message----- >> >> > > > > > > > >> >> >From: Mike Burns [mailto:mburns@redhat.com] >> >> > > > > > > > >> >> >Sent: Wednesday, February 08, 2012 4:31 PM >> >> > > > > > > > >> >> >To: Li, David >> >> > > > > > > > >> >> >Cc: Perry Myers; users(a)ovirt.org >> >> > > > > > > > >> >> >Subject: RE: [Users] Pxeboot >> >> > > > > > > > >> >> > >> >> > > > > > > > >> >> >On Wed, 2012-02-08 at 15:43 -0800, Li, David wrote: >> >> > > > > > > > >> >> >> Ok, I think we are on the same page now >> >> > > > > > > > >> >> >> regarding >> >stateless node. >> >> > > > > > > > >> >> >> It looks like the achipel diff you just >> >> > > > > > > > >> >> >> pulled in might be able to do this. But I >> >> > > > > > > > >> >> >> can't quite make it out what the kernel >> >> > > > > > > > >> >> >> option should >> >> > > > > > > > >be. >> >> > > > > > > > >> >> >> Is it "stateless=1"? >> >> > > > > > > > >> >> >> >> >> > > > > > > > >> >> > >> >> > > > > > > > >> >> >stateless=1 or just stateless, both will work. >> >> > > > > > > > >> >> > >> >> > > > > > > > >> >> > >> >> > > > > > > > >> >> >> David >> >> > > > > > > > >> >> >> >> >> > > > > > > > >> >> >> >-----Original Message----- >> >> > > > > > > > >> >> >> >From: Mike Burns [mailto:mburns@redhat.com] >> >> > > > > > > > >> >> >> >Sent: Wednesday, February 08, 2012 3:27 PM >> >> > > > > > > > >> >> >> >To: Li, David >> >> > > > > > > > >> >> >> >Cc: Perry Myers; users(a)ovirt.org >> >> > > > > > > > >> >> >> >Subject: Re: [Users] Pxeboot >> >> > > > > > > > >> >> >> > >> >> > > > > > > > >> >> >> >On Wed, 2012-02-08 at 15:19 -0800, Li, David >wrote: >> >> > > > > > > > >> >> >> >> Perry, >> >> > > > > > > > >> >> >> >> >> >> > > > > > > > >> >> >> >> I am glad you brought this up. >> >> > > > > > > > >> >> >> >> I 'd be perfectly happy to run the root >> >> > > > > > > > >> >> >> >> fs entirely in >> >RAM. >> >> > > > > > > > >> >> >> >> In fact that would >> >> > > > > > > > >> >> >> >be ideal for me. It's just I am not quite >> >> > > > > > > > >> >> >> >sure how to use pxeboot to achieve this. >> >> > > > > > > > >> >> >> >> >> >> > > > > > > > >> >> >> >> I am doing a test now using the tftpboot >> >> > > > > > > > >> >> >> >> files >> >created from the iso. >> >> > > > > > > > >> >> >> >> As far as I see, the kernel boot options >> >(pxelinux.cfg/default) has: >> >> > > > > > > > >> >> >> >> >> >> > > > > > > > >> >> >> >> root=live:/ovirt-node-image-2.2.2-1.1.fc1 >> >> > > > > > > > >> >> >> >> 6.i >> >> > > > > > > > >> >> >> >> so >> >> > > > > > > > >> >> >> >> >> >> > > > > > > > >> >> >> >> With this I can only pxeboot to the >> >> > > > > > > > >> >> >> >> intall screen. What should I use to let >> >> > > > > > > > >> >> >> >> the >> >> > > > > > > > >> >> >> >kernel mount the root fs in memory? >> >> > > > > > > > >> >> >> >Something like >> >> > > > > > > > >root=/dev/ram0? >> >> > > > > > > > >> >> >> >> >> >> > > > > > > > >> >> >> >> David >> >> > > > > > > > >> >> >> > >> >> > > > > > > > >> >> >> >It's not currently possible with ovirt-node. >> >> > > > > > > > >> >> >> >That's the whole stateless feature that we >> >> > > > > > > > >> >> >> >outlined. Once we actually have it >> >> > > > > > > > >> >> >> >implemented, it will be something along the >> >> > > > > > > > >> >> >> >lines of adding "stateless" to >> >> > > > > > > > >> >> >the kernel commandline. >> >> > > > > > > > >> >> >> > >> >> > > > > > > > >> >> >> >Mike >> >> > > > > > > > >> >> >> >> >> >> > > > > > > > >> >> >> >> >> >> > > > > > > > >> >> >> >> >-----Original Message----- >> >> > > > > > > > >> >> >> >> >From: Perry Myers >> >> > > > > > > > >> >> >> >> >[mailto:pmyers@redhat.com] >> >> > > > > > > > >> >> >> >> >Sent: Wednesday, February 08, 2012 2:54 >> >> > > > > > > > >> >> >> >> >PM >> >> > > > > > > > >> >> >> >> >To: Mike Burns >> >> > > > > > > > >> >> >> >> >Cc: Li, David; users(a)ovirt.org >> >> > > > > > > > >> >> >> >> >Subject: Re: [Users] Pxeboot >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> >On 02/08/2012 05:03 PM, Mike Burns wrote: >> >> > > > > > > > >> >> >> >> >> On Wed, 2012-02-08 at 13:46 -0800, Li, >> >> > > > > > > > >> >> >> >> >> David >> >wrote: >> >> > > > > > > > >> >> >> >> >>> Mike, >> >> > > > > > > > >> >> >> >> >>> >> >> > > > > > > > >> >> >> >> >>> If I understand this correctly, today >> >> > > > > > > > >> >> >> >> >>> I should be able to pxeboot and nfs >> >> > > > > > > > >> >> >> >> >>> mount the >> >root fs from a remote server. >> >> > > > > > > > >> >> >> >> >>> Apart from setting up the pxe stuff, >> >> > > > > > > > >> >> >> >> >>> I 'd have to populate the ovirt node >> >> > > > > > > > >> >> >> >> >>> root fs on the server >> >> > > > > > > > >> >> >> >> >>> - perhaps steal it from a disk install. >> >> > > > > > > > >> >> >> >> >>> In other words I am concerned about >> >> > > > > > > > >> >> >> >> >>> the point from which the kernel >> >> > > > > > > > >> >> >> >> >>> starts to execute /init script (in >> >> > > > > > > > >> >> >> >> >>> the initramfs) to the >> >point /init is able to mount the final root fs from a remote server. >> >> > > > > > > > >> >> >> >> >> >> >> > > > > > > > >> >> >> >> >> No, there is no way to set this up >> >> > > > > > > > >> >> >> >> >> currently in >> >ovirt-node. >> >> > > > > > > > >> >> >> >> >> You could install using a remote iscsi >> >> > > > > > > > >> >> >> >> >> lun if you have a hardware iscsi HBA, >> >> > > > > > > > >> >> >> >> >> but there isn't a way to mount a >> >> > > > > > > > >> >> >> >> >> remote nfs share as the >> >> > > > > > > > >> >> >root fs. >> >> > > > > > > > >> >> >> >> >> >> >> > > > > > > > >> >> >> >> >> Supporting a remote NFS share as the >> >> > > > > > > > >> >> >> >> >> root fs isn't even something that >> >> > > > > > > > >> >> >> >> >> requested as an RFE at this point or >> >> > > > > > > > >> >> >> >> >> on the roadmap as far as >> >I'm aware. >> >> > > > > > > > >> >> >> >> >> >> >> > > > > > > > >> >> >> >> >> It sounds like what you're really >> >> > > > > > > > >> >> >> >> >> looking for is a shared root fs that >> >> > > > > > > > >> >> >> >> >> multiple hosts could use. This is >> >> > > > > > > > >> >> >> >> >> something that we will probably look >> >> > > > > > > > >> >> >> >> >> into eventually, but it's not on the >> >> > > > > > > > >> >> >> >> >> immediate >> >> > > > > > > > >> >> >roadmap. >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> >Given that the rootfs of oVirt Node is >> >> > > > > > > > >> >> >> >> >fairly small and in a truly stateless >> >> > > > > > > > >> >> >> >> >environment would just run out of system >> >> > > > > > > > >> >> >> >> >RAM, there's no real reason to try to do >> >> > > > > > > > >> >> >> >> >a shared NFS based >> >> > > > > > > > >rootfs. >> >> > > > > > > > >> >> >> >> >It's an unnecessary complication I >> >> > > > > > > > >> >> >> >> >think, if the end goal is to move to >> >> > > > > > > > >> >> >> >> >truly >> >> > > > > > > > >> >> >> >stateless. >> >> > > > > > > > >> >> >> >> > >> >> > > > > > > > >> >> >> >> >For larger systems where the rootfs is >> >> > > > > > > > >> >> >> >> >on the order of GB's, shared root may >> >> > > > > > > > >> >> >> >> >make more >> >sense. >> >> > > > > > > > >> >> >> >> >> >____________________________________________ >> >> > > > > > > > >> >> >> >> ___ Users mailing list Users(a)ovirt.org >> >> > > > > > > > >> >> >> >> http://lists.ovirt.org/mailman/listinfo/u >> >> > > > > > > > >> >> >> >> ser >> >> > > > > > > > >> >> >> >> s >> >> > > > > > > > >> >> >> > >> >> > > > > > > > >> >> >> >> >> > > > > > > > >> >> > >> >> > > > > > > > >> >> >> >> > > > > > > > >> >> >> >_______________________________________________ >> >> > > > > > > > >> >> Users mailing list Users(a)ovirt.org >> >> > > > > > > > >> >> http://lists.ovirt.org/mailman/listinfo/users >> >> > > > > > > > >> > >> >> > > > > > > > >> >> >> > > > > > > > >> >> >_______________________________________________ >> >> > > > > > > > >> Users mailing list Users(a)ovirt.org >> >> > > > > > > > >> http://lists.ovirt.org/mailman/listinfo/users >> >> > > > > > > > > >> >> > > > > > > > >> >> > > > > > > >> >> > > > > > > >> >> > > > > > > _______________________________________________ >> >> > > > > > > Users mailing list >> >> > > > > > > Users(a)ovirt.org >> >> > > > > > > http://lists.ovirt.org/mailman/listinfo/users >> >> > > > > > >> >> > > > > > >> >> > > > > > _______________________________________________ >> >> > > > > > Users mailing list >> >> > > > > > Users(a)ovirt.org >> >> > > > > > http://lists.ovirt.org/mailman/listinfo/users >> >> > > > > >> >> > > > > >> >> > > > >> >> > > > >> >> > > >> >> > > >> >> > > _______________________________________________ >> >> > > Users mailing list >> >> > > Users(a)ovirt.org >> >> > > http://lists.ovirt.org/mailman/listinfo/users >> >> > >> >> > >> >> > _______________________________________________ >> >> > Users mailing list >> >> > Users(a)ovirt.org >> >> > http://lists.ovirt.org/mailman/listinfo/users >> >> >> >> >> >> _______________________________________________ >> >> Users mailing list >> >> Users(a)ovirt.org >> >> http://lists.ovirt.org/mailman/listinfo/users >> > >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >

2 17

[Users] Difference between RHEV and ovirt
by patrick 13 Feb '12

13 Feb '12

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

2 1

[Users] Problem with required packages when installing ovirt-engine
by Terry Phelps 13 Feb '12

13 Feb '12

I'm new here, and am trying to install ovirt-engine, as documented on ovirt.org/get-ovirt, and in the installation guide. I've worked with RPM-based distributions (RHEL, Centos, Scientific Linux) for quite a while, but have never worked with Fedora. Please tell me what I'm doing wrong, or failing to do: I am trying to install ovirt-engine on a newly-built Scientific Linux 6.1 (just like RHEL 6.1) machine. I did the "wget ...ovirt-engine.repo", and removed the classpathx-jaf RPM. Then I tried to "yum install ovirt-engine", and got a number of errors: Error: Package: ovirt-engine-tools-common-3.0.0_0001-1.6.fc16.x86_64 (ovirt-engine-stable) Requires: jakarta-commons-jxpath Error: Package: ovirt-engine-log-collector-3.0.0_0001-1.6.fc16.x86_64 (ovirt-engine-stable) Requires: python(abi) = 2.7 Installed: python-2.6.6-20.el6.x86_64 (@anaconda-ScientificLinux-201107271550.x86_64) python(abi) = 2.6 Error: Package: ovirt-engine-tools-common-3.0.0_0001-1.6.fc16.x86_64 (ovirt-engine-stable) Requires: jakarta-commons-configuration Error: Package: ovirt-engine-jboss-deps-3.0.0_0001-1.6.fc16.x86_64 (ovirt-engine-stable) Requires: hsqldb >= 1:1.8.0.10-9 Installed: 1:hsqldb-1.8.0.10-8.el6.x86_64 (@anaconda-ScientificLinux-201107271550.x86_64) hsqldb = 1:1.8.0.10-8.el6 Error: Package: ovirt-engine-3.0.0_0001-1.6.fc16.x86_64 (ovirt-engine-stable) Requires: libc.so.6(GLIBC_2.14)(64bit) Error: Package: ovirt-engine-jboss-deps-3.0.0_0001-1.6.fc16.x86_64 (ovirt-engine-stable) Requires: jakarta-commons-discovery >= 1:0.4-7 Installed: 1:jakarta-commons-discovery-0.4-5.4.el6.noarch (@anaconda-ScientificLinux-201107271550.x86_64) I'm suppose this means that I need newer versions of some packages that are installed now, and these are not available in a yum repo that my yum can see. The only change to the installed yum environment I have made is to add the ovirt-engine repo. I don't see anything in the docs about pointing to some Fedora repo, or some such thing, but perhaps that's what I need to do. Can someone please enlighten me?

4 4

[Users] Ovirt Support life (timeframe) - upgrade path ?
by Morgan Cox 13 Feb '12

13 Feb '12

Hi. As Fedora the default system that Ovirt is packaged for does this mean that Ovirt will have the same (short) support life of 18 months ? I ask as that is a bit short to have in enterprise .. I.e if I install Ovirt in Fedora 16 will support life run out when Fedora 16 runs out or will I be able to upgrade Ovirt/Fedora to the next version? Are there going packages for Centos ? If so will they be supported longer ? If this information is out there already can you point me to the right direction ? Regards

6 5

[Users] Two fence devices per server.
by Nathan Stratton 12 Feb '12

12 Feb '12

Just installed the latest oVirt, must admit you guys have done a great job. One issue I am having tho is that with my setup each server has 2 power supplies and the two supplies are one two different APC power strips. Is there any way to configure fencing to work with two devices per server? ><> Nathan Stratton CTO, BlinkMind, Inc. nathan at robotics.net nathan at blinkmind.com http://www.robotics.net http://www.blinkmind.com

3 3

[Users] Unable to add ISOs to default ISO storage domain
by Andrew Dunlop 12 Feb '12

12 Feb '12

I have been trying to upload ISOs onto my ISO Storage Domain, set up when I ran engine-setup. I can run the command and the .iso file is correctly put in place, however this never appears in the available images for this domain on the web-admin. I notice that there are no file entries in https://xxxx.xxxx.co.uk:8443/api/storagedomains/a677acff-601b-4b6d-86ce-079… just what is given in the verbose output from the uploader. Any ideas what the problem might be? I have tried a couple of ISOs and have also done a cleanup and setup. Below is the verbose output from the uploader: [admin@xxxx ~]$ sudo engine-iso-uploader -v -f -i ISOs upload Downloads/TinyCore-current.iso [sudo] password for admin: Please provide the REST API password for the admin@internal oVirt Engine user (CTRL+D to abort): DEBUG: URL is https://xxxx.xxxx.co.uk:8443/api/storagedomains?search=name%3DISOs DEBUG: Returned XML is <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <storage_domains> <storage_domain href="/api/storagedomains/a677acff-601b-4b6d-86ce-0798f3833629" id="a677acff-601b-4b6d-86ce-0798f3833629"> <name>ISOs</name> <link href="/api/storagedomains/a677acff-601b-4b6d-86ce-0798f3833629/permissions" rel="permissions"/> <link href="/api/storagedomains/a677acff-601b-4b6d-86ce-0798f3833629/files" rel="files"/> <type>iso</type> <master>false</master> <storage> <type>nfs</type>srmr <address>xxxx.xxxx.co.uk</address> <path>/isos</path> </storage>users@ <available>48318382080</available> <used>4294967296</used> <committed>0</committed> <storage_format>v1</storage_format> </storage_domain> </storage_domains> DEBUG: id=a677acff-601b-4b6d-86ce-0798f3833629 address=xxxx.xxxx.co.uk path=/isos DEBUG: local NFS mount point is /tmp/tmpX03eVj DEBUG: NFS mount command (/bin/mount -t nfs -o rw,sync,soft xxxx.xxxx.co.uk:/isos /tmp/tmpX03eVj) DEBUG: /bin/mount -t nfs -o rw,sync,soft xxxx.xxxx.co.uk:/isos /tmp/tmpX03eVj DEBUG: _cmds(['/bin/mount', '-t', 'nfs', '-o', 'rw,sync,soft', 'xxxx.xxxx.co.uk:/isos', '/tmp/tmpX03eVj']) DEBUG: returncode(0) DEBUG: STDOUT() DEBUG: STDERR() DEBUG: Size of Downloads/TinyCore-current.iso: 12507136 bytes 12214.0 1K-blocks 11.0 MB DEBUG: Available space in /tmp/tmpX03eVj/a677acff-601b-4b6d-86ce-0798f3833629/images/11111111-1111-1111-1111-111111111111: 48557457408 bytes 47419392.0 1K-blocks 46308.0 MB DEBUG: euid(0) egid(0) DEBUG: euid(0) egid(0) DEBUG: URL is https://xxxx.xxxx.co.uk:8443/api/storagedomains/a677acff-601b-4b6d-86ce-079… DEBUG: Returned XML is <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <files/> DEBUG: /bin/umount -t nfs -f /tmp/tmpX03eVj DEBUG: /bin/umount -t nfs -f /tmp/tmpX03eVj DEBUG: _cmds(['/bin/umount', '-t', 'nfs', '-f', '/tmp/tmpX03eVj']) DEBUG: returncode(0) DEBUG: STDOUT() DEBUG: STDERR()

10 31