Re: [Users] trouble with imported windows VM

2013-04-30 Thread Vered Volansky
Jonathan,

I've asked around (with people not that familiar with v2v) and we're thinking 
of two options -
1. Assuming that the disks weren't imported with the vm at all use v2v to 
import each disk separately, then create a new VM and configure it from the top.
2. If the disks were indeed imported, create a new VM with those disks, 
configure it and remove the old one.

Good luck with that,
Vered

- Original Message -
 From: Jonathan Horne jho...@skopos.us
 To: Richard W.M. Jones rjo...@redhat.com
 Cc: users@ovirt.org
 Sent: Monday, April 29, 2013 3:55:12 PM
 Subject: Re: [Users] trouble with imported windows VM
 
 I did a conversion with all disks connected on the KVM at once (which, the
 KVM version of the VM works fine, all SQL services start and DBs come up
 fine).
 
 When I import the VM with virt-v2v, the new VM will not boot until I remove
 the D drive.
 
 Rich, copying the disk over manually sounds like a viable plan, but im not
 sure what target directory to put it in.  is there some specific place it
 should go when copying in by hand?
 
 Thanks,
 jonathan
 
 -Original Message-
 From: Richard W.M. Jones [mailto:rjo...@redhat.com]
 Sent: Wednesday, April 24, 2013 3:58 PM
 To: Jonathan Horne
 Cc: Itamar Heim; Laszlo Hornyak; users@ovirt.org; Allon Mureinik
 Subject: Re: [Users] trouble with imported windows VM
 
 
 On Wed, Apr 24, 2013 at 05:14:50PM +, Jonathan Horne wrote:
  This is my current gotcha.  If I import it with a single disk from KVM (C
  drive only), its successful.  If I add the 2nd disk to KVM and import it,
  it will import both disks, but I get the error at the beginning of this
  thread.  If I detach the 2nd imported disk, it boots again.
 
  Now, I made another VM on kvm that contained only my D drive, and imported
  that.  After the import, I got this:
 
  [root@d0lppc021 ~]# virt-v2v -i libvirt -ic
  qemu+ssh://root@rnd8/system -o rhev -os d0lppc021.skopos.me:/opt/nfs
  -of qcow2 -oa sparse -n ovirtmgmt ws08-svr-3Donly
  ws08-svr-03-0_copy.raw: 100%
  [=
  ]D 4h09m19s
  virt-v2v: No root device found in this operating system image.
 
 
  The D drive contains only things like SQL db files and other related data.
  Am I using virt-v2v incorrectly for this 2nd disk (in either scenario, a
  single VM with 2 disks, or even on a standalone (and albeit unbootable) VM
  with just the D drive)?
 
 The bad news is that virt-v2v won't work on a data disk.  It has to be
 presented with either just the operating system disk, or all disks at once.
 
 The good news is that you don't need to convert data disks!  virt-v2v knows
 nothing about them, and would do nothing to them.  Simply copy the data disk
 over to the export domain using 'scp' or 'dd' or whatever.
 
 Rich.
 
 --
 Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
 Fedora Windows cross-compiler. Compile Windows programs, test, and build
 Windows installers. Over 100 libraries supported.
 http://fedoraproject.org/wiki/MinGW
 
 
 This is a PRIVATE message. If you are not the intended recipient, please
 delete without copying and kindly advise us by e-mail of the mistake in
 delivery. NOTE: Regardless of content, this e-mail shall not operate to bind
 SKOPOS to any order or other contract unless pursuant to explicit written
 agreement or government initiative expressly permitting the use of e-mail
 for such purpose.
 ___
 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] Error Attaching NFS Data Domain to Data Center - oVirt 3.3

2013-04-30 Thread Vered Volansky
Hi Sherry,

Since it doesn't seem like permissions, the next guess would be - 
There was a workaround done in regard to broken watchdog.
This workaround is in the latest sanlock for fedora 18, which you are already 
using.
If this is indeed the case, all you have to do is update sanlock to latest, 
which can be found in
http://koji.fedoraproject.org/koji/buildinfo?buildID=408258 .

In case this doesn't help, or you already have the latest sanlock, we'll need 
more information in order to detect the issue.
We'd need the following logs:
sanlock.log and /var/log/messages.log from both engine and vdsm, just to be on 
the safe side.
Please attach the full logs.

Thanks,
Vered

