Re: [ovirt-users] USB

2016-05-16 Thread Brett I. Holcomb
On Sun, 2016-05-15 at 14:40 +0300, Nisim Simsolo wrote:
> Hi
> 
> You can attach host device directly from virtual machines tab ->
> select VM -> host devices sub tab -> "add device" button.
> 
> But first you need to verify your BIOS is supporting intel VT-d or
> AMD vi.
> And you also need to activate it in the kernel. The next link
> describes how to do it: 
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linu
> x/7/html/Virtualization_Deployment_and_Administration_Guide/chap-
> Guest_virtual_machine_device_configuration.html#sect-
> Guest_virtual_machine_device_configuration-PCI_devices
> 
> note: Instead of adding "intel_iommu=pt" in the grub cmdline, add
> "intel_iommu=on" or "amd_iommu=on".
> 
> Thank you  Nsim and Martin.  I'll give that  a try.
As a point of information has anyone tried USB/IP or Incentives Pro?___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Adding another host to my cluster

2016-05-16 Thread Gervais de Montbrun
Hi Roy,

I've added /var/log/ovirt-engine/engine.log to my DropBox: 
https://www.dropbox.com/sh/21lkl6ao3hv2r85/AADDMCK4Dp7UYgs5P6dMQxHKa/vdsm?dl=0 


When I look in the engine.log, I see the error "unable to load number from 
serial.txt"
I did a find for serial.txt and the only file that comes up is: 
/etc/pki/ovirt-engine/serial.txt 
(Makes sense that this is the file it wants to read)
When I open /etc/pki/ovirt-engine/serial.txt, it is an empty file. 
[root@cultivar ovirt-engine]# cat /etc/pki/ovirt-engine/serial.txt
[root@cultivar ovirt-engine]# 

What should be in serial.txt?

I don't understand where to find the other log that you mention in your email 
below. I don't see any paths listed in the UI when I click on the failed event 
for certificate enrollment.

Cheers,
Gervais



> On May 15, 2016, at 5:10 PM, Roy Golan  > wrote:
> 
> 
> 
> On Sun, May 15, 2016 at 1:32 AM, Gervais de Montbrun  > wrote:
> Hey Folks,
> 
> I'm still stuck here... I believe the issue may be because the Enrolling 
> certificates stage is failing...
> 
> Any idea's how to sort this out?
> 
> I see:
>   Installing Host Cultivar2. Enrolling certificate
>   Failed to install Host Cultivar2. Certificate enrollment failed.
>   Host Cultivar2 installation failed. Certificate enrollement failed.
> 
> Any attempt to re-install fails at this step.
> 
> Cheers,
> Gervais
> 
> 
> 
> I also see in the logs that the manager (ovirt-engine) rejected the host 
> addition to the setup. Please add the /var/log/ovirt-engine/engine.log from 
> the engine machine. Also, the engine machine has the install log - open one 
> of the Event logs in the UI that says you host installation failed and you 
> will see it retrieved the install log to a path under your engine. Please 
> include this as well.
>  
> 
>> On May 13, 2016, at 1:36 PM, Gervais de Montbrun > > wrote:
>> 
>> Hi Nir,
>> 
>> Thank you for you input.
>> 
>> It was suggest that I try starting vdsm from the shell so I could see the 
>> output in an effort to solve my issue: 
>> http://lists.ovirt.org/pipermail/users/2016-May/039690.html 
>> 
>> 
>> Cheers,
>> Gervais
>> 
>> 
>> 
>>> On May 13, 2016, at 12:12 PM, Nir Soffer >> > wrote:
>>> 
>>> On Fri, May 13, 2016 at 3:37 PM, Gervais de Montbrun
>>> > wrote:
 Hi Charles,
 
 I think the problem I am having is due to the setup failing and not
 something in vdsm configs as I have never gotten this server to start up
 properly and the BRIDGE ethernet interface + ovirt routes are not setup.
 
 I put the logs here:
 https://www.dropbox.com/sh/5ugyykqh1lgru9l/AACXxRYWr3tgd0WbBVFW5twHa?dl=0 
 
 
 hosted-engine--deploy-logs.zip # Logs from when I tried to deploy and it
 failed
 vdsm.tar.gz # /var/log/vdsm
 
 Output from running vdsm from the command line:
 
 [root@cultivar2 log]# su -s /bin/bash vdsm
