xen July 2007

xen@lists.fedoraproject.org

55 participants
58 discussions

How is network bridging for Xen handled in F7?
by Christian Reiter 06 Feb '08

06 Feb '08

Hi! Can anybody tell me where i can find docs about handling network bridges for xen domUs in Fedora 7? Something changed since FC6, so i cannot figure out how to create simple bridges without dhcp for my xen domUs. All what i want is: xenbrINTERNET should bridge to eth1 xenbrLAN should bridge to eth0 eth0 and eth1 of my dom0 should also have an IP Address. I do not want routing or nat for my domUs. Thanks! regards, christian

3 7

Guest VM dropping connection.
by Ubaidul Khan 15 Jan '08

15 Jan '08

I am running RHEL5 Guest and Host. The guest OS is dropping network connections occasionally(I noticed my ssh session suddenly terminated). The guest is configured with private network interface and a public network interface. Following are the bridge/network settings for the host: bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif2.0 vif1.0 peth0 vif0.0 xenbr1 8000.fefffffffffe no vif2.1 peth1 vif0.3 xenbr1 is dedicated to provide the private network link for the guest os. Following is the guest OS configuration: # Automatically generated xen config file name = "saleen_webvm0" memory = "1000" disk = [ 'tap:aio:/vms/img/redhat/linux/es/5.0/x86_64/saleen_webvm0.img,xvda,w','phy:/dev/sdc,xvdb,w' ] vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0','mac=00:16:3e:2f:9e:b1, bridge=xenbr1',] # vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0',] vfb = ["type=vnc,vncunused=1"] uuid = "122374dc-26a3-cb0d-99f8-3393e2481777" bootloader="/usr/bin/pygrub" vcpus=2 on_reboot = 'restart' on_crash = 'restart' Following is the output of ifconfig: eth0 Link encap:Ethernet HWaddr 00:14:4F:40:D8:70 inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe40:d870/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:79313 errors:0 dropped:0 overruns:0 frame:0 TX packets:1167 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6619719 (6.3 MiB) TX bytes:115448 (112.7 KiB) eth1 Link encap:Ethernet HWaddr 00:14:4F:40:D8:71 inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe40:d871/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:720 (720.0 b) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:105404 errors:0 dropped:0 overruns:0 frame:0 TX packets:13455 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9122426 (8.6 MiB) TX bytes:1997833 (1.9 MiB) Base address:0x8c00 Memory:fa5e0000-fa600000 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FE inet6 addr: fe80::fcff:ffff:feff:fffe/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:9239102 errors:0 dropped:0 overruns:0 frame:0 TX packets:5337342 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12420212276 (11.5 GiB) TX bytes:523849820 (499.5 MiB) Base address:0x8800 Memory:fa5c0000-fa5e0000 vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:2174 errors:0 dropped:0 overruns:0 frame:0 TX packets:80032 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:446031 (435.5 KiB) TX bytes:6941997 (6.6 MiB) vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:10084 errors:0 dropped:0 overruns:0 frame:0 TX packets:89284 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:1186096 (1.1 MiB) TX bytes:7380350 (7.0 MiB) vif2.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:5337343 errors:0 dropped:0 overruns:0 frame:0 TX packets:9239082 errors:0 dropped:20 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:403712612 (385.0 MiB) TX bytes:12383227754 (11.5 GiB) Any help is greately appreciated. _________________________________________________________________ http://liveearth.msn.com

3 3

domUs become unaccessible running 2.6.20-1.2962.fc6xen on host
by Asrai khn 23 Aug '07

23 Aug '07