- Original Message -
 From: Sherry Yu s...@redhat.com
 To: Allon Mureinik amure...@redhat.com
 Cc: users@ovirt.org
 Sent: Monday, April 29, 2013 7:23:14 PM
 Subject: Re: [Users] Error Attaching NFS Data Domain to Data Center - oVirt 
 3.3
 
 Hi Allon, vdsm has write permission to the directory on NFS. I can see that
 on the hypervisor host the NFS share is mounted and directories have been
 created by vdsm. vdsm log is attached. The error is at
 AcquireHostIdFailure: Cannot acquire host id:
 ('a7138327-930c-49d7-9f39-c34ee36fc7fb', SanlockException(19, 'Sanlock
 lockspace add failure', 'No such device')). Appreciate any input!
 
 [root@sbhost-58 vdsm]# df -k
 
 storage2.phx.salab.redhat.com:/data/sap/ovirt-domain 309637120 187031552
 106876928 64%
 /rhev/data-center/mnt/storage2.phx.salab.redhat.com:_data_sap_ovirt-domain
 
 [root@sbhost-58 dom_md]# pwd
 /rhev/data-center/mnt/storage2.phx.salab.redhat.com:_data_sap_ovirt-domain/a7138327-930c-49d7-9f39-c34ee36fc7fb/dom_md
 
 [root@sbhost-58 dom_md]# ls -la
 total 2060
 drwxr-xr-x. 2 vdsm kvm 4096 Apr 25 20:35 .
 drwxr-xr-x. 4 vdsm kvm 4096 Apr 25 20:35 ..
 -rw-rw. 1 vdsm kvm 1048576 Apr 25 20:35 ids
 -rw-rw. 1 vdsm kvm 0 Apr 25 20:35 inbox
 -rw-rw. 1 vdsm kvm 2097152 Apr 25 20:35 leases
 -rw-r--r--. 1 vdsm kvm 319 Apr 25 20:35 metadata
 -rw-rw. 1 vdsm kvm 0 Apr 25 20:35 outbox
 
 vdsm.log:
 
 Thread-186874::DEBUG::2013-04-29
 12:16:05,229::BindingXMLRPC::161::vds::(wrapper) [10.3.76.215]
 Thread-186874::DEBUG::2013-04-29
 12:16:05,229::task::568::TaskManager.Task::(_updateState)
 Task=`6a316ab2-3d08-44d4-b3d9-60620f23fc72`::moving from state init - state
 preparing
 Thread-186874::INFO::2013-04-29
 12:16:05,230::logUtils::41::dispatcher::(wrapper) Run and protect:
 validateStorageServerConnection(domType=1,
 spUUID='----', conList=[{'port': '',
 'connection': 'storage2.phx.salab.redhat.com:/data/sap/ovirt-domain', 'iqn':
 '', 'portal': '', 'user': '', 'protocol_version': 'auto', 'password':
 '**', 'id': 'c925e43f-ff52-45ae-8484-e4ac6b670143'}], options=None)
 Thread-186874::INFO::2013-04-29
 12:16:05,230::logUtils::44::dispatcher::(wrapper) Run and protect:
 validateStorageServerConnection, Return response: {'statuslist': [{'status':
 0, 'id': 'c925e43f-ff52-45ae-8484-e4ac6b670143'}]}
 Thread-186874::DEBUG::2013-04-29
 12:16:05,230::task::1151::TaskManager.Task::(prepare)
 Task=`6a316ab2-3d08-44d4-b3d9-60620f23fc72`::finished: {'statuslist':
 [{'status': 0, 'id': 'c925e43f-ff52-45ae-8484-e4ac6b670143'}]}
 Thread-186874::DEBUG::2013-04-29
 12:16:05,230::task::568::TaskManager.Task::(_updateState)
 Task=`6a316ab2-3d08-44d4-b3d9-60620f23fc72`::moving from state preparing -
 state finished
 Thread-186874::DEBUG::2013-04-29
 12:16:05,231::resourceManager::830::ResourceManager.Owner::(releaseAll)
 Owner.releaseAll requests {} resources {}
 Thread-186874::DEBUG::2013-04-29
 12:16:05,231::resourceManager::864::ResourceManager.Owner::(cancelAll)
 Owner.cancelAll requests {}
 Thread-186874::DEBUG::2013-04-29
 12:16:05,231::task::957::TaskManager.Task::(_decref)
 Task=`6a316ab2-3d08-44d4-b3d9-60620f23fc72`::ref 0 aborting False
 Thread-186875::DEBUG::2013-04-29
 12:16:05,240::BindingXMLRPC::161::vds::(wrapper) [10.3.76.215]
 Thread-186875::DEBUG::2013-04-29
 12:16:05,240::task::568::TaskManager.Task::(_updateState)
 Task=`e6da9cb6-f577-44bd-a8ba-d08d8946a027`::moving from state init - state
 preparing
 Thread-186875::INFO::2013-04-29
 12:16:05,240::logUtils::41::dispatcher::(wrapper) Run and protect:
 connectStorageServer(domType=1,
 spUUID='----', conList=[{'port': '',
 'connection': 'storage2.phx.salab.redhat.com:/data/sap/ovirt-domain', 'iqn':
 '', 'portal': '', 'user': '', 'protocol_version': 'auto', 'password':
 '**', 'id': 'c925e43f-ff52-45ae-8484-e4ac6b670143'}], options=None)
 Thread-186875::INFO::2013-04-29
 12:16:05,247::logUtils::44::dispatcher::(wrapper) Run and protect:
 connectStorageServer, Return response: {'statuslist': [{'status': 0, 'id':
 'c925e43f-ff52-45ae-8484-e4ac6b670143'}]}
 Thread-186875::DEBUG::2013-04-29
 12:16:05,248::task::1151::TaskManager.Task::(prepare)
 Task=`e6da9cb6-f577-44bd-a8ba-d08d8946a027`::finished: {'statuslist':
 [{'status': 0, 'id': 

Re: [Users] Unable to install F18 on a VM from engine.

2013-04-30 Thread snmishra


Quoting Alon Bar-Lev alo...@redhat.com:


I don't understand...
How did you add the host to the engine? Using Add Host or hack?
If Add Host, can you please attach the relevant log from  
/var/log/ovirt-engine/host-deploy?

Thanks!


I did not install engine from RPM, it was built from source. I do not  
see any host-deploy log file on engine.


I did use add host capability of webadmin to add the host.

I have since reinstalled F18 on the host and installed VDSM using  
latest RPMs. But ran into same situation. Install failed at Preparing  
to install.


-Sharad


- Original Message -

From: snmis...@linux.vnet.ibm.com
To: users@ovirt.org
Sent: Monday, April 29, 2013 11:12:35 PM
Subject: [Users] Unable to install F18 on a VM from engine.

Hi,

I have an F18 engine built from latest (April 28) source. Have
another F18 box running VDSM from RPMs. Added this VDSM host to the
engine. Also have F18 iso image on host for VM installs. Added a new
VM from engine, went to run once and attached the F18 image. Opened
console, started installing Fedora on hard drive, all the install
screens went okay and finally clicked on Begin Install. It brings up
Preparing to install and then just hangs. The host status on engine
goes from up to Non Operational. I have tried it a few times and
everytime, it either fails at Preparing to install or at about 15%
complete.

engine.log -

2013-04-29 12:55:03,932 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
(DefaultQuartzScheduler_Worker-10) Command SpmStatusVDS execution
failed. Exception: VDSNetworkException: java.net.ConnectException:
Connection refused
2013-04-29 12:55:03,935 INFO
[org.ovirt.engine.core.bll.storage.SetStoragePoolStatusCommand]
(DefaultQuartzScheduler_Worker-10) [69ded27f] Running command:
SetStoragePoolStatusCommand internal: true. Entities affected :  ID:
5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool
2013-04-29 12:55:03,947 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.ListVDSCommand]
(DefaultQuartzScheduler_Worker-5) Command ListVDS execution failed.
Exception: VDSNetworkException: java.net.ConnectException: Connection
refused
2013-04-29 12:55:03,950 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(DefaultQuartzScheduler_Worker-5) Failed to refresh VDS , vds =
1827db83-672c-41fe-bf4f-d29a5e25bf3f : host_1, VDS Network Error,
continuing.
java.net.ConnectException: Connection refused
2013-04-29 12:55:04,305 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
(DefaultQuartzScheduler_Worker-10) [69ded27f]
IrsBroker::Failed::GetStoragePoolInfoVDS due to: ConnectException:
Connection refused
2013-04-29 12:55:07,305 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler_Worker-8) Command GetCapabilitiesVDS execution
failed. Exception: VDSNetworkException: java.net.ConnectException:
Connection refused
2013-04-29 12:55:07,306 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(DefaultQuartzScheduler_Worker-8) Failed to refresh VDS , vds =
1827db83-672c-41fe-bf4f-d29a5e25bf3f : host_1, VDS Network Error,
continuing.
java.net.ConnectException: Connection refused
2013-04-29 12:55:10,883 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
(DefaultQuartzScheduler_Worker-7) Command GetCapabilitiesVDS execution
failed. Exception: VDSNetworkException: java.net.ConnectException:
Connection refused
2013-04-29 12:55:10,885 WARN
[org.ovirt.engine.core.vdsbroker.VdsManager]
(DefaultQuartzScheduler_Worker-7) Failed to refresh VDS , vds =
1827db83-672c-41fe-bf4f-d29a5e25bf3f : host_1, VDS Network Error,
continuing.
java.net.ConnectException: Connection refused
2013-04-29 12:55:14,330 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler_Worker-3) START,
GetHardwareInfoVDSCommand(HostName = host_1, HostId =
1827db83-672c-41fe-bf4f-d29a5e25bf3f, vds=Host[host_1]), log id:
523f572b
2013-04-29 12:55:14,614 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler_Worker-3) XML RPC error in command
GetHardwareInfoVDS ( HostName = host_1 ), the error was:
java.util.concurrent.ExecutionException:
java.lang.reflect.InvocationTargetException, type
'exceptions.TypeError':cannot marshal None unless allow_none is enabled
2013-04-29 12:55:14,616 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler_Worker-3) Command GetHardwareInfoVDS execution
failed. Exception: VDSNetworkException:
org.apache.xmlrpc.XmlRpcException: type
'exceptions.TypeError':cannot marshal None unless allow_none is enabled
2013-04-29 12:55:14,618 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
(DefaultQuartzScheduler_Worker-3) FINISH, GetHardwareInfoVDSCommand,
log id: 523f572b
2013-04-29 12:55:14,827 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand]
(DefaultQuartzScheduler_Worker-3) START, FullListVdsCommand( HostId =

Re: [Users] trouble with imported windows VM

2013-04-30 Thread Jonathan Horne
I did try to create a new VM and add the 2 disks that were originally imported, 
but still no go.  The vm refuses to boot.

I was also unable to import just the D drive attached to a VM, it gave me the 
error  virt-v2v: No root device found in this operating system image.  Right 
now I am trying to consolidate the KVM virtual machine down to 1 disk 
partitioned to the necessary C and D drives, and ill try an import like that 
(since it was previously successful coming from KVM with just the one disk).

-Original Message-
From: Vered Volansky [mailto:ve...@redhat.com]
Sent: Tuesday, April 30, 2013 6:45 AM
To: Jonathan Horne
Cc: Richard W.M. Jones; users@ovirt.org
Subject: Re: [Users] trouble with imported windows VM

Jonathan,

I've asked around (with people not that familiar with v2v) and we're thinking 
of two options - 1. Assuming that the disks weren't imported with the vm at all 
use v2v to import each disk separately, then create a new VM and configure it 
from the top.
2. If the disks were indeed imported, create a new VM with those disks, 
configure it and remove the old one.

Good luck with that,
Vered

- Original Message -
 From: Jonathan Horne jho...@skopos.us
 To: Richard W.M. Jones rjo...@redhat.com
 Cc: users@ovirt.org
 Sent: Monday, April 29, 2013 3:55:12 PM
 Subject: Re: [Users] trouble with imported windows VM

 I did a conversion with all disks connected on the KVM at once (which,
 the KVM version of the VM works fine, all SQL services start and DBs
 come up fine).

 When I import the VM with virt-v2v, the new VM will not boot until I
 remove the D drive.

 Rich, copying the disk over manually sounds like a viable plan, but im
 not sure what target directory to put it in.  is there some specific
 place it should go when copying in by hand?

 Thanks,
 jonathan

 -Original Message-
 From: Richard W.M. Jones [mailto:rjo...@redhat.com]
 Sent: Wednesday, April 24, 2013 3:58 PM
 To: Jonathan Horne
 Cc: Itamar Heim; Laszlo Hornyak; users@ovirt.org; Allon Mureinik
 Subject: Re: [Users] trouble with imported windows VM


 On Wed, Apr 24, 2013 at 05:14:50PM +, Jonathan Horne wrote:
  This is my current gotcha.  If I import it with a single disk from
  KVM (C drive only), its successful.  If I add the 2nd disk to KVM
  and import it, it will import both disks, but I get the error at the
  beginning of this thread.  If I detach the 2nd imported disk, it boots 
  again.
 
  Now, I made another VM on kvm that contained only my D drive, and
  imported that.  After the import, I got this:
 
  [root@d0lppc021 ~]# virt-v2v -i libvirt -ic
  qemu+ssh://root@rnd8/system -o rhev -os d0lppc021.skopos.me:/opt/nfs
  -of qcow2 -oa sparse -n ovirtmgmt ws08-svr-3Donly
  ws08-svr-03-0_copy.raw: 100%
  [===
  == ]D 4h09m19s
  virt-v2v: No root device found in this operating system image.
 
 
  The D drive contains only things like SQL db files and other related data.
  Am I using virt-v2v incorrectly for this 2nd disk (in either
  scenario, a single VM with 2 disks, or even on a standalone (and
  albeit unbootable) VM with just the D drive)?

 The bad news is that virt-v2v won't work on a data disk.  It has to be
 presented with either just the operating system disk, or all disks at once.

 The good news is that you don't need to convert data disks!  virt-v2v
 knows nothing about them, and would do nothing to them.  Simply copy
 the data disk over to the export domain using 'scp' or 'dd' or whatever.

 Rich.

 --
 Richard Jones, Virtualization Group, Red Hat
 http://people.redhat.com/~rjones Fedora Windows cross-compiler.
 Compile Windows programs, test, and build Windows installers. Over 100 
 libraries supported.
 http://fedoraproject.org/wiki/MinGW

 
 This is a PRIVATE message. If you are not the intended recipient,
 please delete without copying and kindly advise us by e-mail of the
 mistake in delivery. NOTE: Regardless of content, this e-mail shall
 not operate to bind SKOPOS to any order or other contract unless
 pursuant to explicit written agreement or government initiative
 expressly permitting the use of e-mail for such purpose.
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users



This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to 
any order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] trouble with imported windows VM