>>> 
>>> This cannot work unless supervdsmd is running...
>>> 
 [vdsm@cultivar2 log]$ python /usr/share/vdsm/vdsm
 (PID: 6521) I am the actual vdsm 4.17.26-1.el7
 cultivar2.grove.silverorange.com 
  (3.10.0-327.el7.x86_64)
 VDSM will run with cpu affinity: frozenset([1])
 /usr/bin/taskset --all-tasks --pid --cpu-list 1 6521 (cwd None)
 SUCCESS:  = '';  = 0
 Starting scheduler vdsm.Scheduler
 started
 Run and protect:
 registerDomainStateChangeCallback(callbackFunc=>>> 0x381b158>)
 Run and protect: registerDomainStateChangeCallback, Return response: None
 Trying to connect to Super Vdsm
 Preparing MOM interface
 Using named unix socket /var/run/vdsm/mom-vdsm.sock
 Unregistering all secrests
 trying to connect libvirt
 recovery: started
 Setting channels' timeout to 30 seconds.
 Starting VM channels listener thread.
 Listening at 0.0.0.0:54321 
 Adding detector 
 recovery: completed in 0s
 Adding detector >>> 0x382e5a8>
 Starting executor
 Starting worker jsonrpc.Executor/0
 Worker started
 Starting worker jsonrpc.Executor/1
 Worker started
 Starting worker jsonrpc.Executor/2
 Worker started
 Starting worker jsonrpc.Executor/3
 Worker started
 Starting worker jsonrpc.Executor/4
 Worker started
 Starting worker jsonrpc.Executor/5
 Worker started
 Starting worker jsonrpc.Executor/6
 Worker started
 Starting worker jsonrpc.Executor/7
 Worker started
 XMLRPC 

Re: [ovirt-users] Adding another host to my cluster

2016-05-16 Thread Gervais de Montbrun
Roy,

Thank you so much for asking for the logs on the engine. The serial.txt bein 
blank was my issue. I found a solution in the following thread online here: 
http://lists.ovirt.org/pipermail/users/2014-November/028870.html
I did the exact same thing that Dinuwan did to solve his issue back in 2014 and 
was able to enrol my new server and install the hosted-engine just fine on it.

I am not certain what caused serial.txt to be empty and am will to share logs 
to anyone from the oVirt team who might want to see them. For my purposes, I'm 
considering this issue solved.

Thanks to everyone who offered advice and suggestions.

Cheers,
Gervais



> On May 16, 2016, at 2:04 PM, Gervais de Montbrun  
> wrote:
> 
> Hi Roy,
> 
> I've added /var/log/ovirt-engine/engine.log to my DropBox: 
> https://www.dropbox.com/sh/21lkl6ao3hv2r85/AADDMCK4Dp7UYgs5P6dMQxHKa/vdsm?dl=0
>  
> 
> 
> When I look in the engine.log, I see the error "unable to load number from 
> serial.txt"
> I did a find for serial.txt and the only file that comes up is: 
> /etc/pki/ovirt-engine/serial.txt 
> (Makes sense that this is the file it wants to read)
> When I open /etc/pki/ovirt-engine/serial.txt, it is an empty file. 
>   [root@cultivar ovirt-engine]# cat /etc/pki/ovirt-engine/serial.txt
>   [root@cultivar ovirt-engine]# 
> 
> What should be in serial.txt?
> 
> I don't understand where to find the other log that you mention in your email 
> below. I don't see any paths listed in the UI when I click on the failed 
> event for certificate enrollment.
> 
> Cheers,
> Gervais
> 
> 
> 
>> On May 15, 2016, at 5:10 PM, Roy Golan > > wrote:
>> 
>> 
>> 
>> On Sun, May 15, 2016 at 1:32 AM, Gervais de Montbrun > > wrote:
>> Hey Folks,
>> 
>> I'm still stuck here... I believe the issue may be because the Enrolling 
>> certificates stage is failing...
>> 
>> Any idea's how to sort this out?
>> 
>> I see:
>>  Installing Host Cultivar2. Enrolling certificate
>>  Failed to install Host Cultivar2. Certificate enrollment failed.
>>  Host Cultivar2 installation failed. Certificate enrollement failed.
>> 
>> Any attempt to re-install fails at this step.
>> 
>> Cheers,
>> Gervais
>> 
>> 
>> 
>> I also see in the logs that the manager (ovirt-engine) rejected the host 
>> addition to the setup. Please add the /var/log/ovirt-engine/engine.log from 
>> the engine machine. Also, the engine machine has the install log - open one 
>> of the Event logs in the UI that says you host installation failed and you 
>> will see it retrieved the install log to a path under your engine. Please 
>> include this as well.
>>  
>> 
>>> On May 13, 2016, at 1:36 PM, Gervais de Montbrun >> > wrote:
>>> 
>>> Hi Nir,
>>> 
>>> Thank you for you input.
>>> 
>>> It was suggest that I try starting vdsm from the shell so I could see the 
>>> output in an effort to solve my issue: 
>>> http://lists.ovirt.org/pipermail/users/2016-May/039690.html 
>>> 
>>> 
>>> Cheers,
>>> Gervais
>>> 
>>> 
>>> 
 On May 13, 2016, at 12:12 PM, Nir Soffer > wrote:
 
 On Fri, May 13, 2016 at 3:37 PM, Gervais de Montbrun
 > wrote:
