xen August 2006

xen@lists.fedoraproject.org

49 participants
51 discussions

initscripts, xen and bonding
by Axel Thimm 04 Mar '07

04 Mar '07

Hi, I'm having a hard time getting bonding to work on FC5t3. It looks like the bond0 interface bond0 is renamed to pbond0 by xen [*] and the enslaving does not work anymore then. It works if I log on the terminal and ifenslave the devices to pbond0 instead of bond0 after the boot process has finished. But I want this to be handled automatically during reboots, so I tried assigning the bonding slaves to pbond0 as a master in the ifcfg-eth{0,1} scripts, but that doesn't work. What is causing the bond0 rename and should this renaming be considered by initscript? Is this a user error or should I file this against bugzilla? xen or initscripts? Thanks! [*] The only reference I found was a Japanese site and google's translation of it. http://translate.google.com/translate?hl=en&sl=ja&u=http://hoop.euqset.org/… -- Axel.Thimm at ATrpms.net

3 8

Simple testing results for Xen and VMX on FC5-test2.
by You, Yongkang 12 Jan '07

12 Jan '07

Hi all, I have done a simple checking for Xen and VMX on FC5-test2. Basically, I can create VMX on FC5-test2 IA32. But FC5-test2 IA32e (x86-64) doesn't provide Xen and Xen0 kernel, so didn't do Xen and VMX testing for it. Beside of testing Xen and VMX, I also found some issues about installation, which I have updated the bug #179078 as a NB. The following is the testing results only for Xen and VMX. ========================= 1. *** IA32E hasn't RPMS about Xen hypervisor and Xen0/XenU kernels. __FAIL__ 2. *** In order to boot up IA32 Xen0, I have to add pci=noacpi as the boot parameters of Xen0 kernel, or system will hang when initial PCI. I don't know if it is only related to my Machine. __FAIL__ 3. After install IA32 Xen RPMs, I can see /boot/grub/grub.conf has been changed with Xen kernels. __PASS__ 4. *** /usr/lib/xen/boot/vmxloader isn't in the RPM package, so VMX Guest couldn't be created. I suspected build system hasn't bcc, it is from DEV86 package. __FAIL__ 5. After copy a useable vmxloader to the destination, IA32 VMX Guest can be created successfully! __PASS__ 6. VMX has good network connection and Xwindows started. __PASS__ 7. XenU can be created and works well. __PASS__ 8. Couldn't get Xen Changeset by "xm info" or "xm dmesg". 9. The new kernel names of Xen/Xen0/XenU seemed a little confused. E.g. the Xen0 name is like vmlinuz-2.6.15-1.29_FC5hypervisor. I thought hypervisor is for Xen.gz. Xen0 is the Service OS. ========================== Any comments please let me know. But I will have 8 days holiday from tomorrow, so emails reply might be slow and occasional. [FYI] We are planning to do more testing for FC5-test3. Best Regards, Yongkang (Kangkang) 永康

4 4

vif not being created for domU - possible hotplug problem?
by Hilton Day 05 Sep '06

05 Sep '06

