virt

virt@lists.centos.org

1610 discussions

CentOS 6 and KVM woes
by Trey Dockendorf 17 Jul '11

17 Jul '11

I have decided to migrate my latest KVM server to CentOS 6.0 and am beginning to get a little frustrated with some issues that worked perfectly in 5.6. Right now I've given up on getting virbr0 and NAT to work, but now I need networking bridging to work, but nothing seems to fix the issue. I have not had much experience with troubleshooting KVM so could really use some pointers on resolving this issue. I have successfully bridged one of the server's NICs to br0, and I can ping the IP remotely that is assigned to br0, but none of the VMs that worked in 5.6's KVM are able to access the network. Please let me know what information would be useful to troubleshoot this. Here's what I have so far... ifcfg-eth3... --------------------------------- DEVICE="eth3" HWADDR="00:1B:21:A1:CF:76" ONBOOT="yes" BRIDGE=br0 ifcfg-br0 -------------------------------- DEVICE=br0 TYPE=Bridge BOOTPROTO=static ONBOOT=yes IPADDR=.... BROADCAST=.... NETMASK=.... NETWORK=.... # brctl show bridge name bridge id STP enabled interfaces br0 8000.001b21a1cf76 no eth3 sysctl.conf has these 3 additional lines... net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 net.bridge.bridge-nf-call-arptables = 0 Again I can ping br0's IP remotely , but no VMs assigned to it can access even that network's gateway. I have disabled iptables and ip6tables for now while trying to get this to work. The VMs , worked just fine in 5.6 and I have done nothing different but import them with virsh. Thanks - Trey

6 11

IPtables and Libvirt
by Trey Dockendorf 17 Jul '11

17 Jul '11

Running CentOS 6 I have noticed that Libvirt will automatically configure IPtables once a VM is using the built in NAT , or "default" network. How do I modify the IPtable rules without breaking libvirt's ability to configure these rules? This is the firewall settings on a fresh install with no VMs using virbr0... -------------------------- Table: filter Chain INPUT (policy ACCEPT) num target prot opt source destination 1 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 2 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 3 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 4 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 5 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain FORWARD (policy ACCEPT) num target prot opt source destination 1 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-is-bridged 2 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) num target prot opt source destination And this is what I see after a reboot or once a VM uses the NAT ---------------------------- Table: mangle Chain PREROUTING (policy ACCEPT) num target prot opt source destination Chain INPUT (policy ACCEPT) num target prot opt source destination Chain FORWARD (policy ACCEPT) num target prot opt source destination Chain OUTPUT (policy ACCEPT) num target prot opt source destination Chain POSTROUTING (policy ACCEPT) num target prot opt source destination 1 CHECKSUM udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:68 CHECKSUM fill Table: nat Chain PREROUTING (policy ACCEPT) num target prot opt source destination Chain POSTROUTING (policy ACCEPT) num target prot opt source destination 1 MASQUERADE tcp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 2 MASQUERADE udp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 3 MASQUERADE all -- 192.168.122.0/24 !192.168.122.0/24 Chain OUTPUT (policy ACCEPT) num target prot opt source destination Table: filter Chain INPUT (policy ACCEPT) num target prot opt source destination 1 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53 2 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 3 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:67 4 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 5 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 6 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 7 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 8 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 9 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain FORWARD (policy ACCEPT) num target prot opt source destination 1 ACCEPT all -- 0.0.0.0/0 192.168.122.0/24 state RELATED,ESTABLISHED 2 ACCEPT all -- 192.168.122.0/24 0.0.0.0/0 3 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 4 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 5 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 6 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-is-bridged 7 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) num target prot opt source destination My concern is that if I begin to add custom rules that it will break this setup. If I run "service iptables save" after adding a rule, IPtables will then have saved this dynamic configuration. I assume it's dynamic because "/etc/sysconfig/iptables" does not reflect the second set of rules I pasted, but rather the first even when the second set is showing as active. Thanks - Trey

1 0

Xen and timekeeping
by Dmitry E. Mikhailov 11 Jul '11

11 Jul '11