2013-04-30 Thread Richard W.M. Jones
On Tue, Apr 30, 2013 at 02:27:16PM +, Jonathan Horne wrote:
 I did try to create a new VM and add the 2 disks that were
 originally imported, but still no go.  The vm refuses to boot.

You need to be much more specific about how it refuses to boot.

 I was also unable to import just the D drive attached to a VM, it
 gave me the error  virt-v2v: No root device found in this operating
 system image. 

As explained earlier, data disks don't need any conversion.  There is
nothing that virt-v2v could do with them, and it isn't able to operate
on data disks, only on operating systems.

 Right now I am trying to consolidate the KVM virtual machine down to
 1 disk partitioned to the necessary C and D drives, and ill try an
 import like that (since it was previously successful coming from KVM
 with just the one disk).

A word of caution: Don't use Windows logical disks.  Use regular
partitions.  Although we now support LDM upstream, that support is not
in RHEL 6.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Configure local storage: VAR__TYPE__STORAGE__DOMAIN, VAR__ACTION__ADD, ACTION_TYPE_FAILED_STORAGE_CONNECTION_NOT_EXIST

2013-04-30 Thread Allon Mureinik
my pleasure.
Sorry it took so long to get to it.

- Original Message -
 From: Dennis Böck den...@webdienstleistungen.com
 To: Allon Mureinik amure...@redhat.com, d...@redhat.com
 Cc: users@oVirt.org users@ovirt.org
 Sent: Monday, April 29, 2013 10:47:18 AM
 Subject: AW: [Users] Configure local storage: VAR__TYPE__STORAGE__DOMAIN, 
 VAR__ACTION__ADD,
 ACTION_TYPE_FAILED_STORAGE_CONNECTION_NOT_EXIST
 
 Hi Allon,
 
 yes - that's it! Now it works. Thanks a lot.
 
 
 
 Von: Allon Mureinik [amure...@redhat.com]
 Gesendet: Montag, 22. April 2013 17:20
 An: d...@redhat.com
 Cc: Dennis Böck; users@oVirt.org
 Betreff: Re: [Users] Configure local storage: VAR__TYPE__STORAGE__DOMAIN,
 VAR__ACTION__ADD, ACTION_TYPE_FAILED_STORAGE_CONNECTION_NOT_EXIST
 
 arg, I always think of the easiest things last.
 
 I reproduced this exact error on my env when I chowned the SD's directory to
 vdsm:kvm, but left the parent directories with no permissions.
 Since your directory is /home/virtualisierungs/vms
 please check the permissions for /home, /home/virtualisierungs and
 /home/virtualisierungs/vms
 
 
 
 
 - Original Message -
  From: Dafna Ron d...@redhat.com
  To: Dennis Böck den...@webdienstleistungen.com
  Cc: users@oVirt.org users@ovirt.org
  Sent: Monday, April 22, 2013 3:02:33 PM
  Subject: Re: [Users] Configure local storage: VAR__TYPE__STORAGE__DOMAIN,
  VAR__ACTION__ADD,
  ACTION_TYPE_FAILED_STORAGE_CONNECTION_NOT_EXIST
 
  hi Dennis,
 
  The error you are getting is indeed that the directory that you are
  trying to use does not exist.
 
  can you send me the following information?
 
  ls -l output for /home/virtualisierung/
  the exact path that you are using in the configure local storage dialogue.
  what nfs version do you have on the host?
  what is the vdsm version on your host?
 
 
  Thanks,
  Dafna
 
 
  On 04/22/2013 01:53 PM, Dennis Böck wrote:
   Dear Dafina,
  
   vdsm and engine logs attached.
   I used the most current Fedora 18 nfs (nts-utils-1.2.7-6.fc18.x86_64)
  
   
   Von: Dafna Ron [d...@redhat.com]
   Gesendet: Sonntag, 21. April 2013 11:06
   An: Dennis Böck
   Cc: Itamar Heim; users@oVirt.org
   Betreff: Re: [Users] Configure local storage: VAR__TYPE__STORAGE__DOMAIN,
   VAR__ACTION__ADD, ACTION_TYPE_FAILED_STORAGE_CONNECTION_NOT_EXIST
  
   are you using regular nfs domain or posix? what nfs version are you
   using?
   can you please send us full vdsm and engine logs.
  
  
   On 04/21/2013 12:04 PM, Dennis Böck wrote:
   No, unfortunately not.
  
   -Ursprüngliche Nachricht-
   Von: Itamar Heim [mailto:ih...@redhat.com]
   Gesendet: Samstag, 20. April 2013 20:16
   An: Dennis Böck
   Cc: Allon Mureinik; users@oVirt.org
   Betreff: Re: [Users] Configure local storage:
   VAR__TYPE__STORAGE__DOMAIN,
   VAR__ACTION__ADD, ACTION_TYPE_FAILED_STORAGE_CONNECTION_NOT_EXIST
  
   On 04/12/2013 06:19 PM, Dennis Böck wrote:
   I installed ovirt-engine all-in-one package and tried again to
   configure
   vdsm on the host. But again the point AIO: Adding local storage
   failed, see log attached.
   was this resolved?
  
   Best regards
   Dennis
  
   
   Von: users-boun...@ovirt.org [users-boun...@ovirt.org]quot; im
   Auftrag von quot;Dennis Böck [den...@webdienstleistungen.com]
   Gesendet: Donnerstag, 11. April 2013 16:24
   An: Allon Mureinik
   Cc: users@oVirt.org
   Betreff: Re: [Users] Configure local storage:
   VAR__TYPE__STORAGE__DOMAIN, VAR__ACTION__ADD,
   ACTION_TYPE_FAILED_STORAGE_CONNECTION_NOT_EXIST
  
   Dear Allon,
  
   I checked it: the path /home/virtualisierung/local-storage did exist
   (and still exists). Owner: vdsm, Group: kvm Rights: drwxr-xr-x I
   installed the engine and vdsm on the same host - can this lead to
   problems?
  
   Best regards
   Dennis
   
   Von: Allon Mureinik [amure...@redhat.com]
   Gesendet: Donnerstag, 11. April 2013 09:50
   An: Dennis Böck
   Cc: users@oVirt.org
   Betreff: Re: AW: [Users] Configure local storage:
   VAR__TYPE__STORAGE__DOMAIN, VAR__ACTION__ADD,
   ACTION_TYPE_FAILED_STORAGE_CONNECTION_NOT_EXIST
  
   Looks as though the path really doesn't exist:
   Thread-162::INFO::2013-04-09
   17:43:26,275::logUtils::41::dispatcher::(wrapper) Run and protect:
   connectStorageServer(domType=4,
   spUUID='----', conList=[{'connection':
   '/home/virtualisierung/local-storage', 'iqn': '', 'portal': '',
   'user': '', 'password': '**', 'id':
   '----', 'port': ''}], options=None)
   Thread-162::ERROR::2013-04-09
   17:43:26,275::hsm::2215::Storage.HSM::(connectStorageServer) Could not
   connect to storageServer Traceback (most recent call last):