> Hi Charles,
> 
> I think the problem I am having is due to the setup failing and not
> something in vdsm configs as I have never gotten this server to start up
> properly and the BRIDGE ethernet interface + ovirt routes are not setup.
> 
> I put the logs here:
> https://www.dropbox.com/sh/5ugyykqh1lgru9l/AACXxRYWr3tgd0WbBVFW5twHa?dl=0 
> 
> 
> hosted-engine--deploy-logs.zip # Logs from when I tried to deploy and it
> failed
> vdsm.tar.gz # /var/log/vdsm
> 
> Output from running vdsm from the command line:
> 
> [root@cultivar2 log]# su -s /bin/bash vdsm
 
 This cannot work unless supervdsmd is running...
 
> [vdsm@cultivar2 log]$ python /usr/share/vdsm/vdsm
> (PID: 6521) I am the actual vdsm 4.17.26-1.el7
> cultivar2.grove.silverorange.com 
>  (3.10.0-327.el7.x86_64)
> VDSM will run with cpu affinity: frozenset([1])
> /usr/bin/taskset --all-tasks --pid --cpu-list 1 6521 (cwd None)
> SUCCESS:  = '';  = 0
> Starting scheduler vdsm.Scheduler
> started
> Run and protect:
> registerDomainStateChangeCallback(callbackFunc= at
> 0x381b158>)
> Run and protect: registerDomainStateChangeCallback, Return response: None
> Trying to connect to Super Vdsm
> Preparing MOM interface

[ovirt-users] During Hosted Engine Deployment. CPU Type not listed as compatible. No selection to choose from.

2016-05-16 Thread Langley, Robert
Host is a Dell PowerEdge 2950 with an Intel Xeon 5160 (Woodcrest) processor.
I'm stuck at the prompt, "Please specify the CPU type to be used by the VM []" 
during the deployment.
There is nothing to select. No compatible CPU type is shown.
The server is from 2008 and I'm needing to use these older servers to get 
started, before I can bring in the newer ones that are busy hosting VMs.
The other Dell PE 2950 is from 2007 and I was able to bring up the engine on 
that one. It is a Conroe CPU. I won't get into my mistake with that deployment. 
I'm working on recovering from that one.
I wanted to post about this, because I was trying to add this one (2008) as an 
additional host and it wouldn't add, due to the processor.
So, one question (in addition to the problem above) is whether or not I can use 
two hosts with two different processors for the hosted engine?
Thanks
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] VMs seems to be slow, while snapshot delete is happening

2016-05-16 Thread SATHEESARAN

On 05/14/2016 02:38 AM, Greg Padgett wrote:

On 05/12/2016 03:46 AM, SATHEESARAN wrote:

Hi All,

I have created a VM with 60GB of disk space.
I have started I/O inside the VM, after sometime when the disk was 
4GB full,

I took a snapshot of the disk from UI.

I/O kept continuing and the new image file ( overlay file ) was 15GB in
size.

Now I deleted the snapshot.
I think this would initiate block-merges.
During this time, my I/O was were slower, till the snapshot delete is
completed.

Its not very slow, but slow.
Is this a known behavior ?


Hi Satheesaran,

