similar to: guests not shutting down when host shuts down

On 10.07.2013 11:37, Lentes, Bernd wrote: > Hi, > > i have a SLES 11 SP2 64bit host with three guests: > - Windows XP 32 > - Ubuntu 12.04 LTS 64bit > - SLES 11 SP2 64bit > > The SLES guest shuts down with the host shutdown. The others not. When i shutdown these two guests with the virt-manager, they shutdown fine. > ACPI is activated in virt-manager for both of them.

Michal wrote: > -----Original Message----- > From: Michal Privoznik [mailto:mprivozn@redhat.com] > Sent: Wednesday, July 10, 2013 12:45 PM > To: Lentes, Bernd > Cc: libvirt-ML (libvirt-users@redhat.com) > Subject: Re: [libvirt-users] guests not shutting down when > host shuts down > > On 10.07.2013 11:37, Lentes, Bernd wrote: > > Hi, > > > > i have a

Hi All, I am running on CentOS Released 6.1 final. Been using and running Linux KVM quite well for quite some time, something goes wrong after I perform yum upgrade. I created new VM yesterday without any problem, same exact installation procedure, installed FreeBSD 8.2. I tried to create a new VM today after yum upgrade, it's able to detect the hard disk, when I start commit FreeBSD 8.2

Hi All. I'm trying to setup a guest within my hypervisor that acts as a Console Server, using 10 USB to Serial adapters. The Host is all setup and can access each Serial Port without problems. I have attempted to add the Serial Connections to a Guest, using both Virtual Machine Manager and by editing the .XML file, and I can add up to 4 Serial devices (Including one for console access to the

Greetings - I shutdown one of my Centos 6.2 VMs for some offline maintenance and am now unable to get it to restart. I am also unable to create and start a new VM. The host system is Centos 6.2, fully up to date. I have been searching Google for two days and have not been successful in getting a VM to start. I have restarted libvirtd, but did not want to shutdown my other two running VMs and

Hi there, I have used qemu to install FreeBSD 9.2 release, and i can boot it fine with: $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img I then made virsh aware of my brand new VM (see attached XML), but when i run it via virsh, It hangs after the bootloader whith this message: Booting... CPU doesn't support long mode From the log, here is the generated qemu command:

Hello, I'm using virt-manager on my F23 box to run a Windows 10 image but the performance is so bad it's killing me. I have "vmx" flag in /proc/cpuinfo # lsmod |grep kvm kvm_intel 167936 6 kvm 503808 1 kvm_intel virtio-win-0.1.112-1.noarch But no virtio modules loaded. Should they be loaded nowadays? The disk format used is vmdk with no

Hello, I am running into issues restoring VMs during reboot for some of my XP VMs - the environment is QEMU 2.2.0, libvirt 1.2.12 on CentOS 6.5 with KVM and libvirt-guests is set to suspend at shutdown. The weird part is Windows 7 is restored properly from the managedsave however XP does not, doing a start from virsh shows this: virsh # start xp-check error: Failed to start domain xp-check

On Mon, 2015-06-29 at 13:47 -0700, Greg Bailey wrote: > I've installed it on a KVM guest on a CentOS 7 host. I was hoping it wasn't going to come to that. That is, I hope it's not a CentOS 6 issue. > I've always had more success using the drivers obtained from running the > spice guest tools vs. the virtio-win stuff. I use: > >

Just a quick correction and apologies, the actual issue is that http will not work, https will so I dont think this is a bug as such I think this is by design likely for security. Looking at the man page for qemu-kvm it states http will work with examples given however only https works, my best guess from looking at the spec file from the srpm is that it has only been enabled in the centos

Hi. I've been running CentOS 5 for ages. (Thanks!) I went to install 6.3 - I downloaded the 64-bit DVD 1 image, and put it on a USB drive. Booted into a screen that said boot will start in 10.. 9... 8.. 7.. 6.. 5.. 4.. 3.. 2.. 1.. 10.. and so on, infinite loop, the boot never starts. I tried booting in text mode, but it doesn't boot, just goes back to the menu. Is there some way to

@Michal: Thanks for your reply! Indeed I have found a package in the AUR (libvirt-zfs) and only had to change to the current version and add zfs-utils as dependency in the PKGBUILD. Now I don't get the previous error anymore but I still cannot setup a VM because I constantly get errors due to wrong permissions. I have tried to change the permissions in: - /etc/libvirt/qemu.conf -

On Thu, Nov 14, 2013 at 12:48:51PM +1300, Christian Gagneraud wrote: > On 14/11/13 10:53, Christian Gagneraud wrote: > >Hi there, > > > >I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > >with: > >$ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > > >I then made virsh aware of my brand new VM (see attached XML),

Hi, I'm running the latest libvirt 0.9.9. I'm trying to start a VIF of type "Ethernet". I know there are problems with that because you need to be root in order to control the tun/tap driver. I changed my qemu.conf file to user = "root" group = "root" clear_emulator_capabilities = 0 However, I still get an error when trying to start my VM: [root]# virsh

Hi, I have a fedora21 system that's been running fine under normal network activity, but trying to perform a full backup of the 300GB filesystem is taking forever because the network speed appears to be very slow. Using rsync, the transfer speeds reach a max of like 180kB/s. Using rsync to copy files on the local filesystem is greater than 55MB/s, so I don't think it's a disk

Any error in your host logs? On Sunday, 30 October 2016, Steven Tardy <sjt5atra at gmail.com> wrote: > > > On Oct 30, 2016, at 3:27 AM, Paul R. Ganci <ganci at nurdog.com > <javascript:;>> wrote: > > > > grub> set root=(hd0,msdos2) > > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 > root=(hd0,msdos2)/ > > grub> initrd

I'm having some trouble creating KVM domains with RBD block devices using virsh. I've managed to get virsh to define the domain, but it gives an error when trying to start the domain: error: Failed to start domain test0 error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/3 kvm: -drive

I am trying to make Qemu agent work with libvirt thanks to https://github.com/NixOS/nixops/pull/922 with libvirt 4.1.0. I've been trying to make it work for quite some time but I still haven't the slightest idea of what is wrong, I keep seeing "Guest agent is not responding: QEMU guest agent is not connected" as the program I use (nixops) calls the libvirt python API. I

Hello, CentOS 7.2 I have three Server on all is now broken the KVM System, it is not possible to start KVM Clients ? Have any a hint why ? Thanks for a answer -- mit freundlichen Gr??en / best regards, G?nther J. Niederwimmer

Hi Daniel, I have noticed that it will fail exactly as you said if <cdrom> is first in the boot order, if <hd> is first in the boot order the XML validates and it starts as usual. first in log except below is with cdrom set to first in boot order, second is with hd set first. 2018-08-09 11:39:28.625+0000: starting up libvirt version: 3.9.0, package: 14.el7_5.6 (CentOS BuildSystem