search for: hipervisor

...m install qemu yum install libvirt yum install virt-manager then I started the libvirtd as follow: /etc/init.d/lbvirtd start So , it ran well. However, after a few days , when I ran the command "virt-manager" , it showed as in the attachment. it seemed that ti cannot connect the hipervisor. Then I did a little test: I ran the conmand "virsh list" , but it didnot work,either. Then I used Python as follows: import libvirt cc = libvirt.open(r'qemu:///system' ) but it didnot work,either. All the test above are under root . I hope that someone can give me some sugg...

...qemu-kvm yum install qemu yum install libvirt yum install virt-manager then I started the libvirtd as follow: /etc/init.d/lbvirtd start So , it ran well. However, after a few days , when I ran the command "virt-manager" , it showed as bellow: it seemed that ti cannot connect the hipervisor. Then I did a little test: I ran the conmand "virsh list" , but it didnot work,either. Then I used Python as follows: import libvirt cc = libvirt.open(r'qemu:///system') but it didnot work,either. All the test above are under root . I hope that someone can give me some sugge...

Hi, I'm trying remote connection with qemu hypervisor on FSL PPC board. The libvirt server is the PPC board. root at ppc:~# ifconfig eth0 10.193.20.109 root at ppc:~# libvirtd -d root at ppc:~# virsh -c qemu:///system define test.xml root at ppc:~# virsh -c qemu:///system start test root at ppc:~# virsh -c qemu:///system list --all Id Name State

...eric virtio > > code will fetch it from the ccw_device. > > Right! For some reason dma_mask is a pointer. And I need virtio core to > use a sane value for virtio_ccw devices. > > > Don't you potentially need > > something for other ccw_devices in that protected hipervisor case as > > well (e.g for 3270)? > > > Maybe, maybe not. The first stage is likely to be virito only. I would > prefer sorting out stuff like 3270 as the need arises. Also see my > response to patch 4 (Message-Id: <20190409141114.7dcce94a at oc2783563651>). As long a...

Hi all, I''ve a serious problem with my dom0 xen installation, that''s why I''m blocked to daily work. I come to describe my virtualization scenary and the arised problem. Hardware is a Dell server with 3 physicall ethernet network cards and 16 GB RAM. Initially installed CentOS-5.2 with Xen-3.0.3 and 2.6.18-128.el5xen kernel. Dom0 with 7 domU paravirtuallized (they have

Hi all, I''ve a serious problem with my dom0 xen installation, that''s why I''m blocked to daily work. I come to describe my virtualization scenary and the arised problem. Hardware is a Dell server with 3 physicall ethernet network cards and 16 GB RAM. Initially installed CentOS-5.2 with Xen-3.0.3 and 2.6.18-128.el5xen kernel. Dom0 with 7 domU paravirtuallized (they have

...t; possible. Do you have any suggestions? From what I see, you set the mask from the virtio-ccw side, then propagate it up to the general ccw_device, and then the generic virtio code will fetch it from the ccw_device. Don't you potentially need something for other ccw_devices in that protected hipervisor case as well (e.g for 3270)? > > > > > > + > > > + ret = dma_set_mask_and_coherent(&cdev->dev, DMA_BIT_MASK(64)); > > > + if (ret) > > > + ret = dma_set_mask_and_coherent(&cdev->dev, > > > + DMA_BIT_MASK(32)); > >...

These patches combine HVSource and HVTarget into a single Converter. This should make it more obvious where to hack without losing any practical flexibility. GuestOS remains separate. GuestOS is now a misnomer, because it's really only a Linux distro abstraction. It will be useless for Windows, for example. Functions which you'd expect to be different on a non-RH distro should live in

The following patches are where I'm currently at with ESX support. I can now import a domain from ESX along with its storage. Note that I'm not yet doing any conversion. In fact, I've never even tested past the import stage (I just had an exit in there). The meat is really in the 4th patch. The rename of MetadataReader->Connection was because the Connection is now really providing

With this patchset I have successfully[1] imported a RHEL 5 guest directly from ESX with the following command line: virt-v2v -ic 'esx://yellow.marston/?no_verify=1' -op transfer RHEL5-64 Login details are stored in ~/.netrc Note that this is the only guest I've tested against. I haven't for example, checked that I haven't broken Xen imports. Matt [1] With the exception of