It sounds like this was a live merge, ie snapshot removal while the VM 
was running.  This is currently implemented as a block commit, where 
data from the snapshot (your 15GB overlay, in this case) is merged down.


For snapshot deletion to complete, this means that your concurrent I/O 
and the data already in the overlay have to be written into the 
next-lower image.  So in short, yes, depending on the storage system 
backing your VM, I/O may slow down a bit until completion.


HTH,
Greg

Greg,

Thanks for that information.
I too expected it, but really wanted to confirm the behavior.

-- Satheesaran S
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt & gluster - which copy is written to?

2016-05-16 Thread Alexander Wels
On Thursday, May 12, 2016 12:05:22 AM Bill Bill wrote:
> Hello,
> 
> Let’s say I have a 5 node converged cluster of oVirt & glusterFS with a
> replica count of “3”.
 
> Host1 - replica
> Host2 - replica
> Host3 - replica
> Host4
> Host5
> 
> If I spin a VM up on Host1 – does the first replica get created local to
> that server?
 
> In the event I move the VM to another host, does the replica of the disk
> follow the VM so essentially it’s writing to a local copy first or does it
> “always” write across the network.
 
> For example, with VMware, the disk will follow the VM to the hypervisor you
> move it to so that the writes are essentially “local”.
 
> I have not been able to find anything on the internet or in the
> documentation that specifies how this process works. Ideally, you wouldn’t
> want a VM residing on Host1 that accesses its disk on Host3. Multiple that
> by hundreds of VM’s and it would create a ton of unnecessary network
> congestion.
 
While I cannot answer your actual question as I don't know enough about the 
internal implementation of how oVirt interacts with gluster. I just want to 
point out major difference between oVirt and VMWare. In oVirt storage domains 
are attached to data centers, not hosts. So there is no does the disk move 
from host1 to host2. The disk is on the storage domain and host1 and host2 and 
every other host in the data center has access to the storage domain.


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


[ovirt-users] Unable to install 3.6.5 under CentOS 6.7

2016-05-16 Thread Tom Lambdin
Hi,

Although the release note indicates that 3.6.5 is supported under CentOS/RHEL 
6.7, when we attempt to update to the the latest version under CentOS 6.7, the 
highest version we can get from the repo is 3.6.3.
If we spin up a brand new machine running CentOS 7.2, we do however 
successfully get 3.6.5. Ideally we’d like to avoid having to migrate our 
management host to CentOS 7 at this time.
Is there something we’re missing here or is there a problem with the repo 
configuration?

Regards,

-Tom Lambdin



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] vioscsi.sys BSOD with Win 7

2016-05-16 Thread Ladi Prosek
On Wed, May 11, 2016 at 8:55 AM, Tomas Jelinek  wrote:
> Hi Ladi,
>
> do you know if the upstream virtio drivers are correctly signed?
> In particular:
> http://resources.ovirt.org/pub/ovirt-3.6/rpm/el6/noarch/ovirt-guest-tools-iso-3.6-3.fc23.noarch.rpm

This is one of the first builds signed only with the new SHA-2 based
certificate which is not supported on Windows 7 out-of-the-box.
Installing a hotfix per:

https://technet.microsoft.com/en-us/library/security/3033929.aspx

will fix it.

> If yes, any idea what can be the issue Cam faces?

As for the original BSOD, the problem there was trying to load Win8
vioscsi.sys on Win7 and should be fixed by pointing Windows to the
Win7 subdirectory like you wrote.

Relevant bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1289406 (signing issue)
https://bugzilla.redhat.com/show_bug.cgi?id=1296633 (target OS version mismatch)

Thanks,
Ladi

