search for: vmhost

...en message may give details useful for debugging the problem. message: Xenctrl.Error [ memory 10340716 KiB free; to be scrubbed 0 KiB; total 12286 MiB]: 1: Operation not permitted Any idea what might be going? Here are log files that may be relevant: * xcp-xapi.log [20130705T23:36:17.922Z|debug|vmhost|145 UNIX /var/lib/xcp/xapi|VM.start R:5de44eac7eab|audit] VM.start: VM = ''fca13dc3-464e-579e-35be-f320d07c8ca2 (VM1)'' [20130705T23:36:17.927Z|debug|vmhost|145 UNIX /var/lib/xcp/xapi|VM.start R:5de44eac7eab|xapi] Using wlb recommendations for choosing a host has been disabled or wl...

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 iscsitarget-0.4.14.96-0.amherst.x86_64 here's everything my system knows about ke...

...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 \ --source-host vmhost \ --source-dev iqn.2013-11.vmhost:vmpool \ --target /dev/disk/by-path 2) virsh pool-start foo error: Failed to start pool foo error: internal error: cannot find session virsh -c qemu:///system pool-start foo error: Failed to start pool foo error: internal err...

[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"

...nd 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 \ > --source-host vmhost \ > --source-dev iqn.2013-11.vmhost:vmpool \ > --target /dev/disk/by-path > > 2) > virsh pool-start foo > error: Failed to start pool foo > error: internal error: cannot find session > > virsh -c qemu:///system pool-start foo > err...

...> 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 \ > > --source-host vmhost \ > > --source-dev iqn.2013-11.vmhost:vmpool \ > > --target /dev/disk/by-path > > > > 2) > > virsh pool-start foo > > error: Failed to start pool foo > > error: internal error: cannot find session > > > > virs...

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' device='d...

...ile, 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 have (an intel i5): [root at vmhost ~]# virsh nodeinfo CPU model: x86_64 CPU(s): 4 CPU frequency: 1600 MHz CPU socket(s): 1 Core(s) per socket: 4 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 5904548 kB and this is what virsh thinks my vm has: [root at vmhost ~]# virsh vcpuin...

...em' type='usb' managed='yes'> <source> <vendor id='0x051d'/> <product id='0x0002'/> </source> </hostdev> checking with "virsh dumpxml" that the lines went away, and then restarting [root@vmhost ~]# virsh start nagios error: Failed to start domain nagios error: internal error Did not find USB device 51d:2 bus:2 device:3 [root@vmhost ~]# As you can see, it is still acting like the usb device is defined. What am I missing here?

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' Usage: samba-tool domain <subcommand> Available subcommands: classicupgrade - Upgrade from Samba classic (NT4-...

...;> >>> I followed the documentation¹ but got stuck at section 12.1.5.4.3. >>> >>> 1) >>> virsh pool-define-as \ >>> --name foo \ >>> --type iscsi \ >>> --source-host vmhost \ >>> --source-dev iqn.2013-11.vmhost:vmpool \ >>> --target /dev/disk/by-path >>> >>> 2) >>> virsh pool-start foo >>> error: Failed to start pool foo >>> error: internal error: cannot find session >&gt...

...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 vm client and wanted to save it: root at vmhost:/tmp# /usr/bin/virsh save test /export/vms/dump/test.dump error: Failed to save domain test to /export/vms/dump/test.dump error: operation failed: domain save job: unexpectedly failed root at vmhost:/tmp# cat /var/log/libvirt/qemu/test.log 2013-02-04 17:06:10.792+0000: starting up LC_ALL=C PATH=/u...

...ervices. I've checked poermissions and postfix master.cf How can I troubleshoot or does anyone have a quick answer? Thanks! Here's the output of dovecot -n and postconf -n The same config files are on both hosts and only the installation under VMWare Server has the problem. [root at vmhost ~]# dovecot -n # 1.0.13: /etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u...

...the documentation¹ but got stuck at section 12.1.5.4.3. > >>> > >>> 1) > >>> virsh pool-define-as \ > >>> --name foo \ > >>> --type iscsi \ > >>> --source-host vmhost \ > >>> --source-dev iqn.2013-11.vmhost:vmpool \ > >>> --target /dev/disk/by-path > >>> > >>> 2) > >>> virsh pool-start foo > >>> error: Failed to start pool foo > >>> error: internal...

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 > or directory > > [root@vmhost ~]# > > But, virsh dumpxml voip shows no info onto the .iso > >...

...> > > > What you'll need to do is from your team interface create the tagged > interfaces. Then create a bridge for each vlan and associate the tagged > interface with the bridge. > > When the guest is connected to that bridge the traffic will then be tagged > by the vmhost on the way out so you don't need any tagged configuration in > the guest. > > Thanks James I will try to configure the bridge in the vlan.

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