search for: vmhosts

Hey! I am following the steps at http://wiki.xenproject.org/wiki/XCP_Beginners_Guide for creating a VM. I''ve setup my test VM with 1GiB min/max memory. I''ve assigned 2GiB of memory to dom0 (http://wiki.xen.org/wiki/Xen_Best_Practices) . My box has 12GB of physical memory and runs Ubuntu 13.04. When I do "xe vm-start", I get the following: The server failed to handle

I'm having trouble updating my iscsitarget modules, and it seems to be related to a naming convention mixup? here's the output of the build command: [root at vmhost ~]# rpmbuild --rebuild --sign iscsitarget-0.4.14.96-0.amherst.src.rpm Installing iscsitarget-0.4.14.96-0.amherst.src.rpm error: Failed build dependencies: kernel-devel = 2.6.9-42.0.10.ELlarge is needed by

Hi! I'm new to libvirt and face problems connecting to an iSCSI target. What I intend to do is to connect libvirt (I tried virt-manager and virsh) to an iSCSI target and then boot from the LUNs which contain the VMs. I followed the documentation¹ but got stuck at section 12.1.5.4.3. 1) virsh pool-define-as \ --name foo \ --type iscsi

[root at vmhost vms]# virsh detach-disk puppet vdb error: No found disk whose source path or target is vdb [root at vmhost vms]# virsh --version 0.10.2 [root at vmhost vms]# This probably was solved already but if not, "No found disk" probably sounds better if it was "No disk found"

On 12/17/2013 07:13 PM, Marco wrote: > Hi! > > I'm new to libvirt and face problems connecting to an iSCSI target. > What I intend to do is to connect libvirt (I tried virt-manager and > virsh) to an iSCSI target and then boot from the LUNs which contain > the VMs. > > I followed the documentation¹ but got stuck at section 12.1.5.4.3. > > 1) > virsh

On 2013–12–21 John Ferlan wrote: > On 12/17/2013 07:13 PM, Marco wrote: > > Hi! > > > > I'm new to libvirt and face problems connecting to an iSCSI target. > > What I intend to do is to connect libvirt (I tried virt-manager and > > virsh) to an iSCSI target and then boot from the LUNs which contain > > the VMs. > > > > I followed the

Trying to start one of my vms, a centos one at that, but am getting the following message: [root@vmhost ~]# virsh start voip --paused error: Failed to start domain voip error: cannot open file '/var/tmp/FreePBX-5.211.65-3-x86_64-Full-1388073872.iso': No such file or directory [root@vmhost ~]# But, virsh dumpxml voip shows no info onto the .iso <disk type='file'

I have a Windows XP vm and would like to know how should I set its cpu so it is seen by the vm as a proper 32bit one. In its xml file, I have <os> <type arch='i686' machine='rhel6.2.0'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> <bootmenu enable='yes'/> </os> And this is the machine I

In trying to find out why my usb passthrough is not working, I decided to edit (virsh edit) the config file for the vm client, removing the following lines <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x051d'/> <product id='0x0002'/> </source> </hostdev>

When I say busybox it''s actually VMware ESX server which seems to use busybox (which I guess is the case a number of other software appliances) . Reason for wanting to install puppet is to run the cli tools to create nightly vmware snapshots. I''m happy to give it a go (and add the docs to the wiki) but I''m not too sure at this stage how big a task this might be and what,

Hello all, I'm having problems using the "samba-tool" tool. From the documentation i've read, the following command 'should' work. Apparently i'm missing something. #### [root at vmhost bin]# pwd /usr/local/samba/bin [root at vmhost bin]# ./samba-tool domain provision --realm=mytest.local --domain=MYTEST --adminpass='welcome' --server-role='dc'

On 12/22/2013 10:09 AM, Marco wrote: > On 2013–12–21 John Ferlan wrote: > >> On 12/17/2013 07:13 PM, Marco wrote: >>> Hi! >>> >>> I'm new to libvirt and face problems connecting to an iSCSI target. >>> What I intend to do is to connect libvirt (I tried virt-manager and >>> virsh) to an iSCSI target and then boot from the LUNs which

I am running libvirt 0.9.8, virsh -V Virsh command line tool of libvirt 0.9.8 See web site at http://libvirt.org/ Compiled with support for: Hypervisors: Xen QEmu/KVM UML OpenVZ LXC Test Networking: Remote Daemon Network Bridging Nwfilter VirtualPort Storage: Dir Disk Filesystem SCSI Multipath iSCSI LVM Miscellaneous: AppArmor Secrets Debug Readline in an ubuntu 12.04.1 install. I created a

Hi all, Recently installed dovecot and postfix under Fedora8 and it works great. Then I installed both postfix and dovecot under VMWare Server (different machine) copying the same configuration files but changing the hostname and domain as appropriate. When testing the installation using: telnet hostname 143, I receive * OK Dovecot ready But when I telnet on port 25, I receive: Trying

On 2013–12–23 John Ferlan wrote: > On 12/22/2013 10:09 AM, Marco wrote: > > On 2013–12–21 John Ferlan wrote: > > > >> On 12/17/2013 07:13 PM, Marco wrote: > >>> Hi! > >>> > >>> I'm new to libvirt and face problems connecting to an iSCSI target. > >>> What I intend to do is to connect libvirt (I tried virt-manager and

On Thu, Mar 6, 2014 at 12:16 AM, Mauricio Tavares <raubvogel@gmail.com> wrote: > Trying to start one of my vms, a centos one at that, but am > getting the following message: > > [root@vmhost ~]# virsh start voip --paused > error: Failed to start domain voip > error: cannot open file > '/var/tmp/FreePBX-5.211.65-3-x86_64-Full-1388073872.iso': No such file

On Wed, Apr 6, 2016 at 9:47 PM, James Hogarth <james.hogarth at gmail.com> wrote: > On 6 Apr 2016 2:35 p.m., "Francis Mendoza" <francis at mytechrepublic.com> > wrote: > > > > Im configuring my KVM and in my network configuration I have 4 Network > > lancard > > > > 2 nic = using teaming0 for management with access port configured in the

Hi As you may''ve seen from my last posts I''m struggling to get the setup on my subject line to work without flaws. I''ve tried compiling the Kernel from Source, I''ve also tried Fedora 14, which has a flaky pv_ops Dom0 kernel which DOESN''T work at all, but none of these seem to work. I''m a mid-time XEN user, I just love it and want to stay

Hi As you may''ve seen from my last posts I''m struggling to get the setup on my subject line to work without flaws. I''ve tried compiling the Kernel from Source, I''ve also tried Fedora 14, which has a flaky pv_ops Dom0 kernel which DOESN''T work at all, but none of these seem to work. I''m a mid-time XEN user, I just love it and want to stay

Im configuring my KVM and in my network configuration I have 4 Network lancard 2 nic = using teaming0 for management with access port configured in the switch side 2 nic = using teaming1 for guest VM DATA ports. and in the switch is configured for LACP with trunk allowing vlan 10,20,30,40,50 and configured in the CentOS7 the vlan 10, vlan 20,30,40,50 im sure its already working because I tried