Hi everyone, I have the problem with Xen domU's and timekeeping in dom0. Time in dom0 was incorrect by 5 hours due to wrong timezone assumed. Fixed it by ntpdate ntp.nist.gov. The time on a dom0 was changed. I didn't append xen.independent_wallclock=1 to sysctl.conf thus the time in all domU's was also changed. But THEY DIDN'T "KNOW" THAT! The 'date' output in domU shows time unchanged, as before, incorrect by 5 hours. But any current_time-dependent operations don't behave correctly. Quagga's OSPFd daemon doesn't add routes. 'service dhcpd stop' hangs forever while correctly stopping the daemon. AFAIK, it hangs on 'killproc' [root@gbuh-ufa init.d]# grep killproc dhcpd -A 2 -B 2 echo -n $"Shutting down $prog: " killproc $prog RETVAL=$? [ $RETVAL = 0 ] && rm -f $lockfile From http://www.novell.com/coolsolutions/feature/15380.html killproc: killproc kills a process which is given by a full path to the executable. ...cut... (by default a SIGTERM is sent, then a SIGKILL if the process does not die within 5 seconds). So a 5 seconds interval becomes 5 hours and 5 seconds - something I'm not willing to wait for. The problem was worked around when I did a 'date 07111158' on a dom0 and all domU's semi-simultaneously. Is this behaviour normal or should I file a bug? Best regards, Dmitry Mikhailov dom0: Hardware: Intel 5000P chipset, 2 CPUs, total 8 cores [root@xensrv ~]# cat /etc/redhat-release CentOS release 5.6 (Final) [root@xensrv ~]# uname -a Linux xensrv 2.6.18-238.el5xen #1 SMP Thu Jan 13 16:41:45 EST 2011 x86_64 x86_64 x86_64 GNU/Linux [root@xensrv ~]# rpm -q ntp ntp-4.2.2p1-9.el5.centos.2.1 [root@xensrv ~]# cat /proc/cpuinfo - 8 times the following processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5420 @ 2.50GHz stepping : 6 cpu MHz : 1998.000 cache size : 6144 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu tsc msr pae cx8 apic mtrr cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc pni vmx est ssse3 cx16 sse4_1 lahf_lm bogomips : 6237.52 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: domU#0 [root@gbuh-ufa init.d]# cat /etc/redhat-release CentOS release 5.5 (Final) [root@gbuh-ufa init.d]# uname -a Linux gbuh-ufa 2.6.18-238.el5xen #1 SMP Thu Jan 13 17:49:40 EST 2011 i686 i686 i386 GNU/Linux domU#1 [root@buhserv ~]# cat /etc/redhat-release CentOS release 5.6 (Final) [root@buhserv ~]# uname -a Linux buhserv 2.6.18-238.el5xen #1 SMP Thu Jan 13 16:41:45 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

1 0

virtio-win for c6?
by Rainer Traut 11 Jul '11

11 Jul '11

Hi there, I know it's in the supplementary channel and there is no srpm to rebuild windows drivers. But are these drivers anywhere available so that I can use them without a rhn subscription? Thx Rainer

3 6

"CentOS on a stick"
by Dennis Jacobfeuerborn 07 Jul '11

07 Jul '11

Hi, I'm looking into setting up a redundant firewall and I'm wondering how feasible it is to use an USB stick as the only storage device in these systems (i.e. no HDs). The logs will go to a remote logging server but I'm wondering what else needs to be changed to make something like this possible. The idea is to have both systems running independent of each other with the iptables rules being manually kept in sync and conntrackd syncing the connection tracking data. Has anyone experience with this and how would one go about creating such a USB drive? So far I've only used USB for installation but not as an actual root fs itself. Regards, Dennis

1 0

xm attach-block reboots entire server
by Steve Campbell 06 Jul '11

06 Jul '11

I'm still trying to get xen working before Centos 6 and KVM just for experience. I seem to be able to do most of what I what with VMs, but I've run into another problem with CD/DVDs. I can get a DVD mounted on the host domain just fine, but when I try and attach-block to a running guest VM, the entire server reboots. I've tried many different commands versions based on what Google finds, but I'm not getting anywhere. I end up using scp to copy the data from the host to the guest. The guest is basically defined as a full virtualized domain. I'm using /dev/scd0 as the device (it's listed on the mount command) as both frontend and backend devices. And I've tried a few other devices as well, but the same result. Anyone know of a reason or fix, please? steve campbell

3 3

where can i download PV drivers for CENTOS 5.5 HVM Guest
by veerasena reddy 05 Jul '11

05 Jul '11

Hi, This is VeeraSena Reddy (shortly called VSR), recently started working on XEN. I installed CENTOS 5.5 as HVM Guest on XEN-3.4.3 and now i would like to install and test PV Drivers on this guest. Can anyone please guide me where can I get PV drivers for CENTOS 5.5 HVM guest? Thanks in Advance. Regards, VSR.

