[libvirt-users] help filtering spam
by Joe Linoff
Hi Folks:
I am now receiving spam email every few minutes as result of signing up
for this mailing list and it is starting to become a challenge.
Has anyone had any success filtering it?
Regards,
Joe
12 years
[libvirt-users] No driver found during virt-install / kickstart
by Joe Linoff
Hi Folks:
I am getting a "No driver found" dialogue when I try to build a guest
using virt-install using a kickstart file. I am stuck. I am not sure how
to fix or even debug this problem.
Can anyone suggest a way forward?
Here are the commands that I am using:
$ # ================================================================
$ # Create the volume
$ # ================================================================
virsh vol-create default /tools/vm/guests/guest1-vol.xml
$ # ================================================================
$ # Create a mount for the virt-install --location option.
$ # ================================================================
mkdir /opt/mnt
mount -o loop,ro /tools/iso/CentOS-6.3-x86_64-bin-DVD1.iso /opt/mnt
$ # ================================================================
$ # Create the kickstart file (used system-config-kickstart).
$ # ================================================================
$ cat /export/tools/vm/guests/guest1-ks.cfg
#platform=x86, AMD64, or Intel EM64T
#version=DEVEL
# Firewall configuration
firewall --enabled --http --ssh
# Install OS instead of upgrade
install
# Use CDROM installation media
cdrom
# Root password
rootpw --iscrypted $1$DAzH1SN3$6yzxoq6oRrXNw.qMkJU0H1
# System authorization information
auth --useshadow --passalgo=sha512
# Use graphical install
graphical
firstboot --disable
# System keyboard
keyboard us
# System language
lang en_US
# SELinux configuration
selinux --enforcing
# Installation logging level
logging --level=debug
# System timezone
timezone America/Los_Angeles
# Network information
network --bootproto=static --device=eth0 --gateway=192.168.2.1
--ip=192.168.2.68 --nameserver=192.168.2.71 --netmask=255.255.255.0
--onboot=on
# System bootloader configuration
bootloader --location=mbr
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all
%packages
@base
@client-mgmt-tools
@compat-libraries
@console-internet
@emacs
@hardware-monitoring
@network-file-system-client
@network-tools
@performance
@postgresql
@security-tools
@system-admin-tools
@virtualization-client
%end
EOF
$ # ================================================================
$ # Run virt-install
$ # ================================================================
virt-install \
--accelerate \
--location "/opt/mnt" \
--disk device=disk,path="/var/lib/libvirt/images/guest1.img" \
--graphics vnc \
--name "guest1" \
--os-type linux \
--os-variant rhel6 \
--ram 2048 \
--vcpus 2,maxvcpus=2 \
-v \
-w bridge:br0 \
-x 'ks=nfs:192.168.2.140:/export/tools/vm/guests/guest1-ks.cfg
ksdevice=eth0 ip=192.168.2.82 netmask=255.255.255.0
dns=192.168.2.71,8.8.8.8 gateway=192.168.2.1'
Regards,
Joe
12 years
[libvirt-users] Failed to bind socket to '/var/run/libvirt/libvirt-sock': Permission denied
by 何鑫
Hi all, When I start self-built libvirtd by "libvirtd -d -l -f libvirtd.conf", it shows that error : virNetSocketNewListenUNIX:346 : Failed to bind socket to '/var/run/libvirt/libvirt-sock': Permission denied I have removed some requested comments in libvirtd.conf. The key settings are shown as below: listen_tcp = 1 tcp_port = "16509" listen_addr = "0.0.0.0" unix_sock_group = "root" unix_sock_rw_perms = "0770" unix_sock_ro_perms = "0777" unix_sock_dir = "/var/run/libvirt" Is there any thing wrong? Need I start libvirtd by root?
Thanks a lot!
Best Regards!Corey
12 years
[libvirt-users] re-create disk image file
by Joe Linoff
Hi Everybody:
I am curious about how to re-create a disk image file from a running
guest when the original disk image file is accidentally deleted. This
came up recently during a test scenario but I couldn't figure out how to
do it.
Thanks,
Joe
12 years
[libvirt-users] CPU Mode= Host passthrough
by Michael Beham
Hi,
I´m doing some research on Nested Virtualization with KVM and Xen. My
cpu on bare-metal system is a Opteron_G4 --> (AMD Opteron 4280).
qemu-version 1.0; libvirt 0.9.12
For nesting KVM in KVM I´m adding the <cpu mode='host-passthrough'/>
command to the XML-File of the VM on Layer 0. So I´m able to install KVM
in KVM and create nested guests at Layer 2.
L2 --> Nested VM
L1 --> KVM / XEN
L0 --> KVM
If i try the same with installing Xen in the VM on Layer 1 Xen don´t
boot and I get following error:
Panic on CPU 0:
GENERAL PROTECTION FAULT
[error_code=0000]
If I remove <cpu mode='host-passthrough'/> command from the VM´s XML Xen
boot is successful and Nesting Xen in KVM works!
May this problem depends on the following problem -->
https://bugzilla.redhat.com/show_bug.cgi?id=804224
12 years
[libvirt-users] virsh vol-create-as failing on NFS automount for chmod (dynamic_ownership = 0)
by Joe Linoff
Hi Everyone:
I am trying to create a volume using the vol-create-as command but it
fails with an "Operation not permitted" error. It appears to be caused
by an attempt to run chown on an NFS mounted file system but I have set
dynamic_ownership to 0 in /etc/qemu.conf.
Is it possible to disable the chown operation? If not, is there a guide
that describes how to create storage pools on NFS filers? I have read
http://libvirt.org/storage.html but there was no discussion of to work
around this problem.
Any help would be greatly appreciated.
Here is the command and error message:
$ virsh vol-create-as default webtst 10G
error: Failed to create vol webtst
error: cannot create path '/var/lib/libvirt/images/webtst': Operation
not permitted
The /var/lib/libvirt/images is linked to a common filer:
/shared/vm/images. The permissions on the directory are 0777.
When I looked at tail /var/log/libvirt/libvirtd.log it showed that the
problem was occurring because a chown command:
2012-11-05 02:55:44.841+0000: 26384: info : libvirt version: 0.9.10,
package: 21.el6_3.5 (CentOS BuildSystem <http://bugs.centos.org>,
2012-10-11-13:57:12, c6b9.bsys.dev.centos.org)
2012-11-05 02:55:44.841+0000: 26384: error :
virFileOpenForceOwnerMode:796 : cannot chown
'/var/lib/libvirt/images/webtst' to (0, 0): Operation not permitted
2012-11-05 02:55:44.841+0000: 26384: error :
virStorageBackendCreateRaw:401 : cannot create path
'/var/lib/libvirt/images/webtst': Operation not permitted
Regards,
Joe
12 years
[libvirt-users] error: Unable to add port vnet1 to OVS bridge ovsbr: Operation not permitted
by Radhika Niranjan
Hi,
>
> I am using libvirt version 0.9.13 with Ubuntu 12.10
>
> When I try to start a VM with an openvswitch bridge interface I get the
> error:
>
> error: Failed to start domain kvm113-2
> error: Unable to add port vnet1 to OVS bridge ovsbr: Operation not
> permitted
>
>
> Here is my bridge configuration:
> <interface type='bridge'>
> <mac address='52:54:00:c7:db:d2'/>
> <source bridge='ovsbr'/>
> <virtualport type='openvswitch'>
> <parameters interfaceid='40e21558-217c-d8ef-c9a9-5275fa4b4a46'/>
> </virtualport>
> <model type='virtio'/>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x05'
> function='0x0'/>
> </interface>
>
>
> This configuration previously worked fine.
>
> Request your help and insights.
>
> WIth best regards
> Radhika
>
12 years
[libvirt-users] hotplug
by Douglas Russell
Another separate thread for a slightly separate issue.
For some reason, hotplugging disks does not work for me.
I built my guest with ubuntu's vmbuilder. It's Precise, virtual.
I have acpiphp in my /etc/modules file:
$ lsmod
Module Size Used by
psmouse 97443 0
serio_raw 13211 0
virtio_balloon 13108 0
acpiphp 24231 0
floppy 70365 0
hotplug_pci seems to be compiled into the kernel:
$ grep HOTPLUG_PCI /boot/config-3.2.0-32-virtual
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_FAKE=m
CONFIG_HOTPLUG_PCI_ACPI=m
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
CONFIG_HOTPLUG_PCI_CPCI=y
CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m
CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m
CONFIG_HOTPLUG_PCI_SHPC=m
But when I attach a disk, absolutely nothing happens in the guest. No
messages in the logs, no change to /proc/partitions, no new device nodes.
When I reboot, the disk appears.
Any ideas?
Thanks,
Douglas
12 years