Hi, I'm running with fc5, kernel-xen0-2.6.17-1.2174. Yesterday I had a working Xen installation with a domU also running FC5, same kernel, udev, xen, libvirt, and same hardware. Following a rebuild of the host and reinstall/update of FC5 to same update levels, I'm now hitting a problem installing a domU, where it appears its not setting up a bridged interface for the domU. I think it might be hotplug related? I've got the same udev, and its running, and I can see the rules files in /etc/udev/rules.d. Below is the output of several logs and commands.. as far as I can see, the network-bridge script is good, and its set up my interfaces correctly. One minor complication is that my bridged ethernet card is on device eth2, but I've got the amendment in xend-config.sxp to call "(network-script 'network-bridge netdev=eth2')". I checked the kernel-xen list in bugzilla but couldn't find anything there on hotplug problems. Any help in figuring out the root cause would be much appreciated! Having gone from working to not-working in a reinstall of the same setup has me very confused. #### brctl show #### bridge name bridge id STP enabled interfaces xenbr2 8000.feffffffffff no peth2 vif0.2 #### ifconfig #### eth2 Link encap:Ethernet HWaddr 00:14:6C:8C:2E:25 inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::214:6cff:fe8c:2e25/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:353 errors:0 dropped:0 overruns:0 frame:0 TX packets:396 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:42427 (41.4 KiB) TX bytes:97320 (95.0 KiB) 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:660 errors:0 dropped:0 overruns:0 frame:0 TX packets:660 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3375221 (3.2 MiB) TX bytes:3375221 (3.2 MiB) peth2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:362 errors:0 dropped:0 overruns:0 frame:0 TX packets:457 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:43683 (42.6 KiB) TX bytes:104598 (102.1 KiB) Interrupt:18 vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:396 errors:0 dropped:0 overruns:0 frame:0 TX packets:354 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:97320 (95.0 KiB) TX bytes:42517 (41.5 KiB) xenbr2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:62 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9920 (9.6 KiB) TX bytes:468 (468.0 b) #### /var/log/xen-hotplug.log #### interface vif1.0 does not exist! #### /var/log/xend.log #### [2006-08-30 11:17:25 xend] INFO (SrvDaemon:283) Xend Daemon started [2006-08-30 11:17:25 xend] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-08-30 11:17:25 xend.XendDomainInfo] DEBUG (XendDomainInfo:207) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 10867218609L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 961860, 'maxmem_kb': -4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-08-30 11:17:25 xend.XendDomainInfo] INFO (XendDomainInfo:219) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-08-30 11:17:25 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm path in store for existing domain 0 [2006-08-30 11:17:25 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing VM details: {'name': 'Domain-0', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '940', 'maxmem': '940'} [2006-08-30 11:17:25 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '962560', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-08-30 11:17:25 xend] DEBUG (XendDomain:153) number of vcpus to use is 0 [2006-08-30 11:17:25 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch [2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:185) XendDomainInfo.create(['vm', ['name', 'xen-www'], ['memory', '256'], ['maxmem', '256'], ['vcpus', '1'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux', ['kernel', '/var/lib/xen/vmlinuz.1WDQ9c'], ['ramdisk', '/var/lib/xen/initrd.img.jBbqHv'], ['args', ' root=/dev/xvd method=ftp://virtual/pub ']]], ['device', ['vbd', ['dev', '/dev/xvda'], ['uname', 'file:/dev/raid/xen_www'], ['mode', 'w']]], ['device', ['vif', ['mac', '00:16:3e:11:48:67'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge']]]]) [2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:291) parseConfig: config is ['vm', ['name', 'xen-www'], ['memory', '256'], ['maxmem', '256'], ['vcpus', '1'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['linux', ['kernel', '/var/lib/xen/vmlinuz.1WDQ9c'], ['ramdisk', '/var/lib/xen/initrd.img.jBbqHv'], ['args', ' root=/dev/xvd method=ftp://virtual/pub ']]], ['device', ['vbd', ['dev', '/dev/xvda'], ['uname', 'file:/dev/raid/xen_www'], ['mode', 'w']]], ['device', ['vif', ['mac', '00:16:3e:11:48:67'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge']]]] [2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:390) parseConfig: result is {'uuid': None, 'on_crash': 'destroy', 'on_reboot': 'destroy', 'image': ['linux', ['kernel', '/var/lib/xen/vmlinuz.1WDQ9c'], ['ramdisk', '/var/lib/xen/initrd.img.jBbqHv'], ['args', ' root=/dev/xvd method=ftp://virtual/pub ']], 'on_poweroff': 'destroy', 'bootloader_args': None, 'cpus': None, 'name': 'xen-www', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 256, 'device': [('vbd', ['vbd', ['dev', '/dev/xvda'], ['uname', 'file:/dev/raid/xen_www'], ['mode', 'w']]), ('vif', ['vif', ['mac', '00:16:3e:11:48:67'], ['bridge', 'xenbr0'], ['script', '/etc/xen/scripts/vif-bridge']])], 'bootloader': None, 'cpu': None, 'maxmem': 256} [2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:1216) XendDomainInfo.construct: None [2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:1248) XendDomainInfo.initDomain: 1 1.0 [2006-08-30 11:22:23 xend] DEBUG (balloon:134) Balloon: free 62; need 257; retries: 10. [2006-08-30 11:22:23 xend] DEBUG (balloon:143) Balloon: setting dom0 target to 745. [2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:987) Setting memory target of domain Domain-0 (0) to 745 MiB. [2006-08-30 11:22:23 xend] DEBUG (balloon:128) Balloon: free 257; need 257; done. [2006-08-30 11:22:23 xend] INFO (image:134) buildDomain os=linux dom=1 vcpus=1 [2006-08-30 11:22:23 xend] DEBUG (image:177) dom = 1 [2006-08-30 11:22:23 xend] DEBUG (image:178) image = /var/lib/xen/vmlinuz.1WDQ9c [2006-08-30 11:22:23 xend] DEBUG (image:179) store_evtchn = 1 [2006-08-30 11:22:23 xend] DEBUG (image:180) console_evtchn = 2 [2006-08-30 11:22:23 xend] DEBUG (image:181) cmdline = root=/dev/xvd method=ftp://virtual/pub [2006-08-30 11:22:23 xend] DEBUG (image:182) ramdisk = /var/lib/xen/initrd.img.jBbqHv [2006-08-30 11:22:23 xend] DEBUG (image:183) vcpus = 1 [2006-08-30 11:22:23 xend] DEBUG (image:184) features = [2006-08-30 11:22:23 xend] DEBUG (blkif:24) exception looking up device number for /dev/xvda: [Errno 2] No such file or directory: '/dev/xvda' [2006-08-30 11:22:23 xend] DEBUG (DevController:110) DevController: writing {'virtual-device': '51712', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/51712'} to /local/domain/1/device/vbd/51712. [2006-08-30 11:22:23 xend] DEBUG (DevController:112) DevController: writing {'domain': 'xen-www', 'frontend': '/local/domain/1/device/vbd/51712', 'dev': '/dev/xvda', 'state': '1', 'params': '/dev/raid/xen_www', 'mode': 'w', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/51712. [2006-08-30 11:22:23 xend] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:11:48:67', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. [2006-08-30 11:22:23 xend] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'xen-www', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/1/device/vif/0', 'mac': '00:16:3e:11:48:67', 'frontend-id': '1'} to /local/domain/0/backend/vif/1/0. [2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing VM details: {'uuid': '5b6415d8-f3a6-d64b-67c8-d8f7afb98e95', 'on_reboot': 'destroy', 'start_time': '1156900943.67', 'on_poweroff': 'destroy', 'name': 'xen-www', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'destroy', 'image': "(linux (kernel /var/lib/xen/vmlinuz.1WDQ9c) (ramdisk /var/lib/xen/initrd.img.jBbqHv) (args ' root=/dev/xvd method=ftp://virtual/pub '))", 'maxmem': '256'} [2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'console/ring-ref': '237071', 'console/port': '2', 'name': 'xen-www', 'console/limit': '1048576', 'vm': '/vm/5b6415d8-f3a6-d64b-67c8-d8f7afb98e95', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '237072', 'store/port': '1'} [2006-08-30 11:22:23 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch [2006-08-30 11:22:23 xend] DEBUG (DevController:143) Waiting for devices vif. [2006-08-30 11:22:23 xend] DEBUG (DevController:149) Waiting for 0. [2006-08-30 11:22:23 xend] DEBUG (DevController:449) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2006-08-30 11:22:23 xend] DEBUG (DevController:449) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2006-08-30 11:22:23 xend] DEBUG (DevController:463) hotplugStatusCallback 2. [2006-08-30 11:22:23 xend] ERROR (SrvBase:87) Request wait_for_devices failed. Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85, in perform return op_method(op, req) File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomain.py", line 72, in op_wait_for_devices return self.dom.waitForDevices() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1511, in waitForDevices self.waitForDevices_(c) File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1063, in waitForDevices_ return self.getDeviceController(deviceClass).waitForDevices() File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", line 145, in waitForDevices return map(self.waitForDevice, self.deviceIDs()) File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", line 161, in waitForDevice raise VmError("Device %s (%s) could not be connected. " VmError: Device 0 (vif) could not be connected. Backend device not found. [2006-08-30 11:22:24 xend] INFO (XendDomain:365) Domain xen-www (1) unpaused. #### /var/log/messages #### Aug 30 11:17:26 virtual kernel: Bridge firewalling registered Aug 30 11:17:26 virtual kernel: device vif0.2 entered promiscuous mode Aug 30 11:17:26 virtual NET[2453]: /sbin/dhclient-script : updated /etc/resolv.conf Aug 30 11:17:26 virtual kernel: audit(1156900646.201:3): dev=vif0.2 prom=256 old_prom=0 auid=4294967295 Aug 30 11:17:26 virtual kernel: xenbr2: port 1(vif0.2) entering learning state Aug 30 11:17:26 virtual dhclient: bound to 192.168.0.10 -- renewal in 43167 seconds. Aug 30 11:17:26 virtual kernel: xenbr2: topology change detected, propagating Aug 30 11:17:26 virtual kernel: xenbr2: port 1(vif0.2) entering forwarding state Aug 30 11:17:26 virtual kernel: r8169: peth2: link up Aug 30 11:17:26 virtual kernel: device peth2 entered promiscuous mode Aug 30 11:17:26 virtual kernel: audit(1156900646.249:4): dev=peth2 prom=256 old_prom=0 auid=4294967295 Aug 30 11:17:26 virtual kernel: xenbr2: port 2(peth2) entering learning state Aug 30 11:17:26 virtual kernel: xenbr2: topology change detected, propagating Aug 30 11:17:26 virtual kernel: xenbr2: port 2(peth2) entering forwarding state Aug 30 11:20:37 virtual ntpd[2004]: synchronized to LOCAL(0), stratum 10 Aug 30 11:20:37 virtual ntpd[2004]: kernel time sync disabled 0041 Aug 30 11:21:40 virtual ntpd[2004]: kernel time sync enabled 0001 Aug 30 11:22:23 virtual logger: /etc/xen/scripts/vif-bridge: brctl addif xenbr0 vif1.0 failed Aug 30 11:22:46 virtual ntpd[2004]: synchronized to 192.231.203.132, stratum 2

2 2

Re: [Fedora-xen] Experiencing boot problems with xen3
by Paul Larson 31 Aug '06

31 Aug '06

On Thursday 31 August 2006 13:05, you wrote: > Eric Benton wrote: > > Paul Larson wrote: > >> On Thursday 31 August 2006 09:00, you wrote: > >>> Yes thank you, > >>> I did that, but when booting the xen kernel it paniced, now I'm trying > >>> to build Xen with VT support -> any suggestions on that? > >> > >> What was the panic? I noticed that you aren't including an initrd. > >> Depending on what kind of panic you got, that may be the source of > >> your problem (not compiling some things in that needed to be there, > >> and not including initrd). > >> > >> With Fedora, you're probably better off biting the bullet and just > >> always building an initrd for it. It'll likely save you a lot of > >> headaches later. > >> > >> -Paul Larson > > > > Hi Paul, > > I did what you said and I'm currently writing this email after > > successfully booting from the xen kernel. > > > > Thanks for your help! > > Eric. > > Hi Again, > > During boot time (which succeeds at the end) there are couple of errors: > 1. auditd fails to start > 2. a lot of python import errors are shown from the xen site package > > Do you know what might cause those errors please? I haven't seen that with FC6-test2 or rawhide, though I haven't looked at Rawhide in a while. What are you testing on, and what changes did you make when you rebuilt xen? -Paul Larson

1 0

Experiencing boot problems with xen3
by Eric Benton 31 Aug '06

31 Aug '06

Hi, I'm trying to install xen3 over a FC5 linux system. I had downloaded xen3 sources and built them with the following commands: make world make install Then, I added the following lines to grub.conf - title Xen 3.0 root (hd0,3) kernel /boot/xen-3.0.gz dom0_mem=262144 module /boot/vmlinuz-2.6-xen0 root=/dev/sda4 ro console=tty0 But I'm getting Error 15: file not found when trying to boot. I saw that other people got this error as well but I couldn't resolved it... Please advise me on how to solve this problem, I attached grub.conf, the output of mount and the dirlist of the /boot directory. Thanks in advanced, Eric. total 16252 drwxr-xr-x 3 root root 4096 Aug 31 10:18 . drwxr-xr-x 23 root root 4096 Aug 31 12:30 .. -rw-r--r-- 1 root root 63847 Mar 14 23:19 config-2.6.15-1.2054_FC5smp -rw-rw-r-- 1 root root 60474 Aug 31 10:18 config-2.6.16.13-xen -rw-r--r-- 1 root root 66118 Aug 8 23:27 config-2.6.17-1.2174_FC5smp drwxr-xr-x 2 root root 4096 Aug 31 12:12 grub -rw-r--r-- 1 root root 1022815 Aug 30 02:50 initrd-2.6.15-1.2054_FC5smp.img -rw-r--r-- 1 root root 1044087 Aug 31 02:39 initrd-2.6.17-1.2174_FC5smp.img -rw-r--r-- 1 root root 831559 Mar 14 23:19 System.map-2.6.15-1.2054_FC5smp -rw-rw-r-- 1 root root 726886 Aug 31 10:18 System.map-2.6.16.13-xen -rw-r--r-- 1 root root 852903 Aug 8 23:27 System.map-2.6.17-1.2174_FC5smp -rw-r--r-- 1 root root 4131330 Aug 31 10:18 vmlinux-syms-2.6.16.13-xen -rw-r--r-- 1 root root 1564844 Mar 14 23:19 vmlinuz-2.6.15-1.2054_FC5smp -rw-r--r-- 1 root root 1534498 Aug 31 10:18 vmlinuz-2.6.16.13-xen lrwxrwxrwx 1 root root 21 Aug 31 10:18 vmlinuz-2.6.16-xen -> vmlinuz-2.6.16.13-xen -rw-r--r-- 1 root root 1803745 Aug 8 23:27 vmlinuz-2.6.17-1.2174_FC5smp lrwxrwxrwx 1 root root 21 Aug 31 10:18 vmlinuz-2.6-xen -> vmlinuz-2.6.16.13-xen -rw-r--r-- 1 root root 223175 Aug 31 10:13 xen-3.0.2-3.gz lrwxrwxrwx 1 root root 14 Aug 31 10:13 xen-3.0.gz -> xen-3.0.2-3.gz lrwxrwxrwx 1 root root 14 Aug 31 10:13 xen-3.gz -> xen-3.0.2-3.gz lrwxrwxrwx 1 root root 14 Aug 31 10:13 xen.gz -> xen-3.0.2-3.gz -rw-r--r-- 1 root root 2586399 Aug 31 10:13 xen-syms-3.0.2-3 /dev/sda4 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda6 on /mnt/win-e type ntfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) automount(pid2157) on /net type autofs (rw,fd=4,pgrp=2157,minproto=2,maxproto=4) # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,3) # kernel /boot/vmlinuz-version ro root=/dev/sda4 # initrd /boot/initrd-version.img #boot=/dev/sda default=2 timeout=10 splashimage=(hd0,3)/boot/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.17-1.2174_FC5smp) root (hd0,3) kernel /boot/vmlinuz-2.6.17-1.2174_FC5smp ro root=LABEL=/ rhgb quiet initrd /boot/initrd-2.6.17-1.2174_FC5smp.img title Xen 3.0 / XenLinux 2.6 root (hd0,3) kernel /boot/xen-3.0.gz dom0_mem=262144 module /boot/vmlinuz-2.6-xen0 root=LABEL=/ ro console=tty0 #title Fedora Core (2.6.15-1.2054_FC5smp) # root (hd0,3) # kernel /boot/vmlinuz-2.6.15-1.2054_FC5smp ro root=LABEL=/ rhgb quiet # initrd /boot/initrd-2.6.15-1.2054_FC5smp.img title Windows XP rootnoverify (hd0,0) chainloader +1

2 1

xenguest-install problem with 08/28 build
by Mark Wisner 30 Aug '06

30 Aug '06

I am seeing the following failure while doing a xenguest-install. **************************************************** What is the name of your virtual machine? vm1 How much RAM should be allocated (in megabytes)? 512 What would you like to use as the disk (path)? /var/xen/vm1/hda How large would you like the disk to be (in gigabytes)? 5 What is the install location? http://porkchop.redhat.com/nightly/rawhide-latest/tree-i386/ Starting install... libvir: Xen Daemon error : GET operation failed: No such domain vm1 libvir: Xen Daemon error : POST operation failed: No such domain vm1 Failed to get devices for domain vm1 Traceback (most recent call last): File "/usr/sbin/xenguest-install", line 237, in ? main() File "/usr/sbin/xenguest-install", line 229, in main r = guest.start_install(True) File "/usr/lib/python2.4/site-packages/xeninst/ParaVirtGuest.py", line 183, in start_install self.domain = conn.createLinux(cxml, 0) File "/usr/lib/python2.4/site-packages/libvirt.py", line 249, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed') libvirt.libvirtError: virDomainCreateLinux() failed *********************************************************** I did a clean install with the 08/28 build. Kernel is 2.6.17-1.2586.fc6xen. I am running on an IBM x335 with 1.5 GB or Ram and a 32GB SCSI drive. I also see a failure while running virt-manager but that could be a user problem. I am still investigating it. Mark K. Wisner Advisory Software Engineer IBM Linux Technology Center 3039 Cornwallis Rd RTP, NC 27709 Tel. 919-754-4274 Cell 919-649-5813

6 6

UPS on ttyS0 in dom0
by Kanwar Ranbir Sandhu 30 Aug '06

30 Aug '06

Hello All, This is my first post to the fedora-xen list. I've been on the xen-users list for a few months now. Up until this weekend, I was using xen on a RHEL 4 box to run 3 CentOS 4 domUs. I'm now running xen on a FC5 dom0. I had some problems during the transition, one of which was really odd. But, I got that fixed now, so I'm happy - mostly. My main reason for switching over to FC5 was so that I could use the separate xen0 and xenU kernels (didn't want to compile my own). I needed the separate kernels in order to monitor my UPS, which is connected to the external serial port (the serial port is disabled in the xensource kernel RPM). However, the damn thing still doesn't work - I'm completely baffled. Here's my current kernel config for dom0: title Fedora Core (2.6.17-1.2174_FC5xen0) root (hd0,0) kernel /xen.gz-2.6.17-1.2174_FC5 module /vmlinuz-2.6.17-1.2174_FC5xen0 ro root=/dev/vg00/root xencons=tty module /initrd-2.6.17-1.2174_FC5xen0.img That gives me this crap out: kernel: WARNING: Failed to register Xen virtual console driver as 'tty1' Very nice. I thought that maybe I had to disable tty1 in /etc/inittab, so I did, but the error remained. Hoping for the best, I tried accessing the UPS anyway, and I was handed more turd on a stick: Sun Aug 20 18:59:33 EDT 2006 apcupsd FATAL ERROR in smartsetup.c at line 61 Cannot open UPS port /dev/ttyS0: No such device or address Sun Aug 20 18:59:33 EDT 2006 apcupsd error shutdown completed Perfect. So, I switch xencons=tty to xencons=off, but the result is the same. Using console=vga on the xen line didn't help either. Incidentally, ttyS0 _does_ exist: [root@xenmaster src]# ls -l /dev/ttyS0 crw------- 1 root root 4, 64 Aug 21 06:05 /dev/ttyS0 Does anyone have any ideas? Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2142_FC4 i686 GNU/Linux 15:56:37 up 2 days, 9:26, 3 users, load average: 0.42, 0.52, 0.46

2 3

domu sftp to dom0 reboots system.....
by Tom Bishop 28 Aug '06

28 Aug '06

Have discovered using the 64bit version of fc5xen (2.6.17-1.2174_FC5xen0), when you sftp from one dom to another it reboots the whole box. SSH appears to work just fine, was wondering if this is something anyone has seen or is unique to me, thanks.

1 0

FC5--Xen3.0.2--dom0 and domU iptables, communication
by dgreen＠CLEMSON.EDU 27 Aug '06

27 Aug '06

Situation: Running a simple UDP client/server program where the client on one domU on one computer sends echo packets to another domU on another computer, server sends echoes back. They do this on a specified port (will use any port between 5000-6000). This program works on non-Xen machines in various environments, Linux and Solaris. Program just hangs on the domUs. I believe I need help with my ports to allow connections and UDP/TCP packets to go through ports 5000-6000. -------------------------------------------- My environment: (machine1) domU 10.0.0.1 <-> (machine1) dom0 172.16.48.252 <-> (machine2) dom0 172.16.48.253 <-> (machine1) domU 10.0.1.1 dom0s -- FC5 (2.6.17-1.2157_FC5xen0, using 512MB RAM) domUs -- FC5 (2.6.17-1.2157_FC5xen0, using 256MB RAM) -NAT scripts (network-nat, vif-nat) are used on bootup -can ping and ssh between dom0 and domUs (on both machines) -I have disabled selinux and firewall ------------------------------------------------- My routing table on (machine1) dom0: Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 vif1.0 10.0.1.0 172.16.48.253 255.255.255.0 UG 0 0 0 eth0 172.16.48.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 172.16.48.1 0.0.0.0 UG 0 0 0 eth0 ------------------------------------------------- My routing table on (machine1) domU: Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 eth0 ------------------------------------------------- 'iptables -L' on (machine1) dom0: Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- 10.0.0.1 anywhere PHYSDEV match --physdev-in vif1.0 ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif1.0 udp spt:bootpc dpt:bootps Chain OUTPUT (policy ACCEPT) target prot opt source destination ------------------------------------------------ 'iptables -L' on (machine1) domU: Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT tcp -- anywhere anywhere tcp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh REJECT all -- anywhere anywhere reject-with icmp-host-prohibited ----------------------------------- Would like domU on machine1 to have the ability to use tcp/udp over ports 5000-6000 with domU on machine2. Sorry if the columns aren't aligned. Any help sent, thanks in advance. Vince

1 0

FC5/xen/iptables kernel panic -- further testing
by master＠bradleyland.com 26 Aug '06

26 Aug '06

The current rpms of kernel 2.6.17-1.2174_FC5xen0 and xen-3.0.2-3.FC5 seem to have a problem. If I use shorewall to create a set of iptables rules and xend is running, I get a kernel panic whenever network IO occurs, usually within seconds. If I shut xend down, no panic. As an experiment, I installed the fc6 kernel -- 2.6.17-1.2517.fc6xen as well as the somewhat later fc6 kernel and the problem was solved. However, due to the mismatch between the kernel and xen (and the fact this is an fc5 system), no guests will start. They crash right when init should be starting. So, somewhere between the 2174 and 2517 kernel versions, this bug was fixed but is not available as an fc5 rpm set. Hence, there doesn't seem to be a working fc5/xen/iptables combo available. Or maybe there is something else wrong on the system. Given the 2517 kernel solved the problem, this seems unlikely. Does anyone have any information on when/if this fix will be backported into fc5? As of now, I'm stuck. I can either run xen and no iptables, or no xen and have a firewall. I played around trying to get a later rpm version of xen installed, but there were just too many dependencies. I need the 2.6.17 kernel for the improved raid5 support. Thanks, Dave

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen August 2006