Re: [ovirt-users] importing a qcow2 disk into ovirt 3.5?
On 10/21/2014 11:23 AM, Federico Alberto Sayd wrote: On 21/10/14 02:27, Paul Jansen wrote: I've just been doing some searching to try and work out how to get a vmware windows VM into ovirt. It seems that the newest virtv2v has dropped support for importing from an ESXi standalone machine - and now only works with vcenter. I didn't have any success with using the current virt-v2v attaching to an ESXi host. I've prepared the VM by first removing the vmware tools and have installled the various virtio drivers, as well as running the 'mergeide' registry file to enable IDE. I've used 'qemu-img' to convirt this VMDK file to QCOW2. It does not appear that there is a straightforward way for me to import this new qcow2 disk into ovirt. It seems my best option at the moment is to export the VMware VM as an OVA and then try and use a newer virt-v2v to import this into ovirt. Alternatively I could construct a VM in virt-manager and attach the converted qcow2 disk to it, and then use virt-v2v to import this into ovirt. Can someone suggest an alternative course of action? It seems strange that I can't just import a disk into ovirt, construct a VM and attach the disk. Is there anything int he works to make this process easier? Thanks, Paul ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users I have not found a way to import qcow2 disk into oVirt. The last time I needed to import a qcow2 disk to oVirt I created a vm in a kvm server (my pc..) with virt-manager, then I added the qcow disk, and booted the vm with clonezilla. Then I created a VM in oVirt, provisioned with similar disks and booted also with clonezilla. Then I cloned from kvm to oVirt. After I deleted the native kvm vm and disks. In this way I bypassed all the import, export, ova compatibility, virt2virt, etc. Simple and practical Regards ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Wrote this awhile back as a quick qcow to ovf implementation to import into ovirt-engine/rhevm. There are newer options but this does the job really quick. Will wrap the qcow image into an exploded ova structure or zipped. You can then import it directly into engine with engine-image-uploader. https://jboggs.fedorapeople.org/guest-image-ovf-creator.py https://jboggs.fedorapeople.org/guest-image-ovf-creator.py ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Unable to install oVirt Node 3.0.1: Exception: RunTimeError('Failed to partition/format')
On 10/21/2013 08:59 AM, Gabi C wrote:
Hello!
Had same problem on IBM xSeries 3650. Aparently was an RAID problem
(Serve RID in my case). I had to wipe the disk, recreate the array an
wait until it was OK and only after that I manage to install.
On Mon, Oct 21, 2013 at 3:45 PM, Edgars M. edgars.maz...@gmail.com
mailto:edgars.maz...@gmail.com wrote:
Hi
I am trying to install oVirt Node
(ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso) on DELL R805 server,
but every time install fails with Exception: RunTimeError('Failed
to partition/format'). I also
tried ovirt-node-iso-3.0.1-1.0.2.vdsm.el6.iso version and the same
error occures. I tried different partition sizes and I always make
sure that partitions dont exceed the total disk space. I browsed
log fails and could not find anything relevant. I am really out of
ideas...
Any advise?
Thanks
Edgars
___
Users mailing list
Users@ovirt.org mailto:Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Once it fails, press F2 to drop to shell. /tmp/ovirt.log
/var/log/ovirt.log and /var/log/ovirt-node.log will have the debug
messages in it. Paste those in here if you can.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt Node install to USB stick - required 70GB disk space?
On 01/07/2013 07:33 AM, Alexandre Santos wrote: 2013/1/7 Jure Kranjc jure.kra...@arnes.si: Hi, has anybody installed ovirt-node on a bootable usb stick? If the hypervisor is less than 1GB in size, why does installation require 70GB of disk space? It would be perfect to run nodes from usb without any disks. Thanks Jure Kranjc ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Sorry for not asnwering to the list, here are my previous post: How much memory do you have? It seems that it's calculating how much swap it will need and turns that needs at least 70 GB disk space. There is a thread in this forum that has the calculations that ovirt does for it. You can change this values on the boot options. Alex ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Those values are also shown on the installer screen right before entering the password and can be changed ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] some problems on ovirt node while testing latest nightly
On 09/11/2012 10:44 AM, Jorick Astrego wrote: - Original Message - - We have Intel Xenon E5520 Nehalem based cpu's in these local storage nodes. These are still recognized as the Conroe family. Even though BZ#737104 was supposed to have been fixed. (http://gerrit.ovirt.org/#/c/5035/ ) Not ovirt-node directly, I don't think, but a couple things to check. What are the cpu flags on the host (from engine gui)? Is the NX bit set correctly? This is all cpu info I can find in the engine gui CPU Name: Intel Conroe Family CPU Type:Intel(R) Xeon(R) CPU E5520 @ 2.27GHz This is /proc/cpuinfo processor: 15 vendor_id: GenuineIntel cpu family: 6 model: 26 model name: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz stepping: 5 microcode: 0xf cpu MHz: 1600.000 cache size: 8192 KB physical id: 1 siblings: 8 core id: 3 cpu cores: 4 apicid: 23 initial apicid: 23 fpu: yes fpu_exception: yes cpuid level: 11 wp: yes flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida dtherm tpr_shadow vnmi flexpriority ept vpid bogomips: 4532.68 clflush size: 64 cache_alignment: 64 address sizes: 40 bits physical, 48 bits virtual power management: - Most of our nodes use iSCSI but some will need local storage. When trying to setup local storage I get this error: When I check in the directory there is a directory with a UUID containing the folder dom_md and images. I tried clearing the directory and adding storage domain but I get permission errors: run: su - vdsm -s /bin/sh And then delete the directory with the UUID? How does it get there in the first place? This will make auto deployment a bit more difficult. -- Kind Regards, Jorick Astrego Netbulae B.V. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Can you also get the output of virsh capabilites? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] problem building latest node iso image from git
On 08/28/2012 10:34 AM, Jorick Astrego wrote: Hi, After some unsuccessful attempts to install the stable node image on our hardware, I found a patch that can help me. I followed all the steps in the wiki to build a node image and got the build process working (Fedora 17). The successfully built iso fails to start correctly and I get a login prompt. During the built process I had some errors that could be the cause: Installing: sed # [ 43/507] install-info: No such file or directory for /usr/share/info/sed.info.gz Installing: libidn # [ 62/507] install-info: No such file or directory for /usr/share/info/libidn.info.gz Installing: which# [ 73/507] install-info: No such file or directory for /usr/share/info/which.info.gz Installing: grep # [101/507] install-info: No such file or directory for /usr/share/info/grep.info.gz Installing: diffutils# [163/507] install-info: No such file or directory for /usr/share/info/diffutils.info Installing: wget # [215/507] install-info: No such file or directory for /usr/share/info/wget.info.gz Installing: krb5-workstation # [226/507] install-info: No such file or directory for /usr/share/info/krb5-user.info.gz Installing: groff# [227/507] install-info: No such file or directory for /usr/share/info/groff.info Installing: gnupg2 # [287/507] install-info: No such file or directory for /usr/share/info/gnupg.info Installing: gettext # [298/507] install-info: No such file or directory for /usr/share/info/gettext.info.gz Installing: tog-pegasus # [361/507] /usr/share/Pegasus/scripts/genOpenPegasusSSLCerts: line 31: hostname: command not found Installing: grub2# [386/507] install-info: No such file or directory for /usr/share/info/grub2.info.gz install-info: No such file or directory for /usr/share/info/grub2-dev.info.gz Installing: libvirt-cim # [449/507] /var/tmp/rpm-tmp.KwDxnP: line 5: /etc/init.d/tog-pegasus: No such file or directory Installing: vdsm # [501/507] /usr/libexec/vdsm/vdsm-gencerts.sh: line 29: hostname: command not found error reading information on service cgconfig: No such file or directory umount: /tmp/lorax.imgutils.f8u8hE: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) losetup: /dev/loop2: detach failed: Device or resource busy Traceback (most recent call last): File /sbin/mkefiboot, line 139, in module opt.diskname) File /sbin/mkefiboot, line 38, in mkmacboot mkhfsimg(None, outfile, label=label, graft=graft) File /usr/lib/python2.7/site-packages/pylorax/imgutils.py, line 310, in mkhfsimg mkfsargs=[-v, label], graft=graft) File /usr/lib/python2.7/site-packages/pylorax/imgutils.py, line 293, in mkfsimage do_grafts(graft, mnt, preserve) File /usr/lib/python2.7/site-packages/pylorax/imgutils.py, line 206, in __exit__ umount(self.mnt) File /usr/lib/python2.7/site-packages/pylorax/imgutils.py, line 120, in umount os.rmdir(mnt) OSError: [Errno 16] Device or resource busy: '/tmp/lorax.imgutils.f8u8hE' Fixing boot menu /usr/share/info/dir: could not read (No such file or directory) and could not create (No such file or directory) Removing python source files /etc/selinux/targeted/contexts/files/file_contexts: line 768 has invalid context system_u:object_r:selinux_login_config_t:s0 /etc/selinux/targeted/contexts/files/file_contexts: line 1739 has invalid context system_u:object_r:squid_cron_exec_t:s0 /etc/selinux/targeted/contexts/files/file_contexts: line 4225 has invalid context system_u:object_r:ovirt_exec_t:s0 /etc/selinux/targeted/contexts/files/file_contexts: line 4457 has invalid context system_u:object_r:ovirt_exec_t:s0 /etc/selinux/targeted/contexts/files/file_contexts: has invalid context system_u:object_r:selinux_login_config_t:s -- Kind Regards, Netbulae Jorick Astrego Netbulae B.V. Site:http://www.netbulae.eu ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users The build continued so it might be ok although some thing need to
Re: [Users] Building node image
On 06/21/2012 01:18 PM, Olivier Doucet wrote: Hi, I'm trying to build node image myself to test latest patches. I've followed tutorial http://www.ovirt.org/wiki/Node_Building and I'm stuck when doing make iso publish in ovirt-node-iso/ folder with following error : rm -f *.ks Node Creator script is: ../ovirt-node/recipe//node-creator cp ../ovirt-node/recipe//*.ks . rm -f version.ks ( \ echo PRODUCT='oVirt Node Hypervisor' ;\ echo PRODUCT_SHORT='oVirt Node Hypervisor' ;\ echo PACKAGE=ovirt-node-iso ;\ echo VERSION=2.4.0 ;\ echo RELEASE=999.1.fc17 ;\ ) version.ks ksflatten -c ovirt-node-image.ks -o ovirt-node-iso.ks ../ovirt-node/recipe//node-creator ovirt-node-iso.ks Traceback (most recent call last): File /bin/livecd-creator, line 215, in module sys.exit(main()) File /bin/livecd-creator, line 178, in main title=title, product=product) File /usr/lib/python2.7/site-packages/imgcreate/live.py, line 53, in __init__ useplugins=useplugins) File /usr/lib/python2.7/site-packages/imgcreate/creator.py, line 792, in __init__ ImageCreator.__init__(self, ks, name, releasever=releasever, tmpdir=tmpdir, useplugins=useplugins) File /usr/lib/python2.7/site-packages/imgcreate/creator.py, line 85, in __init__ self.__sanity_check() File /usr/lib/python2.7/site-packages/imgcreate/creator.py, line 413, in __sanity_check raise CreatorError(No packages or groups specified) imgcreate.errors.CreatorError: No packages or groups specified ERROR: ISO build failed. make: *** [iso] Error 1 Is there something I did wrong ? Olivier ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users This is a bug, workaround right now is to install older pykickstart package until pykickstart-1.99.13 is available http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=37975 https://bugzilla.redhat.com/show_bug.cgi?id=819672 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Booting oVirt node image 2.3.0, no install option
On 04/18/2012 08:40 AM, Adam vonNieda wrote: Yep, that's exactly the same issue. Mine was a 16Gb Sandisk Cruiser. When I switched to a no-name older 4Gb stick, it worked fine. I set mine up exactly as you did as well, dd from a Mac. Mine booted the kernel just fine as well. I tried booting up setting the rootpw=hash as well, but that didn't work for me, so I was unable to collect any information from the blkid command. I tried it three times, and I know I was doing it correctly. Joey's comments below.. -Adam Joey's comments I did go back and take a look at mount_live and made sure it contains a specific patch to handle usb drives properly. If you can get back to a shell prompt. run blkid and capture the output. If it's way too much to type then just the usb drive output should be ok. Link to shell prompt instructions http://ovirt.org/wiki/Node_Troubleshooting#Boot_up_problems On 4/18/12 5:02 AM, Jason Lawerak...@thegeekhood.net wrote: I think I just hit the exact same issue with a Sandisk Crusier Blade 4GB USB stick. I bought 4 of them to try and setup a test system (before we commit to real hardware) and at least 2 of them failed with both 2.2 and 2.3 ovirt isos being copied using dd from a mac. I copied to a old 8gb Strontium USB stick I had lying around and worked without issue. So it appears to be an issue with the stick. I can provide more specific information on the stick or such if that is useful. It wouldn't surprise me if its due to the low cost nature of the stick (cost $5 AUD) but I am curious as it booted the kernel fine. Jason On 18/04/2012, at 4:48 AM, Adam vonNieda wrote: Turns out that there might be an issue with my thumb drive. I tried another, and it worked fine. Thanks very much for the responses folks! -Adam On 4/17/12 10:11 AM, Joey Boggsjbo...@redhat.com wrote: On 04/17/2012 10:51 AM, Adam vonNieda wrote: Thanks for the reply Joey. I saw that too, and thought maybe my USB thumb drive was set to read only, but it's not. This box doesn't have a DVD drive, I'll try a different USB drive, and if that doesn't work, I'll dig up an external DVD drive. Thanks again, -Adam Adam vonNieda a...@vonnieda.org On Apr 17, 2012, at 9:07, Joey Boggsjbo...@redhat.com wrote: On 04/17/2012 09:45 AM, Adam vonNieda wrote: Hi folks, Still hoping someone can give me a hand with this. I can't install overt-node 2.3.0 on a on a Dell C2100 server because it won't start the graphical interface. I booted up a standard F16 image this morning, and the graphical installer does start during that process. Logs are below. Thanks very much, -Adam /tmp/ovirt.log == /sbin/restorecon set context /var/cache/yum-unconfined_u:object_r:rpm_var_cache_t:s0 failed:'Read-only file system' /sbin/restorecon reset /var/cache/yum context unconfined_u:object_r:file_t:s0-unconfined_u:object_r:rpm_var_cache _t :s0 /sbin/restorecon reset /etc/sysctl.conf context system_u:object_r:etc_runtime_t:s0-system_u:object_r:system_conf_t: s0 /sbin/restorecon reset /boot-kdump context system_u:object_r:boot_t:s0-system_u:object_r:default_t:s0 2012-04-16 09:36:26,827 - INFO - ovirt-config-installer - live device /dev/sdb 2012-04-16 09:36:26,836 - DEBUG - ovirtfunctions - cat /proc/mounts|grep -q none /live 2012-04-16 09:36:26,836 - DEBUG - ovirtfunctions - 2012-04-16 09:36:26,915 - DEBUG - ovirtfunctions - umount /live 2012-04-16 09:36:26,915 - DEBUG - ovirtfunctions - 2012-04-16 09:36:27,455 - ERROR - ovirtfunctions - Failed to mount_live() /var/log/ovirt.log == Apr 16 09:35:53 Starting ovirt-early oVirt Node Hypervisor release 2.3.0 (1.0.fc16) Apr 16 09:35:53 Updating /etc/default/ovirt Apr 16 09:35:54 Updating OVIRT_BOOTIF to '' Apr 16 09:35:54 Updating OVIRT_INIT to '' Apr 16 09:35:54 Updating OVIRT_UPGRADE to '' Apr 16 09:35:54 Updating OVIRT_STANDALONE to '1' Apr 16 09:35:54 Updating OVIRT_BOOTPARAMS to 'nomodeset crashkernel=512M-2G:64M,2G-:128M elevator=deadline quiet rd_NO_LVM rhgb rd.luks=0 rd.md=0 rd.dm=0' Apr 16 09:35:54 Updating OVIRT_RHN_TYPE to 'classic' Apr 16 09:35:54 Updating OVIRT_INSTALL to '1' Apr 16 09:35:54 Updating OVIRT_ISCSI_INSTALL to '1' Apr 16 09:36:08 Setting temporary admin password: F8Ax67kfRPSAw Apr 16 09:36:09 Setting temporary root password: F8Ax67kfRPSAw Apr 16 09:36:09 Skip runtime mode configuration. Apr 16 09:36:09 Completed ovirt-early Apr 16 09:36:09 Starting ovirt-awake. Apr 16 09:36:09 Node is operating in unmanaged mode. Apr 16 09:36:09 Completed ovirt-awake: RETVAL=0 Apr 16 09:36:09 Starting ovirt Apr 16 09:36:09 Completed ovirt Apr 16 09:36:10 Starting ovirt-post Apr 16 09:36:20 Hardware virtualization detected Volume group HostVG not found Skipping volume group HostVG Restarting network (via systemctl): [ OK ] Apr 16 09:36:20 Starting ovirt-post Apr 16 09:36:21 Hardware virtualization detected Volume group HostVG not found Skipping volume group HostVG
Re: [Users] Booting oVirt node image 2.3.0, no install option
On 04/17/2012 09:45 AM, Adam vonNieda wrote: Hi folks, Still hoping someone can give me a hand with this. I can't install overt-node 2.3.0 on a on a Dell C2100 server because it won't start the graphical interface. I booted up a standard F16 image this morning, and the graphical installer does start during that process. Logs are below. Thanks very much, -Adam /tmp/ovirt.log == /sbin/restorecon set context /var/cache/yum-unconfined_u:object_r:rpm_var_cache_t:s0 failed:'Read-only file system' /sbin/restorecon reset /var/cache/yum context unconfined_u:object_r:file_t:s0-unconfined_u:object_r:rpm_var_cache_t:s0 /sbin/restorecon reset /etc/sysctl.conf context system_u:object_r:etc_runtime_t:s0-system_u:object_r:system_conf_t:s0 /sbin/restorecon reset /boot-kdump context system_u:object_r:boot_t:s0-system_u:object_r:default_t:s0 2012-04-16 09:36:26,827 - INFO - ovirt-config-installer - live device /dev/sdb 2012-04-16 09:36:26,836 - DEBUG - ovirtfunctions - cat /proc/mounts|grep -q none /live 2012-04-16 09:36:26,836 - DEBUG - ovirtfunctions - 2012-04-16 09:36:26,915 - DEBUG - ovirtfunctions - umount /live 2012-04-16 09:36:26,915 - DEBUG - ovirtfunctions - 2012-04-16 09:36:27,455 - ERROR - ovirtfunctions - Failed to mount_live() /var/log/ovirt.log == Apr 16 09:35:53 Starting ovirt-early oVirt Node Hypervisor release 2.3.0 (1.0.fc16) Apr 16 09:35:53 Updating /etc/default/ovirt Apr 16 09:35:54 Updating OVIRT_BOOTIF to '' Apr 16 09:35:54 Updating OVIRT_INIT to '' Apr 16 09:35:54 Updating OVIRT_UPGRADE to '' Apr 16 09:35:54 Updating OVIRT_STANDALONE to '1' Apr 16 09:35:54 Updating OVIRT_BOOTPARAMS to 'nomodeset crashkernel=512M-2G:64M,2G-:128M elevator=deadline quiet rd_NO_LVM rhgb rd.luks=0 rd.md=0 rd.dm=0' Apr 16 09:35:54 Updating OVIRT_RHN_TYPE to 'classic' Apr 16 09:35:54 Updating OVIRT_INSTALL to '1' Apr 16 09:35:54 Updating OVIRT_ISCSI_INSTALL to '1' Apr 16 09:36:08 Setting temporary admin password: F8Ax67kfRPSAw Apr 16 09:36:09 Setting temporary root password: F8Ax67kfRPSAw Apr 16 09:36:09 Skip runtime mode configuration. Apr 16 09:36:09 Completed ovirt-early Apr 16 09:36:09 Starting ovirt-awake. Apr 16 09:36:09 Node is operating in unmanaged mode. Apr 16 09:36:09 Completed ovirt-awake: RETVAL=0 Apr 16 09:36:09 Starting ovirt Apr 16 09:36:09 Completed ovirt Apr 16 09:36:10 Starting ovirt-post Apr 16 09:36:20 Hardware virtualization detected Volume group HostVG not found Skipping volume group HostVG Restarting network (via systemctl): [ OK ] Apr 16 09:36:20 Starting ovirt-post Apr 16 09:36:21 Hardware virtualization detected Volume group HostVG not found Skipping volume group HostVG Restarting network (via systemctl): [ OK ] Apr 16 09:36:22 Starting ovirt-cim Apr 16 09:36:22 Completed ovirt-cim WARNING: persistent config storage not available /var/log/vdsm/vdsm.log === MainThread::INFO::2012-04-16 09:36:21,828::vdsm::71::vds::(run) I am the actual vdsm 4.9-0 MainThread::DEBUG::2012-04-16 09:36:23,873::resourceManager::376::ResourceManager::(registerNamespace) Registering namespace 'Storage' MainThread::DEBUG::2012-04-16 09:36:23,874::threadPool::45::Misc.ThreadPool::(__init__) Enter - numThreads: 10.0, waitTimeout: 3, maxTasks: 500.0 MainThread::DEBUG::2012-04-16 09:36:23,918::multipath::85::Storage.Misc.excCmd::(isEnabled) '/usr/bin/sudo -n /bin/cat /etc/multipath.conf' (cwd None) MainThread::INFO::2012-04-16 09:36:25,000::vdsm::71::vds::(run) I am the actual vdsm 4.9-0 MainThread::DEBUG::2012-04-16 09:36:25,199::resourceManager::376::ResourceManager::(registerNamespace) Registering namespace 'Storage' MainThread::DEBUG::2012-04-16 09:36:25,200::threadPool::45::Misc.ThreadPool::(__init__) Enter - numThreads: 10.0, waitTimeout: 3, maxTasks: 500.0 MainThread::DEBUG::2012-04-16 09:36:25,231::multipath::85::Storage.Misc.excCmd::(isEnabled) '/usr/bin/sudo -n /bin/cat /etc/multipath.conf' (cwd None) MainThread::DEBUG::2012-04-16 09:36:25,243::multipath::85::Storage.Misc.excCmd::(isEnabled) SUCCESS: err = '';rc = 0 MainThread::DEBUG::2012-04-16 09:36:25,244::multipath::109::Storage.Multipath::(isEnabled) multipath Defaulting to False MainThread::DEBUG::2012-04-16 09:36:25,244::misc::487::Storage.Misc::(rotateFiles) dir: /etc, prefixName: multipath.conf, versions: 5 MainThread::DEBUG::2012-04-16 09:36:25,244::misc::508::Storage.Misc::(rotateFiles) versions found: [0] MainThread::DEBUG::2012-04-16 09:36:25,244::multipath::118::Storage.Misc.excCmd::(setupMultipath) '/usr/bin/sudo -n /bin/cp /etc/multipath.conf /etc/multipath.conf.1' (cwd None) MainThread::DEBUG::2012-04-16 09:36:25,255::multipath::118::Storage.Misc.excCmd::(setupMultipath) FAILED:err = 'sudo: unable to mkdir /var/db/sudo/vdsm: Read-only file system\nsudo: sorry, a password is required to run sudo\n';rc = 1 MainThread::DEBUG::2012-04-16 09:36:25,256::multipath::118::Storage.Misc.excCmd::(setupMultipath) '/usr/bin/sudo -n /usr/sbin/persist
Re: [Users] proliant errors trying to install ovirt-node image
On 03/05/2012 01:34 PM, Joe Pruett wrote: On 03/05/2012 08:04 AM, Joe Pruett wrote: On 03/05/2012 07:00 AM, Joey Boggs wrote: On 03/05/2012 07:49 AM, Huy, Hermann (NSN - DE/Munich) wrote: -Original Message- From:users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of ext Joe Pruett Sent: Sunday, March 04, 2012 2:11 AM To:users@ovirt.org Subject: [Users] proliant errors trying to install ovirt-node image i've already found the info on the list about the global name 'disk' not defined error and i've tried both an iso from the jenkins url listed, as well as creating my own git area using the 2.2.3 tagged code and making the one line change to fix that python error. but neither of those images work either. i get a generic ovirt node hypervisor installation failed message. i've poked around the log viewers and at the end i see it complaining that the gpt partition label has no bios bootable partition, but it isn't clear if that is really the issue. I ran into the same problems as you when trying to install on a HP ProLiant BL460c G1 blade. The Red Hat Bugzilla report #798030 TUI Installation fails with Grub error seems to address exactly this kind of problem. The grub2-setup complaining has got its reason: In file script/storage.py the disk partitioning is done using a GPT, but no partition with flag bios_grub is created. I modified the source (mis-)using the first partition (EFI partition) in case of a non-EFI boot as a bios_grub flagged partition. This partition is much bigger than necessary (grub2.info recommends one or two MB), thus leaving some room for optimization for the experts when fixing the problem. Please find the patch that allowed successful installation in the attachment. Can you submit this through gerrit, its looks fine to me and I don't see any problem merging it. http://ovirt.org/wiki/Working_with_gerrit.ovirt.org i'll be testing this later and will give feedback. i'm wondering if there might be more cciss driver issues. i haven't dug into the source to figure out the root pw so i could more easily look at the log files or export them. can someone enlighten me with that more quickly than i can find it? As I am stuck to reading log files online or exporting them via screen shots, I am also interested in learning about better ways of exporting. The root password isn't set by default, you can however press F2 inside the installer or the configuration menus to get to a shell prompt and setup networking to get logs off there. i discovered that the root pw is explicitly locked. f2 does nothing at the error screen, alt-f2 shows a login prompt. does f2 stop working at some point during the process? ok, i've dug into this more. my system does not have efi, but the install process is creating an efi partition and making it bootable. it looks like it always does this, all that efi presence seems to do is change the starting sector for the efi partition. so i can't quite see how this works for anyone else :-). and i got f2 to work. it doesn't work while in a log viewer, but does work at the final 'install failed' screen. so i can poke around now. what logs or other info would be of use to look at this more? i may also try installing a non cciss card into this box to see if that is the real root of the problem. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Main install logs are: /tmp/ovirt.log and once the install finishes it will switch over to /var/log/ovirt.log ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Still unable to boot in system with UEFI
On 02/16/2012 08:38 AM, Federico Alberto Sayd wrote: El 15/02/12 13:35, Joey Boggs escribió: On 02/15/2012 11:05 AM, Federico Alberto Sayd wrote: El 15/02/12 12:34, Joey Boggs escribió: On 02/15/2012 10:20 AM, Federico Alberto Sayd wrote: El 14/02/12 13:29, Joey Boggs escribió: On 02/14/2012 10:36 AM, Federico Alberto Sayd wrote: El 14/02/12 10:35, Joey Boggs escribió: On 02/14/2012 08:29 AM, Federico Alberto Sayd wrote: 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Can you boot the image like you did with the grub livecd and run efibootmgr -v also mount /dev/disk/by-label/EFI and run find on where you mounted it. Ok, efibootmgr -v Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables. Try 'modprobe efivars' as root I can't mount /dev/disk/by-label/EFI, when I create a directory and try to mount the partition, mount says: mount: /dev/sda1 already mounted or disco busy however, mount output don't show that /dev/sda1 is mounted Some directories are in read only mode and I could not create a directory to mount the partition, I tried into /config and /live. /dev/disk/by-label/EFI points to /dev/sda1 and disco is the directory mount point. Also, /proc/efi/vars/ and /sys/firmware/efi/vars/ are not present Thanks ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Ah.. was assuming the grub disc you booted from was EFI enabled. Try booting the node iso in EFI mode and run through those steps again. Super grub disk detects the grub.cfg from ovirt's installation and loads the system from this configuration. Therefore I assume that the kernel parameters from grub config loads the system with EFI enabled. The grub config from grub's console is: setparams 'oVirt Node Hypervisor 2.2.2-2.2.fc16' set root=(hd0,3) linux /vmlinuz0 root=live:LABEL=Root ro rootfstype=auto rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline quiet rd_NO_LVM rhgb rd.luks=0 rd.md=0 rd.dm=0 initrd /initrd0.img EFI boot process is done before the grub config comes into play, and the grub config has a few extra lines in it. The machine I'm testing on when you goto the boot menu will show UEFI: $CD_DEVICE_NAME or for boot entries for ovirt it would show: oVirt Node Hypervisor If your grub cd supports efi booting it will be noticeable in the boot menu. In order to do an efi installation it has to be booted in efi mode for it to properly setup the boot entries. Before the Ovirt entry on Grub menu, Grub2 displays the config detected: setparams '(hd0,gpt3)/grub2/grub.cfg' 'hd0,gpt3' '(hd0,gpt3)/grub2/grub.cfg' cfg_device=$2 cfg=$3 root=$cfg_device configfile $cfg Is there where UEFI: parameter must be present? Sorry, I am a newbie to UEFI and Grub2, meanwhile I am reading all I can about Grub2 and UEFI Thanks Thanks ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users You would see it just past the machine posting, on mine you would press F8 to reach a boot menu and then select cd/usb/etc from there. The uefi trigger happens similar to the machine reading a mbr on a drive. One way to notice if its working or not it a higher resolution perception on the monitor, text is smaller and the screen doesn't appear as the normal 80x25 console line/columns. You just need to find the right combination of keys to get in the menu. By livecd-tools defaults the ovirt-node iso supports efi loading. Grub2/uefi support in Fedora isn't quite there yet, so in this case we're still using legacy grub's efi loader and writing an alternate grub config to match it, similar to how Fedora is doing it until grub2 support is there. I guess now I understand you. I have been searching in the UEFI text interface of the blade and it allows browse the EFI System Partition and choose a file to boot. However this EFI interface don't show any file to boot. Then I booted the system with another livecd and mounted the EFI partition; I found that there was not any file in the EFI partition. It seems that blade don't boot because it don't find the efi boot archives. Could it be that ovirt installation fails to write efi boot files? Any
Re: [Users] Still unable to boot in system with UEFI
On 02/14/2012 10:36 AM, Federico Alberto Sayd wrote: El 14/02/12 10:35, Joey Boggs escribió: On 02/14/2012 08:29 AM, Federico Alberto Sayd wrote: 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Can you boot the image like you did with the grub livecd and run efibootmgr -v also mount /dev/disk/by-label/EFI and run find on where you mounted it. Ok, efibootmgr -v Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables. Try 'modprobe efivars' as root I can't mount /dev/disk/by-label/EFI, when I create a directory and try to mount the partition, mount says: mount: /dev/sda1 already mounted or disco busy however, mount output don't show that /dev/sda1 is mounted Some directories are in read only mode and I could not create a directory to mount the partition, I tried into /config and /live. /dev/disk/by-label/EFI points to /dev/sda1 and disco is the directory mount point. Also, /proc/efi/vars/ and /sys/firmware/efi/vars/ are not present Thanks ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Ah.. was assuming the grub disc you booted from was EFI enabled. Try booting the node iso in EFI mode and run through those steps again. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