> thank you,
> Tomas
>
> - Original Message -
>> From: "Arman Khalatyan" 
>> To: "Cam Mac" 
>> Cc: "Tomas Jelinek" , "users" 
>> Sent: Tuesday, May 10, 2016 9:19:49 PM
>> Subject: Re: [ovirt-users] vioscsi.sys BSOD with Win 7
>>
>> Same bsod was with win2008 server, in order to fix it we changed nics to
>> e1000 and disks to IDE. Now it boots w/o trouble.
>> Am 10.05.2016 7:43 nachm. schrieb "Cam Mac" :
>>
>> > Hi Tomas,
>> >
>> > The install went ok, but Windows complains:
>> >
>> > "File: \windows\system32\drivers\vioscsi.sys
>> > status: 0xc428
>> > Windows cannot verify the digital signature for this file"
>> >
>> > Regards,
>> >
>> > Campbell
>> >
>> > On Tue, May 10, 2016 at 6:29 PM, Cam Mac  wrote:
>> >
>> >> Hi Tomas,
>> >>
>> >> Thanks, I will test that later tonight and let you know.
>> >>
>> >> Regards,
>> >>
>> >> Cam
>> >>
>> >> On Tue, May 10, 2016 at 3:28 PM, Tomas Jelinek 
>> >> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> please try to install this guest tools:
>> >>>
>> >>> http://resources.ovirt.org/pub/ovirt-3.6/rpm/el6/noarch/ovirt-guest-tools-iso-3.6-3.fc23.noarch.rpm
>> >>>
>> >>> Also please make sure you point windows to the correct driver in the
>> >>> sub-directory for w7
>> >>>
>> >>> Tomas
>> >>>
>> >>> - Original Message -
>> >>> > From: "Cam Mac" 
>> >>> > To: users@ovirt.org
>> >>> > Sent: Monday, May 9, 2016 7:28:57 PM
>> >>> > Subject: [ovirt-users] vioscsi.sys BSOD with Win 7
>> >>> >
>> >>> > Hi,
>> >>> >
>> >>> > I'm running oVirt 3.6.3.4-1.el7.centos and when I install a Win 7
>> >>> guest VM,
>> >>> > using VirtIO disk, networking etc, it goes through the install process
>> >>> ok,
>> >>> > but blue screens upon boot with a vioscsi.sys error (attached). I have
>> >>> tried
>> >>> > the official version ovirt-guest-tools-iso 3.6.0 0.2_master.fc22, as
>> >>> well as
>> >>> > some earlier and later versions. I am using a PXE boot method with a
>> >>> Windows
>> >>> > deployment server, which has the drivers from the oVirt tools ISO
>> >>> installed
>> >>> > (indeed, it picks up the drive and networking and I can see it
>> >>> installing
>> >>> > the drivers). I have tried with the generic IDE and rtl8139 config on
>> >>> the
>> >>> > guest, and it also fails with the same vioscsi.sys error after
>> >>> rebooting
>> >>> > upon finishing installation even though I'm using IDE as the disk
>> >>> driver.
>> >>> >
>> >>> > I have uploaded a win 7 x64 ISO and tried installing that, and it
>> >>> loads the
>> >>> > VirtIO viostor driver (using the method at:
>> >>> >
>> >>> https://www.ovirt.org/documentation/how-to/virtual-machines/create-a-windows-7-virtual-machine/
>> >>> > ), and even manages to partition the disks, but fails to install on
>> >>> the disk
>> >>> > (screenshot attached).
>> >>> >
>> >>> > I've tried temporarily removing the vioscsi files from the install
>> >>> server as
>> >>> > a last resort, but as expected it fails to install properly, though I
>> >>> > thought it used the viostor driver instead.
>> >>> >
>> >>> > Thanks for any help.
>> >>> >
>> >>> > Regards,
>> >>> >
>> >>> > Cam
>> >>> >
>> >>> > ___
>> >>> > Users mailing list
>> >>> > Users@ovirt.org
>> >>> > http://lists.ovirt.org/mailman/listinfo/users
>> >>> >
>> >>>
>> >>
>> >>
>> >
>> > ___
>> > Users mailing list
>> > Users@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/users
>> >
>> >
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] USB

2016-05-16 Thread Brett I. Holcomb
How do I get a VM to see USB devices?  If I understand it correctly I
have to go to Edit VM -> Console and enable USB native.  I have the
console options set to use usb.  However, I'm finding conflicting
information.  Supposedly libvirt will allow sharing of a USB device
over a network but to start with I'd be happy just being able to
connect a usb device to the host and having it detected.  I have some
programmable devices I'd like to program in Linux using my VM.

Has anyone uses usbip and if so how well does  it work?



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


Re: [ovirt-users] vioscsi.sys BSOD with Win 7