File /usr/share/vdsm/storage/hsm.py, line 2211, in
connectStorageServer
  conObj.connect()
File 

Re: [Users] forced shutdown with client agent

2013-04-30 Thread Gianluca Cecchi
On Tue, Apr 23, 2013 at 8:58 AM, Michal Skrivanek wrote:



 do we allow users to cancel the shutdown?
 nope.
 It can be stopped inside the guest, well, if you manage to do that in that 
 short time.


BTW: I tried today with ovirt 3.2.1 and it is not possible to
interrupt shutdown, at least with shutdown -c command

With agent inside a CentOS 6.4 VM the comamnd run is:

[root@c2 ~]# ps -ef|grep shut
root 15767  1581  0 23:39 ?00:00:00 rhev-shutdown -h +1
System Administrator has initiated shutdown of this Virtual Machine.
Virtual Machine is shutting down.
root 15768 15767  0 23:39 ?00:00:00 [shutdown] defunct
root 15799 15781  0 23:40 pts/000:00:00 grep shut

If you try to cancel it with
shutdown -c

you get

shutdown: Cannot find pid of running shutdown

I don't know if Michal meant instead to kill the pid processes
themselves (15767 and and 15768 in my case)

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Unable to install F18 on a VM from engine.

2013-04-30 Thread snmishra