Hi, We have recently update kernel-xen on all of our hosts (3) and its vms all running fc6. kernel-xen 2.6.20-1.2962.fc6xen is doing good on two hosts and all its vms (10), however its giving lot of problem on third host. when i reboots the host into latest kernel-xen the domUs become unaccessible in a while hardly run for 10 minutes, 'xm list' still shows there status but i can't access it from outside. We are using loop back files for domUs File system, for testing i rebooted host into last working kernel 2.6.20-1.2952.fc6xen and domUs into latest kernel-xen and its doing pretty good, which mean latest kernel-xen is only giving problem at host side. when running 2.6.20-1.2962 on host it giving this in /var/log/messages Jul 12 10:42:45 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:42:50 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:42:50 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:42:55 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:42:55 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:00 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:00 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:05 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:05 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:10 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:10 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:15 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:15 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:20 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:20 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:25 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:25 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:30 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:30 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:35 xxxx kernel: printk: 4 messages suppressed. Thanks. Askar

1 1

Running SLES 10 as pv guest in Fedora 7
by Felix Schwarz 14 Aug '07

14 Aug '07

Hi, I tried to run a SLES 10 installation as (pv) guest in Fedora 7 but the guest does not start. First, I installed SLES using HVM which was somewhat slow (due to Suse's graphics mode) but worked. After that I installed kernel-xen from the SLES install media. I found Gerd Hoffmann's very helpful page http://et.redhat.com/~kraxel/xen/suse-guest.html and tried to incorporate his suggestions regarding the domUloader. My current config: ----------------------------------------------------------------- name = "sles10_64_test" memory = "512" disk = [ 'tap:aio:/var/lib/xen/images/sles10_64_test,hda,w', ] vif = [ 'mac=00:16:3e:4a:f5:f0, bridge=eth0', ] vfb = [ 'type=vnc,vncunused=1' ] uuid = "b1fd65e84128ced2dc435bb9d2e1861e" bootloader="/tmp/sles-install/domUloader.py" bootentry = "hda2:/boot/vmlinuz-xen,/boot/initrd-xen" vcpus=1 on_reboot = 'restart' on_crash = 'restart' ----------------------------------------------------------------- /tmp/sles-install/domUloader.py exists and is executable, SElinux is configured as permissive. I guess something is wrong with the bootloader, from /var/log/xen/xend.log: ----------------------------------------------------------------- 2007-07-26 19:28:47 4590] DEBUG (XendDomainInfo:1463) XendDomainInfo.constructDomain [2007-07-26 19:28:47 4590] DEBUG (balloon:113) Balloon: 538932 KiB free; need 2048; done. [2007-07-26 19:28:47 4590] DEBUG (XendDomain:443) Adding Domain: 33 [2007-07-26 19:28:47 4590] DEBUG (XendDomainInfo:1517) XendDomainInfo.initDomain: 33 256 [2007-07-26 19:28:47 25532] DEBUG (XendBootloader:100) Launching bootloader as ['/tmp/sles-install/domUloader.py ', '--output=/var/run/xend/boot/xenbl.24430', '-q', '/var/lib/xen/images/sles10_64_test']. (xm command hangs, nothing happens anymore, have to kill the guest) ----------------------------------------------------------------- Did anyone manage to run SLES {9,10} as pv guest? thank you for reading :-) fs

4 7

Possible to delegate hardware to domU?
by Arik Raffael Funke 08 Aug '07

08 Aug '07

Hi, is it possible to hide hardware from dom0 and delegate it to a domU with the out-of-the-box Fedora xen? I.e. with pciback. I would like to delegate a network interface to one of my domU's. Can anybody confirm either that it is or that it is not possible? Thanks. - Arik

2 1

Any workaround available for my SCSI problem?
by Doug Eubanks 06 Aug '07

06 Aug '07

Has there been any word or workaround to the SCSI problem I reported with the xen kernel earlier this month? Thanks, Doug Eubanks

1 1

AMD Opteron Quad Core CPU Availability
by Robert L Cochran 02 Aug '07

02 Aug '07

Can anyone suggest a good retail source of AMD Opteron CPUs when the quad core versions become available? Also what would be a good motherboard for these CPUs. I assume the quad core units (all versions and price levels of them) support full virtualization. Thanks Bob Cochran Greenbelt, Maryland, USA

4 3

SElinux causes kernel bug on F7(?)
by Felix Schwarz 28 Jul '07

28 Jul '07

Hi, after upgrading my SElinux on Fedora 7 (x86_64) to selinux-policy-2.6.4-28.fc7 and selinux-policy-targeted-2.6.4-28.fc7, I can't start Xen guests anymore. Every time I do 'xm create xenguest' I get a message "invalid opcode: 0000 [2] SMP" on all consoles together with some long call traces in syslog [1]. Immediately before I updated SElinux, the guest creation failed due to losetup policy restrictions. After the update, I get "invalid opcode" messages. If I put SElinux into permissive mode, I can at least start the xen guest. I think it is the same problem as in bug 248834 [2]. So my question is: * Is it really SElinux which causes the problem? * Are there other Xen users out there which can reproduce this problem? * Is this the right list to ask this question or should I ask on the SElinux list? * How can I help to fix this problem? Thank you very much fs [1] https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=159998 [2] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248834

1 1

make config works, make menuconfig not works???
by Songtao Liu 27 Jul '07

27 Jul '07

Hi I am using Fedora6 and when I use make config, it works but make menuconfig not works. How can I fix it, to let the make menuconfig work? Thanks [root@localhost 2.6.20-1.2948.fc6-i686]# make menuconfig HOSTCC scripts/kconfig/lxdialog/checklist.o In file included from scripts/kconfig/lxdialog/checklist.c:24: scripts/kconfig/lxdialog/dialog.h:32:20: error: curses.h: No such file or directory In file included from scripts/kconfig/lxdialog/checklist.c:24: scripts/kconfig/lxdialog/dialog.h:97: error: expected specifier-qualifier-list before âchtypeâ scripts/kconfig/lxdialog/dialog.h:187: error: expected â)â before â*â token scripts/kconfig/lxdialog/dialog.h:193: error: expected â)â before â*â token scripts/kconfig/lxdialog/dialog.h:195: error: expected â)â before â*â token scripts/kconfig/lxdialog/dialog.h:196: error: expected â)â before â*â token scripts/kconfig/lxdialog/dialog.h:197: error: expected â)â before â*â token scripts/kconfig/lxdialog/dialog.h:198: error: expected â)â before â*â token scripts/kconfig/lxdialog/dialog.h:200: error: expected â)â before â*â token scripts/kconfig/lxdialog/checklist.c:31: error: expected â)â before â*â token scripts/kconfig/lxdialog/checklist.c:59: error: expected â)â before â*â token scripts/kconfig/lxdialog/checklist.c:95: error: expected â)â before â*â token scripts/kconfig/lxdialog/checklist.c: In function âdialog_checklistâ: scripts/kconfig/lxdialog/checklist.c:116: error: âWINDOWâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:116: error: (Each undeclared identifier is reported only once scripts/kconfig/lxdialog/checklist.c:116: error: for each function it appears in.) scripts/kconfig/lxdialog/checklist.c:116: error: âdialogâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:116: error: âlistâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:116: warning: left-hand operand of comma expression has no effect scripts/kconfig/lxdialog/checklist.c:129: warning: implicit declaration of function âgetmaxyâ scripts/kconfig/lxdialog/checklist.c:129: error: âstdscrâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:130: error: âKEY_MAXâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:131: warning: implicit declaration of function âgetmaxxâ scripts/kconfig/lxdialog/checklist.c:137: error: âCOLSâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:138: error: âLINESâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:140: warning: implicit declaration of function âdraw_shadowâ scripts/kconfig/lxdialog/checklist.c:142: warning: implicit declaration of function ânewwinâ scripts/kconfig/lxdialog/checklist.c:143: warning: implicit declaration of function âkeypadâ scripts/kconfig/lxdialog/checklist.c:143: error: âTRUEâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:145: warning: implicit declaration of function âdraw_boxâ scripts/kconfig/lxdialog/checklist.c:146: error: âstruct dialog_colorâ has no member named âatrâ scripts/kconfig/lxdialog/checklist.c:146: error: âstruct dialog_colorâ has no member named âatrâ scripts/kconfig/lxdialog/checklist.c:147: warning: implicit declaration of function âwattrsetâ scripts/kconfig/lxdialog/checklist.c:147: error: âstruct dialog_colorâ has no member named âatrâ scripts/kconfig/lxdialog/checklist.c:148: warning: implicit declaration of function âmvwaddchâ scripts/kconfig/lxdialog/checklist.c:150: warning: implicit declaration of function âwaddchâ scripts/kconfig/lxdialog/checklist.c:151: error: âstruct dialog_colorâ has no member named âatrâ scripts/kconfig/lxdialog/checklist.c:154: warning: implicit declaration of function âprint_titleâ scripts/kconfig/lxdialog/checklist.c:156: error: âstruct dialog_colorâ has no member named âatrâ scripts/kconfig/lxdialog/checklist.c:157: warning: implicit declaration of function âprint_autowrapâ scripts/kconfig/lxdialog/checklist.c:164: warning: implicit declaration of function âsubwinâ scripts/kconfig/lxdialog/checklist.c:171: error: âstruct dialog_colorâ has no member named âatrâ scripts/kconfig/lxdialog/checklist.c:171: error: âstruct dialog_colorâ has no member named âatrâ scripts/kconfig/lxdialog/checklist.c:189: warning: implicit declaration of function âprint_itemâ scripts/kconfig/lxdialog/checklist.c:192: warning: implicit declaration of function âprint_arrowsâ scripts/kconfig/lxdialog/checklist.c:195: warning: implicit declaration of function âprint_buttonsâ scripts/kconfig/lxdialog/checklist.c:197: warning: implicit declaration of function âwnoutrefreshâ scripts/kconfig/lxdialog/checklist.c:199: warning: implicit declaration of function âdoupdateâ scripts/kconfig/lxdialog/checklist.c:202: warning: implicit declaration of function âwgetchâ scripts/kconfig/lxdialog/checklist.c:210: error: âKEY_UPâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:210: error: âKEY_DOWNâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:220: error: âFALSEâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:221: warning: implicit declaration of function âscrollokâ scripts/kconfig/lxdialog/checklist.c:222: warning: implicit declaration of function âwscrlâ scripts/kconfig/lxdialog/checklist.c:232: warning: implicit declaration of function âwrefreshâ scripts/kconfig/lxdialog/checklist.c:293: warning: implicit declaration of function âdelwinâ scripts/kconfig/lxdialog/checklist.c:297: error: âKEY_LEFTâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:298: error: âKEY_RIGHTâ undeclared (first use in this function) scripts/kconfig/lxdialog/checklist.c:310: warning: implicit declaration of function âon_key_escâ scripts/kconfig/lxdialog/checklist.c:312: error: âKEY_RESIZEâ undeclared (first use in this function) make[1]: *** [scripts/kconfig/lxdialog/checklist.o] Error 1 make: *** [menuconfig] Error 2 [root@localhost 2.6.20-1.2948.fc6-i686]#

2 1

Kernel panic - not syncing: Attepmted to kill init!
by taoj2＠cs.rpi.edu 26 Jul '07

26 Jul '07

Hi, While I use "xm create -c guestvm" to create the domain at Fedora Core 6, the following error msg appears: Kernel panic - not syncing: Attepmted to kill init! This never happened before, when several guest domains are running with CPU usage < 5%, and I was trying to create a new one. This time, the CPU usage of the running guest domains are 25%, much higher than before, and above error msg appears while I create a new guest domain. Is this due to the reason of not enough resource can be allocated to the new domain? Any clue? Thanks. Best Angel

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen July 2007