2016-05-16 Thread Ladi Prosek
On Wed, May 11, 2016 at 1:46 PM, Cam Mac  wrote:
> Hi Ladi,
>
>>
>>
>> We will try just the win 7 drivers that shipped with 3.6.3 rather than the
>> SHA-2 signed FC23 drivers and I'll get back to you. I have a question:
>> if I try to build a Win2k12 server via WDS, I assume I will have to add
>> the 2k12 drivers and then remove them again if I go to build a Win 7 VM
>> as Win 7 will presumably try to pick up the 2k12 driver? Or can they
>> co-exist?
>> WDS has a build process whenever drivers are added (e.g., for KVM, VMWare
>> etc) for available drivers. Do you know when the fix will be available?
>>
>
> Sorry for replying to my own post, but it turns out that there should be a
> way in WDS to
> set separate build directories for Win 7 and 2012, so please disregard that
> question.
>
> The build appears to be going well so far, no BSODs.
>
> Thanks very much for the help Ladi!

No worries, I'm glad that you're not blocked anymore.

> Any ideas on when the newly signed drivers will be available?

Shouldn't take more than a few weeks, I'll keep you posted.

Thanks,
Ladi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] oVirt & gluster - which copy is written to?

2016-05-16 Thread Bill Bill
Hello,

Let’s say I have a 5 node converged cluster of oVirt & glusterFS with a replica 
count of “3”.

Host1 - replica
Host2 - replica
Host3 - replica
Host4
Host5

If I spin a VM up on Host1 – does the first replica get created local to that 
server?

In the event I move the VM to another host, does the replica of the disk follow 
the VM so essentially it’s writing to a local copy first or does it “always” 
write across the network.

For example, with VMware, the disk will follow the VM to the hypervisor you 
move it to so that the writes are essentially “local”.

I have not been able to find anything on the internet or in the documentation 
that specifies how this process works. Ideally, you wouldn’t want a VM residing 
on Host1 that accesses its disk on Host3. Multiple that by hundreds of VM’s and 
it would create a ton of unnecessary network congestion.

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


Re: [ovirt-users] vioscsi.sys BSOD with Win 7

2016-05-16 Thread Ladi Prosek
On Wed, May 11, 2016 at 11:18 AM, Cam Mac  wrote:
> Oops forgot attachment.
>
> On Wed, May 11, 2016 at 10:17 AM, Cam Mac  wrote:
>>>
>>>
>>> > do you know if the upstream virtio drivers are correctly signed?
>>> > In particular:
>>> >
>>> > http://resources.ovirt.org/pub/ovirt-3.6/rpm/el6/noarch/ovirt-guest-tools-iso-3.6-3.fc23.noarch.rpm
>>>
>>> This is one of the first builds signed only with the new SHA-2 based
>>> certificate which is not supported on Windows 7 out-of-the-box.
>>> Installing a hotfix per:
>>>
>>> https://technet.microsoft.com/en-us/library/security/3033929.aspx
>>>
>>> will fix it.
>>>
>>
>> Thanks Ladi.

No worries. I forgot to mention that this will be fixed in a future
driver release, either by dual-signing the binaries with both SHA-1
and SHA-2 or only SHA-1. Requiring the Windows hotfix is a workaround
until then.

>>>
>>> > If yes, any idea what can be the issue Cam faces?
>>>
>>> As for the original BSOD, the problem there was trying to load Win8
>>> vioscsi.sys on Win7 and should be fixed by pointing Windows to the
>>> Win7 subdirectory like you wrote.
>>>
>>> Relevant bugs:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1289406 (signing issue)
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1296633 (target OS version
>>> mismatch)
>>>
>>
>> The crash mentions vioscsi.sys, not viostor.sys, which the second bug
>> report mentioned.

It is the same issue though, I have checked the timestamp in your BSOD
screenshot. The driver running on the system at the time of crash was
a build targeted at Win8 or newer.

>> The other thing
>> is that the crash happens after the install, upon first reboot.
>> The
>> contents of the Windows guest tools ISO
>> are copied to the Windows Deployment server from where they are installed.

Can you feed only the Win7 subset of the ISO to WDS? Sorry, I am not
familiar with WDS enough to be more helpful.

The problem with all the virtio-win releases so far is that the
drivers don't declare the minimum Windows version they support. So
Windows (or in this case WDS?) is free to choose any of them, usually
going after the highest version which tends to be the Win8 variety.
This will also be fixed soon.