Quoting Alon Bar-Lev alo...@redhat.com:


- Original Message -

From: snmis...@linux.vnet.ibm.com
To: Alon Bar-Lev alo...@redhat.com
Cc: users@ovirt.org
Sent: Tuesday, April 30, 2013 4:50:19 PM
Subject: Re: [Users] Unable to install F18 on a VM from engine.


Quoting Alon Bar-Lev alo...@redhat.com:

 I don't understand...
 How did you add the host to the engine? Using Add Host or hack?
 If Add Host, can you please attach the relevant log from
 /var/log/ovirt-engine/host-deploy?
 Thanks!

I did not install engine from RPM, it was built from source. I do not
see any host-deploy log file on engine.

I did use add host capability of webadmin to add the host.


This is unsupported in current master development mode. If you like  
you can try upcoming new packaging[1][2] and provide some feedback.




Alon,

   I appreciate your quick responses. Thank you.

   So far I have been using wiki page -  
http://www.ovirt.org/Building_oVirt_engine

   and for eclipse - http://www.ovirt.org/Building_oVirt_Engine/IDE
   for engine development and its worked well, except I never  
actually installed OS on my VMs. This is the first time doing it and  
its failing.


   Are you suggesting that I stop using above wiki and instead use  
otopi [1][2]?


   My main struggle right now is to add another fedora machine as  
