Search Results

Search found 54 results on 3 pages for 'virsh'.

Page 1/3 | 1 2 3  | Next Page >

  • virsh vcpu_period and vcpu_quota

    - by Programster
    I have been looking into ways to divide my CPU amongst KVM guests other than by just setting vCPU access limits. I understand the concept of cpu_shares which can be set/displayed with virsh schedinfo, but I also found vcpu_period and vcpu_quota listed with this command as shown below: Looking at the man page, I know what the acceptable input values are but could somebody please explain in simple terms what these two parameters actually do?

    Read the article

  • Why is "sudo virsh" hanging in the console?

    - by technophobia
    I wanted to experiment with OpenStack on my iMac: So I installed Ubuntu Cloud Live Image on a VM and I also ran DevStack on a fresh Ubuntu 64-bit Server VM. The DevStack script hangs on the following line: instances=`sudo virsh list --all | grep $INSTANCE_NAME_PREFIX | sed "s/.*\($INSTANCE_NAME_PREFIX[0-9a-fA-F]*\).*/\1/g"` I commented that block and ran the script again, this time it did not hang; thus completing its run. I attempted to run sudo virsh list --all on my CloudLive VM and it just hands until I break out of it. Why is sudo virsh hanging? Your help is appreciated. Note 1: The virsh command responds without sudo. Note 2: Not sure it matters, but I'm running my Virtual Machines in VMWare Fusion.

    Read the article

  • virsh XML interface allocation

    - by Kaushik Koneru
    I am trying to launch VM using a XML. This VM will be having 5 interfaces each connected to certain bridge. Issue here is allocation of these interfaces is random. My XML <interface type='bridge'> <mac address='52:54:00:9f:14:b3'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='e1000'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type='bridge'> <mac address='52:54:00:9f:14:b4'/> <source bridge='br1'/> <target dev='vnet2'/> <model type='e1000'/> <alias name='net1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x10' function='0x0'/> </interface> <interface type='bridge'> <mac address='52:54:00:9f:14:b5'/> <source bridge='br2'/> <target dev='vnet2'/> <model type='e1000'/> <alias name='net3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x12' function='0x0'/> </interface> <interface type='bridge'> <mac address='52:54:00:9f:14:c4'/> <source bridge='br3'/> <target dev='vnet3'/> <model type='e1000'/> <alias name='net4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x18' function='0x0'/> </interface> Allocation of interfaces are random mean e th6 will be connected to br3 ; eth7 -- br4 eth8 -- br2 eth9 -- br0. Is there any way to make it static?? At the same time is there anyway of assigning IP Address to these eth interfaces through XML file itself??

    Read the article

  • installing kvm on centos 6.2 getting error: virsh sysinfo error: failed to get sysinfo

    - by Grant
    # virsh sysinfo error: failed to get sysinfo error: unsupported configuration: Host SMBIOS information is not available # virsh -c qemu:///system sysinfo error: failed to get sysinfo error: unsupported configuration: Host SMBIOS information is not available Following this tutorial to the letter: http://eduardo-lago.blogspot.com/2012/01/how-to-install-kvm-and-libvirt-on.html Everything else works fine except this command: virsh sysinfo outputs error. Help!

    Read the article

  • error in qemu monitor wavcapture with virsh

    - by Aniket Awati
    I have VM running on qemu-kvm. I am managing it with libvirt and command line tool virsh. I want to record the audio output of the VM. Here is what I am trying - virsh qemu-monitor-command -hmp VM_NAME wavcapture VM.wav This is the output I am getting : Failed to open wave file `vm.wav' Reason: Permission denied Failed to add wave capture I have tried to create a dummy vm.wav with 777 permissions. But I still get the same error.

    Read the article

  • kvm memory changes via virsh not propagating to vm

    - by kevintmckay
    Hi I just started using kvm on rhel6 and after creating a vm I tried to increase the memory but the changes I amde in the xml file do not propogate to vm, even after bouncing vm and restarting libvert? [root@kvm01 qemu]# virsh dominfo dev-kvm01 Id: 2 Name: dev-kvm01 UUID: 9b2bf581-2807-3116-b176-60e9c0559943 OS Type: hvm State: running CPU(s): 2 CPU time: 1975.3s Max memory: 7864320 kB Used memory: 7864320 kB Persistent: yes Autostart: disable Security model: selinux Security DOI: 0 Security label: system_u:system_r:svirt_t:s0:c47,c760 (enforcing) [iknowmed@dev-kvm01 ~]$ free total used free shared buffers cached Mem: 3632284 3614508 17776 0 3980 3491676 -/+ buffers/cache: 118852 3513432 Swap: 5668856 0 5668856

    Read the article

  • I don't see the running guest in virsh

    - by Louise Hoffman
    Using CentOS 5 with KVM. I have downloaded this KVM applicance, and when unzipped it is just a .img file. No xml file supplied. I can start the guest with /usr/libexec/qemu-kvm -hda /data/kvm/slash.img -m 512 and it works. Now I would like to make a config file for the guest. The problem is when I do # virsh -c qemu:///system list Id Name State ---------------------------------- # I don't see the guest as expected. Does anyone know what is wrong?

    Read the article

  • virsh console and tty size

    - by pehrs
    I have a virtualization server to which I connect over ssh. If I now change the size of the window it will automatically propagate to the server. It's most easily seen using stty -a, checking the columns and row values. I then use virsh console to connect to the serial interface on a KVM based virtual machine. When I now change the size of the window it does not propagate to the virtual server. This is most easily seen by checking stty -a, which is not updated on the virtual machine when I change window size. This means that line breaks does not work correctly in the terminal and any application that relies on window size for formatting (emacs, man, etc) gets messed up unless the window size on the client matches the default size on the server. A workaround is to manually set the window size to match the client window using stty, but I wonder if there is any way to get this information to propagate and set the window size in the virtual machine automatically.

    Read the article

  • qemu command not running directly

    - by Dr. Death
    Can I use "qemu://localhost/system " command directly inplace of "virsh -c qemu://localhost/system " command if my both machines are physically connected in a network as virsh will simply creating the virtual shell between two systems? can I use ssh in place of virtual shell here? I tried this but system gives no directory or file name for qemu even when i had qemu installed properly in my system. but when i use virsh i did not get such errors. Do i need to open any unix socket for doing this?

    Read the article

  • listing of VM's created before libvirt installation or started by any other VM management tool

    - by Dr. Death
    if my VM's are not created using virt-manager or are created using any other tool, then virsh system list command does not give them in the list of running VM's however they are running perfectly on my KVM server. Is there a way to list these VM's in my system list anyhow? I have VM's managed by GKVM, AQEMU, libvirt etc. also some of the user start their VM's using the qemu command as follows: kvm "image name" -m "memory". this starts the VM and allow them to work perfectly. but I am not able to list all these VM's using the virsh system list command.

    Read the article

  • How do I connect to my running VM via virsh?

    - by Avery Chan
    My VM has already been started via virsh start chameleon.ootbdev. When I do a virsh console chameleon.ootbdev I get the following output: Connected to domain chameleon.ootbdev Escape character is ^] error: internal error cannot find character device (null) Doing a google search on this led me to this "solution". Unfortunately, editing the domain via virsh edit chameleon.ootbdev doesn't seem to stick. I suspect the issue is that I'm inserting the XML incorrectly: the instructions from the link ask me to insert the following XML into the domain XML file. <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> I've posted my domain XML file to pastebin here. This is AFTER I've tried to insert the above XML. I inserted this XML after the </devices> block. My primary question is: How do I connect to the running VM? A secondary question would be: How do I edit the domain file with the above XML and get the changes to stick?

    Read the article

  • How to mount a cdrom to a kvm/qemu domain?

    - by ??O?????
    I have set up a virtual machine running Windows XP on my Ubuntu laptop. Using the virt-manager GUI application, I can insert a CD in my drive and go to Details?IDE CDROM 1 and click on the Connect button. Then the CD becomes available in my virtual machine. How can I do the same through the command line? Obviously, I'd like to be able to disconnect from the command line too. Note: I can start the VM from the command line using virsh start testbed (testbed being the name of the domain/VM).

    Read the article

  • Virsh: Different XML with edit than dumpxml. Why?

    - by Dave Vogt
    I'm trying to fetch the VNC access data from a virtual machine managed by libVirt. However, when I run virsh dumpxml $machine, the vnc passwd is missing: <graphics type='vnc' port='-1' autoport='yes'/> Checking the same using virsh edit $machine, I see the password is actually there: <graphics type='vnc' port='-1' autoport='yes' passwd='asdf'/> Why is this? Is this intentional (what reason?), or could this be a bug?

    Read the article

  • How do I extend the virsh/qemu/libvirt Timeout?

    - by Nick
    There's a known issue with starting virtual machines with large hard drive images. Apparently, the time-out is 3 seconds, but in reality, it can take up to 15 seconds for a machine to start. I've read several bug reports, and people confirming it's a time-out problem, but I have yet to see a solution. Is there an option I can pass, like: virsh start MyMachine --ignore-timeout Or a config file that needs changed? Thanks!

    Read the article

  • virt-install says name is in use, but virsh list --all is empty. Where is virt-install finding this name?

    - by Jay _silly_evarlast_ Wren
    virt-install says name is in use, but virsh list --all says there is nothing. jrwren@delays:{%22}~ $ virt-install -d -n android -r 512 --disk android.qcow2 -s 4 -c /d/cd\ images/android-x86-2.2-generic.iso --vnc --noautoconsole [Thu, 05 Jul 2012 16:57:19 virt-install 23170] DEBUG (cli:220) Launched with command line: /usr/bin/virt-install -d -n android -r 512 --disk android.qcow2 -s 4 -c /d/cd images/android-x86-2.2-generic.iso --vnc --noautoconsole [Thu, 05 Jul 2012 16:57:19 virt-install 23170] DEBUG (cli:326) Requesting libvirt URI default [Thu, 05 Jul 2012 16:57:19 virt-install 23170] DEBUG (cli:328) Received libvirt URI qemu:///session [Thu, 05 Jul 2012 16:57:20 virt-install 23170] DEBUG (virt-install:259) Requesting virt method 'default', hv type 'default'. [Thu, 05 Jul 2012 16:57:20 virt-install 23170] DEBUG (virt-install:469) Received virt method 'hvm' [Thu, 05 Jul 2012 16:57:20 virt-install 23170] DEBUG (virt-install:470) Hypervisor name is 'kvm' [Thu, 05 Jul 2012 16:57:20 virt-install 23170] DEBUG (cli:950) --graphics compat generated: vnc [Thu, 05 Jul 2012 16:57:20 virt-install 23170] ERROR (cli:597) Guest name 'android' is already in use. (venv)jrwren@delays:{%22}~ $ sudo virsh -c qemu:///system list --all Id Name State ---------------------------------- Where is virt-install finding this name? edit: I should mention that LIBVIRT_DEFAULT_URI is not set.

    Read the article

  • PCI hotplug doesn't seem to work

    - by user245454
    In virsh I detach a PCI bus from host and attach it to a VM. I don't see any errors in these steps. But I don't see the PCI device listed in the VM. virsh # nodedev-dettach pci_0000_01_00_0 Device pci_0000_01_00_0 dettached virsh # attach-device VM1 pci_add.xml Device attached successfully $ cat pci_add.xml <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x000' bus='0x01' slot='0x00' function='0x0'/> </source> </hostdev> Is PCI hot plug not supported? I am using Ubuntu 12.04.3(kernel 3.8.0-34). I can add the same PCI device through virsh edit VM1 and start the VM1. This way I am able to see the device.

    Read the article

  • Libvirt installation - Centos

    - by sethu
    I am currently using Centos 6. I want to use the latest version of libvirt (libvirt 0.9.4). The machine already has libvirt 0.8.1 installed . I did yum remove libvirt to remove the existing libvirt and I compiled 0.9.4 from source using : ./configure --prefix=/ make make install ldconfig /etc/init.d/libvirtd start After the installation is complete, I wanted to use the virsh interface. Once I enter virsh , I get : virsh /lib/libvirt.so.0: version 'LIBVIRT_PRIVATE 0.8.1' not found (required by virsh) Can somone let me know how to solve this issue? Correct me if I am doing something wrong. Thanks a lot ! Sethu

    Read the article

  • 2xAMD Opteron 6128 with libvirt, Physical CPU 13 doesn't exist

    - by yak
    I need help with libvirt(?) problem. Server specs: ProLiant DL165 G7 2x AMD Opteron(tm) Processor 6128 System: Debian GNU/Linux testing (wheezy) 3.2.0-3-amd64 libvirt 0.9.12-5 kvm 1:1.1.2+dfsg-2 $ grep processor /proc/cpuinfo | wc -l 16 $ virsh nodeinfo setlocale: No such file or directory CPU model: x86_64 CPU(s): 16 CPU frequency: 800 MHz CPU socket(s): 2 Core(s) per socket: 4 Thread(s) per core: 1 NUMA cell(s): 1 Memory size: 66114200 KiB $ virsh capabilities .. <topology> <cells num='4'> <cell id='0'> <cpus num='4'> <cpu id='0'/> <cpu id='1'/> <cpu id='2'/> <cpu id='3'/> </cpus> </cell> <cell id='1'> <cpus num='4'> <cpu id='4'/> <cpu id='5'/> <cpu id='6'/> <cpu id='7'/> </cpus> </cell> <cell id='2'> <cpus num='4'> <cpu id='12'/> <cpu id='13'/> <cpu id='14'/> <cpu id='15'/> </cpus> </cell> <cell id='3'> <cpus num='4'> <cpu id='8'/> <cpu id='9'/> <cpu id='10'/> <cpu id='11'/> </cpus> </cell> </cells> </topology> .. $ virsh vcpupin vm 0 13,12,11,10,9,8,7,6,5 error: Physical CPU 13 doesn't exist. error: cpulist: Invalid format. Question? Why my VM Guests use only first 8 CPUs and next 8 are idling? $ for host in virsh list | awk '{print $2}'; do virsh vcpuinfo $host; done | grep ^CPU: | sort | uniq CPU: 0 CPU: 1 CPU: 2 CPU: 3 CPU: 4 CPU: 5 CPU: 6 CPU: 7 Any ideas how to change it?

    Read the article

  • What steps should I take to debug this non-starting hvm virtual machine?

    - by Ophidian
    I have a dom0 machine running CentOS 5.4 with all the latest updates using Xen as my hypervisor. I am using Xen in part because this machine was set up prior to KVM being included in RHEL, and in part because KVM's network bridging configuration is not nearly as simple as Xen's. The dom0 machine is headless and I do all of my VM management via virsh from the command line. I have two hvm domU's: A web server running CentOS 5.4 A mail server running Gentoo Both VM's are backed by LV's on the dom0 but do not use LVM in the domU. Both have virtually identical libvirt configurations (differing by expected things like name, UUID, NIC MAC, VNC port, etc). The web server domU (WSdomU hereafter) does not start since applying the most recent kernel update (kernel-xen-2.6.18-164.15.1.el5.x86_64 and kernel-2.6.18-164.15.1.el5.x86_64 for the dom0 and WSdomU respectively). By 'not start' I mean it appears to be running but it does not use an CPU cycles, does not bring up a graphical console, and does not respond on the network. The WSdomU is listed as no state rather than the normal running or blocked in xentop. The mail server domU starts fine and functions normally. Here are the steps I have taken so far that did not solve the problem: Reboot the dom0 to see if things come up on their own Check xen dmesg on dom0 Check xend logs (a cursory viewing did not show anything blatant; specific suggestions of things to look for would be appreciated) Attempted to connect to the WSdomU's graphical (VNC) console from the dom0 Shutdown the mail server domU and attempt to start the WSdomU Check the SELinux labels on backing LV's (they're the same) Set SELinux to permissive and attempt to start the WSdomU Use virsh edit to try tweaking the WSdomU config virsh undefine, reboot, virsh define the WSdomU config dd the WSdomU LV to an .img file, copy it to my Fedora desktop and run it under KVM (works fine) What steps should I take next to debug this? I will edit in any additional configuration's requested in the comments.

    Read the article

  • SOLVED:Bootloader isn't executable booting XEN PV Guest with virtual-manager

    - by user2284355
    I am going insane with an error I am encountering while trying to install a PV Guest of Debian Wheezy on a Ubuntu Server precise Xen default build with libvirt. The steps I take with virt-manager are the following: 1.Net install via: http://ftp.es.debian.org/debian/dists/stable/main/installer-amd64/ 2.Install process is flawless, installed via VNC over virt-manager 3.When the VM starts I get the following error: Error starting domain: POST operation failed: xend_post: error from xen daemon: (xend.err "Bootloader isn't executable") Most answers i have found on google say that I need to edit the VM's .cfg file and correct the path to pygrub but virt-manager does not seem to create this file (I have searched the entire drive with "find". Another detail is that virsh list --all shows no VMs (Not even dom0) while the command xm list shows all of them. Any help is much appreciated. EDIT: Connected remotely via virsh: virsh -c xen+ssh://user@ip dumpxml vmname Found line: /usr/bin/pygrub ln -s /usr/lib/xen-4.1/bin/pygrub /usr/bin/pygrub Now it works. If anyone can think of a better solution give me a shout. Cheers

    Read the article

  • KVM/Qemu Guest Shutdown problems

    - by Gaia
    on both host and guest running CentOS 6.3 with KVM/Qemu virtualization, I have the following scenarios: "virsh shutdown kvm1" did not shutdown at all. virsh lists guest as running. "service libvirt-guests stop" did not shutdown in 280 seconds (shutdown_timeout=300. on_shutdown=shutdown) "shutdown now" from within guest, guest becomes unreachable. virsh lists guest as running, though it could not connect to it. "shutdown -h now" from within guest works. "shutdown -r now" from within guest works. Libvirt logs show nothing for the first 3 scenarios. I can pause the guest fine. Bottom line, I cannot shutdown from outside the guest. What do I check to figure out what is going on?

    Read the article

  • Scanning for new disks attached using virtio?

    - by larsks
    I can successfully attach disks to a running KVM instance using virsh attach-disk... virsh attach-disk node-1 /dev/vg_lunsr/lun1 vdb Disk attached successfully ...but these new devices aren't seen by the guest without a reboot, which almost defeats the purpose of dynamic attachment. If these were SCSI devices I would use e.g. /sys/class/scsi_host/host0/scan to request the SCSI drivers to scan for new devices. Is there an equivalent capability for the virtio block driver?

    Read the article

  • libvirt and VirtualBox / Getting Started

    - by Marc Lucas
    I'm trying to get started on libvirt with VirtualBox as a virtualization solution. I installed everything and VirtualBox itself is running when using their VBoxHeadless command. However, libvirt fails to connect to VirtualBox: # virsh -c vbox:///session libvir: error : could not connect to vbox:///session error: failed to connect to the hypervisor I could not find any hints in the libvirt documentation that point to whether I have to make any domain specific configuration before using virsh. Does anyone have a hint? Or even better, maybe a tutorial that works through the way of using libvirt, virsh or it's APIs (my later goal) from the ground up.

    Read the article

  • Juju bootstrap fails to start network on local environment

    - by Amith KK
    I've followed the instructions at https://juju.ubuntu.com/CharmSchool and rebooted 5 times...... I cant seem to do a juju-bootstrap (local) This is the output: amith@amith-desktop:~$ juju bootstrap 2011-11-24 17:08:05,708 INFO Bootstrapping environment 'local' (type: local)... 2011-11-24 17:08:05,710 INFO Checking for required packages... 2011-11-24 17:08:06,593 INFO Starting networking... error: Failed to start network default error: internal error Child process (dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --listen-address 192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253 --dhcp-no-override) status unexpected: exit status 2 Command '['virsh', 'net-start', 'default']' returned non-zero exit status 1 2011-11-24 17:08:07,217 ERROR Command '['virsh', 'net-start', 'default']' returned non-zero exit status 1 Is there any fix at all?

    Read the article

  • libvirt + ESX (HTTP response code 400 for call to 'Login')

    - by Coops
    I'm trying to connect to a vSphere cluster using the information from the libvirt documentation. $ virsh -c "vpx://[email protected]/dc1/dc1-cluster-e01/dc1-vsphere-e04/?no_verify=1" Enter root's password for 10.51.4.11: error: internal error HTTP response code 400 for call to 'Login' error: failed to connect to the hypervisor I seem to be able to establish a connection, but it fails with a "HTTP code 400". If I provide the incorrect password it fails with a 'login credentials' error, so it looks like I am getting a connection, but it's failing for another reason. Wireshark is no help as it's all done over SSL/TLS. Any thoughts folks? UPDATE: 15:21 28/02/11 FYI - I'm running libvirt-0.8.3 (the Ubuntu package recompiled with the ESX flag enabled). When I put virsh into debug mode it returns this: [snip] Enter root's password for 10.51.4.11: 15:19:09.011: debug : do_open:1249 : driver 3 ESX returned ERROR 15:19:09.011: debug : virUnrefConnect:294 : unref connection 0x98aa8f8 1 15:19:09.011: debug : virReleaseConnect:249 : release connection 0x98aa8f8 error: internal error HTTP response code 400 for call to 'Login' error: failed to connect to the hypervisor

    Read the article

1 2 3  | Next Page >