aehusain@buffalo.edu
2009-Mar-12 04:24 UTC
[Xen-users] Xen Cpufreq modules and Networking Issue!
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; } Dear All, I was trying to set up a virtual network with fc7 Dom0 and ubuntu 8 (Hardy) & Fedora 9 (etc) as DomU images on AMD Opetron 152 processor based machine. I was able to successfuly establish a virtual network using bridge connection Xen Network configuration. After that I tried to install cpufreq-utils on Dom0 which did the installation of "cpufreq-utils 002" package using "yum". Even after installing that when did ''cpufreq-info'' on command line, I was getting "no active driver available" error message. Just to repeat the experiment, I removed the "Virtualization" modules of Xen by booting machine on basic FC7 kernel and reinstalled the Xen using following commands: 1. yum gourpinstall "Virtualization" 2. yum install xen I rebooted in xen kernel and to my amazment find that Dom0 is no more connected in network. The o/p of ifconfig is On dom0: #ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3651 errors:0 dropped:0 overruns:0 frame:0 TX packets:3651 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:26398676 (25.1 MiB) TX bytes:26398676 (25.1 MiB) tmpbridge Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:128.205.39.118 Bcast:128.205.39.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:8975 (8.7 KiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:4323 (4.2 KiB) xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:4416 (4.3 KiB) As there was no "eth0" device configured, I added eth0 using "ifup eth0", the o/p after doing that action is [root@steelbug ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:E0:81:58:BF:2A inet addr:128.205.39.118 Bcast:128.205.39.255 Mask:255.255.255.0 inet6 addr: fe80::2e0:81ff:fe58:bf2a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:84 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3018 (2.9 KiB) TX bytes:17853 (17.4 KiB) Interrupt:23 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3651 errors:0 dropped:0 overruns:0 frame:0 TX packets:3651 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:26398676 (25.1 MiB) TX bytes:26398676 (25.1 MiB) tmpbridge Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:128.205.39.118 Bcast:128.205.39.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:8975 (8.7 KiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:4323 (4.2 KiB) xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:4416 (4.3 KiB) this is the output with no virtual machine running as domU. By doing this dom0 gets connected to network but I am not able to connect to any domU (ping) or vice versa. [root@steelbug ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination On domU : root@ubuntu-pristine:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3e:27:07:79 inet addr:128.205.39.150 Bcast:128.205.39.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4378 (4.2 KB) TX bytes:274 (274.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) With respect to ''cpufreq'' not working, I have checked the BIOS settings and enabled ''CoolNQuiet'' settings for it, I can do the cpu throttling if booted in basic fc7 kernel but cpufreq folder (/sys/devices/system/cpu/arch/x86_64) is not present in the system. Does this mean that cpufreq is not supported by xen hypervisor ? Now, I am not able to establish virtual network and also cpufreq module is not working for Dom0. Please provide some guidance if somebody have solutions to any of these two issues or both of it. Thanks & Regards! Ata E Husain Bohra Student - CSE Department University at Buffalo, New York _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users