>> When I try an alternative install using a Win 7 ISO, rather than PXE boot,
>> it fails at a different point. This is using
>> the oVirt Windows guest tools ISO that is in the 3.6.3 repos. When it
>> comes to installing to disk, I change the CD
>> to the guest tools ISO and browse to the win7 drivers
>> (ovirt-tools-setup/drivers/virtio/viostor/w7/amd64/, which has
>> the viostor drivers), but then the installer complains it cannot install
>> on the disk, even though it can successfully
>> create partitons on it (see attached screenshot).

What does it say when you click "Show details"?

>> Thanks,
>>
>> Cam
>>
>>
>>> >
>>> > - Original Message -
>>> >> From: "Arman Khalatyan" 
>>> >> To: "Cam Mac" 
>>> >> Cc: "Tomas Jelinek" , "users" 
>>> >> Sent: Tuesday, May 10, 2016 9:19:49 PM
>>> >> Subject: Re: [ovirt-users] vioscsi.sys BSOD with Win 7
>>> >>
>>> >> Same bsod was with win2008 server, in order to fix it we changed nics
>>> >> to
>>> >> e1000 and disks to IDE. Now it boots w/o trouble.
>>> >> Am 10.05.2016 7:43 nachm. schrieb "Cam Mac" :
>>> >>
>>> >> > Hi Tomas,
>>> >> >
>>> >> > The install went ok, but Windows complains:
>>> >> >
>>> >> > "File: \windows\system32\drivers\vioscsi.sys
>>> >> > status: 0xc428
>>> >> > Windows cannot verify the digital signature for this file"
>>> >> >
>>> >> > Regards,
>>> >> >
>>> >> > Campbell
>>> >> >
>>> >> > On Tue, May 10, 2016 at 6:29 PM, Cam Mac  wrote:
>>> >> >
>>> >> >> Hi Tomas,
>>> >> >>
>>> >> >> Thanks, I will test that later tonight and let you know.
>>> >> >>
>>> >> >> Regards,
>>> >> >>
>>> >> >> Cam
>>> >> >>
>>> >> >> On Tue, May 10, 2016 at 3:28 PM, Tomas Jelinek
>>> >> >> 
>>> >> >> wrote:
>>> >> >>
>>> >> >>> Hi,
>>> >> >>>
>>> >> >>> please try to install this guest tools:
>>> >> >>>
>>> >> >>>
>>> >> >>> http://resources.ovirt.org/pub/ovirt-3.6/rpm/el6/noarch/ovirt-guest-tools-iso-3.6-3.fc23.noarch.rpm
>>> >> >>>
>>> >> >>> Also please make sure you point windows to the correct driver in
>>> >> >>> the
>>> >> >>> sub-directory for w7
>>> >> >>>
>>> >> >>> Tomas
>>> >> >>>
>>> >> >>> - Original Message -
>>> >> >>> > From: "Cam Mac" 
>>> >> >>> > To: users@ovirt.org
>>> >> >>> > Sent: Monday, May 9, 2016 7:28:57 PM
>>> >> >>> > Subject: [ovirt-users] vioscsi.sys BSOD with Win 7
>>> >> >>> >
>>> >> >>> > Hi,
>>> >> >>> >
>>> >> >>> > I'm running oVirt 3.6.3.4-1.el7.centos and when I install a Win
>>> >> >>> > 7
>>> >> >>> guest VM,
>>> >> >>> > using VirtIO disk, networking etc, it goes through the install
>>> >> >>> > process
>>> >> >>> ok,
>>> >> >>> > but blue screens upon boot 

[ovirt-users] How to migrate un-migratable VMs?

2016-05-16 Thread Nicolas Ecarnot

Hi,

Some VMs are doing high guest-memory writes (mainly files and mail 
servers, but not only), so migrations are reproductively failing.

I found some info here :
https://bugzilla.redhat.com/show_bug.cgi?id=919201
that confirm what I was fearing.

This BZ is aging from dinosaurs times, so I was wondering now we're in 
the 3.6.x age and 4.x coming, are there advices one may give to migrate 
those verbose VMs?


I guess increasing the allowed page memory is not a correct answer as it 
will fill as before.


Any thoughts?

--
Nicolas ECARNOT
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] disk order in vm and disk order in export

2016-05-16 Thread Fabrice Bacchella
I have a VM with the following disks (in the ordrer return by a get query):
 

...
vm_sys
17179869184 <- 16GiB
virtio_scsi
true
image