host and create VMs and run those VMs. There are various wikis/web  
pages that are out there to get one up and running with VDSM, but its  
always been touch and go. Can you suggest one that works for F18 host?



Thanks
Sharad Mishra


[1] https://github.com/alonbl/ovirt-engine/tree/otopi
[2] https://github.com/alonbl/ovirt-engine/blob/otopi/README.developer



I have since reinstalled F18 on the host and installed VDSM using
latest RPMs. But ran into same situation. Install failed at Preparing
to install.

-Sharad

 - Original Message -
 From: snmis...@linux.vnet.ibm.com
 To: users@ovirt.org
 Sent: Monday, April 29, 2013 11:12:35 PM
 Subject: [Users] Unable to install F18 on a VM from engine.

 Hi,

 I have an F18 engine built from latest (April 28) source. Have
 another F18 box running VDSM from RPMs. Added this VDSM host to the
 engine. Also have F18 iso image on host for VM installs. Added a new
 VM from engine, went to run once and attached the F18 image. Opened
 console, started installing Fedora on hard drive, all the install
 screens went okay and finally clicked on Begin Install. It brings up
 Preparing to install and then just hangs. The host status on engine
 goes from up to Non Operational. I have tried it a few times and
 everytime, it either fails at Preparing to install or at about 15%
 complete.

 engine.log -

 2013-04-29 12:55:03,932 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
 (DefaultQuartzScheduler_Worker-10) Command SpmStatusVDS execution
 failed. Exception: VDSNetworkException: java.net.ConnectException:
 Connection refused
 2013-04-29 12:55:03,935 INFO
 [org.ovirt.engine.core.bll.storage.SetStoragePoolStatusCommand]
 (DefaultQuartzScheduler_Worker-10) [69ded27f] Running command:
 SetStoragePoolStatusCommand internal: true. Entities affected :  ID:
 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool
 2013-04-29 12:55:03,947 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.ListVDSCommand]
 (DefaultQuartzScheduler_Worker-5) Command ListVDS execution failed.
 Exception: VDSNetworkException: java.net.ConnectException: Connection
 refused
 2013-04-29 12:55:03,950 WARN
 [org.ovirt.engine.core.vdsbroker.VdsManager]
 (DefaultQuartzScheduler_Worker-5) Failed to refresh VDS , vds =
 1827db83-672c-41fe-bf4f-d29a5e25bf3f : host_1, VDS Network Error,
 continuing.
 java.net.ConnectException: Connection refused
 2013-04-29 12:55:04,305 ERROR
 [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
 (DefaultQuartzScheduler_Worker-10) [69ded27f]
 IrsBroker::Failed::GetStoragePoolInfoVDS due to: ConnectException:
 Connection refused
 2013-04-29 12:55:07,305 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
 (DefaultQuartzScheduler_Worker-8) Command GetCapabilitiesVDS execution
 failed. Exception: VDSNetworkException: java.net.ConnectException:
 Connection refused
 2013-04-29 12:55:07,306 WARN
 [org.ovirt.engine.core.vdsbroker.VdsManager]
 (DefaultQuartzScheduler_Worker-8) Failed to refresh VDS , vds =
 1827db83-672c-41fe-bf4f-d29a5e25bf3f : host_1, VDS Network Error,
 continuing.
 java.net.ConnectException: Connection refused
 2013-04-29 12:55:10,883 ERROR
 [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
 (DefaultQuartzScheduler_Worker-7) Command GetCapabilitiesVDS execution
 failed. Exception: VDSNetworkException: java.net.ConnectException:
 Connection refused
 2013-04-29 12:55:10,885 WARN
 [org.ovirt.engine.core.vdsbroker.VdsManager]
 (DefaultQuartzScheduler_Worker-7) Failed to refresh VDS , vds =
 1827db83-672c-41fe-bf4f-d29a5e25bf3f : host_1, VDS Network Error,
 continuing.
 

Re: [Users] Unable to install F18 on a VM from engine.

2013-04-30 Thread Alon Bar-Lev


- Original Message -
 From: snmis...@linux.vnet.ibm.com
 To: Alon Bar-Lev alo...@redhat.com
 Cc: users@ovirt.org
 Sent: Wednesday, May 1, 2013 1:02:27 AM
 Subject: Re: [Users] Unable to install F18 on a VM from engine.
 
 
 Quoting Alon Bar-Lev alo...@redhat.com:
 
  - Original Message -
  From: snmis...@linux.vnet.ibm.com
  To: Alon Bar-Lev alo...@redhat.com
  Cc: users@ovirt.org
  Sent: Tuesday, April 30, 2013 4:50:19 PM
  Subject: Re: [Users] Unable to install F18 on a VM from engine.
 
 
  Quoting Alon Bar-Lev alo...@redhat.com:
 
   I don't understand...
   How did you add the host to the engine? Using Add Host or hack?
   If Add Host, can you please attach the relevant log from
   /var/log/ovirt-engine/host-deploy?
   Thanks!
 
  I did not install engine from RPM, it was built from source. I do not
  see any host-deploy log file on engine.
 
  I did use add host capability of webadmin to add the host.
 
  This is unsupported in current master development mode. If you like
  you can try upcoming new packaging[1][2] and provide some feedback.
 
 
 Alon,
 
 I appreciate your quick responses. Thank you.
 
 So far I have been using wiki page -
 http://www.ovirt.org/Building_oVirt_engine
 and for eclipse - http://www.ovirt.org/Building_oVirt_Engine/IDE
 for engine development and its worked well, except I never
 actually installed OS on my VMs. This is the first time doing it and
 its failing.
 
 Are you suggesting that I stop using above wiki and instead use
 otopi [1][2]?

Yes. We invested a lot of effort to create a fully functional development 
environment, similar to production setup.
 
 My main struggle right now is to add another fedora machine as
 host and create VMs and run those VMs. There are various wikis/web
 pages that are out there to get one up and running with VDSM, but its
 always been touch and go. Can you suggest one that works for F18 host?

Sure... if you use[1][2] and follow the instructions, you will be able to 
install vanilla f18 host and then simply use the Add Host functionality of 
the engine. The engine will deploy the host including vdsm. This is the major 
improvement of the environment compared to the hacky solutions of the past.

It is relatively new and changing, so any feedback will be appreciated.

Thanks,
Alon

 
 
 Thanks
 Sharad Mishra
 
  [1] https://github.com/alonbl/ovirt-engine/tree/otopi
  [2] https://github.com/alonbl/ovirt-engine/blob/otopi/README.developer
 
 
  I have since reinstalled F18 on the host and installed VDSM using
  latest RPMs. But ran into same situation. Install failed at Preparing
  to install.
 
  -Sharad
  
   - Original Message -
   From: snmis...@linux.vnet.ibm.com
   To: users@ovirt.org
   Sent: Monday, April 29, 2013 11:12:35 PM
   Subject: [Users] Unable to install F18 on a VM from engine.
  
   Hi,
  
   I have an F18 engine built from latest (April 28) source. Have
   another F18 box running VDSM from RPMs. Added this VDSM host to the
   engine. Also have F18 iso image on host for VM installs. Added a new
   VM from engine, went to run once and attached the F18 image. Opened
   console, started installing Fedora on hard drive, all the install
   screens went okay and finally clicked on Begin Install. It brings up
   Preparing to install and then just hangs. The host status on engine
   goes from up to Non Operational. I have tried it a few times and
   everytime, it either fails at Preparing to install or at about 15%
   complete.
  
   engine.log -
  
   2013-04-29 12:55:03,932 ERROR
   [org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand]
   (DefaultQuartzScheduler_Worker-10) Command SpmStatusVDS execution
   failed. Exception: VDSNetworkException: java.net.ConnectException:
   Connection refused
   2013-04-29 12:55:03,935 INFO
   [org.ovirt.engine.core.bll.storage.SetStoragePoolStatusCommand]
   (DefaultQuartzScheduler_Worker-10) [69ded27f] Running command:
   SetStoragePoolStatusCommand internal: true. Entities affected :  ID:
   5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool
   2013-04-29 12:55:03,947 ERROR
   [org.ovirt.engine.core.vdsbroker.vdsbroker.ListVDSCommand]
   (DefaultQuartzScheduler_Worker-5) Command ListVDS execution failed.
   Exception: VDSNetworkException: java.net.ConnectException: Connection
   refused
   2013-04-29 12:55:03,950 WARN
   [org.ovirt.engine.core.vdsbroker.VdsManager]
   (DefaultQuartzScheduler_Worker-5) Failed to refresh VDS , vds =
   1827db83-672c-41fe-bf4f-d29a5e25bf3f : host_1, VDS Network Error,
   continuing.
   java.net.ConnectException: Connection refused
   2013-04-29 12:55:04,305 ERROR
   [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand]
   (DefaultQuartzScheduler_Worker-10) [69ded27f]
   IrsBroker::Failed::GetStoragePoolInfoVDS due to: ConnectException:
   Connection refused
   2013-04-29 12:55:07,305 ERROR
   [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand]
   

Re: [Users] Error Attaching NFS Data Domain to Data Center - oVirt 3.3

2013-04-30 Thread Sherry Yu
I upgraded kernel, sanlock, and its dependencies on the f18 host, and the error 
is gone.

Thanks,
Sherry

- Original Message -
| Hi Sherry,
| 
| Since it doesn't seem like permissions, the next guess would be -
| There was a workaround done in regard to broken watchdog.
| This workaround is in the latest sanlock for fedora 18, which you are already
| using.
| If this is indeed the case, all you have to do is update sanlock to latest,
| which can be found in
| http://koji.fedoraproject.org/koji/buildinfo?buildID=408258 .
| 
| In case this doesn't help, or you already have the latest sanlock, we'll need
| more information in order to detect the issue.
| We'd need the following logs:
| sanlock.log and /var/log/messages.log from both engine and vdsm, just to be
| on the safe side.
| Please attach the full logs.
| 
| Thanks,
| Vered
| 
| - Original Message -
|  From: Sherry Yu s...@redhat.com
|  To: Allon Mureinik amure...@redhat.com
|  Cc: users@ovirt.org
|  Sent: Monday, April 29, 2013 7:23:14 PM
|  Subject: Re: [Users] Error Attaching NFS Data Domain to Data Center - oVirt
|  3.3
|  
|  Hi Allon, vdsm has write permission to the directory on NFS. I can see that
|  on the hypervisor host the NFS share is mounted and directories have been
|  created by vdsm. vdsm log is attached. The error is at
|  AcquireHostIdFailure: Cannot acquire host id:
|  ('a7138327-930c-49d7-9f39-c34ee36fc7fb', SanlockException(19, 'Sanlock
|  lockspace add failure', 'No such device')). Appreciate any input!
|  
|  [root@sbhost-58 vdsm]# df -k
|  
|  storage2.phx.salab.redhat.com:/data/sap/ovirt-domain 309637120 187031552
|  106876928 64%
|  /rhev/data-center/mnt/storage2.phx.salab.redhat.com:_data_sap_ovirt-domain
|  
|  [root@sbhost-58 dom_md]# pwd
|  
/rhev/data-center/mnt/storage2.phx.salab.redhat.com:_data_sap_ovirt-domain/a7138327-930c-49d7-9f39-c34ee36fc7fb/dom_md
|  
|  [root@sbhost-58 dom_md]# ls -la
|  total 2060
|  drwxr-xr-x. 2 vdsm kvm 4096 Apr 25 20:35 .
|  drwxr-xr-x. 4 vdsm kvm 4096 Apr 25 20:35 ..
|  -rw-rw. 1 vdsm kvm 1048576 Apr 25 20:35 ids
|  -rw-rw. 1 vdsm kvm 0 Apr 25 20:35 inbox
|  -rw-rw. 1 vdsm kvm 2097152 Apr 25 20:35 leases
|  -rw-r--r--. 1 vdsm kvm 319 Apr 25 20:35 metadata
|  -rw-rw. 1 vdsm kvm 0 Apr 25 20:35 outbox
|  
|  vdsm.log:
|  
|  Thread-186874::DEBUG::2013-04-29
|  12:16:05,229::BindingXMLRPC::161::vds::(wrapper) [10.3.76.215]
|  Thread-186874::DEBUG::2013-04-29
|  12:16:05,229::task::568::TaskManager.Task::(_updateState)
|  Task=`6a316ab2-3d08-44d4-b3d9-60620f23fc72`::moving from state init -
|  state
|  preparing
|  Thread-186874::INFO::2013-04-29
|  12:16:05,230::logUtils::41::dispatcher::(wrapper) Run and protect:
|  validateStorageServerConnection(domType=1,
|  spUUID='----', conList=[{'port': '',
|  'connection': 'storage2.phx.salab.redhat.com:/data/sap/ovirt-domain',
|  'iqn':
|  '', 'portal': '', 'user': '', 'protocol_version': 'auto', 'password':
|  '**', 'id': 'c925e43f-ff52-45ae-8484-e4ac6b670143'}], options=None)
|  Thread-186874::INFO::2013-04-29
|  12:16:05,230::logUtils::44::dispatcher::(wrapper) Run and protect:
|  validateStorageServerConnection, Return response: {'statuslist':
|  [{'status':
|  0, 'id': 'c925e43f-ff52-45ae-8484-e4ac6b670143'}]}
|  Thread-186874::DEBUG::2013-04-29
|  12:16:05,230::task::1151::TaskManager.Task::(prepare)
|  Task=`6a316ab2-3d08-44d4-b3d9-60620f23fc72`::finished: {'statuslist':
|  [{'status': 0, 'id': 'c925e43f-ff52-45ae-8484-e4ac6b670143'}]}
|  Thread-186874::DEBUG::2013-04-29
|  12:16:05,230::task::568::TaskManager.Task::(_updateState)
|  Task=`6a316ab2-3d08-44d4-b3d9-60620f23fc72`::moving from state preparing -
|  state finished
|  Thread-186874::DEBUG::2013-04-29
|  12:16:05,231::resourceManager::830::ResourceManager.Owner::(releaseAll)
|  Owner.releaseAll requests {} resources {}
|  Thread-186874::DEBUG::2013-04-29
|  12:16:05,231::resourceManager::864::ResourceManager.Owner::(cancelAll)
|  Owner.cancelAll requests {}
|  Thread-186874::DEBUG::2013-04-29
|  12:16:05,231::task::957::TaskManager.Task::(_decref)
|  Task=`6a316ab2-3d08-44d4-b3d9-60620f23fc72`::ref 0 aborting False
|  Thread-186875::DEBUG::2013-04-29
|  12:16:05,240::BindingXMLRPC::161::vds::(wrapper) [10.3.76.215]
|  Thread-186875::DEBUG::2013-04-29
|  12:16:05,240::task::568::TaskManager.Task::(_updateState)
|  Task=`e6da9cb6-f577-44bd-a8ba-d08d8946a027`::moving from state init -
|  state
|  preparing
|  Thread-186875::INFO::2013-04-29
|  12:16:05,240::logUtils::41::dispatcher::(wrapper) Run and protect:
|  connectStorageServer(domType=1,
|  spUUID='----', conList=[{'port': '',
|  'connection': 'storage2.phx.salab.redhat.com:/data/sap/ovirt-domain',
|  'iqn':
|  '', 'portal': '', 'user': '', 'protocol_version': 'auto', 'password':
|  '**', 'id': 'c925e43f-ff52-45ae-8484-e4ac6b670143'}], options=None)
|  Thread-186875::INFO::2013-04-29
|