7 9

More than 32G on memory in a domU guest?
by Norman Gaywood 29 Jun '11

29 Jun '11

I must be missing something obvious. I have a large domU guest: dom0# cat /etc/xen/turing name = "turing" uuid = "8d3383a0-f0ae-f0b1-215d-c2e04115e9fe" maxmem = 40000 memory = 40000 vcpus = 12 bootloader = "/usr/bin/pygrub" kernel = "/var/lib/xen/boot_kernel.nrTJko" ramdisk = "/var/lib/xen/boot_ramdisk.y6Gcn9" extra = "ro root=/dev/mapper/SYSTEM-root SYSFONT=latarcyrheb-sun16 LANG=en_AU.UTF-8 KEYTABLE=us console=hvc0 earlyprintk=xen" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1,keymap=en-us" ] disk = [ "phy:/dev/VM/system,xvda,w", "phy:/dev/VM/home,xvdb,w" ] vif = [ "mac=00:16:3e:7d:d0:91,bridge=xenbr0,script=vif-bridge,vifname=vif3.0" ] dom0# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 3907 16 r----- 66831.9 turing 1 40000 12 r----- 1842736.7 So it looks like I should have 40G of memory available to my guest. The guest boots like this (from /etc/grub.conf of guest): title Fedora (2.6.35.13-92.fc14.x86_64) root (hd0,0) kernel /vmlinuz-2.6.35.13-92.fc14.x86_64 ro root=/dev/mapper/SYSTEM-root SYSFONT=latarcyrheb-sun16 LANG=en_AU.UTF-8 KEYTABLE=us console=hvc0 earlyprintk=xen initrd /initramfs-2.6.35.13-92.fc14.x86_64.img However, the guest reports this: domU# grep MemTotal /proc/meminfo MemTotal: 32870604 kB What did I miss? Additional info: dom0# xm info host : neumann.une.edu.au release : 2.6.18-238.12.1.el5xen version : #1 SMP Tue May 31 14:02:29 EDT 2011 machine : x86_64 nr_cpus : 16 nr_nodes : 1 sockets_per_node : 4 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2132 hw_caps : bfebfbff:20100800:00000000:00000940:000ce33d:00000000:00000001 total_memory : 65534 free_memory : 20354 node_to_cpu : node0:0-15 xen_major : 3 xen_minor : 1 xen_extra : .2-238.12.1.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-50) cc_compile_by : mockbuild cc_compile_domain : centos.org cc_compile_date : Tue May 31 13:13:40 EDT 2011 xend_config_format : 2 -- Norman Gaywood, Computer Systems Officer University of New England, Armidale, NSW 2351, Australia ngaywood(a)une.edu.au Phone: +61 (0)2 6773 3337 http://mcs.une.edu.au/~norm Fax: +61 (0)2 6773 3312 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html

1 1

New to virtualization - can't use more than one CD when installing a new VM
by Steve Campbell 28 Jun '11

28 Jun '11

I've done a search through all the Centos-virt emails, but can't find the answer. I'm trying to install my first VM using Centos 5.5 as the host as well as the VM OS. It starts fine using VMM, but when it asks for the second disk of 8 CDs, the first one isn't ejected, although unmounted because I can open the tray, and won't recognize that the second CD is inserted. Was I wrong in not waiting for the ejection, or am I missing something in the host setup. I'm using xen, if that matters from the 5.5 release. Thanks for any clarity. steve campbell

5 6

common error
by Nehemiah Dacres 28 Jun '11

28 Jun '11

I am trying to install centos 5.4 on a centos 5.2 xen host. Technically this is rocks cluster and thats axillary software but the avalanch installer may be the hiccup this is what shows up in the xen log any suggestions Watching /local/domain/13/logdirty/next-active xs_read(): vncpasswd get error. /vm/84384fb8-e6a6-3a84-8027-e79b841fdc7b/vncpasswd. char device redirected to /dev/pts/4 qemu_map_cache_init nr_buckets = 10000 shared page at pfn 1ffff buffered io page at pfn 1fffd xs_read(/vm/84384fb8-e6a6-3a84-8027-e79b841fdc7b/rtc/timeoffset): read error I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Triggered log-dirty buffer switch -- Nehemiah I. Dacres System Administrator Advanced Technology Group Saint Louis University

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt