Tag Info

New answers tagged

1

I was able to answer my own question after a few days of research. You must pass "ds=nocloud" as a kernel option to the VM. Here's how I did it. #!/bin/sh export VM_NAME=cirros$$ IMAGES_BASE=/var/lib/libvirt/images cp $IMAGES_BASE/cirros/cirros-0.3.0-i386-blank.img $IMAGES_BASE/$VM_NAME.img virt-install -r 256 \ -n $VM_NAME \ --vcpus=1 \ --import ...


0

I use qemu-kvm+libvirt with exactly the configuration you're asking about, for the reasons you listed, but additionally because I get much better performance without the KVM host's filesystem layer in scope. If you add the VG as a 'storage pool' in virt-manager, you can create such VMs using its user-friendly wizard. (But I just write the XML by hand these ...


2

Theres a lot of free memory, but these zones are totally fragmented: Node 0 Normal: 1648026*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 6592104kB Node 1 Normal: 8390977*4kB 1181188*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB There are very few non-zero order pages left, none in one ...


0

If you are using qemu with -snapshot to avoid that the disk images gets modified qemu could behave like this when it keeps the disk modifications in a temporary file which might fill up a partition or ram disk like /dev/shm. There is some more information about this at ...


3

After verifying base guest configuration file (xml) found the problem. <vcpu placement='static' cpuset='2'>1</vcpu> Since I used same template for creating all VMs after cloning, all VMs were using same CPU.


0

Looks like I created this problem my self by restarting the firewall on my host, for other reasons. Libvirtd adds network filter rules to the firewall when libvirtd starts up. Restarting your firewall will remove these rules. You need to restart libvirtd if you restart your firewall.


1

NetCrunch 8 is an all-in-one network monitoring/management suite that'll handle your VMs out of the box. It's not FOSS, but it's a price leader, and if you've got a budget it's worth checking out.


0

I had the same problem and this worked for me : https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1273522.html rm -rf /var/cache/libvirt/qemu/capabilities/* And after a reboot it was fine.


0

In this case the answer was simple. I had: <component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86"> When I needed: <component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" ...


1

the procedure that we use to generate the official Windows Server 2012 R2 evaluation images for OpenStack is detailed here: https://github.com/cloudbase/windows-openstack-imaging-tools Windows OpenStack images (KVM and Hyper-V): http://www.cloudbase.it/ws2012r2/


1

bond-mode 0 This is the problem. Bridging doesn't support modes 0 and 6, In fact, for optimal performance, you should stick to either mode 1 or 4


1

The kernel you updated to likely does not have scheduler support you are looking for e.g. you should be seeing something like this egrep 'CONFIG_IOSCHED_.*=y' /boot/config-`uname -r` CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y Where did you get that 3.14 kernel? If you were building it make sure you have those config options set ...


-2

PROXMOX cannot be installed on a VPS. It also needs to be on installed on 3 servers for a cluster at minimum.


2

Set the wanted disk as virtio-disk0, with target of /dev/vda. The order the disks appear in, in the XML is also important, so make sure the OS disk comes first


0

Ok problem solved: The problem was a misconfiguration in libvirt. The virtual bridge was configured in isolated mode, after switching to routed virtual network and adding the route: 10.8.0.0/24 gw 10.10.10.1 to the VM guests everything worked as expected.


0

I just experienced the same issue on Gentoo after upgrading to kernel 3.16.5 from kernel 3.12.21. I skipped kernel 3.14.14 as it caused by USB2 support to disappear. I am running this: jserink@jserinki7 ~/qemu/vde $ qemu-system-x86_64 --version QEMU emulator version 2.1.1, Copyright (c) 2003-2008 Fabrice Bellard While on kernel 3.16.5 I have this issue, ...



Top 50 recent answers are included