Re: [ovirt-users] USB
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_Linux/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". Another thing worth mentioning, USB hotplug is not supported yet, so if your programmable device is resetting the USB connection each time you program it, the USB will be detached from the VM and you will have to attach it again in order to see it. On Sun, May 15, 2016 at 8:34 AM, Brett I. Holcomb wrote: > 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 > -- Nisim Simsolo QE -Testing Engineer IRC: nsimsolo int phone - 8272305 mobile - 054-4779934 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] USB
- Original Message - > From: "Nisim Simsolo" > To: biholc...@l1049h.com > Cc: users@ovirt.org > Sent: Sunday, May 15, 2016 1:40:07 PM > Subject: Re: [ovirt-users] USB > > 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_Linux/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". > > Another thing worth mentioning, USB hotplug is not supported yet, so if > your programmable device is resetting the USB connection each time you > program it, the USB will be detached from the VM and you will have to > attach it again in order to see it. USB passthrough does not require IOMMU, only PCI devices do. The docs need improvement in that regard. > On Sun, May 15, 2016 at 8:34 AM, Brett I. Holcomb > wrote: > > > 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 > > > > > > -- > Nisim Simsolo > QE -Testing Engineer > IRC: nsimsolo > int phone - 8272305 > mobile - 054-4779934 > > ___ > 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: [ovirt-users] Adding another host to my cluster
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 server running > Starting executor > Starting worker periodic/0 > Worker started > Starting worker periodic/1 > Worker started > Starting worker periodic/2 > Worker started > Starting worker periodic/3 > Worker started > trying to connect libvirt > Panic: Connect to supervdsm service failed: [Errno 2] No such file or > directory > Traceback (most recent call last): > File "/usr/share/vdsm/supervdsm.py", line 78, in _connect > utils.retry(self._manager.connect, Exception, timeout=60, tries=3) > File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 959, in retry > return func() > File "/usr/lib64/python2.7/multiprocessing/managers.py", line 500, in > connect > conn = Client(self._address, authkey=self._authkey) > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 173, in > Client > c = SocketClient(address) > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 308, in > SocketClient > s.connect(address) > File "/usr/lib64/python2.7/socket.py", line 224, in meth > return getattr(self._sock,name)(*args) > error: [Errno 2] No such file or directory > > > Vdsm tries to connect to supervdsmd on startup, and if it is not running > it will fail. > > You can do: > > systemctl start supervdsmd > > And they you can run vdsmd from the shell. > > But why do you need to run vdsm from the shell? > > Nir > > > > > ___ > 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: [ovirt-users] vioscsi.sys BSOD with Win 7
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 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 >>> >>
Re: [ovirt-users] vioscsi.sys BSOD with Win 7
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
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
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?
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