vm_data
virtio_scsi
false


1099511627776 <- 1 TiB.
0


lun


So the first one is a 16 GiB virtual disk, the second one a 1 iTB direct access 
LUN that will contains data.

But once booterd, I see:
lsblk   
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda   8:00 1T  0 disk 
...
sdb   8:16   016G  0 disk 
...

and :
ls -l /dev/disk/by-*/*
...
lrwxrwxrwx. 1 root root  9 May 16 09:03 
/dev/disk/by-path/pci-:00:04.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx. 1 root root  9 May 16 09:03 
/dev/disk/by-path/pci-:00:04.0-scsi-0:0:0:1 -> ../../sdb

So the first disk sda is the second non bootable disk.
What set the disk order associated to a VM ? Is there a way to enforce that the 
first disk is really the first disk ?___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to install 3.6.5 under CentOS 6.7

2016-05-16 Thread Yedidyah Bar David
On Mon, May 16, 2016 at 12:58 PM, Tom Lambdin  wrote:
> Hi,
>
> Although the release note indicates that 3.6.5 is supported under CentOS/RHEL 
> 6.7, when we attempt to update to the the latest version under CentOS 6.7, 
> the highest version we can get from the repo is 3.6.3.
> If we spin up a brand new machine running CentOS 7.2, we do however 
> successfully get 3.6.5. Ideally we’d like to avoid having to migrate our 
> management host to CentOS 7 at this time.
> Is there something we’re missing here or is there a problem with the repo 
> configuration?

The repo does contain ovirt-engine-3.6.5.3-1.el6.noarch.rpm [1].

Did you try 'yum clean all'?

Please post your repo files and output of relevant yum commands.

Thanks,

[1] 
http://plain.resources.ovirt.org/pub/ovirt-3.6/rpm/el6/noarch/ovirt-engine-3.6.5.3-1.el6.noarch.rpm

>
> Regards,
>
> -Tom Lambdin
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



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


Re: [ovirt-users] Unable to install 3.6.5 under CentOS 6.7

2016-05-16 Thread Tom Lambdin
Hi,

So I’ve just checked again and it now works. Very strange. Thanks for the quick 
response anyway.

-Tom

> On 16 May 2016, at 11:12, Yedidyah Bar David  wrote:
> 
> On Mon, May 16, 2016 at 12:58 PM, Tom Lambdin  wrote:
>> Hi,
>> 
>> Although the release note indicates that 3.6.5 is supported under 
>> CentOS/RHEL 6.7, when we attempt to update to the the latest version under 
>> CentOS 6.7, the highest version we can get from the repo is 3.6.3.
>> If we spin up a brand new machine running CentOS 7.2, we do however 
>> successfully get 3.6.5. Ideally we’d like to avoid having to migrate our 
>> management host to CentOS 7 at this time.
>> Is there something we’re missing here or is there a problem with the repo 
>> configuration?
> 
> The repo does contain ovirt-engine-3.6.5.3-1.el6.noarch.rpm [1].
> 
> Did you try 'yum clean all'?
> 
> Please post your repo files and output of relevant yum commands.
> 
> Thanks,
> 
> [1] 
> http://plain.resources.ovirt.org/pub/ovirt-3.6/rpm/el6/noarch/ovirt-engine-3.6.5.3-1.el6.noarch.rpm
> 
>> 
>> Regards,
>> 
>> -Tom Lambdin
>> 
>> 
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>> 
> 
> 
> 
> --
> Didi



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] oVirt Node 3.6

2016-05-16 Thread Anantha Raghava

Hi,

I attempted to download the oVirt Node 3.6 from 
http://resources.ovirt.org/pub/ovirt-3.6-snapshot/iso/ovirt-node-iso/ 
and I also find there is another ovirt-node-ng. Which one should we 
download.


I downloaded the one at 
http://resources.ovirt.org/pub/ovirt-3.6-snapshot/iso/ovirt-node-iso/, 
but this iso file seems to have an issue. Although it boots the server 
properly at around 66% into installation, the installer throws up an 
error - I/O error, file not found or some thing of this sort. 
Installation doesn't go forward at all. We have to power off the server, 
reboot with CentOS DVD install using yum local install command.


Are these files proper? Which one should we use?
--

Thanks & Regards,


Anantha Raghava



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