From xlot at onlinewarrior.com Fri Sep 1 14:46:43 2006 From: xlot at onlinewarrior.com (Hilton Day) Date: Sat, 02 Sep 2006 00:46:43 +1000 Subject: [Fedora-xen] PAE confusion using FC5 kernel-xen - is it PAE or not? Message-ID: <44F847D3.9020701@onlinewarrior.com> Hi, I've been playing around with FC5 and Xen, using kernel-xen0 and kernel-xenU for dom0 and domU's respectively.. Unfortunately I hit a snag in that I can't get pci pass-through for ethernet cards to a xenU kernel as there's no support for ethernet card drivers.. so I had a look at the new kernel-xen. And I've hit a confusing snag, to do with PAE where I get conflicting messages in xend-debug.log. Two scenarios give different PAE messages: Scenario 1: dom0: kernel-xen-2.6.17-1.2174 domU: kernel-xen-2.6.17-1.2174 This gives the xend-debug.log messages: ERROR: Non PAE-kernel on PAE host. ERROR: Error constructing guest OS Which I thought was odd, as they're the same kernel? So I tried switching dom0 back to a non-PAE kernel build.. xen0 Scenario 2: dom0: kernel-xen0-2.6.17-1.2174 domU: kernel-xen-2.6.17-1.2174 However, when I try to "xm create" the domU this gives me: ERROR: PAE-kernel on non-PAE host. ERROR: Error constructing guest OS So my confusion is that I'm being told that kernel-xen is a PAE kernel by the debug, *and* that its a non-PAE kernel by the debug. I'd have thought that scenario 1 above would work. I checked the files in kernel-xenU and kernel-xen with an "rpm -ql", and can't see any conflicts in /boot - they have separate filenames for config, initrd, system.map, vmlinuz kernel etc. Anyone have any idea whats up here, and how I can get kernel-xen to boot on the DomU so I can get the pass-through working? (I want to set up one of the domU's as a gateway/proxy/firewall for the others) I can't use FC6 currently - it has no support for combined software RAID5/LVM2 setups which is what I'm running for dom0. My grub.conf on the domU is: #boot=/dev/xvda default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.17-1.2174_FC5xen) root (hd0,0) kernel /vmlinuz-2.6.17-1.2174_FC5xen ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.17-1.2174_FC5xen.img title Fedora Core (2.6.17-1.2174_FC5xenU) root (hd0,0) kernel /vmlinuz-2.6.17-1.2174_FC5xenU ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.17-1.2174_FC5xenU.img title Fedora Core (2.6.15-1.2054_FC5xenU) root (hd0,0) kernel /vmlinuz-2.6.15-1.2054_FC5xenU ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.15-1.2054_FC5xenU.img -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3295 bytes Desc: S/MIME Cryptographic Signature URL: From benton71 at gmail.com Sat Sep 2 13:59:21 2006 From: benton71 at gmail.com (Eric Benton) Date: Sat, 02 Sep 2006 16:59:21 +0300 Subject: [Fedora-xen] cdrom cannot be found in xen0 Message-ID: <44F98E39.8070006@gmail.com> I'd compiled the sources of xen3 unstable and booted successfuly into xen0, where xend is working and everything is ok. The only problem is, I can't find my cdrom under /dev. I'm running FC5 and when not at xen0, my cdrom is at /dev/hdc Is it something related to udev? or the initrd? Thanks in advance, Eric. From mike at mommabears.com Sun Sep 3 00:57:05 2006 From: mike at mommabears.com (MJang) Date: Sat, 02 Sep 2006 17:57:05 -0700 Subject: [Fedora-xen] Xen VT Notebooks Message-ID: <1157245026.5240.11.camel@localhost> Folks, Hoping for advice on notebooks suited to Xen. If you've had success enabling VT, what notebook model are you using? I've asked on the Xen mailing list as well - am considering a new notebook, and have heard that HP has disabled VT on all of their Dual Core and AMD X2 TL-50 (and above) notebooks. I know, I know, avoid the T2300E (and below), the Core 2 Duo T5500, and anything less than TL-50. I gather from some messages that some notebooks allow end-users to enable it via the BIOS, others (namely HP) do not. Don't know if that's true, but HP pre-sales support says that they don't have any documentation on the issue. So much for HP sales . . . Still awaiting a reply from Dell. Thanks, Mike From samfw at redhat.com Tue Sep 5 15:26:19 2006 From: samfw at redhat.com (Sam Folk-Williams) Date: Tue, 05 Sep 2006 11:26:19 -0400 Subject: [Fedora-xen] vif not being created for domU - [Solved] In-Reply-To: <44F50508.1070805@onlinewarrior.com> References: <44F4F64A.5040208@onlinewarrior.com> <44F50508.1070805@onlinewarrior.com> Message-ID: <1157469979.4457.45.camel@samfw.rdu.redhat.com> On Wed, 2006-08-30 at 13:24 +1000, Hilton Day wrote: > After some reading, it appears the problem is that the bridge device > gets named differently than expected by the xenguest-install.py script. > I filed a BZ on this: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=205148 Thanks, Sam > The bridge interface created by the network-bridge script was called > "xenbr2", as it was bridging device eth2. > > Changing my xend-config.sxp to force the name of the bridge device to be > "xenbr0" enabled the domU to access the bridge device and get an address > via dhcp. The change made was to alter the line that calls the bridge > script in xend-config.sxp to be: > > (network-script 'network-bridge netdev=eth2 bridge=xenbr0') > > Looks like the xenguest-install.py is hardcoded with the bridge device > on line 174: > > vif = [ 'type=ioemu,bridge=xenbr0,mac=%(mac)s' ] > > Hilton. > > Hilton Day wrote: > > 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 > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Sam Folk-Williams, RHCE Red Hat Global Support Services Phone: 919/754-4558 GPG ID: 1B0D46BA -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From katzj at redhat.com Wed Sep 6 12:42:21 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 06 Sep 2006 08:42:21 -0400 Subject: [Fedora-xen] Re: rawhide report: 20060906 changes In-Reply-To: <200609061051.k86Ap6Ks009977@hs20-bc2-6.build.redhat.com> References: <200609061051.k86Ap6Ks009977@hs20-bc2-6.build.redhat.com> Message-ID: <1157546541.25608.32.camel@aglarond.local> On Wed, 2006-09-06 at 06:51 -0400, buildsys at redhat.com wrote: > xen-3.0.2-33 > ------------ > * Tue Sep 05 2006 Jeremy Katz - 3.0.2-33 > - update pvfb patch based on upstream feedback Heads up that this also requires the 2627 kernel in guests using the paravirt framebuffer. The last round of upstream review had some minor protocol changes, but hopefully those are all behind us now. Unfortunately, the kernel build finished at 4:02 am (the rawhide compose starts at 4 am). So for now, I've put the previous tools package (-32) at http://people.redhat.com/~katzj/xen/ Jeremy From thomas.vonsteiger at bluewin.ch Wed Sep 6 15:36:00 2006 From: thomas.vonsteiger at bluewin.ch (thomas.vonsteiger at bluewin.ch) Date: Wed, 6 Sep 2006 17:36:00 +0200 Subject: [Fedora-xen] interface tun0 does not exist! Message-ID: <005101c6d1ca$27dfb890$0401a8c0@athlon> Hello, I can not setup any guest's becose of missing interfaces. /var/log/xend-debug.log: Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the loopback driver supports. If the loopback driver is a module, you may raise this limit by passing it as a parameter (nloopbacks=); if the driver is compiled statically into the kernel, then you may set the parameter using loopback.nloopbacks= on the domain 0 kernel command line. interface tun0 does not exist! interface tun0 does not exist! interface tun0 does not exist! interface tun0 does not exist! >From dmesg: bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex bnx2: eth2 NIC Link is Up, 1000 Mbps full duplex bnx2: eth3 NIC Link is Up, 1000 Mbps full duplex /etc/grub.conf: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/fcvg/slash # initrd /initrd-version.img #boot=/dev/cciss/c0d0 default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu title Fedora Core (2.6.17-1.2174_FC5xen) root (hd0,0) kernel /xen.gz-2.6.17-1.2174_FC5-PAE dom0_mem=512000 loopback.nloopbacks=128 module /vmlinuz-2.6.17-1.2174_FC5xen ro root=/dev/fcvg/slash module /initrd-2.6.17-1.2174_FC5xen.img title Fedora Core (2.6.17-1.2174_FC5smp) root (hd0,0) kernel /vmlinuz-2.6.17-1.2174_FC5smp ro root=/dev/fcvg/slash initrd /initrd-2.6.17-1.2174_FC5smp.img title Fedora Core 5 (2.6.15-1.2054_FC5smp) root (hd0,0) kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=/dev/fcvg/slash initrd /initrd-2.6.15-1.2054_FC5smp.img Hardware: HP DL380 G5, 16G memory, 4 nic's from type bnx2, eth0 - eth3 are all there. ifconfig -a prints eth0,eth1,eth2,eth3,lo With kernel parameter "loopback.nloopbacks=128" i have the same problem. Again with loopback.nloopbacks= .32,48,128,164,256. always no tun0 or xenbr0. What can be wrong here ? Many thanks for any help. Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.vonsteiger at bluewin.ch Wed Sep 6 16:20:22 2006 From: thomas.vonsteiger at bluewin.ch (thomas.vonsteiger at bluewin.ch) Date: Wed, 6 Sep 2006 18:20:22 +0200 Subject: AW: [Fedora-xen] interface tun0 does not exist! -> HALF SOLVED In-Reply-To: <005101c6d1ca$27dfb890$0401a8c0@athlon> Message-ID: <006801c6d1d0$5a4e9520$0401a8c0@athlon> Hello again, I found the problem..stubid.. I have installed kernel-xen With kernel-xen0 the interface are there. Becose then I can use only 4Gb memory. What can I to now do use 16G of memory ? Thomas _____ Von: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Im Auftrag von thomas.vonsteiger at bluewin.ch Gesendet: Mittwoch, 6. September 2006 17:36 An: fedora-xen at redhat.com Betreff: [Fedora-xen] interface tun0 does not exist! Hello, I can not setup any guest's becose of missing interfaces. /var/log/xend-debug.log: Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the loopback driver supports. If the loopback driver is a module, you may raise this limit by passing it as a parameter (nloopbacks=); if the driver is compiled statically into the kernel, then you may set the parameter using loopback.nloopbacks= on the domain 0 kernel command line. interface tun0 does not exist! interface tun0 does not exist! interface tun0 does not exist! interface tun0 does not exist! >From dmesg: bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex bnx2: eth2 NIC Link is Up, 1000 Mbps full duplex bnx2: eth3 NIC Link is Up, 1000 Mbps full duplex /etc/grub.conf: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/fcvg/slash # initrd /initrd-version.img #boot=/dev/cciss/c0d0 default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu title Fedora Core (2.6.17-1.2174_FC5xen) root (hd0,0) kernel /xen.gz-2.6.17-1.2174_FC5-PAE dom0_mem=512000 loopback.nloopbacks=128 module /vmlinuz-2.6.17-1.2174_FC5xen ro root=/dev/fcvg/slash module /initrd-2.6.17-1.2174_FC5xen.img title Fedora Core (2.6.17-1.2174_FC5smp) root (hd0,0) kernel /vmlinuz-2.6.17-1.2174_FC5smp ro root=/dev/fcvg/slash initrd /initrd-2.6.17-1.2174_FC5smp.img title Fedora Core 5 (2.6.15-1.2054_FC5smp) root (hd0,0) kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=/dev/fcvg/slash initrd /initrd-2.6.15-1.2054_FC5smp.img Hardware: HP DL380 G5, 16G memory, 4 nic's from type bnx2, eth0 - eth3 are all there. ifconfig -a prints eth0,eth1,eth2,eth3,lo With kernel parameter "loopback.nloopbacks=128" i have the same problem. Again with loopback.nloopbacks= .32,48,128,164,256. always no tun0 or xenbr0. What can be wrong here ? Many thanks for any help. Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.vonsteiger at bluewin.ch Fri Sep 8 04:57:50 2006 From: thomas.vonsteiger at bluewin.ch (thomas.vonsteiger at bluewin.ch) Date: Fri, 8 Sep 2006 06:57:50 +0200 Subject: [Fedora-xen] multiple nic's with vlan -> bridge or bridge -> vlan Message-ID: <005d01c6d303$562cb150$0401a8c0@athlon> Hello, Whats the experience with multiple nic's and vlan's/bridge's for xen guests ? Is it better to build network configs for xen guest's with: eth0 - vlan's - bridge's - domU's eth1 - vlan's - bridge's - domU's or eth0 - bridge - vlan's -domU's eth1 - bridge - vlan's -domU's regards, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From dansgan at yahoo.it Fri Sep 8 11:57:43 2006 From: dansgan at yahoo.it (Daniele Sgandurra) Date: Fri, 8 Sep 2006 13:57:43 +0200 (CEST) Subject: [Fedora-xen] Exception when starting xend: error while reading /vm/00000000-0000-0000-0000-000000000000/ssidref Message-ID: <20060908115743.63359.qmail@web27904.mail.ukl.yahoo.com> I've been using Xen for 3 months, but now I've problems when starting xend: I'm using Fedora 5 with Xen installed from binaries (I have also tried with compiled versions but it doesn't work either): $ uname -a Linux localhost.localdomain 2.6.16-xen #1 SMP Mon Jul 3 18:18:42 CEST 2006 i686 i686 i386 GNU/Linux $ python -V Python 2.4.3 # xend start # xm list Error: Error connecting to xend: No such file or directory. Is xend running? This is the output from /var/log/xend.log: -------------------------------------------- [2006-09-08 13:42:05 xend] INFO (SrvDaemon:278) Xend Daemon started [2006-09-08 13:42:05 xend] INFO (SrvDaemon:282) Xend changeset: Thu Apr 13 15:18:37 2006 +0100 9617:5802713c159b. [2006-09-08 13:42:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:200) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 30441112756L, 'ssidref': 65537, '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': 429056, 'maxmem_kb': -4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-09-08 13:42:05 xend.XendDomainInfo] INFO (XendDomainInfo:212) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-09-08 13:42:05 xend.XendDomainInfo] WARNING (XendDomainInfo:234) (5, 'Input/output error, while reading /vm/00000000-0000-0000-0000-000000000000/ssidref') [2006-09-08 13:42:05 xend] ERROR (SrvDaemon:292) Exception starting xend ((5, 'Input/output error, while reading /vm/00000000-0000-0000-0000-000000000000/ssidref')) Traceback (most recent call last): File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/server/SrvDaemon.py", line 286, in run servers = SrvServer.create() File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/server/SrvServer.py", line 108, in create root.putChild('xend', SrvRoot()) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/server/SrvRoot.py", line 40, in __init__ self.get(name) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/web/SrvDir.py", line 82, in get val = val.getobj() File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/web/SrvDir.py", line 52, in getobj self.obj = klassobj() File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 39, in __init__ self.xd = XendDomain.instance() File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomain.py", line 582, in instance inst.init() File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomain.py", line 77, in init True)) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 236, in recreate vm = XendDomainInfo(xeninfo, domid, dompath, True, priv) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 435, in __init__ self.augmentInfo(priv) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 520, in augmentInfo self.readVMDetails(entries)) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 463, in readVMDetails return self.gatherVm(*params) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 606, in gatherVm return xstransact.Gather(self.vmpath, *args) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py", line 305, in Gather return complete(path, lambda t: t.gather(*args)) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py", line 325, in complete result = f(t) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py", line 305, in return complete(path, lambda t: t.gather(*args)) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py", line 179, in gather val = self._read(key) File "/xen/xen-3.0.2-2/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py", line 49, in _read '%s, while reading %s' % (ex.args[1], path)) RuntimeError: (5, 'Input/output error, while reading /vm/00000000-0000-0000-0000-000000000000/ssidref') -------------------------------------------- I've tried to re-install Xen from binary or from source but I cannot get it work. Any ideas/suggestions? Thank you very much. __________________________________________________ Do You Yahoo!? Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi http://mail.yahoo.it From gregor.pirnaver at email.si Fri Sep 8 22:35:40 2006 From: gregor.pirnaver at email.si (Gregor Pirnaver) Date: Sat, 09 Sep 2006 00:35:40 +0200 Subject: [Fedora-xen] Recurring Zombie (XenU used as a web server) Message-ID: <20060908223542.A95158B9A3@www1.email.si> For some weeks I have a problem with XenU domain used as web server. It is turning into Zombie domain: # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 641 4 r----- 263.6 Zombie-wwwmain 2 512 1 ----cd 5238.4 dns 4 128 1 -b---- 20.1 intranet 6 512 1 -b---- 18.7 ldap 5 128 1 -b---- 61.4 mail 3 512 1 r----- 1078.0 www 1 512 1 -b---- 117.7 wwwextra 7 512 1 -b---- 33.2 (Both Xen0 and XenU are running FC5 with kernel 2.6.17-1.2174.) - How can I find out what is causing this problem? - How can I fix it / work around it / report a bug? This is production machine so I would appriciate any pointers. I didn't have this problem before. Maybe new kernel is causing the problem? Is there a way to get older versions of kernel packages? I would also like to note that when this happens networking doesn't work in ANY XenU domain. E.g.: # xm console dns after login trying to ping Google IP: # ping 72.14.221.104 PING 72.14.221.104 (72.14.221.104) 56(84) bytes of data. ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ... and when I run "init 0" in XenU (e.g. in dns XenU): # init 0 it hangs at this step: "Removing module iptables: " When I try to shutdown XenU from Xen0 it also turns to Zombie. E.g. (dns XenU domain turns into Zombie-dns): # xm shutdown dns What can I do? ____________________ http://www.email.si/ From riel at redhat.com Sat Sep 9 17:08:28 2006 From: riel at redhat.com (Rik van Riel) Date: Sat, 09 Sep 2006 13:08:28 -0400 Subject: [Fedora-xen] Recurring Zombie (XenU used as a web server) In-Reply-To: <20060908223542.A95158B9A3@www1.email.si> References: <20060908223542.A95158B9A3@www1.email.si> Message-ID: <4502F50C.4060106@redhat.com> Gregor Pirnaver wrote: > For some weeks I have a problem with XenU domain used as web server. It is > turning into Zombie domain: > > # xm list > Name ID Mem(MiB) VCPUs State Time(s) > Domain-0 0 641 4 r----- 263.6 > Zombie-wwwmain 2 512 1 ----cd 5238.4 Is that a fully virtualized domain, or paravirt ? > (Both Xen0 and XenU are running FC5 with kernel 2.6.17-1.2174.) > > - How can I find out what is causing this problem? > - How can I fix it / work around it / report a bug? If it is paravirt, you can "xm sysrq " to get some debugging output. If the domain in question is fully virt, do you have a stale qemu-dm hanging around? -- What is important? What you want to be true, or what is true? From ManognaR_C at infosys.com Tue Sep 12 09:43:11 2006 From: ManognaR_C at infosys.com (Manogna Ramakrishna Chebiyyam) Date: Tue, 12 Sep 2006 15:13:11 +0530 Subject: [Fedora-xen] how to determine CPU Slice Message-ID: Hi, Some one please give me a pointer as to how to determine the CPU Slice of a domain U Thanks in advance "If we knew what it was we were doing, it would not be called research, would it?" Albert Einstien **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Wed Sep 13 13:38:09 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 13 Sep 2006 14:38:09 +0100 Subject: [Fedora-xen] how to determine CPU Slice In-Reply-To: References: Message-ID: <20060913133809.GB27081@redhat.com> On Tue, Sep 12, 2006 at 03:13:11PM +0530, Manogna Ramakrishna Chebiyyam wrote: > Some one please give me a pointer as to how to determine the CPU Slice > of a domain U What exactly do you mean by CPU slice ? The CPU time used by a domain since it started ? libvirt provides an API virDomainGetInfo() for retrieving stats about a running domain. One of the fields in the struct it fills is 'cpuTime' which is a running counter of CPU time allocated to the DomU since it started, measured in nanoseconds. You can access this from C / Python / Perl, or just run 'virsh dominfo [name | id | uuid]' from the shell. eg # virsh dominfo demo1 Id: 6 Name: demo1 UUID: 7c29eaa6-68e3-1891-abef-7334079927a1 OS Type: linux State: blocked CPU(s): 2 CPU time: 14.8s Max memory: 723968 kB Used memory: 723776 kB Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From xenresu at gmail.com Wed Sep 13 15:29:03 2006 From: xenresu at gmail.com (XenResu) Date: Wed, 13 Sep 2006 11:29:03 -0400 Subject: [Fedora-xen] Is it possible to create a FC5 domU from ISO (without xenguest-install.py)? Message-ID: <8ff8d19d0609130829r20379cb4xe2dd2fb2015b307d@mail.gmail.com> Using the FC5 images/xen kernel and initrd, the init launches but doesn't find an installation method (no driver found) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Justin.Osborn at jhuapl.edu Wed Sep 13 18:50:44 2006 From: Justin.Osborn at jhuapl.edu (Osborn, Justin D.) Date: Wed, 13 Sep 2006 14:50:44 -0400 Subject: [Fedora-xen] vTPM on 2.6.17-1.2174_FC5 Message-ID: <7B95239DDD54E54B9BFA23847142B1EE12CB1F@aplesnation.dom1.jhuapl.edu> Hello, I'm working on a project which involves getting the vTPM set up with Xen. However while building the latest kernel rpm (2.6.17-1.2174_FC5) I noticed that the vTPM front end driver is not included. I downloaded Xen from xensource and the vTPM front end driver is included, however Xen 3.0.2 builds off of the 2.6.16 kernel which doesn't have TPM v1.2 support. I thought about just patching the vTPM front end driver into 2.6.17 but when I looked at Xen's vTPM backend driver code and the Fedora version, the Fedora version was much newer and had a lot of changes. So what's the best thing to do? Should I try to patch 1.2 TPM support into 2.6.16 or try to bring the vTPM front end driver support into 2.6.17? Is there a more recent FC5 kernel that has the vTPM front end driver support? Thanks, Justin -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron at hp.com Fri Sep 15 18:22:52 2006 From: aron at hp.com (Aron Griffis) Date: Fri, 15 Sep 2006 14:22:52 -0400 Subject: [Fedora-xen] debugging xenguest-install Message-ID: <20060915182251.GC20608@fc.hp.com> I'm attempting to install rawhide to a domU using xenguest-install. However it hangs on "Searching for Fedora Core installations..." This is paravirt on ia64. The installation is running on the xen (text) console, so there appears to be no way to access the debugging information anaconda would be stashing on the other virtual consoles, or in /tmp. xm list shows domU is spinning; the CPU time is climbing steadily. Debugging suggestions? Thanks, Aron From aron at hp.com Fri Sep 15 20:25:33 2006 From: aron at hp.com (Aron Griffis) Date: Fri, 15 Sep 2006 16:25:33 -0400 Subject: [Fedora-xen] debugging xenguest-install In-Reply-To: <20060915182251.GC20608@fc.hp.com> References: <20060915182251.GC20608@fc.hp.com> Message-ID: <20060915202533.GE20608@fc.hp.com> Attempting to debug, I started the "installation" with xenguest-install -n domu -r 512 -f /root/domu.img \ -s 4 --nographics -p \ -l http://hummer.zko.hp.com/fedora/linux/core/development/ia64/os/ \ -x 'ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe rescue nomount' but it appears rescue mode doesn't work with today's rawhide, at least not under xenguest-install: Running anaconda, the Fedora Core rescue mode - please wait... Traceback (most recent call last): File "/usr/bin/anaconda", line 703, in ? rescue.runRescue(anaconda) File "/usr/lib/anaconda/rescue.py", line 260, in runRescue runShell(screen) UnboundLocalError: local variable 'screen' referenced before assignment install exited abnormally [1/1] The bug looks apparent in rescue.py: screen is only initialized under the condition: if not methodUsesNetworking(anaconda.id.methodstr) Aron From jason at planet57.com Sat Sep 16 06:48:39 2006 From: jason at planet57.com (Jason Dillon) Date: Fri, 15 Sep 2006 23:48:39 -0700 Subject: [Fedora-xen] Guest install wedges host Message-ID: <5FA19DEF-318D-41F7-B3B6-3B41533608E5@planet57.com> Hi, I was just setting up Xen for the first time on FC5, which was relatively easy... the most trouble was knowing to disable selinux so that xend would start up properly on boot. After I set it to permissive it looked good, and I started to install a FC5 guest. / usr/sbin/xenguest-install.py started up the installation (which was pulled from http from a host next to the xen host, serving a mounted FC-5-x86_64-DVD.iso) and it got as far as the dialog telling me that it may take a while to initialize, and then it wedged the Xen host. The host was fully updated to the latest patches as of today. At this point the machine is hosed, and is gonna need someone to power- cycle it to get it back to life, which unfortunately probably won't happen until monday at the earliest. I am just curious if anyone else has run into similar issues, or if there are any known work arounds? # uname -a Linux butters 2.6.17-1.2187_FC5xen0 #1 SMP Mon Sep 11 01:51:30 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux The machine has like 15g of memory, almost 100g of disk and 4 dual core cpus (which the kernel sees as 8 cpus). I'd really like to use Xen... instead of VMware... though I it is going to be hard to debug since this machine is like 300 miles from me with crummy support, so if it wedges again, its another few days to kick it. Any ideas welcome. Thanks, --jason From adrian at creative.net.au Sun Sep 17 14:29:33 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Sun, 17 Sep 2006 22:29:33 +0800 Subject: [Fedora-xen] FC5 xen crash Message-ID: <20060917142933.GA1458@skywalker.creative.net.au> I've recently upgraded a xen-3 FC5 dom0 host to the latest Xen packages (2187_FC5xen0 and xenU), and this happened in a domU shortly after boot: ------------[ cut here ]------------ kernel BUG at net/core/dev.c:1206! invalid opcode: 0000 [#1] SMP Modules linked in: xt_tcpudp iptable_mangle iptable_nat ip_nat ip_conntrack nfnetlink iptable_filter ip_tables ipv6 x_tables xennet dm_snapshot dm_zero dm_mirror dm_mod raid1 CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010297 (2.6.17-1.2187_FC5xenU #1) EIP is at skb_gso_segment+0x29/0xc9 eax: 00000000 ebx: c7849ec4 ecx: 00050003 edx: c05f7700 esi: c7849ec4 edi: 00000008 ebp: c7eb8000 esp: c0651b84 ds: 007b es: 007b ss: 0069 Process swapper (pid: 0, threadinfo=c0650000 task=c05f2800) Stack: <0>00000001 c7849ec4 c69ed300 c055938b c7849ec4 00050003 00000001 c7eb8000 c7849ec4 c7eb8180 00000000 c0564e1e c7849ec4 c7eb8000 c12a7400 00000000 c7eb8000 c0650000 c7849ec4 c055af7e c7eb8000 c7d8bcf4 c7d8bd14 c69ed2cc Call Trace: dev_hard_start_xmit+0x174/0x203 __qdisc_run+0xe0/0x19a dev_queue_xmit+0x1ce/0x2cc ip_output+0x1b6/0x1ec ip_queue_xmit+0x374/0x3b3 _spin_lock_irqsave+0x22/0x27 _spin_unlock_irqrestore+0x9/0x31 __mod_timer+0x96/0x9e tcp_transmit_skb+0x5d2/0x602 __tcp_push_pending_frames+0x6b7/0x789 tcp_data_queue+0x518/0x97f tcp_rcv_established+0x60d/0x695 tcp_v4_do_rcv+0x23/0x2ce tcp_v4_rcv+0x8ee/0x964 ip_local_deliver+0x58/0x1fd ip_local_deliver+0x157/0x1fd ip_rcv+0x3e9/0x423 netif_receive_skb+0x21a/0x298 netif_poll+0x8b0/0xae1 [xennet] net_rx_action+0xcd/0x1fe __do_softirq+0x70/0xef do_softirq+0x40/0x67 do_IRQ+0x1f/0x25 evtchn_do_upcall+0x66/0x9f hypervisor_callback+0x3d/0x48 safe_halt+0x84/0xa7 xen_idle+0x46/0x4e cpu_idle+0x94/0xad start_kernel+0x346/0x34c Has anyone seen this at all? Any ideas where to start digging for clues? Adrian From xlot at onlinewarrior.com Sun Sep 17 23:50:04 2006 From: xlot at onlinewarrior.com (Hilton Day) Date: Mon, 18 Sep 2006 09:50:04 +1000 Subject: [Fedora-xen] FC5 xen crash In-Reply-To: <20060917142933.GA1458@skywalker.creative.net.au> References: <20060917142933.GA1458@skywalker.creative.net.au> Message-ID: <450DDF2C.4090601@onlinewarrior.com> Check the xen log files for more info: /var/log/xend-debug.log /var/log/xend.log You don't say which architecture you're running.. if its i386, it could be a PAE issue. More recent FC5 xen kernels have PAE turned on by default, but the older ones don't, causing it to barf when trying to start a non-PAE kernel inside a PAE dom0. Although I think from memory this only affects the kernel-xen package, and not the kernel-xen0/kernel-xenU packages (unsure now.. I've moved to FC6 since test2). Either way, the xen log files will be a good source to start figuring out whats up. Adrian Chadd wrote: > I've recently upgraded a xen-3 FC5 dom0 host to the latest Xen packages > (2187_FC5xen0 and xenU), and this happened in a domU shortly after boot: > > ------------[ cut here ]------------ > kernel BUG at net/core/dev.c:1206! > invalid opcode: 0000 [#1] > SMP > Modules linked in: xt_tcpudp iptable_mangle iptable_nat ip_nat ip_conntrack nfnetlink iptable_filter ip_tables ipv6 x_tables xennet dm_snapshot dm_zero dm_mirror dm_mod raid1 > CPU: 0 > EIP: 0061:[] Not tainted VLI > EFLAGS: 00010297 (2.6.17-1.2187_FC5xenU #1) > EIP is at skb_gso_segment+0x29/0xc9 > eax: 00000000 ebx: c7849ec4 ecx: 00050003 edx: c05f7700 > esi: c7849ec4 edi: 00000008 ebp: c7eb8000 esp: c0651b84 > ds: 007b es: 007b ss: 0069 > Process swapper (pid: 0, threadinfo=c0650000 task=c05f2800) > Stack: <0>00000001 c7849ec4 c69ed300 c055938b c7849ec4 00050003 00000001 c7eb8000 > c7849ec4 c7eb8180 00000000 c0564e1e c7849ec4 c7eb8000 c12a7400 00000000 > c7eb8000 c0650000 c7849ec4 c055af7e c7eb8000 c7d8bcf4 c7d8bd14 c69ed2cc > Call Trace: > dev_hard_start_xmit+0x174/0x203 __qdisc_run+0xe0/0x19a > dev_queue_xmit+0x1ce/0x2cc ip_output+0x1b6/0x1ec > ip_queue_xmit+0x374/0x3b3 _spin_lock_irqsave+0x22/0x27 > _spin_unlock_irqrestore+0x9/0x31 __mod_timer+0x96/0x9e > tcp_transmit_skb+0x5d2/0x602 __tcp_push_pending_frames+0x6b7/0x789 > tcp_data_queue+0x518/0x97f tcp_rcv_established+0x60d/0x695 > tcp_v4_do_rcv+0x23/0x2ce tcp_v4_rcv+0x8ee/0x964 > ip_local_deliver+0x58/0x1fd ip_local_deliver+0x157/0x1fd > ip_rcv+0x3e9/0x423 netif_receive_skb+0x21a/0x298 > netif_poll+0x8b0/0xae1 [xennet] net_rx_action+0xcd/0x1fe > __do_softirq+0x70/0xef do_softirq+0x40/0x67 > do_IRQ+0x1f/0x25 evtchn_do_upcall+0x66/0x9f > hypervisor_callback+0x3d/0x48 safe_halt+0x84/0xa7 > xen_idle+0x46/0x4e cpu_idle+0x94/0xad > start_kernel+0x346/0x34c > > Has anyone seen this at all? Any ideas where to start digging for clues? > > > > Adrian > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From thomas.vonsteiger at bluewin.ch Tue Sep 19 08:55:02 2006 From: thomas.vonsteiger at bluewin.ch (thomas.vonsteiger at bluewin.ch) Date: Tue, 19 Sep 2006 10:55:02 +0200 Subject: [Fedora-xen] xen guest eth1 tun interface goes to the wrong bridge Message-ID: <001b01c6dbc9$4b917090$0401a8c0@athlon> Hello, We have setup 6 xen guests VT(rhel3) on dmo0 FC5 and for each guest there are 2 network interfaces eth0/eth1. Now if we start the xen guests all the tun interfaces for eth1 goes to xenbr1 and not do the defined bridge tsmbr1 oder tsmbr2 ? Where are the scripts for setup tun interface ? Has anybody a solution for this problem ? 2 Guests have this vif config: vif = [ 'type=ioemu,bridge=xenbr1,mac=02:00:00:00:01:01', 'type=ioemu,bridge=tsmbr1,mac=02:00:00:00:01:02' ] And 2 guest have this vif config: vif = [ 'type=ioemu,bridge=xenbr1,mac=02:00:00:00:01:09', 'type=ioemu,bridge=tsmbr2,mac=02:00:00:00:01:10' ] bridge name bridge id STP enabled interfaces tsmbr1 8000.921f6ab823a2 no tun1 vif1.1 vif2.1 tsmbr2 8000.feffffffffff no vif3.1 vif4.1 vif5.1 vif7.1 vif9.1 xenbr0 8000.82469d13d88a no peth0 tun14 tun15 vif0.0 vif8.0 xenbr1 8000.06939ed49977 no peth1 tun0 tun10 tun11 tun12 tun13 tun2 tun3 tun4 tun5 tun6 tun7 tun8 tun9 vif0.1 vif1.0 vif2.0 vif3.0 vif4.0 vif5.0 vif7.0 vif9.0 xenbr2 8000.feffffffffff no peth2 vif0.2 vif8.1 many thanks, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From fred.yang at intel.com Tue Sep 19 16:12:14 2006 From: fred.yang at intel.com (Yang, Fred) Date: Tue, 19 Sep 2006 09:12:14 -0700 Subject: [Fedora-xen] [Fedora-ia64-list] FC6 Test3 Xen test result Message-ID: <176273AE807A344A8C14F517A8FC59C2973742@scsmsx412.amr.corp.intel.com> Following is the quick Xen test result with FC6 Test3. We will file BZ for the issues tonight; the early data is to get community to fix Xen issues ASAP Thanks, -Fred ==== I have followed Redhat instructions (FC6-test3 can not be installed from CDs) to install FC6-Test3 and do some testing. Both Xen0 and VTI can all boot up, but XenU couldn't be created successfully. Detailed Items: 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass] need manually reinstall kernel-xen rpm package. 2. Boot Native Linux of FC6 Test3 [Pass] 3. Boot Xen of FC6 Test3 [Pass] 4. xend and xm commands are working. [Pass] 5. XenU Domain creating failed. [__FAIL__] 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin) [__FAIL__ (expected)] 7. After manually copy VTI guest firmware, creating VTI domain [Pass] 8. VTI domain with network supported [Pass] 9. 2 VTI domains coexisting testing [Pass] 10. Linux Kernel build in VTI domain [Pass] 11. LTP testing in VTI domain [Pass] 12. SMP VTI domain [Pass] 13. SMP Xen0 [Pass] 14. 1 VTI Windows 2k3 [Pass] a little slower. 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue screen] 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] Other issues: 1) Xen0 operation is a little slower than RHEL4u3. 2) XenU creating failure, please see attachment for the serial output. Best Regards, Yongkang (Kangkang) ?? From huchen at cisco.com Tue Sep 19 17:30:21 2006 From: huchen at cisco.com (Huei-Ping Chen) Date: Tue, 19 Sep 2006 10:30:21 -0700 (PDT) Subject: [Fedora-xen] source for building kernel-xen0 ? Message-ID: <200609191730.k8JHULYq011924@sj-core-2.cisco.com> Hi, I am a newbie here, and I have installed fedora core 5, xen, xen0, xenU on my thinkpad laptop, follows the quick start guide, I can bring up guest xenU, everything works fine, including networking. now I want to learn more about xen, and want to build everything from scartch, there are some rpm comes with fedora 5, like some kernel-xen-devel package, but it only include the headers file, no C codes at all, so I googled though every where, but I could ot find the source RPM for that, the only xen source I can find is xen-3.o.???.src.rpm, which builds kernel ends with "xen", not "xen0", so I am wondering where do I find the source or building xen0 ? or, I should just use the "xen-3.o.???.src.rpm" ? thanks, -- Ping From berrange at redhat.com Tue Sep 19 17:38:22 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 19 Sep 2006 18:38:22 +0100 Subject: [Fedora-xen] source for building kernel-xen0 ? In-Reply-To: <200609191730.k8JHULYq011924@sj-core-2.cisco.com> References: <200609191730.k8JHULYq011924@sj-core-2.cisco.com> Message-ID: <20060919173822.GD19146@redhat.com> On Tue, Sep 19, 2006 at 10:30:21AM -0700, Huei-Ping Chen wrote: > Hi, > > I am a newbie here, and I have installed fedora core 5, xen, xen0, xenU on > my thinkpad laptop, follows the quick start guide, I can bring up guest > xenU, everything works fine, including networking. > > now I want to learn more about xen, and want to build everything from > scartch, > there are some rpm comes with fedora 5, like some kernel-xen-devel package, > but it only include the headers file, no C codes at all, > > so I googled though every where, but I could ot find the source RPM for that, > the only xen source I can find is xen-3.o.???.src.rpm, which builds kernel > ends with "xen", not "xen0", > > so I am wondering where do I find the source or building xen0 ? or, I should > just use the "xen-3.o.???.src.rpm" ? In Fedora land, all kernels, baremetal, Dom0 and DomU are built from a single master source RPM. The latest errata for FC5 is http://download.fedora.devel.redhat.com/pub/fedora/linux/core/updates/5/SRPMS/kernel-2.6.17-1.2187_FC5.src.rpm The 'xen' SRPM that you see is just used to build & package the corresponding userspace bits. Bear in mind that if you're modifying stuff make absolutely sure you use matched versions of the kernel & userland bits. For FC5 the latest userland SRPM for Xen is http://download.fedora.devel.redhat.com/pub/fedora/linux/core/updates/5/SRPMS/xen-3.0.2-3.FC5.src.rpm Regards Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From huchen at cisco.com Tue Sep 19 17:55:46 2006 From: huchen at cisco.com (Huei-Ping Chen) Date: Tue, 19 Sep 2006 10:55:46 -0700 (PDT) Subject: [Fedora-xen] source for building kernel-xen0 ? Message-ID: <200609191755.k8JHtkQW026019@sj-core-1.cisco.com> Cool! thanks for the pointer, now I am ready for my adventure! > Date: Tue, 19 Sep 2006 18:38:22 +0100 > From: "Daniel P. Berrange" > To: Huei-Ping Chen > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] source for building kernel-xen0 ? > User-Agent: Mutt/1.4.1i > Authentication-Results: sj-dkim-8.cisco.com; header.From=berrange at redhat.com; dkim=neutral > > On Tue, Sep 19, 2006 at 10:30:21AM -0700, Huei-Ping Chen wrote: > > Hi, > > > > I am a newbie here, and I have installed fedora core 5, xen, xen0, xenU on > > my thinkpad laptop, follows the quick start guide, I can bring up guest > > xenU, everything works fine, including networking. > > > > now I want to learn more about xen, and want to build everything from > > scartch, > > there are some rpm comes with fedora 5, like some kernel-xen-devel package, > > but it only include the headers file, no C codes at all, > > > > so I googled though every where, but I could ot find the source RPM for that, > > the only xen source I can find is xen-3.o.???.src.rpm, which builds kernel > > ends with "xen", not "xen0", > > > > so I am wondering where do I find the source or building xen0 ? or, I should > > just use the "xen-3.o.???.src.rpm" ? > > In Fedora land, all kernels, baremetal, Dom0 and DomU are built from a > single master source RPM. The latest errata for FC5 is > > http://download.fedora.devel.redhat.com/pub/fedora/linux/core/updates/5/SRPMS/ke rnel-2.6.17-1.2187_FC5.src.rpm > > The 'xen' SRPM that you see is just used to build & package the corresponding > userspace bits. > > Bear in mind that if you're modifying stuff make absolutely sure you use > matched versions of the kernel & userland bits. For FC5 the latest userland > SRPM for Xen is > > http://download.fedora.devel.redhat.com/pub/fedora/linux/core/updates/5/SRPMS/xe n-3.0.2-3.FC5.src.rpm > > Regards > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| > |=- Perl modules: http://search.cpan.org/~danberr/ -=| > |=- Projects: http://freshmeat.net/~danielpb/ -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From henning_sprang at gmx.de Tue Sep 19 18:03:23 2006 From: henning_sprang at gmx.de (Henning Sprang) Date: Tue, 19 Sep 2006 20:03:23 +0200 Subject: [Fedora-xen] xen guest eth1 tun interface goes to the wrong bridge In-Reply-To: <001b01c6dbc9$4b917090$0401a8c0@athlon> References: <001b01c6dbc9$4b917090$0401a8c0@athlon> Message-ID: <5bb00b3f0609191103j6a0e3e4bqa6fa91e832d7cb8f@mail.gmail.com> On 9/19/06, thomas.vonsteiger at bluewin.ch wrote: > > > > Hello, Again for all who still didn't realize it yet: please DON'T post HTML Mails to mailing lists!!! It really looks ugly and doesn't motivate people to help you... Heninng From y-oguchi at jp.fujitsu.com Tue Sep 19 23:22:38 2006 From: y-oguchi at jp.fujitsu.com (y-oguchi at jp.fujitsu.com) Date: Wed, 20 Sep 2006 08:22:38 +0900 Subject: [Fedora-xen] Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result In-Reply-To: <176273AE807A344A8C14F517A8FC59C2973742@scsmsx412.amr.corp.intel.com> References: <176273AE807A344A8C14F517A8FC59C2973742@scsmsx412.amr.corp.intel.com> Message-ID: Fred, Yongkang, > Other issues: > 1) Xen0 operation is a little slower than RHEL4u3. > 2) XenU creating failure, please see attachment for the serial output. I can't find the attachment. Could you repost the serial log? Thanks, Yoshi Oguchi "Yang, Fred" wrote? > Following is the quick Xen test result with FC6 Test3. We will file BZ for the issues tonight; the early data is to get community to fix Xen issues ASAP > Thanks, > -Fred > > ==== > I have followed Redhat instructions (FC6-test3 can not be installed from CDs) to install FC6-Test3 and do some testing. Both Xen0 and VTI can all boot up, but XenU couldn't be created successfully. > > Detailed Items: > 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass] need manually reinstall kernel-xen rpm package. > 2. Boot Native Linux of FC6 Test3 [Pass] > 3. Boot Xen of FC6 Test3 [Pass] > 4. xend and xm commands are working. [Pass] > 5. XenU Domain creating failed. [__FAIL__] > 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin) [__FAIL__ (expected)] > 7. After manually copy VTI guest firmware, creating VTI domain [Pass] > 8. VTI domain with network supported [Pass] > 9. 2 VTI domains coexisting testing [Pass] > 10. Linux Kernel build in VTI domain [Pass] > 11. LTP testing in VTI domain [Pass] > 12. SMP VTI domain [Pass] > 13. SMP Xen0 [Pass] > 14. 1 VTI Windows 2k3 [Pass] a little slower. > 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue screen] > 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] > > Other issues: > 1) Xen0 operation is a little slower than RHEL4u3. > 2) XenU creating failure, please see attachment for the serial output. > > Best Regards, > Yongkang (Kangkang) ?? > > _______________________________________________ > Xen-ia64-devel mailing list > Xen-ia64-devel at lists.xensource.com > http://lists.xensource.com/xen-ia64-devel From fred.yang at intel.com Wed Sep 20 00:26:13 2006 From: fred.yang at intel.com (Yang, Fred) Date: Tue, 19 Sep 2006 17:26:13 -0700 Subject: [Fedora-xen] RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result Message-ID: <176273AE807A344A8C14F517A8FC59C2973D86@scsmsx412.amr.corp.intel.com> Here it comes! -Fred >-----Original Message----- >From: y-oguchi at jp.fujitsu.com [mailto:y-oguchi at jp.fujitsu.com] >Sent: Tuesday, September 19, 2006 4:23 PM >To: Yang, Fred; fedora-xen at redhat.com >Cc: xen-ia64-devel at lists.xensource.com >Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result > >Fred, Yongkang, > >> Other issues: >> 1) Xen0 operation is a little slower than RHEL4u3. >> 2) XenU creating failure, please see attachment for the serial output. > >I can't find the attachment. >Could you repost the serial log? > >Thanks, >Yoshi Oguchi > >"Yang, Fred" wrote? >> Following is the quick Xen test result with FC6 Test3. We will file >BZ for the issues tonight; the early data is to get community to fix Xen >issues ASAP >> Thanks, >> -Fred >> >> ==== >> I have followed Redhat instructions (FC6-test3 can not be installed >from CDs) to install FC6-Test3 and do some testing. Both Xen0 and VTI >can all boot up, but XenU couldn't be created successfully. >> >> Detailed Items: >> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass] need >manually reinstall kernel-xen rpm package. >> 2. Boot Native Linux of FC6 Test3 [Pass] >> 3. Boot Xen of FC6 Test3 [Pass] >> 4. xend and xm commands are working. [Pass] >> 5. XenU Domain creating failed. [__FAIL__] >> 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin) > [__FAIL__ (expected)] >> 7. After manually copy VTI guest firmware, creating VTI domain >[Pass] >> 8. VTI domain with network supported [Pass] >> 9. 2 VTI domains coexisting testing [Pass] >> 10. Linux Kernel build in VTI domain [Pass] >> 11. LTP testing in VTI domain [Pass] >> 12. SMP VTI domain [Pass] >> 13. SMP Xen0 [Pass] >> 14. 1 VTI Windows 2k3 [Pass] a little slower. >> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue screen] >> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] >> >> Other issues: >> 1) Xen0 operation is a little slower than RHEL4u3. >> 2) XenU creating failure, please see attachment for the serial output. >> >> Best Regards, >> Yongkang (Kangkang) ?? >> >> _______________________________________________ >> Xen-ia64-devel mailing list >> Xen-ia64-devel at lists.xensource.com >> http://lists.xensource.com/xen-ia64-devel -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xenU_serial_out.txt URL: From yongkang.you at intel.com Wed Sep 20 02:07:02 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Wed, 20 Sep 2006 10:07:02 +0800 Subject: [Fedora-xen] RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result Message-ID: <094BCE01AFBE9646AF220B0B3F367AAB588FCA@pdsmsx413.ccr.corp.intel.com> Hi Fred & Yoshi, The former XenU creating failure issue seemed to be the config issue. Now I can create XenU. But XenU booting process met an old bug. It will cost a long time to check hard disk IRQ response from hda to hdh. After that, xenU met the problem of mounting root partition to start services, and then XenU booting failed (Kill init). I am not sure if it is because initrd issue. I will continue to check it. Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: xen-ia64-devel-bounces at lists.xensource.com >[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of Yang, >Fred >Sent: 2006?9?20? 8:26 >To: y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >Cc: xen-ia64-devel at lists.xensource.com >Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result > >Here it comes! >-Fred > >>-----Original Message----- >>From: y-oguchi at jp.fujitsu.com [mailto:y-oguchi at jp.fujitsu.com] >>Sent: Tuesday, September 19, 2006 4:23 PM >>To: Yang, Fred; fedora-xen at redhat.com >>Cc: xen-ia64-devel at lists.xensource.com >>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >> >>Fred, Yongkang, >> >>> Other issues: >>> 1) Xen0 operation is a little slower than RHEL4u3. >>> 2) XenU creating failure, please see attachment for the serial output. >> >>I can't find the attachment. >>Could you repost the serial log? >> >>Thanks, >>Yoshi Oguchi >> >>"Yang, Fred" wrote? >>> Following is the quick Xen test result with FC6 Test3. We will file >>BZ for the issues tonight; the early data is to get community to fix Xen >>issues ASAP >>> Thanks, >>> -Fred >>> >>> ==== >>> I have followed Redhat instructions (FC6-test3 can not be installed >>from CDs) to install FC6-Test3 and do some testing. Both Xen0 and VTI >>can all boot up, but XenU couldn't be created successfully. >>> >>> Detailed Items: >>> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass] need >>manually reinstall kernel-xen rpm package. >>> 2. Boot Native Linux of FC6 Test3 [Pass] >>> 3. Boot Xen of FC6 Test3 [Pass] >>> 4. xend and xm commands are working. [Pass] >>> 5. XenU Domain creating failed. [__FAIL__] >>> 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin) >> [__FAIL__ (expected)] >>> 7. After manually copy VTI guest firmware, creating VTI domain >>[Pass] >>> 8. VTI domain with network supported [Pass] >>> 9. 2 VTI domains coexisting testing [Pass] >>> 10. Linux Kernel build in VTI domain [Pass] >>> 11. LTP testing in VTI domain [Pass] >>> 12. SMP VTI domain [Pass] >>> 13. SMP Xen0 [Pass] >>> 14. 1 VTI Windows 2k3 [Pass] a little slower. >>> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue >screen] >>> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] >>> >>> Other issues: >>> 1) Xen0 operation is a little slower than RHEL4u3. >>> 2) XenU creating failure, please see attachment for the serial output. >>> >>> Best Regards, >>> Yongkang (Kangkang) ?? >>> >>> _______________________________________________ >>> Xen-ia64-devel mailing list >>> Xen-ia64-devel at lists.xensource.com >>> http://lists.xensource.com/xen-ia64-devel From yongkang.you at intel.com Wed Sep 20 05:46:22 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Wed, 20 Sep 2006 13:46:22 +0800 Subject: [Fedora-xen] RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result Message-ID: <094BCE01AFBE9646AF220B0B3F367AAB588FCB@pdsmsx413.ccr.corp.intel.com> Hi, I have reported 2 bugs to redhat bugzilla: [Bug 207227] New: Xen0 reboot command can not reboot Tiger4 machine. [Bug 207241] New: XenU domain can not be created successfully. New xenU created failure serial log has been pasted to the bug. I also notice FC6-test3 Xen0 operation is a little slower, compared with RHEL4u3. I assign 2 vcpus to Xen0. When I destroy domains or do some heavy IO operations, Xen0 operations will be blocked for a while. I didn't track this to bugzilla. There are also a lot of unaligned accessing from some applications. They should be common FC6-test3 issues. Sometime Xen0 monitor will print "Bug: soft lockup detected on CPU#0(or #1)" Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: xen-ia64-devel-bounces at lists.xensource.com >[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of You, >Yongkang >Sent: 2006?9?20? 10:07 >To: Yang, Fred; y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >Cc: xen-ia64-devel at lists.xensource.com >Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result > >Hi Fred & Yoshi, > >The former XenU creating failure issue seemed to be the config issue. Now I >can create XenU. But XenU booting process met an old bug. It will cost a long >time to check hard disk IRQ response from hda to hdh. > >After that, xenU met the problem of mounting root partition to start services, >and then XenU booting failed (Kill init). I am not sure if it is because initrd issue. >I will continue to check it. > >Best Regards, >Yongkang (Kangkang) ?? > >>-----Original Message----- >>From: xen-ia64-devel-bounces at lists.xensource.com >>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of Yang, >>Fred >>Sent: 2006?9?20? 8:26 >>To: y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>Cc: xen-ia64-devel at lists.xensource.com >>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >> >>Here it comes! >>-Fred >> >>>-----Original Message----- >>>From: y-oguchi at jp.fujitsu.com [mailto:y-oguchi at jp.fujitsu.com] >>>Sent: Tuesday, September 19, 2006 4:23 PM >>>To: Yang, Fred; fedora-xen at redhat.com >>>Cc: xen-ia64-devel at lists.xensource.com >>>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >>> >>>Fred, Yongkang, >>> >>>> Other issues: >>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>> 2) XenU creating failure, please see attachment for the serial output. >>> >>>I can't find the attachment. >>>Could you repost the serial log? >>> >>>Thanks, >>>Yoshi Oguchi >>> >>>"Yang, Fred" wrote? >>>> Following is the quick Xen test result with FC6 Test3. We will file >>>BZ for the issues tonight; the early data is to get community to fix Xen >>>issues ASAP >>>> Thanks, >>>> -Fred >>>> >>>> ==== >>>> I have followed Redhat instructions (FC6-test3 can not be installed >>>from CDs) to install FC6-Test3 and do some testing. Both Xen0 and VTI >>>can all boot up, but XenU couldn't be created successfully. >>>> >>>> Detailed Items: >>>> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass] >need >>>manually reinstall kernel-xen rpm package. >>>> 2. Boot Native Linux of FC6 Test3 [Pass] >>>> 3. Boot Xen of FC6 Test3 [Pass] >>>> 4. xend and xm commands are working. [Pass] >>>> 5. XenU Domain creating failed. [__FAIL__] >>>> 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin) >>> [__FAIL__ (expected)] >>>> 7. After manually copy VTI guest firmware, creating VTI domain >>>[Pass] >>>> 8. VTI domain with network supported [Pass] >>>> 9. 2 VTI domains coexisting testing [Pass] >>>> 10. Linux Kernel build in VTI domain [Pass] >>>> 11. LTP testing in VTI domain [Pass] >>>> 12. SMP VTI domain [Pass] >>>> 13. SMP Xen0 [Pass] >>>> 14. 1 VTI Windows 2k3 [Pass] a little slower. >>>> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue >>screen] >>>> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] >>>> >>>> Other issues: >>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>> 2) XenU creating failure, please see attachment for the serial output. >>>> >>>> Best Regards, >>>> Yongkang (Kangkang) ?? >>>> >>>> _______________________________________________ >>>> Xen-ia64-devel mailing list >>>> Xen-ia64-devel at lists.xensource.com >>>> http://lists.xensource.com/xen-ia64-devel > >_______________________________________________ >Xen-ia64-devel mailing list >Xen-ia64-devel at lists.xensource.com >http://lists.xensource.com/xen-ia64-devel From kwan at digitalhermit.com Wed Sep 20 21:24:48 2006 From: kwan at digitalhermit.com (Kwan Lowe) Date: Wed, 20 Sep 2006 17:24:48 -0400 (EDT) Subject: [Fedora-xen] DomainU crashing - Zombie Message-ID: <34813.192.168.8.100.1158787488.squirrel@digitalhermit.com> Hello all: After doing some recent updates I've noticed that one previously stable domain is now crashing regularly. The dom0 is running 2.6.17-1.2187_FC5xen0 and the corresponding domU kernel on the virtuals. Dom0 hardware is an Athlon XP 2200 with 1G RAM. This occurs under moderately heavy network. The crashed domain is a fileserver image with a physical disk and was serving up a Solaris installation iso when it died. The DomU will not shutdown with "xm shutdown" or "xm destroy" and I need to kill -9 the "xend start" processes to force it down. This also prevents the Dom0 from rebooting. Ahh... And just noticed that I can't "xm shutdown" two running VMs either. They both go to Zombie state. (domain (domid 4) (uuid 314e3d58-a8b9-a7d6-4d86-472aa42cbcc5) (vcpus 1) (cpu_weight 1.0) (memory 256) (maxmem 256) (bootloader /usr/bin/pygrub) (features ) (name Zombie-xm-fc5-001) (on_poweroff destroy) (on_reboot restart) (on_crash restart) (image (linux (ramdisk /var/lib/xen/initrd.huJonl) (kernel /var/lib/xen/vmlinuz.cTMDsO) (args 'ro root=/dev/rootvg/root_lv') ) ) (state ----cd) (shutdown_reason crash) (cpu_time 59.409401921) (online_vcpus 1) (up_time 11961.170969) (start_time 1158775219.69) (store_mfn 235518) (console_mfn 235517) ) -- * The Digital Hermit http://www.digitalhermit.com * Unix and Linux Solutions kwan at digitalhermit.com From yunfeng.zhao at intel.com Wed Sep 20 23:47:20 2006 From: yunfeng.zhao at intel.com (Zhao, Yunfeng) Date: Thu, 21 Sep 2006 07:47:20 +0800 Subject: [Fedora-xen] Testing for Xen of FC6 Test3 -- 1 Message-ID: <10EA09EFD8728347A513008B6B0DA77A05ADE0@pdsmsx411.ccr.corp.intel.com> Hi. We are now doing a full testing for Xen of FC6 Test3. As a part of the full testing, we have already completed a basic functional testing. The testing includes boot vmx guests, installing fc6 test3 ia32/ia32e into vmx, and installing win 2000/xp/2003 into vmx. The test box is an Intel SDV with a presler processor. Following are the test results, and more test results will be available soon. Here are some issues I found in the basic functional testing: 1. Cannot boot fc6 test3 ia32 smp guest, xen0 reboot fc6 test3 ia32 guest can be booted up with 1 vcpu, but if boot it as a smp guest with enabling 2 vcpus and apic=1 in config file, xen0 will reboot. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207418 2. Cannot reboot/poweroff vmx guests. After reboot vmx guest,a white window will be popped up. After poweroff, vmx guest will not be destroyed. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207402 3. VGA issues of win2k and fc6 test3 IA32e guests I cannot install FC6 test3 IA32e guest with graphic mode. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207407 VGA of win2k vmx guest is unusable. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207405 4. Installer of Fc6 test3 ia32e doesn't make initrd After installed fc6 ia32e native and vmx, I could not find initrd. So to boot FC6 Test3 native or vmx, I have to create initrd by myself. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207407 Here is detailed result about the testing: 1. Install windows xp sp2/2000/2003 on ia32-pae/ia32e hv PASS 2. Install FC6-test3 ia32 with graphical mode PASS 3. Install FC6-test3 ia32e with graphical mode FAIL 4. Install FC6-test3 ia32e with text mode PASS 5. Boot FC5 UP IA32/IA32e VMX guests PASS 6. Boot FC6 Test3 IA32 UP VMX guest PASS 7. Boot FC6 Test3 IA32 SMP VMX guest FAIL (Xen0 reboot) 8. Boot FC6 Test3e IA32 UP VMX guest FAIL (No initrd) 9. Boot FC6 Test3e IA32 SMP VMX guest FAIL (No initrd) Thanks Yunfeng From takebe_akio at jp.fujitsu.com Thu Sep 21 01:32:49 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Thu, 21 Sep 2006 10:32:49 +0900 Subject: [Fedora-xen] RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AAB588FCB@pdsmsx413.ccr.corp.intel.com> References: <094BCE01AFBE9646AF220B0B3F367AAB588FCB@pdsmsx413.ccr.corp.intel.com> Message-ID: <71C6DD1DD953F6takebe_akio@jp.fujitsu.com> Hi, Yongkang I think this issue is configuration mistakes. Can you try the following configuration? I cannot try it because I meet another issue... 1. /etc/modprobe.conf for initrd of domU The following configuration would solve the issue of booting domU. [root at tiger156 xen]# cat /etc/modprobe.conf #alias eth0 e1000 #alias scsi_hostadapter mptbase #alias scsi_hostadapter1 mptspi alias eth0 xennet <----this alias scsi_hostadapter xenblk <----and this 2. domU.conf The following configuration would solve the issue of probing ide disk. kernel = "vmlinuz-2.6.17-1.2630.fc6xen" ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img" memory = 512 name = "domU" vif = [ '' ] disk = [ 'file:/xen/image/fc6.root.img,hda1,w' ] root = "/dev/hda1 ro" extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" <----this Best Regards, Akio Takebe >Hi, > >I have reported 2 bugs to redhat bugzilla: >[Bug 207227] New: Xen0 reboot command can not reboot Tiger4 machine. >[Bug 207241] New: XenU domain can not be created successfully. >New xenU created failure serial log has been pasted to the bug. > >I also notice FC6-test3 Xen0 operation is a little slower, compared with >RHEL4u3. I assign 2 vcpus to Xen0. When I destroy domains or do some heavy >IO operations, Xen0 operations will be blocked for a while. I didn't track >this to bugzilla. > >There are also a lot of unaligned accessing from some applications. They >should be common FC6-test3 issues. > >Sometime Xen0 monitor will print "Bug: soft lockup detected on CPU#0(or #1)" > >Best Regards, >Yongkang (Kangkang) $B%b%?%=%*(B > >>-----Original Message----- >>From: xen-ia64-devel-bounces at lists.xensource.com >>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of You, >>Yongkang >>Sent: 2006$B%Hs%d%D(B20$B%M%f(B 10:07 >>To: Yang, Fred; y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>Cc: xen-ia64-devel at lists.xensource.com >>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >> >>Hi Fred & Yoshi, >> >>The former XenU creating failure issue seemed to be the config issue. Now I >>can create XenU. But XenU booting process met an old bug. It will cost a >>long >>time to check hard disk IRQ response from hda to hdh. >> >>After that, xenU met the problem of mounting root partition to start >>services, >>and then XenU booting failed (Kill init). I am not sure if it is because >>initrd issue. >>I will continue to check it. >> >>Best Regards, >>Yongkang (Kangkang) $B%b%?%=%*(B >> >>>-----Original Message----- >>>From: xen-ia64-devel-bounces at lists.xensource.com >>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of Yang, >>>Fred >>>Sent: 2006$B%Hs%d%D(B20$B%M%f(B 8:26 >>>To: y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>>Cc: xen-ia64-devel at lists.xensource.com >>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >>> >>>Here it comes! >>>-Fred >>> >>>>-----Original Message----- >>>>From: y-oguchi at jp.fujitsu.com [mailto:y-oguchi at jp.fujitsu.com] >>>>Sent: Tuesday, September 19, 2006 4:23 PM >>>>To: Yang, Fred; fedora-xen at redhat.com >>>>Cc: xen-ia64-devel at lists.xensource.com >>>>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >>>> >>>>Fred, Yongkang, >>>> >>>>> Other issues: >>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>> 2) XenU creating failure, please see attachment for the serial output. >>>> >>>>I can't find the attachment. >>>>Could you repost the serial log? >>>> >>>>Thanks, >>>>Yoshi Oguchi >>>> >>>>"Yang, Fred" wrote$B!W%3(B >>>>> Following is the quick Xen test result with FC6 Test3. We will file >>>>BZ for the issues tonight; the early data is to get community to fix Xen >>>>issues ASAP >>>>> Thanks, >>>>> -Fred >>>>> >>>>> ==== >>>>> I have followed Redhat instructions (FC6-test3 can not be installed >>>>from CDs) to install FC6-Test3 and do some testing. Both Xen0 and VTI >>>>can all boot up, but XenU couldn't be created successfully. >>>>> >>>>> Detailed Items: >>>>> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass] >>need >>>>manually reinstall kernel-xen rpm package. >>>>> 2. Boot Native Linux of FC6 Test3 [Pass] >>>>> 3. Boot Xen of FC6 Test3 [Pass] >>>>> 4. xend and xm commands are working. [Pass] >>>>> 5. XenU Domain creating failed. [__FAIL__] >>>>> 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin) >>>> [__FAIL__ (expected)] >>>>> 7. After manually copy VTI guest firmware, creating VTI domain >>>>[Pass] >>>>> 8. VTI domain with network supported [Pass] >>>>> 9. 2 VTI domains coexisting testing [Pass] >>>>> 10. Linux Kernel build in VTI domain [Pass] >>>>> 11. LTP testing in VTI domain [Pass] >>>>> 12. SMP VTI domain [Pass] >>>>> 13. SMP Xen0 [Pass] >>>>> 14. 1 VTI Windows 2k3 [Pass] a little slower. >>>>> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue >>>screen] >>>>> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] >>>>> >>>>> Other issues: >>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>> 2) XenU creating failure, please see attachment for the serial output. >>>>> >>>>> Best Regards, >>>>> Yongkang (Kangkang) $B%b%?%=%*(B >>>>> >>>>> _______________________________________________ >>>>> Xen-ia64-devel mailing list >>>>> Xen-ia64-devel at lists.xensource.com >>>>> http://lists.xensource.com/xen-ia64-devel >> >>_______________________________________________ >>Xen-ia64-devel mailing list >>Xen-ia64-devel at lists.xensource.com >>http://lists.xensource.com/xen-ia64-devel > >_______________________________________________ >Xen-ia64-devel mailing list >Xen-ia64-devel at lists.xensource.com >http://lists.xensource.com/xen-ia64-devel From takebe_akio at jp.fujitsu.com Thu Sep 21 02:14:29 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Thu, 21 Sep 2006 11:14:29 +0900 Subject: [Fedora-xen] [FYI] SELinux issue for create domU on xen Message-ID: <73C6DD23AB4DECtakebe_akio@jp.fujitsu.com> Hi, I have the following error. [root at tiger156 xen]# ls /boot/efi/efi/redhat/vmlinuz-2.6.17-1.2630. fc6xen /boot/efi/efi/redhat/vmlinuz-2.6.17-1.2630.fc6xen [root at tiger156 xen]# xm create -c fc6.para.conf Using config file "fc6.para.conf". Error: Kernel image does not exist: /boot/efi/efi/redhat/vmlinuz-2.6.17- 1.2630.fc6xen I don't mistake kernel path of domU config, but this error is shown. I could solve this issue by disabling SELinux. Best Regards, Akio Takebe From takebe_akio at jp.fujitsu.com Thu Sep 21 02:18:07 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Thu, 21 Sep 2006 11:18:07 +0900 Subject: [Fedora-xen] RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result In-Reply-To: <71C6DD1DD953F6takebe_akio@jp.fujitsu.com> References: <094BCE01AFBE9646AF220B0B3F367AAB588FCB@pdsmsx413.ccr.corp.intel.com> <71C6DD1DD953F6takebe_akio@jp.fujitsu.com> Message-ID: <74C6DD242D669Dtakebe_akio@jp.fujitsu.com> Hi, Yongkang I have a small mistake. Please try the following configuration. kernel = "vmlinuz-2.6.17-1.2630.fc6xen" ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img" memory = 512 name = "domU" vif = [ '' ] disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ] <----this root = "/dev/sda1 ro" <--------this extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" <--- -this Best Regards, Akio Takebe >Hi, Yongkang > >I think this issue is configuration mistakes. >Can you try the following configuration? >I cannot try it because I meet another issue... > >1. /etc/modprobe.conf for initrd of domU >The following configuration would solve the issue of booting domU. > [root at tiger156 xen]# cat /etc/modprobe.conf > #alias eth0 e1000 > #alias scsi_hostadapter mptbase > #alias scsi_hostadapter1 mptspi > alias eth0 xennet <----this > alias scsi_hostadapter xenblk <----and this > > >2. domU.conf >The following configuration would solve the issue of probing ide disk. > kernel = "vmlinuz-2.6.17-1.2630.fc6xen" > ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img" > memory = 512 > name = "domU" > vif = [ '' ] > disk = [ 'file:/xen/image/fc6.root.img,hda1,w' ] > root = "/dev/hda1 ro" > extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" <----this > > >Best Regards, > >Akio Takebe > >>Hi, >> >>I have reported 2 bugs to redhat bugzilla: >>[Bug 207227] New: Xen0 reboot command can not reboot Tiger4 machine. >>[Bug 207241] New: XenU domain can not be created successfully. >>New xenU created failure serial log has been pasted to the bug. >> >>I also notice FC6-test3 Xen0 operation is a little slower, compared with >>RHEL4u3. I assign 2 vcpus to Xen0. When I destroy domains or do some heavy >>IO operations, Xen0 operations will be blocked for a while. I didn't track >>this to bugzilla. >> >>There are also a lot of unaligned accessing from some applications. They >>should be common FC6-test3 issues. >> >>Sometime Xen0 monitor will print "Bug: soft lockup detected on CPU#0(or #1)" >> >>Best Regards, >>Yongkang (Kangkang) ???? >> >>>-----Original Message----- >>>From: xen-ia64-devel-bounces at lists.xensource.com >>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of You, >>>Yongkang >>>Sent: 2006?s??20?? 10:07 >>>To: Yang, Fred; y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>>Cc: xen-ia64-devel at lists.xensource.com >>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >>> >>>Hi Fred & Yoshi, >>> >>>The former XenU creating failure issue seemed to be the config issue. Now I >>>can create XenU. But XenU booting process met an old bug. It will cost a >>>long >>>time to check hard disk IRQ response from hda to hdh. >>> >>>After that, xenU met the problem of mounting root partition to start >>>services, >>>and then XenU booting failed (Kill init). I am not sure if it is because >>>initrd issue. >>>I will continue to check it. >>> >>>Best Regards, >>>Yongkang (Kangkang) ???? >>> >>>>-----Original Message----- >>>>From: xen-ia64-devel-bounces at lists.xensource.com >>>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of Yang, >>>>Fred >>>>Sent: 2006?s??20?? 8:26 >>>>To: y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>>>Cc: xen-ia64-devel at lists.xensource.com >>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >>>> >>>>Here it comes! >>>>-Fred >>>> >>>>>-----Original Message----- >>>>>From: y-oguchi at jp.fujitsu.com [mailto:y-oguchi at jp.fujitsu.com] >>>>>Sent: Tuesday, September 19, 2006 4:23 PM >>>>>To: Yang, Fred; fedora-xen at redhat.com >>>>>Cc: xen-ia64-devel at lists.xensource.com >>>>>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test >>>>>result >>>>> >>>>>Fred, Yongkang, >>>>> >>>>>> Other issues: >>>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>>> 2) XenU creating failure, please see attachment for the serial output. >>>>> >>>>>I can't find the attachment. >>>>>Could you repost the serial log? >>>>> >>>>>Thanks, >>>>>Yoshi Oguchi >>>>> >>>>>"Yang, Fred" wrote?? >>>>>> Following is the quick Xen test result with FC6 Test3. We will file >>>>>BZ for the issues tonight; the early data is to get community to fix Xen >>>>>issues ASAP >>>>>> Thanks, >>>>>> -Fred >>>>>> >>>>>> ==== >>>>>> I have followed Redhat instructions (FC6-test3 can not be installed >>>>>from CDs) to install FC6-Test3 and do some testing. Both Xen0 and VTI >>>>>can all boot up, but XenU couldn't be created successfully. >>>>>> >>>>>> Detailed Items: >>>>>> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass] >>>need >>>>>manually reinstall kernel-xen rpm package. >>>>>> 2. Boot Native Linux of FC6 Test3 [Pass] >>>>>> 3. Boot Xen of FC6 Test3 [Pass] >>>>>> 4. xend and xm commands are working. [Pass] >>>>>> 5. XenU Domain creating failed. [__FAIL__] >>>>>> 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin) >>>>> [__FAIL__ (expected)] >>>>>> 7. After manually copy VTI guest firmware, creating VTI domain >>>>>[Pass] >>>>>> 8. VTI domain with network supported [Pass] >>>>>> 9. 2 VTI domains coexisting testing [Pass] >>>>>> 10. Linux Kernel build in VTI domain [Pass] >>>>>> 11. LTP testing in VTI domain [Pass] >>>>>> 12. SMP VTI domain [Pass] >>>>>> 13. SMP Xen0 [Pass] >>>>>> 14. 1 VTI Windows 2k3 [Pass] a little slower. >>>>>> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue >>>>screen] >>>>>> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] >>>>>> >>>>>> Other issues: >>>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>>> 2) XenU creating failure, please see attachment for the serial output. >>>>>> >>>>>> Best Regards, >>>>>> Yongkang (Kangkang) ???? >>>>>> >>>>>> _______________________________________________ >>>>>> Xen-ia64-devel mailing list >>>>>> Xen-ia64-devel at lists.xensource.com >>>>>> http://lists.xensource.com/xen-ia64-devel >>> >>>_______________________________________________ >>>Xen-ia64-devel mailing list >>>Xen-ia64-devel at lists.xensource.com >>>http://lists.xensource.com/xen-ia64-devel >> >>_______________________________________________ >>Xen-ia64-devel mailing list >>Xen-ia64-devel at lists.xensource.com >>http://lists.xensource.com/xen-ia64-devel > > >_______________________________________________ >Xen-ia64-devel mailing list >Xen-ia64-devel at lists.xensource.com >http://lists.xensource.com/xen-ia64-devel From yongkang.you at intel.com Thu Sep 21 05:59:26 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 21 Sep 2006 13:59:26 +0800 Subject: [Fedora-xen] RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result Message-ID: <094BCE01AFBE9646AF220B0B3F367AAB588FDE@pdsmsx413.ccr.corp.intel.com> Hi Akio, Sorry for response late. I just tried with the config you provide (I changed xenU modprobe.conf and fstab). But unfortunately it still couldn't work. XenU booting still report can not find filesystem /dev/root/ and kernel panic. Well, after add "ide0=noprobe" etc. xenU won't complain to check hda, hdb etc. again. Thanks for this information. Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: Akio Takebe [mailto:takebe_akio at jp.fujitsu.com] >Sent: 2006?9?21? 10:18 >To: Akio Takebe; You, Yongkang; Yang, Fred; y-oguchi at jp.fujitsu.com; >fedora-xen at redhat.com >Cc: xen-ia64-devel at lists.xensource.com >Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result > >Hi, Yongkang > >I have a small mistake. > >Please try the following configuration. > kernel = "vmlinuz-2.6.17-1.2630.fc6xen" > ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img" > memory = 512 > name = "domU" > vif = [ '' ] > disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ] <----this > root = "/dev/sda1 ro" <--------this > extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" <--- >-this > >Best Regards, > >Akio Takebe > >>Hi, Yongkang >> >>I think this issue is configuration mistakes. >>Can you try the following configuration? >>I cannot try it because I meet another issue... >> >>1. /etc/modprobe.conf for initrd of domU >>The following configuration would solve the issue of booting domU. >> [root at tiger156 xen]# cat /etc/modprobe.conf >> #alias eth0 e1000 >> #alias scsi_hostadapter mptbase >> #alias scsi_hostadapter1 mptspi >> alias eth0 xennet <----this >> alias scsi_hostadapter xenblk <----and this >> >> >>2. domU.conf >>The following configuration would solve the issue of probing ide disk. >> kernel = "vmlinuz-2.6.17-1.2630.fc6xen" >> ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img" >> memory = 512 >> name = "domU" >> vif = [ '' ] >> disk = [ 'file:/xen/image/fc6.root.img,hda1,w' ] >> root = "/dev/hda1 ro" >> extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" ><----this >> >> >>Best Regards, >> >>Akio Takebe >> >>>Hi, >>> >>>I have reported 2 bugs to redhat bugzilla: >>>[Bug 207227] New: Xen0 reboot command can not reboot Tiger4 machine. >>>[Bug 207241] New: XenU domain can not be created successfully. >>>New xenU created failure serial log has been pasted to the bug. >>> >>>I also notice FC6-test3 Xen0 operation is a little slower, compared with >>>RHEL4u3. I assign 2 vcpus to Xen0. When I destroy domains or do some >heavy >>>IO operations, Xen0 operations will be blocked for a while. I didn't track >>>this to bugzilla. >>> >>>There are also a lot of unaligned accessing from some applications. They >>>should be common FC6-test3 issues. >>> >>>Sometime Xen0 monitor will print "Bug: soft lockup detected on CPU#0(or >#1)" >>> >>>Best Regards, >>>Yongkang (Kangkang) ???? >>> >>>>-----Original Message----- >>>>From: xen-ia64-devel-bounces at lists.xensource.com >>>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of You, >>>>Yongkang >>>>Sent: 2006?s??20?? 10:07 >>>>To: Yang, Fred; y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>>>Cc: xen-ia64-devel at lists.xensource.com >>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >>>> >>>>Hi Fred & Yoshi, >>>> >>>>The former XenU creating failure issue seemed to be the config issue. >Now I >>>>can create XenU. But XenU booting process met an old bug. It will cost a >>>>long >>>>time to check hard disk IRQ response from hda to hdh. >>>> >>>>After that, xenU met the problem of mounting root partition to start >>>>services, >>>>and then XenU booting failed (Kill init). I am not sure if it is because >>>>initrd issue. >>>>I will continue to check it. >>>> >>>>Best Regards, >>>>Yongkang (Kangkang) ???? >>>> >>>>>-----Original Message----- >>>>>From: xen-ia64-devel-bounces at lists.xensource.com >>>>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of >Yang, >>>>>Fred >>>>>Sent: 2006?s??20?? 8:26 >>>>>To: y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>>>>Cc: xen-ia64-devel at lists.xensource.com >>>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test >result >>>>> >>>>>Here it comes! >>>>>-Fred >>>>> >>>>>>-----Original Message----- >>>>>>From: y-oguchi at jp.fujitsu.com [mailto:y-oguchi at jp.fujitsu.com] >>>>>>Sent: Tuesday, September 19, 2006 4:23 PM >>>>>>To: Yang, Fred; fedora-xen at redhat.com >>>>>>Cc: xen-ia64-devel at lists.xensource.com >>>>>>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test >>>>>>result >>>>>> >>>>>>Fred, Yongkang, >>>>>> >>>>>>> Other issues: >>>>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>>>> 2) XenU creating failure, please see attachment for the serial output. >>>>>> >>>>>>I can't find the attachment. >>>>>>Could you repost the serial log? >>>>>> >>>>>>Thanks, >>>>>>Yoshi Oguchi >>>>>> >>>>>>"Yang, Fred" wrote?? >>>>>>> Following is the quick Xen test result with FC6 Test3. We will file >>>>>>BZ for the issues tonight; the early data is to get community to fix Xen >>>>>>issues ASAP >>>>>>> Thanks, >>>>>>> -Fred >>>>>>> >>>>>>> ==== >>>>>>> I have followed Redhat instructions (FC6-test3 can not be installed >>>>>>from CDs) to install FC6-Test3 and do some testing. Both Xen0 and >VTI >>>>>>can all boot up, but XenU couldn't be created successfully. >>>>>>> >>>>>>> Detailed Items: >>>>>>> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass] >>>>need >>>>>>manually reinstall kernel-xen rpm package. >>>>>>> 2. Boot Native Linux of FC6 Test3 [Pass] >>>>>>> 3. Boot Xen of FC6 Test3 [Pass] >>>>>>> 4. xend and xm commands are working. [Pass] >>>>>>> 5. XenU Domain creating failed. [__FAIL__] >>>>>>> 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin) >>>>>> [__FAIL__ (expected)] >>>>>>> 7. After manually copy VTI guest firmware, creating VTI domain >>>>>>[Pass] >>>>>>> 8. VTI domain with network supported [Pass] >>>>>>> 9. 2 VTI domains coexisting testing [Pass] >>>>>>> 10. Linux Kernel build in VTI domain [Pass] >>>>>>> 11. LTP testing in VTI domain [Pass] >>>>>>> 12. SMP VTI domain [Pass] >>>>>>> 13. SMP Xen0 [Pass] >>>>>>> 14. 1 VTI Windows 2k3 [Pass] a little slower. >>>>>>> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue >>>>>screen] >>>>>>> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] >>>>>>> >>>>>>> Other issues: >>>>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>>>> 2) XenU creating failure, please see attachment for the serial output. >>>>>>> >>>>>>> Best Regards, >>>>>>> Yongkang (Kangkang) ???? >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Xen-ia64-devel mailing list >>>>>>> Xen-ia64-devel at lists.xensource.com >>>>>>> http://lists.xensource.com/xen-ia64-devel >>>> >>>>_______________________________________________ >>>>Xen-ia64-devel mailing list >>>>Xen-ia64-devel at lists.xensource.com >>>>http://lists.xensource.com/xen-ia64-devel >>> >>>_______________________________________________ >>>Xen-ia64-devel mailing list >>>Xen-ia64-devel at lists.xensource.com >>>http://lists.xensource.com/xen-ia64-devel >> >> >>_______________________________________________ >>Xen-ia64-devel mailing list >>Xen-ia64-devel at lists.xensource.com >>http://lists.xensource.com/xen-ia64-devel From sanjamg at yahoo.com Thu Sep 21 12:21:29 2006 From: sanjamg at yahoo.com (Sanjam Garg) Date: Thu, 21 Sep 2006 05:21:29 -0700 (PDT) Subject: [Fedora-xen] IP addresses used by domU Message-ID: <20060921122129.80210.qmail@web34108.mail.mud.yahoo.com> Hi I am having FC5 guest run on top FC5 host.I have configured the virtual network card for FC5 in the guest operating system.This network card is expected to have been allotted many IP addresses.Is there a secure way in Xen to get information as to what are those IP's? Thanks Sanjam --------------------------------- Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aron at hp.com Thu Sep 21 14:44:39 2006 From: aron at hp.com (Aron Griffis) Date: Thu, 21 Sep 2006 10:44:39 -0400 Subject: [Fedora-xen] Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AAB588FCB@pdsmsx413.ccr.corp.intel.com> References: <094BCE01AFBE9646AF220B0B3F367AAB588FCA@pdsmsx413.ccr.corp.intel.com> <094BCE01AFBE9646AF220B0B3F367AAB588FCB@pdsmsx413.ccr.corp.intel.com> Message-ID: <20060921144438.GA15829@fc.hp.com> You, Yongkang wrote: [Wed Sep 20 2006, 01:46:22AM EDT] > [Bug 207227] New: Xen0 reboot command can not reboot Tiger4 machine. I think this is a duplicate of bug 203032. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203032 > [Bug 207241] New: XenU domain can not be created successfully. > New xenU created failure serial log has been pasted to the bug. I think the front-end and back-end drivers aren't communicating. I see the same problem with both network and block drivers when attempting xenguest-install. Aron From russell at flora.ca Thu Sep 21 14:49:51 2006 From: russell at flora.ca (Russell McOrmond) Date: Thu, 21 Sep 2006 10:49:51 -0400 Subject: [Fedora-xen] Recurring Zombie (XenU used as a web server) In-Reply-To: <20060908223542.A95158B9A3@www1.email.si> References: <20060908223542.A95158B9A3@www1.email.si> Message-ID: <4512A68F.60107@flora.ca> Gregor Pirnaver wrote: > For some weeks I have a problem with XenU domain used as web server. It is > turning into Zombie domain: I observed the same problem and filed a bug report about it which is active: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 Add yourself to the CC on that bug... -- Russell McOrmond, Internet Consultant: Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theatre, or portable media player from my cold dead hands!" From russell at flora.ca Thu Sep 21 14:58:45 2006 From: russell at flora.ca (Russell McOrmond) Date: Thu, 21 Sep 2006 10:58:45 -0400 Subject: [Fedora-xen] FC5 -- with new "development" Xen kernels/xend Message-ID: <4512A8A5.9060702@flora.ca> Just for kicks I tried the kernel-xen, xen and dependencies from the 'development' yum repository. When trying to create the XenU's it gave me a "Error: (22, 'Invalid argument')". With FC5 there was a xen0 kernel for the Xen0 and a xenU kernel that was put in each XenU. I believe that for the development branch (and FC6) that something different is being done, with the Xen0 using a 'kernel-xen' package: kernel-xen-2.6.17-1.2647.fc6 . I'm gathering that the XenU kernels are also different now (like what happened with the FC4 to FC5 switch), meaning I can't continue to use the xenU kernels I currently have installed. When I mentioned this issue on Bugzilla (In a different context of waiting for a new FC5 kernel with a specific patch https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 ), Herbert Xu mentioned I need to have XenU kernels with the PAE patch. Does anyone know which Fedora kernels to be putting in the XenU's if I'm wanting to use the new "development" xen and kernel-xen? -- Russell McOrmond, Internet Consultant: Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theatre, or portable media player from my cold dead hands!" From kwan at digitalhermit.com Thu Sep 21 15:04:31 2006 From: kwan at digitalhermit.com (Kwan Lowe) Date: Thu, 21 Sep 2006 11:04:31 -0400 (EDT) Subject: [Fedora-xen] Recurring Zombie (XenU used as a web server) In-Reply-To: <4512A68F.60107@flora.ca> References: <20060908223542.A95158B9A3@www1.email.si> <4512A68F.60107@flora.ca> Message-ID: <53094.12.43.115.17.1158851071.squirrel@digitalhermit.com> > Gregor Pirnaver wrote: >> For some weeks I have a problem with XenU domain used as web server. It is >> turning into Zombie domain: > > I observed the same problem and filed a bug report about it which is > active: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 > > Add yourself to the CC on that bug... > This is the bug report I'd found... It looks like yours is the same issue: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204468 -- * The Digital Hermit http://www.digitalhermit.com * Unix and Linux Solutions kwan at digitalhermit.com From berrange at redhat.com Thu Sep 21 15:07:07 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 21 Sep 2006 16:07:07 +0100 Subject: [Fedora-xen] FC5 -- with new "development" Xen kernels/xend In-Reply-To: <4512A8A5.9060702@flora.ca> References: <4512A8A5.9060702@flora.ca> Message-ID: <20060921150707.GD23547@redhat.com> On Thu, Sep 21, 2006 at 10:58:45AM -0400, Russell McOrmond wrote: > > Just for kicks I tried the kernel-xen, xen and dependencies from the > 'development' yum repository. When trying to create the XenU's it gave > me a "Error: (22, 'Invalid argument')". This (utterly useless[1]) error message usually indicates that the guest kernel you are trying to boot is incompatible with your hypervisor. ie, you tried to boot a baremetal kernel as a guest, or in this case you tried to boot a PAE enabled kernel on a non-PAE hypervisor. > Does anyone know which Fedora kernels to be putting in the XenU's if > I'm wanting to use the new "development" xen and kernel-xen? If its called 'kernel-xen' then its PAE enabled, if its called kernel-xenU then its non PAE enabled. So you must either use kernel-xen for both host & guest, or use kernel-xen0 and kernel-xenU. You can't mix use of kernel-xen with kernel-xenU Regards, Dan. [1] I'm working on patches to upstream Xen tools to give sensible error reporting instead of the current method which just returns -EINVAL everywhere :-( -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From clalance at redhat.com Thu Sep 21 15:10:26 2006 From: clalance at redhat.com (Chris Lalancette) Date: Thu, 21 Sep 2006 11:10:26 -0400 Subject: [Fedora-xen] FC5 -- with new "development" Xen kernels/xend In-Reply-To: <4512A8A5.9060702@flora.ca> References: <4512A8A5.9060702@flora.ca> Message-ID: <4512AB62.50304@redhat.com> Russell McOrmond wrote: > > Just for kicks I tried the kernel-xen, xen and dependencies from the > 'development' yum repository. When trying to create the XenU's it gave > me a "Error: (22, 'Invalid argument')". > > With FC5 there was a xen0 kernel for the Xen0 and a xenU kernel that > was put in each XenU. I believe that for the development branch (and > FC6) that something different is being done, with the Xen0 using a > 'kernel-xen' package: kernel-xen-2.6.17-1.2647.fc6 . I'm gathering > that the XenU kernels are also different now (like what happened with > the FC4 to FC5 switch), meaning I can't continue to use the xenU kernels > I currently have installed. > > > When I mentioned this issue on Bugzilla (In a different context of > waiting for a new FC5 kernel with a specific patch > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 ), Herbert > Xu mentioned I need to have XenU kernels with the PAE patch. > > Does anyone know which Fedora kernels to be putting in the XenU's if > I'm wanting to use the new "development" xen and kernel-xen? > Russell, If you look in /var/log/xend-debug.log, I believe you will see something along the lines of "Trying to start non-PAE kernel on PAE hypervisor". FC5 was originally put out with kernel-xen0, a non-PAE hypervisor/dom0, and kernel-xenU, a non-PAE domU kernel. During development for FC6, it was decided to 1) consolidate our -xen0 and -xenU into a single -xen kernel, and 2) make all Xen kernels PAE enabled. Since Xen does not support booting non-PAE paravirt kernels on a PAE hypervisor, or vice-versa, you will not be able to boot up "older" FC5 guests on a development FC6 kernel. That being said, we also decided to make a PAE Xen variant for FC5, also named kernel-xen. What I would suggest is to boot up the "older" FC5 kernel-xen0, and then boot up your guest(s) with the "older" kernel-xenU. Then do the following in the guest: 1) Edit /etc/modprobe.conf to make sure you have alias eth0 xennet alias scsi_hostadapter xenblk 2) Run "yum install kernel-xen". That will grab the PAE variant of the FC5 kernel. Once you have done this, you should be able to shutdown the guest, reboot the host into the FC6 "development" kernel, and then start up your guests, making sure to choose the kernel-xen kernel. I hope that helps. Chris Lalancette From russell at flora.ca Thu Sep 21 15:26:18 2006 From: russell at flora.ca (Russell McOrmond) Date: Thu, 21 Sep 2006 11:26:18 -0400 Subject: [Fedora-xen] Recurring Zombie (XenU used as a web server) In-Reply-To: <53094.12.43.115.17.1158851071.squirrel@digitalhermit.com> References: <20060908223542.A95158B9A3@www1.email.si> <4512A68F.60107@flora.ca> <53094.12.43.115.17.1158851071.squirrel@digitalhermit.com> Message-ID: <4512AF1A.7090606@flora.ca> >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 Kwan Lowe wrote: > This is the bug report I'd found... It looks like yours is the same issue: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204468 I've added a note there. If people can leave their consoles open and see if there is a kernel panic similar to the one that I reported, it may be the same xennet related bug. I've observed the same problem on a number of machines I administer (Mixed Intel, AMD, etc), and each time it seems to come down to the same xennet issue. -- Russell McOrmond, Internet Consultant: Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theatre, or portable media player from my cold dead hands!" From bishoptf at gmail.com Thu Sep 21 15:27:10 2006 From: bishoptf at gmail.com (Tom Bishop) Date: Thu, 21 Sep 2006 10:27:10 -0500 Subject: [Fedora-xen] fedora core 5 stock xen kernels nvidia drivers.... Message-ID: Doea anyine know when the stock fedora xen kernels will be compatiable with the nvidia binary kernels? I have read some posts on nvnet and ther are some ways listed that allows you to do it, but it would be nice if the stocked ones provided that. Also, the current stock Xen kernels do not allow you to "hide" pci cards from dom0, saw a post that mentioned it was turned on during th compile. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sanjamg at yahoo.com Thu Sep 21 16:49:24 2006 From: sanjamg at yahoo.com (Sanjam Garg) Date: Thu, 21 Sep 2006 09:49:24 -0700 (PDT) Subject: [Fedora-xen] IP addresses used by domU In-Reply-To: <27040411.2621158850635105.JavaMail.root@lisa.it-linux.cl> Message-ID: <20060921164924.6357.qmail@web34110.mail.mud.yahoo.com> Hi Thanks for replying.I want to get a list of IPs being used by a virtual machine(domU).I do not want to rule out the future possibility of a user wanting to run his own virtual machines on top of domU.So I need to figure out all the IPs that are being used by the virtual interface dedicated to a virtual machine.I have been constrained from using sniffing to detect IPs because a mean user could use some packet spoofing tool and trick dom0 to expect more IPs that actually present. Thanks once again Sanjam Garg "Patricio A. Bruna" wrote: Can you explain what you meant by: "Is there a secure way in Xen to get information as to what are those IP's"? ----- Original Message ----- From: Sanjam Garg To: xen-devel at lists.xensource.com Cc: fedora-xen at redhat.com Sent: jueves 21 de septiembre de 2006 08H21 GMT-0400 Subject: [Fedora-xen] IP addresses used by domU Hi I am having FC5 guest run on top FC5 host.I have configured the virtual network card for FC5 in the guest operating system.This network card is expected to have been allotted many IP addresses.Is there a secure way in Xen to get information as to what are those IP's? Thanks Sanjam --------------------------------- Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. --------------------------------- Get your email and more, right on the new Yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Thu Sep 21 17:21:47 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 21 Sep 2006 18:21:47 +0100 Subject: [Fedora-xen] IP addresses used by domU In-Reply-To: <20060921122129.80210.qmail@web34108.mail.mud.yahoo.com> References: <20060921122129.80210.qmail@web34108.mail.mud.yahoo.com> Message-ID: <20060921172146.GF23547@redhat.com> On Thu, Sep 21, 2006 at 05:21:29AM -0700, Sanjam Garg wrote: > Hi > > I am having FC5 guest run on top FC5 host.I have configured the virtual > network card for FC5 in the guest operating system.This network card is > expected to have been allotted many IP addresses.Is there a secure way > in Xen to get information as to what are those IP's? You don't mention what mode you've got the Xen Dom0 networking in, but I'll assume you're using the Fedora default which is bridging. With bridging, each DomU's virtual NIC gets pretty much directly connected to the physical LAN. As such Dom0 has no involvement in assigning IP addresses. The DomU will get its IP address either manually (DomU admin setting it in /etc/sysconfig/...) or automatically via DHCP. With bridging there isn't really any 100% reliable way to determine what the DomU's IP address is from Dom0. You can take a best guess by sniffing the network traffic on the vif, but that's all it is - a best 'guess'. Dan -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Thu Sep 21 18:02:56 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 21 Sep 2006 19:02:56 +0100 Subject: [Xen-devel] Re: [Fedora-xen] IP addresses used by domU In-Reply-To: <20060921175011.94155.qmail@web34112.mail.mud.yahoo.com> References: <20060921172146.GF23547@redhat.com> <20060921175011.94155.qmail@web34112.mail.mud.yahoo.com> Message-ID: <20060921180256.GG23547@redhat.com> On Thu, Sep 21, 2006 at 10:50:11AM -0700, Sanjam Garg wrote: > thanks a lot. > > Your assumption on bridging was correct...but the fact is that i > cant use sniffing to make a guess as my system has constraints laid > down by the intentions of the user who may use some packet source > IP spoofing to mislead dom0.if thats all that can be done then i > would need to do something more rigrous... When using bridging the network security concerns are pretty much exactly the same for those of a bare metal machine - the whole point of bridging is that the guest is connecting directly to the LAN as any physical machine would. Thus if you don't trust the admin of the DomU then don't let them connect straight to the network. For example, you can switch Xen to an alternative networking config where DomU's have to be forwarded & NAT'd using IPTables to get LAN access. If you really want to use bridging I guess you could try filtering out any traffic from the DomU's particular vif which has an unexpected source IP address, but really best bet is to go for NAT & remove their direct access Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From yunfeng.zhao at intel.com Thu Sep 21 18:20:29 2006 From: yunfeng.zhao at intel.com (Zhao, Yunfeng) Date: Fri, 22 Sep 2006 02:20:29 +0800 Subject: [Fedora-xen] Testing for Xen of FC6 Test3 -- 2 Message-ID: <10EA09EFD8728347A513008B6B0DA77A05ADEF@pdsmsx411.ccr.corp.intel.com> Hi We have finished some manual device model tests, installation tests and manual function tests. And following are some issues we found in the testing: 1. Blue screen happens when install Windows 2k with ACPI enabled. This issue should also exist in latest xen unstable tree. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207565 2. Fails to boot fc6 test3 IA32 guest with 2048MB mem size The qemu window disappeared when booting. The qemu.log has been pasted in the bug below. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207574 3. Using "vi" on SDL console of VMX guest may cause the guest to hang https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207577 This issue also exists in the latest xen unstable tree. 4. Cannot use special number keys (when open Num Lock) on SDL console of VMX guest. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207578 This isse also exists in the latest xen unstable tree. Detail info: Function Part: IA32 host: Installation of IA32 UP XP SP2/win2k3 Windows Guest w/ ACPI Pass Installation of IA32 UP XP SP2/win2k3 Windows Guest w/o ACPI PASS Installation of IA32 UP Windows 2k Guest w/ ACPI PASS Installation of IA32 UP Windows 2k Guest w/o ACPI FAIL Boot up IA32 UP XP SP2/win2k3/win2k Guest PASS Installation of IA32 FC6-test3 with Graphic/text mode PASS Boot up IA32 FC6-test3 UP GUest PASS Boot up IA32 FC6-test3 SMP Guest FAIL Boot up IA32 RHEL4 UP/SMP Guest PASS Network in VMX Guest PASS IA32e host: Installation of IA32 UP XP SP2/win2k3 Windows Guest w/ ACPI Pass Installation of IA32 UP XP SP2/win2k3 Windows Guest w/o ACPI PASS Installation of IA32 UP Windows 2k Guest w/ ACPI PASS Installation of IA32 UP Windows 2k Guest w/o ACPI FAIL Boot up IA32 UP XP SP2/win2k3/win2k Guest PASS Installation of IA32/IA32e FC6-test3 with Graphic/text mode PASS Boot up IA32 FC6-test3 UP GUest PASS Boot up IA32 FC6-test3 SMP Guest FAIL Boot up IA32e FC6-test3 UP Guest PASS Boot up IA32e FC6-test3 SMP Guest FAIL Boot up IA32 RHEL4 UP/SMP Guest PASS Boot up IA32e RHEL4 UP/SMP Guest PASS Network in VMX Guest PASS Device Model Part: 1. vi in VMX FAIL 2. 4 NIC devices (4 rtl8139 and 4 ne2k) PASS 3. Xwindows and Windows display in VMX PASS 4. Switch between Xwindows and Text mode in VMX PASS 5. keyboard in VMX FAIL 6. Qemu command in Qemu console Window PASS 7. USB mouse in Windows Guest PASS 8. SDL and VNC mode in VMX PASS Thanks Yunfeng From takebe_akio at jp.fujitsu.com Fri Sep 22 05:05:30 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Fri, 22 Sep 2006 14:05:30 +0900 Subject: [Fedora-xen] RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AAB588FDE@pdsmsx413.ccr.corp.intel.com> References: <094BCE01AFBE9646AF220B0B3F367AAB588FDE@pdsmsx413.ccr.corp.intel.com> Message-ID: <7EC6DE04B986CCtakebe_akio@jp.fujitsu.com> Hi, Yongkang and all I can boot up domU by using my special initrd without vif. I think mkinitrd of fc6 make initrd by using dom0 infomation. (for example dom0's /etc/fstab, dom0's pci infomaition. ) So when xm boot domU, domU kernel don't use bootparmeter of domU. The below is a recipe of making my special inird 1. copy initrd # mkdir tmp # cp /boot/efi/efi/redhat/initrd-2.6.18-1.2679.fc6xenU.img tmp/ 2. expand inird # cd tmp # gzip -cd ../initrd-2.6.18-1.2679.fc6xenU.img |cpio -id 3. modify init in initrd # vi init insmod /lib/ohci-hcd.ko echo "Loading ehci-hcd.ko module" insmod /lib/ehci-hcd.ko mount -t usbfs /proc/bus/usb /proc/bus/usb echo "Loading jbd.ko module" insmod /lib/jbd.ko echo "Loading ext3.ko module" insmod /lib/ext3.ko #echo "Loading scsi_mod.ko module" <<<<<< comment out #insmod /lib/scsi_mod.ko <<<<<< comment out #echo "Loading sd_mod.ko module" <<<<<< comment out #insmod /lib/sd_mod.ko <<<<<< comment out #echo "Loading scsi_transport_spi.ko module" <<<<<< comment out #insmod /lib/scsi_transport_spi.ko <<<<<< comment out #echo "Loading mptbase.ko module" <<<<<< comment out #insmod /lib/mptbase.ko <<<<<< comment out #echo "Loading mptscsih.ko module" <<<<<< comment out #insmod /lib/mptscsih.ko <<<<<< comment out #echo "Loading mptspi.ko module" <<<<<< comment out #insmod /lib/mptspi.ko <<<<<< comment out echo "Loading xenblk.ko module" insmod /lib/xenblk.ko mkblkdevs #resume LABEL=SWAP-sda3 <<<<<< comment out echo Creating root device. mkrootdev -t ext3 -o defaults,ro sda1 <<<../initrd-new.img 5. my domU configuration kernel = "/boot/efi/efi/redhat/vmlinuz-2.6.18-1.2679.fc6xen" ramdisk = "/xen/initrd-new.img" memory = 1024 name = "fc6.DomU" #vif = [ '' ] disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ] root = "/dev/sda1 ro" extra = "4 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe selinux=0 rhgb" 6. etc 6.1. copy modlues into domU image file # mount -o loop domU.img /mnt # cp -a /lib/modules/2.6.18-1.2679.fc6xen/ /mnt/lib/modules/ 6.2. disable selinux # vi /etc/sysconfig/selinux SELINUX=disabled <<<< change enforcing to disabled 6.3. modify /etc/fstab in domU.img /dev/sda1 / ext3 defaults 1 1 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 But I cannot use network on domU. I'll check the src.rpm of kernel-xen. Best Regards, Akio Takebe >Hi Akio, > >Sorry for response late. I just tried with the config you provide (I >changed xenU modprobe.conf and fstab). But unfortunately it still couldn't >work. XenU booting still report can not find filesystem /dev/root/ and >kernel panic. > >Well, after add "ide0=noprobe" etc. xenU won't complain to check hda, hdb >etc. again. Thanks for this information. > >Best Regards, >Yongkang (Kangkang) $B%b%?%=%*(B >>-----Original Message----- >>From: Akio Takebe [mailto:takebe_akio at jp.fujitsu.com] >>Sent: 2006$B%Hs%d%D(B21$B%M%f(B 10:18 >>To: Akio Takebe; You, Yongkang; Yang, Fred; y-oguchi at jp.fujitsu.com; >>fedora-xen at redhat.com >>Cc: xen-ia64-devel at lists.xensource.com >>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >> >>Hi, Yongkang >> >>I have a small mistake. >> >>Please try the following configuration. >> kernel = "vmlinuz-2.6.17-1.2630.fc6xen" >> ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img" >> memory = 512 >> name = "domU" >> vif = [ '' ] >> disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ] <----this >> root = "/dev/sda1 ro" <--------this >> extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" <--- >>-this >> >>Best Regards, >> >>Akio Takebe >> >>>Hi, Yongkang >>> >>>I think this issue is configuration mistakes. >>>Can you try the following configuration? >>>I cannot try it because I meet another issue... >>> >>>1. /etc/modprobe.conf for initrd of domU >>>The following configuration would solve the issue of booting domU. >>> [root at tiger156 xen]# cat /etc/modprobe.conf >>> #alias eth0 e1000 >>> #alias scsi_hostadapter mptbase >>> #alias scsi_hostadapter1 mptspi >>> alias eth0 xennet <----this >>> alias scsi_hostadapter xenblk <----and this >>> >>> >>>2. domU.conf >>>The following configuration would solve the issue of probing ide disk. >>> kernel = "vmlinuz-2.6.17-1.2630.fc6xen" >>> ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img" >>> memory = 512 >>> name = "domU" >>> vif = [ '' ] >>> disk = [ 'file:/xen/image/fc6.root.img,hda1,w' ] >>> root = "/dev/hda1 ro" >>> extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" >><----this >>> >>> >>>Best Regards, >>> >>>Akio Takebe >>> >>>>Hi, >>>> >>>>I have reported 2 bugs to redhat bugzilla: >>>>[Bug 207227] New: Xen0 reboot command can not reboot Tiger4 machine. >>>>[Bug 207241] New: XenU domain can not be created successfully. >>>>New xenU created failure serial log has been pasted to the bug. >>>> >>>>I also notice FC6-test3 Xen0 operation is a little slower, compared with >>>>RHEL4u3. I assign 2 vcpus to Xen0. When I destroy domains or do some >>heavy >>>>IO operations, Xen0 operations will be blocked for a while. I didn't track >>>>this to bugzilla. >>>> >>>>There are also a lot of unaligned accessing from some applications. They >>>>should be common FC6-test3 issues. >>>> >>>>Sometime Xen0 monitor will print "Bug: soft lockup detected on CPU#0(or >>#1)" >>>> >>>>Best Regards, >>>>Yongkang (Kangkang) $B!&d'%=!&%9!&%'(B >>>> >>>>>-----Original Message----- >>>>>From: xen-ia64-devel-bounces at lists.xensource.com >>>>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of You, >>>>>Yongkang >>>>>Sent: 2006$B!&%M(Bs$B!&h'%H(B20$B!&%X!&k(B10:07 >>>>>To: Yang, Fred; y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>>>>Cc: xen-ia64-devel at lists.xensource.com >>>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test >>>>>result >>>>> >>>>>Hi Fred & Yoshi, >>>>> >>>>>The former XenU creating failure issue seemed to be the config issue. >>Now I >>>>>can create XenU. But XenU booting process met an old bug. It will cost a >>>>>long >>>>>time to check hard disk IRQ response from hda to hdh. >>>>> >>>>>After that, xenU met the problem of mounting root partition to start >>>>>services, >>>>>and then XenU booting failed (Kill init). I am not sure if it is because >>>>>initrd issue. >>>>>I will continue to check it. >>>>> >>>>>Best Regards, >>>>>Yongkang (Kangkang) $B!&d'%=!&%9!&%'(B >>>>> >>>>>>-----Original Message----- >>>>>>From: xen-ia64-devel-bounces at lists.xensource.com >>>>>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of >>Yang, >>>>>>Fred >>>>>>Sent: 2006$B!&%M(Bs$B!&h'%H(B20$B!&%X!&k(B8:26 >>>>>>To: y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>>>>>Cc: xen-ia64-devel at lists.xensource.com >>>>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test >>result >>>>>> >>>>>>Here it comes! >>>>>>-Fred >>>>>> >>>>>>>-----Original Message----- >>>>>>>From: y-oguchi at jp.fujitsu.com [mailto:y-oguchi at jp.fujitsu.com] >>>>>>>Sent: Tuesday, September 19, 2006 4:23 PM >>>>>>>To: Yang, Fred; fedora-xen at redhat.com >>>>>>>Cc: xen-ia64-devel at lists.xensource.com >>>>>>>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test >>>>>>>result >>>>>>> >>>>>>>Fred, Yongkang, >>>>>>> >>>>>>>> Other issues: >>>>>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>>>>> 2) XenU creating failure, please see attachment for the serial >>>>>>>> output. >>>>>>> >>>>>>>I can't find the attachment. >>>>>>>Could you repost the serial log? >>>>>>> >>>>>>>Thanks, >>>>>>>Yoshi Oguchi >>>>>>> >>>>>>>"Yang, Fred" wrote$B!#%1!&%&(B >>>>>>>> Following is the quick Xen test result with FC6 Test3. We will file >>>>>>>BZ for the issues tonight; the early data is to get community to fix >>>>>>>Xen >>>>>>>issues ASAP >>>>>>>> Thanks, >>>>>>>> -Fred >>>>>>>> >>>>>>>> ==== >>>>>>>> I have followed Redhat instructions (FC6-test3 can not be installed >>>>>>>from CDs) to install FC6-Test3 and do some testing. Both Xen0 and >>VTI >>>>>>>can all boot up, but XenU couldn't be created successfully. >>>>>>>> >>>>>>>> Detailed Items: >>>>>>>> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass] >>>>>need >>>>>>>manually reinstall kernel-xen rpm package. >>>>>>>> 2. Boot Native Linux of FC6 Test3 [Pass] >>>>>>>> 3. Boot Xen of FC6 Test3 [Pass] >>>>>>>> 4. xend and xm commands are working. [Pass] >>>>>>>> 5. XenU Domain creating failed. [__FAIL__] >>>>>>>> 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin) >>>>>>> [__FAIL__ (expected)] >>>>>>>> 7. After manually copy VTI guest firmware, creating VTI domain >>>>>>>[Pass] >>>>>>>> 8. VTI domain with network supported [Pass] >>>>>>>> 9. 2 VTI domains coexisting testing [Pass] >>>>>>>> 10. Linux Kernel build in VTI domain [Pass] >>>>>>>> 11. LTP testing in VTI domain [Pass] >>>>>>>> 12. SMP VTI domain [Pass] >>>>>>>> 13. SMP Xen0 [Pass] >>>>>>>> 14. 1 VTI Windows 2k3 [Pass] a little slower. >>>>>>>> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue >>>>>>screen] >>>>>>>> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] >>>>>>>> >>>>>>>> Other issues: >>>>>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>>>>> 2) XenU creating failure, please see attachment for the serial >>>>>>>> output. >>>>>>>> >>>>>>>> Best Regards, >>>>>>>> Yongkang (Kangkang) $B!&d'%=!&%9!&%'(B >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Xen-ia64-devel mailing list >>>>>>>> Xen-ia64-devel at lists.xensource.com >>>>>>>> http://lists.xensource.com/xen-ia64-devel >>>>> >>>>>_______________________________________________ >>>>>Xen-ia64-devel mailing list >>>>>Xen-ia64-devel at lists.xensource.com >>>>>http://lists.xensource.com/xen-ia64-devel >>>> >>>>_______________________________________________ >>>>Xen-ia64-devel mailing list >>>>Xen-ia64-devel at lists.xensource.com >>>>http://lists.xensource.com/xen-ia64-devel >>> >>> >>>_______________________________________________ >>>Xen-ia64-devel mailing list >>>Xen-ia64-devel at lists.xensource.com >>>http://lists.xensource.com/xen-ia64-devel -------------- next part -------------- A non-text attachment was scrubbed... Name: domU_boot.log Type: application/octet-stream Size: 8905 bytes Desc: not available URL: From takebe_akio at jp.fujitsu.com Fri Sep 22 09:32:29 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Fri, 22 Sep 2006 18:32:29 +0900 Subject: [Fedora-xen] Re: blkbk/netbk modules fail to load on fedora xen/ia64 In-Reply-To: <20060922022456.GA13132@fc.hp.com> References: <20060922011305.GA28162@fc.hp.com> <7AC6DDE9DEC138takebe_akio@jp.fujitsu.com> <20060922022456.GA13132@fc.hp.com> Message-ID: <83C6DE2A05ADADtakebe_akio@jp.fujitsu.com> Hi, Aron and all >> We may have to change dom0_mem of FC6 default to 1GB. >> But I think the best fix is (1) statically link the modules. >> (Because all kernel-xen need blkbk/netbk and xenblk/net. >> ide module is also static link. And because xen community member >> test the statically linked modules, I think the statically linked >> modules is stabler than the dynamic linked modlues.) > >I don't mind asking RH to statically link the modules if there is good >reason. However I don't understand why it is needed. 512M is a lot >of memory! How can it be filled to the extent that the blkbk/netbk >modules won't load? What are their requirements? > Please see the following error message. FATAL: Error inserting blkbk (/lib/modules/2.6.17-1.2566.fc6xen/kernel/drivers/xen/ blkback/blkbk.ko): Cannot allocate memory modprobe: page allocation failure. order:8, mode:0xd0 blkbk.ko request order8 pages in blkif_init(). order8 pages is very big. page_alloc() probably fail when it is requested order8 pages, because page_alloc() must return contiguos pages. Especially after boot and terminate some processes, page_alloc() is hard to allocate order8 pages. So when dom0_mem=1G, page_allo() is easier to allocate them than dom0_mem=512M. And when statically linked modules, page_alloc() is the easest to allocate them. I think implementation of blk/netbk.ko is not good. But I think statically linked modules is the best solution in your solutions. And I think this issue is happened in the case of not only ia64, but also x86. (In the case of x86, default size of dom0_mem is physcal memory size. So this issue is hard to be happened.) Please commets. FYI https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202971 Best Regards, Akio Takebe From yongkang.you at intel.com Fri Sep 22 10:29:46 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Fri, 22 Sep 2006 18:29:46 +0800 Subject: [Fedora-xen] RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result Message-ID: <094BCE01AFBE9646AF220B0B3F367AAB588FFA@pdsmsx413.ccr.corp.intel.com> Hi Akio, Sorry for response late. It is very detailed instructions. :) I found my initrd doesn't preload xenblk.ko. Then it failed to create root device. Now I can create xenU too with your guide. Thank you so much. But did you notice xenU booting is a little slow? Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: Akio Takebe [mailto:takebe_akio at jp.fujitsu.com] >Sent: 2006?9?22? 13:06 >To: You, Yongkang; Yang, Fred; y-oguchi at jp.fujitsu.com; >fedora-xen at redhat.com >Cc: xen-ia64-devel at lists.xensource.com; Akio Takebe >Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result > >Hi, Yongkang and all > >I can boot up domU by using my special initrd without vif. >I think mkinitrd of fc6 make initrd by using dom0 infomation. >(for example dom0's /etc/fstab, dom0's pci infomaition. ) >So when xm boot domU, domU kernel don't use bootparmeter of domU. > >The below is a recipe of making my special inird > >1. copy initrd ># mkdir tmp ># cp /boot/efi/efi/redhat/initrd-2.6.18-1.2679.fc6xenU.img tmp/ > >2. expand inird ># cd tmp ># gzip -cd ../initrd-2.6.18-1.2679.fc6xenU.img |cpio -id > >3. modify init in initrd ># vi init > insmod /lib/ohci-hcd.ko > echo "Loading ehci-hcd.ko module" > insmod /lib/ehci-hcd.ko > mount -t usbfs /proc/bus/usb /proc/bus/usb > echo "Loading jbd.ko module" > insmod /lib/jbd.ko > echo "Loading ext3.ko module" > insmod /lib/ext3.ko > #echo "Loading scsi_mod.ko module" <<<<<< comment out > #insmod /lib/scsi_mod.ko <<<<<< comment out > #echo "Loading sd_mod.ko module" <<<<<< comment out > #insmod /lib/sd_mod.ko <<<<<< comment out > #echo "Loading scsi_transport_spi.ko module" <<<<<< comment out > #insmod /lib/scsi_transport_spi.ko <<<<<< comment out > #echo "Loading mptbase.ko module" <<<<<< comment out > #insmod /lib/mptbase.ko <<<<<< comment out > #echo "Loading mptscsih.ko module" <<<<<< comment out > #insmod /lib/mptscsih.ko <<<<<< comment out > #echo "Loading mptspi.ko module" <<<<<< comment out > #insmod /lib/mptspi.ko <<<<<< comment out > echo "Loading xenblk.ko module" > insmod /lib/xenblk.ko > mkblkdevs > #resume LABEL=SWAP-sda3 <<<<<< comment >out > echo Creating root device. > mkrootdev -t ext3 -o defaults,ro sda1 <<< echo Mounting root filesystem. > mount /sysroot > echo Setting up other filesystems. > setuproot > echo Switching to new root and running init. > switchroot >4. make new initrd ># find . -print | cpio --quiet -c -o | gzip -9 >../initrd-new.img > >5. my domU configuration >kernel = "/boot/efi/efi/redhat/vmlinuz-2.6.18-1.2679.fc6xen" >ramdisk = "/xen/initrd-new.img" >memory = 1024 >name = "fc6.DomU" >#vif = [ '' ] >disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ] >root = "/dev/sda1 ro" >extra = "4 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe selinux=0 >rhgb" > >6. etc > 6.1. copy modlues into domU image file > # mount -o loop domU.img /mnt > # cp -a /lib/modules/2.6.18-1.2679.fc6xen/ /mnt/lib/modules/ > 6.2. disable selinux > # vi /etc/sysconfig/selinux > SELINUX=disabled <<<< change enforcing to disabled > 6.3. modify /etc/fstab in domU.img > /dev/sda1 / ext3 defaults 1 1 > devpts /dev/pts devpts gid=5,mode=620 0 0 > tmpfs /dev/shm tmpfs defaults 0 0 > proc /proc proc defaults 0 0 > sysfs /sys sysfs defaults 0 0 > > >But I cannot use network on domU. >I'll check the src.rpm of kernel-xen. > >Best Regards, > >Akio Takebe > > >>Hi Akio, >> >>Sorry for response late. I just tried with the config you provide (I >>changed xenU modprobe.conf and fstab). But unfortunately it still couldn't >>work. XenU booting still report can not find filesystem /dev/root/ and >>kernel panic. >> >>Well, after add "ide0=noprobe" etc. xenU won't complain to check hda, hdb >>etc. again. Thanks for this information. >> >>Best Regards, >>Yongkang (Kangkang) ???? >>>-----Original Message----- >>>From: Akio Takebe [mailto:takebe_akio at jp.fujitsu.com] >>>Sent: 2006????21?? 10:18 >>>To: Akio Takebe; You, Yongkang; Yang, Fred; y-oguchi at jp.fujitsu.com; >>>fedora-xen at redhat.com >>>Cc: xen-ia64-devel at lists.xensource.com >>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result >>> >>>Hi, Yongkang >>> >>>I have a small mistake. >>> >>>Please try the following configuration. >>> kernel = "vmlinuz-2.6.17-1.2630.fc6xen" >>> ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img" >>> memory = 512 >>> name = "domU" >>> vif = [ '' ] >>> disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ] <----this >>> root = "/dev/sda1 ro" <--------this >>> extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" ><--- >>>-this >>> >>>Best Regards, >>> >>>Akio Takebe >>> >>>>Hi, Yongkang >>>> >>>>I think this issue is configuration mistakes. >>>>Can you try the following configuration? >>>>I cannot try it because I meet another issue... >>>> >>>>1. /etc/modprobe.conf for initrd of domU >>>>The following configuration would solve the issue of booting domU. >>>> [root at tiger156 xen]# cat /etc/modprobe.conf >>>> #alias eth0 e1000 >>>> #alias scsi_hostadapter mptbase >>>> #alias scsi_hostadapter1 mptspi >>>> alias eth0 xennet <----this >>>> alias scsi_hostadapter xenblk <----and this >>>> >>>> >>>>2. domU.conf >>>>The following configuration would solve the issue of probing ide disk. >>>> kernel = "vmlinuz-2.6.17-1.2630.fc6xen" >>>> ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img" >>>> memory = 512 >>>> name = "domU" >>>> vif = [ '' ] >>>> disk = [ 'file:/xen/image/fc6.root.img,hda1,w' ] >>>> root = "/dev/hda1 ro" >>>> extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" >>><----this >>>> >>>> >>>>Best Regards, >>>> >>>>Akio Takebe >>>> >>>>>Hi, >>>>> >>>>>I have reported 2 bugs to redhat bugzilla: >>>>>[Bug 207227] New: Xen0 reboot command can not reboot Tiger4 >machine. >>>>>[Bug 207241] New: XenU domain can not be created successfully. >>>>>New xenU created failure serial log has been pasted to the bug. >>>>> >>>>>I also notice FC6-test3 Xen0 operation is a little slower, compared with >>>>>RHEL4u3. I assign 2 vcpus to Xen0. When I destroy domains or do some >>>heavy >>>>>IO operations, Xen0 operations will be blocked for a while. I didn't track >>>>>this to bugzilla. >>>>> >>>>>There are also a lot of unaligned accessing from some applications. They >>>>>should be common FC6-test3 issues. >>>>> >>>>>Sometime Xen0 monitor will print "Bug: soft lockup detected on >CPU#0(or >>>#1)" >>>>> >>>>>Best Regards, >>>>>Yongkang (Kangkang) ??????? >>>>> >>>>>>-----Original Message----- >>>>>>From: xen-ia64-devel-bounces at lists.xensource.com >>>>>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of >You, >>>>>>Yongkang >>>>>>Sent: 2006??s???20????10:07 >>>>>>To: Yang, Fred; y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>>>>>Cc: xen-ia64-devel at lists.xensource.com >>>>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test >>>>>>result >>>>>> >>>>>>Hi Fred & Yoshi, >>>>>> >>>>>>The former XenU creating failure issue seemed to be the config issue. >>>Now I >>>>>>can create XenU. But XenU booting process met an old bug. It will cost >a >>>>>>long >>>>>>time to check hard disk IRQ response from hda to hdh. >>>>>> >>>>>>After that, xenU met the problem of mounting root partition to start >>>>>>services, >>>>>>and then XenU booting failed (Kill init). I am not sure if it is because >>>>>>initrd issue. >>>>>>I will continue to check it. >>>>>> >>>>>>Best Regards, >>>>>>Yongkang (Kangkang) ??????? >>>>>> >>>>>>>-----Original Message----- >>>>>>>From: xen-ia64-devel-bounces at lists.xensource.com >>>>>>>[mailto:xen-ia64-devel-bounces at lists.xensource.com] On Behalf Of >>>Yang, >>>>>>>Fred >>>>>>>Sent: 2006??s???20????8:26 >>>>>>>To: y-oguchi at jp.fujitsu.com; fedora-xen at redhat.com >>>>>>>Cc: xen-ia64-devel at lists.xensource.com >>>>>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test >>>result >>>>>>> >>>>>>>Here it comes! >>>>>>>-Fred >>>>>>> >>>>>>>>-----Original Message----- >>>>>>>>From: y-oguchi at jp.fujitsu.com [mailto:y-oguchi at jp.fujitsu.com] >>>>>>>>Sent: Tuesday, September 19, 2006 4:23 PM >>>>>>>>To: Yang, Fred; fedora-xen at redhat.com >>>>>>>>Cc: xen-ia64-devel at lists.xensource.com >>>>>>>>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test >>>>>>>>result >>>>>>>> >>>>>>>>Fred, Yongkang, >>>>>>>> >>>>>>>>> Other issues: >>>>>>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>>>>>> 2) XenU creating failure, please see attachment for the serial >>>>>>>>> output. >>>>>>>> >>>>>>>>I can't find the attachment. >>>>>>>>Could you repost the serial log? >>>>>>>> >>>>>>>>Thanks, >>>>>>>>Yoshi Oguchi >>>>>>>> >>>>>>>>"Yang, Fred" wrote???? >>>>>>>>> Following is the quick Xen test result with FC6 Test3. We will file >>>>>>>>BZ for the issues tonight; the early data is to get community to fix >>>>>>>>Xen >>>>>>>>issues ASAP >>>>>>>>> Thanks, >>>>>>>>> -Fred >>>>>>>>> >>>>>>>>> ==== >>>>>>>>> I have followed Redhat instructions (FC6-test3 can not be installed >>>>>>>>from CDs) to install FC6-Test3 and do some testing. Both Xen0 and >>>VTI >>>>>>>>can all boot up, but XenU couldn't be created successfully. >>>>>>>>> >>>>>>>>> Detailed Items: >>>>>>>>> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost >Pass] >>>>>>need >>>>>>>>manually reinstall kernel-xen rpm package. >>>>>>>>> 2. Boot Native Linux of FC6 Test3 [Pass] >>>>>>>>> 3. Boot Xen of FC6 Test3 [Pass] >>>>>>>>> 4. xend and xm commands are working. [Pass] >>>>>>>>> 5. XenU Domain creating failed. [__FAIL__] >>>>>>>>> 6. Missing VTI guest firmware >(/usr/lib/xen/boot/guest_firmware.bin) >>>>>>>> [__FAIL__ (expected)] >>>>>>>>> 7. After manually copy VTI guest firmware, creating VTI domain >>>>>>>>[Pass] >>>>>>>>> 8. VTI domain with network supported [Pass] >>>>>>>>> 9. 2 VTI domains coexisting testing [Pass] >>>>>>>>> 10. Linux Kernel build in VTI domain [Pass] >>>>>>>>> 11. LTP testing in VTI domain [Pass] >>>>>>>>> 12. SMP VTI domain [Pass] >>>>>>>>> 13. SMP Xen0 [Pass] >>>>>>>>> 14. 1 VTI Windows 2k3 [Pass] a little slower. >>>>>>>>> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows >blue >>>>>>>screen] >>>>>>>>> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__] >>>>>>>>> >>>>>>>>> Other issues: >>>>>>>>> 1) Xen0 operation is a little slower than RHEL4u3. >>>>>>>>> 2) XenU creating failure, please see attachment for the serial >>>>>>>>> output. >>>>>>>>> >>>>>>>>> Best Regards, >>>>>>>>> Yongkang (Kangkang) ??????? >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Xen-ia64-devel mailing list >>>>>>>>> Xen-ia64-devel at lists.xensource.com >>>>>>>>> http://lists.xensource.com/xen-ia64-devel >>>>>> >>>>>>_______________________________________________ >>>>>>Xen-ia64-devel mailing list >>>>>>Xen-ia64-devel at lists.xensource.com >>>>>>http://lists.xensource.com/xen-ia64-devel >>>>> >>>>>_______________________________________________ >>>>>Xen-ia64-devel mailing list >>>>>Xen-ia64-devel at lists.xensource.com >>>>>http://lists.xensource.com/xen-ia64-devel >>>> >>>> >>>>_______________________________________________ >>>>Xen-ia64-devel mailing list >>>>Xen-ia64-devel at lists.xensource.com >>>>http://lists.xensource.com/xen-ia64-devel From takebe_akio at jp.fujitsu.com Fri Sep 22 10:38:10 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Fri, 22 Sep 2006 19:38:10 +0900 Subject: [Fedora-xen] RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AAB588FFA@pdsmsx413.ccr.corp.intel.com> References: <094BCE01AFBE9646AF220B0B3F367AAB588FFA@pdsmsx413.ccr.corp.intel.com> Message-ID: <87C6DE3332D18Ctakebe_akio@jp.fujitsu.com> Hi, Yongkang >Hi Akio, > >Sorry for response late. It is very detailed instructions. :) >I found my initrd doesn't preload xenblk.ko. Then it failed to create root >device. >Now I can create xenU too with your guide. Thank you so much. >But did you notice xenU booting is a little slow? Yes, starting sendmail is very slow. I also suspected dom0/domU hanged up. :-) Best Regards, Akio Takebe From philipp.jaggi at snct.lu Fri Sep 22 14:29:06 2006 From: philipp.jaggi at snct.lu (Philipp =?ISO-8859-2?Q?J=E4ggi?=) Date: Fri, 22 Sep 2006 16:29:06 +0200 Subject: [Fedora-xen] BUG: soft lockup detected on CPU#0! Message-ID: Dear Readers Got a strange Problem when I try to start an application. My System: Distro: Fedora Core 5 Kernel: 2.6.17-1.2187_FC5xen0 CPU: Inter Xeon 3.20 GHz RAM: 2.5GB Guest and Dom0 are Fedora Core 5 with 2.6.17-1.2187 Kernels. My Error MSG: BUG: soft lockup detected on CPU#0! softlockup_tick+0x9f/0xb4 timer_interrupt+0x4fc/0x544 hypervisor_callback+0x3d/0x48 handle_IRQ_event+0x42/0x85 __do_IRQ+0x8d/0xdc do_IRQ+0x1a/0x25 evtchn_do_upcall+0x66/0x9f hypervisor_callback+0x3d/0x48 general_protection+0x0/0xc failsafe_callback+0xe/0x40 write_ldt_entry+0xd4/0xdb write_ldt+0x18d/0x1af syscall_call+0x7/0xb After this message, you can see in XenTop that my guest is using 100% of the cpu. After a while, the dom0 is rebooting from itself. But between the crash of the guest and the restart of the dom0, I can work in the dom0. I really can't understand this. Thanks a lot for any help or link... bye Philipp =============================================== Philipp J?ggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 mailto: philipp.jaeggi at snct.lu -------------- next part -------------- An HTML attachment was scrubbed... URL: From francesco.laricchiuta at gmail.com Fri Sep 22 18:26:07 2006 From: francesco.laricchiuta at gmail.com (Francesco Laricchiuta) Date: Fri, 22 Sep 2006 20:26:07 +0200 Subject: [Fedora-xen] Xen0 booting problem with Fedora Core 5 Message-ID: <54aaf81c0609221126j4497696dp9b6a870da2a7fb3f@mail.gmail.com> Hi, i want to install xen 3.0.2 on Fedora Core 5 ( http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5), but i have a problem with boot xen0. i listed all xend-debug.log and xend.log..... - xend-debug.log Exception in thread Thread-3: Traceback (most recent call last): File "/usr/lib/python2.4/threading.py", line 442, in __bootstrap self.run() File "/usr/lib/python2.4/threading.py", line 422, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.4/site-packages/xen/xend/server/XMLRPCServer.py", line 94, in run self.server = UnixXMLRPCServer(XML_RPC_SOCKET, False) File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 152, in __init__ os.makedirs(parent, stat.S_IRWXU) File "/usr/lib/python2.4/os.py", line 159, in makedirs mkdir(name, mode) OSError: [Errno 13] Permission denied: '/var/run/xend' - xend.log [2006-09-22 19:23:29 xend] INFO (SrvDaemon:283) Xend Daemon started [2006-09-22 19:23:29 xend] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-09-22 19:23:29 xend.XendDomainInfo] DEBUG (XendDomainInfo:207) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 20918759483L, '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': 442720, 'maxmem_kb': -4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-09-22 19:23:29 xend.XendDomainInfo] INFO (XendDomainInfo:219) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-09-22 19:23:29 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm path in store for existing domain 0 [2006-09-22 19:23:29 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': '433', 'maxmem': '433'} [2006-09-22 19:23:29 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '443392', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-09-22 19:23:29 xend] DEBUG (XendDomain:153) number of vcpus to use is 0 [2006-09-22 19:23:29 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch [2006-09-22 19:27:31 xend] INFO (SrvDaemon:283) Xend Daemon started [2006-09-22 19:27:31 xend] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-09-22 19:27:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:207) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 20638534618L, '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': 442720, 'maxmem_kb': -4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-09-22 19:27:31 xend.XendDomainInfo] INFO (XendDomainInfo:219) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-09-22 19:27:31 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm path in store for existing domain 0 [2006-09-22 19:27:31 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': '433', 'maxmem': '433'} [2006-09-22 19:27:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '443392', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-09-22 19:27:31 xend] DEBUG (XendDomain:153) number of vcpus to use is 0 [2006-09-22 19:27:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch [2006-09-22 19:35:03 xend] INFO (SrvDaemon:283) Xend Daemon started [2006-09-22 19:35:03 xend] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-09-22 19:35:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:207) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 20321279301L, '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': 442720, 'maxmem_kb': -4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0}) [2006-09-22 19:35:03 xend.XendDomainInfo] INFO (XendDomainInfo:219) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-09-22 19:35:03 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm path in store for existing domain 0 [2006-09-22 19:35:03 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': '433', 'maxmem': '433'} [2006-09-22 19:35:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '443392', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'} [2006-09-22 19:35:03 xend] DEBUG (XendDomain:153) number of vcpus to use is 0 [2006-09-22 19:35:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch Thanks for help -- Francesco Laricchiuta email: francesco.laricchiuta at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From lamb at nmmi.edu Fri Sep 22 20:23:45 2006 From: lamb at nmmi.edu (Bill Lamb) Date: Fri, 22 Sep 2006 14:23:45 -0600 Subject: [Fedora-xen] RE: Install Message-ID: <105647C9BCE66A49A4F7457B866120CD0366167B@mama.nmmi.local> How do you install fedora on a windows machine Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From bench at silentmedia.com Fri Sep 22 20:44:58 2006 From: bench at silentmedia.com (Ben) Date: Fri, 22 Sep 2006 13:44:58 -0700 Subject: [Fedora-xen] RE: Install In-Reply-To: <105647C9BCE66A49A4F7457B866120CD0366167B@mama.nmmi.local> References: <105647C9BCE66A49A4F7457B866120CD0366167B@mama.nmmi.local> Message-ID: <9FCD5BA5-6D3A-4A8B-894B-D58EBA439342@silentmedia.com> It's a lot easier if you get rid of windows...... On Sep 22, 2006, at 1:23 PM, Bill Lamb wrote: > How do you install fedora on a windows machine > > Bob > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From yunfeng.zhao at intel.com Sat Sep 23 00:17:15 2006 From: yunfeng.zhao at intel.com (Zhao, Yunfeng) Date: Sat, 23 Sep 2006 08:17:15 +0800 Subject: [Fedora-xen] Testing for Xen of FC6 Test3 -- 2 Message-ID: <10EA09EFD8728347A513008B6B0DA77A05AE17@pdsmsx411.ccr.corp.intel.com> Two more issues were found on FC6 Test3. 1. Guest crashed when boot FC6 Test3 VMX guest with its PAE kernel host https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207769 Following is error message from serial console: (XEN) (file=traps.c, line=1371) Domain attempted WRMSR 00000199 from 00000000:00000f00 to 00000000:00000c20. (XEN) sh error: sh_remove_shadows(): can't find all shadows of mfn 36ec0 (shadow_flags=00000100) (XEN) domain_crash called from common.c:2251 (XEN) Domain 5 (vcpu#0) crashed on cpu#1: (XEN) ----[ Xen-3.0-unstable Not tainted ]---- (XEN) CPU: 1 (XEN) EIP: 0060:[] (XEN) EFLAGS: 00010082 CONTEXT: hvm (XEN) eax: 0000006b ebx: d469f380 ecx: 0000001d edx: 00000020 (XEN) esi: d469f380 edi: d469f383 ebp: d42afdd8 esp: d42afdcc (XEN) cr0: 8005003b cr3: 001f8da0 (XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 cs: 0060 (XEN) sh_update_paging_modes: postponing determination of shadow mode (XEN) sh_update_paging_modes: postponing determination of shadow mode (XEN) (file=traps.c, line=1371) Domain attempted WRMSR 00000199 from 00000000:00000f00 to 00000000:00000f22. (XEN) (file=hvm.c, line=195) Allocated port 3 for hvm. (XEN) (file=hvm.c, line=195) Allocated port 4 for hvm. (XEN) vmx_do_launch(): GUEST_CR3<=001f8da0, HOST_CR3<=1b073000 2. On FC6 Test3 I have to execute "xend stop; xend start" before can create the VMX guest https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207771 thanks Yunfeng >-----Original Message----- >From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] >On Behalf Of Zhao, Yunfeng >Sent: 2006?9?21? 11:20 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] Testing for Xen of FC6 Test3 -- 2 > >Hi >We have finished some manual device model tests, installation tests and >manual function tests. >And following are some issues we found in the testing: >1. Blue screen happens when install Windows 2k with ACPI enabled. >This issue should also exist in latest xen unstable tree. >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207565 > > 2. Fails to boot fc6 test3 IA32 guest with 2048MB mem size >The qemu window disappeared when booting. The qemu.log has been pasted >in the bug below. >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207574 > >3. Using "vi" on SDL console of VMX guest may cause the guest to hang >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207577 >This issue also exists in the latest xen unstable tree. > >4. Cannot use special number keys (when open Num Lock) on SDL console of >VMX guest. >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207578 >This isse also exists in the latest xen unstable tree. > >Detail info: >Function Part: >IA32 host: >Installation of IA32 UP XP SP2/win2k3 Windows Guest w/ ACPI Pass >Installation of IA32 UP XP SP2/win2k3 Windows Guest w/o ACPI PASS >Installation of IA32 UP Windows 2k Guest w/ ACPI PASS >Installation of IA32 UP Windows 2k Guest w/o ACPI FAIL >Boot up IA32 UP XP SP2/win2k3/win2k Guest PASS >Installation of IA32 FC6-test3 with Graphic/text mode PASS >Boot up IA32 FC6-test3 UP GUest PASS >Boot up IA32 FC6-test3 SMP Guest FAIL >Boot up IA32 RHEL4 UP/SMP Guest PASS >Network in VMX Guest PASS > >IA32e host: >Installation of IA32 UP XP SP2/win2k3 Windows Guest w/ ACPI Pass >Installation of IA32 UP XP SP2/win2k3 Windows Guest w/o ACPI PASS >Installation of IA32 UP Windows 2k Guest w/ ACPI PASS >Installation of IA32 UP Windows 2k Guest w/o ACPI FAIL >Boot up IA32 UP XP SP2/win2k3/win2k Guest PASS >Installation of IA32/IA32e FC6-test3 with Graphic/text mode PASS >Boot up IA32 FC6-test3 UP GUest PASS >Boot up IA32 FC6-test3 SMP Guest FAIL >Boot up IA32e FC6-test3 UP Guest PASS >Boot up IA32e FC6-test3 SMP Guest FAIL >Boot up IA32 RHEL4 UP/SMP Guest PASS >Boot up IA32e RHEL4 UP/SMP Guest PASS >Network in VMX Guest PASS > >Device Model Part: >1. vi in VMX FAIL >2. 4 NIC devices (4 rtl8139 and 4 ne2k) PASS >3. Xwindows and Windows display in VMX PASS >4. Switch between Xwindows and Text mode in VMX PASS >5. keyboard in VMX FAIL >6. Qemu command in Qemu console Window PASS >7. USB mouse in Windows Guest PASS >8. SDL and VNC mode in VMX PASS > >Thanks >Yunfeng > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From riel at redhat.com Sat Sep 23 05:32:12 2006 From: riel at redhat.com (Rik van Riel) Date: Sat, 23 Sep 2006 01:32:12 -0400 Subject: [Fedora-xen] fedora core 5 stock xen kernels nvidia drivers.... In-Reply-To: References: Message-ID: <4514C6DC.20403@redhat.com> Tom Bishop wrote: > Doea anyine know when the stock fedora xen kernels will be compatiable > with the nvidia binary kernels? Wrong way around. Why not ask Nvidia when they will make their drivers compatible with the kernel you want to use? -- What is important? What you want to be true, or what is true? From berrange at redhat.com Sat Sep 23 14:08:41 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Sat, 23 Sep 2006 15:08:41 +0100 Subject: [Fedora-xen] fedora core 5 stock xen kernels nvidia drivers.... In-Reply-To: <4514C6DC.20403@redhat.com> References: <4514C6DC.20403@redhat.com> Message-ID: <20060923140840.GA4578@redhat.com> On Sat, Sep 23, 2006 at 01:32:12AM -0400, Rik van Riel wrote: > Tom Bishop wrote: > >Doea anyine know when the stock fedora xen kernels will be compatiable > >with the nvidia binary kernels? > > Wrong way around. Why not ask Nvidia when they will make > their drivers compatible with the kernel you want to use? And at the same time ask them when they'll open source their drivers, or open their specs to allow the existing open source driver to be improved... Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From xen.mails at gmail.com Sat Sep 23 14:44:04 2006 From: xen.mails at gmail.com (Anand Gupta) Date: Sat, 23 Sep 2006 20:14:04 +0530 Subject: [Fedora-xen] what do you recommend for cluster fs ?? Message-ID: I was wondering what people use / recommend for a cluster fs for use with xen ? Also with this cluster fs, will the domU's be using flat files / lvm ? (it should be the former as per my guess since these flat files will be stored on the cluster fs, but then won't performance hit will be there for these domU's ? ) I don't want to invest in a san/ nas solution, just looking for cost effective. Right now i have a single server which i will use for the cluster fs and slowly add more servers to the cluster as and when i need more space. Atleast thats what i have thought till now. All ideas are welcome. -- regards, Anand Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From hkubota at gmx.net Sat Sep 23 16:13:17 2006 From: hkubota at gmx.net (Harald Kubota) Date: Sun, 24 Sep 2006 01:13:17 +0900 Subject: [Fedora-xen] Re: [Xen-users] what do you recommend for cluster fs ?? In-Reply-To: References: Message-ID: <45155D1D.8070804@gmx.net> Anand Gupta wrote: > I was wondering what people use / recommend for a cluster fs for use > with xen ? I'm currently using a firewire external hard disk. When used with the correct IDE-FW-chipset (Oxford are the only ones working), 4 hosts can connect to one disk concurrently. The other cheap possibility is to use iSCSI (e.g. iet). Or NFS. Harald From riel at redhat.com Sat Sep 23 17:40:14 2006 From: riel at redhat.com (Rik van Riel) Date: Sat, 23 Sep 2006 13:40:14 -0400 Subject: [Fedora-xen] what do you recommend for cluster fs ?? In-Reply-To: References: Message-ID: <4515717E.4030605@redhat.com> Anand Gupta wrote: > I was wondering what people use / recommend for a cluster fs for use > with xen ? > > Also with this cluster fs, will the domU's be using flat files / lvm ? > (it should be the former as per my guess since these flat files will be > stored on the cluster fs, but then won't performance hit will be there > for these domU's ? ) You could also use CLVM to have your guests living on logical volumes that are visible on all cluster hosts. -- "You don't have to be crazy to do this ... but it helps." -- Bob Ross From hkubota at gmx.net Sun Sep 24 00:17:26 2006 From: hkubota at gmx.net (Harald Kubota) Date: Sun, 24 Sep 2006 09:17:26 +0900 Subject: [Fedora-xen] Re: [Xen-users] what do you recommend for cluster fs ?? In-Reply-To: <4515CA94.6000109@ldsys.net> References: <45155D1D.8070804@gmx.net> <4515CA94.6000109@ldsys.net> Message-ID: <4515CE96.8020300@gmx.net> Christopher G. Stach II wrote: > Harald Kubota wrote: > >> Anand Gupta wrote: >> >>> I was wondering what people use / recommend for a cluster fs for use >>> with xen ? >>> >> I'm currently using a firewire external hard disk. When used with the >> correct IDE-FW-chipset (Oxford are the only ones working), 4 hosts can >> connect to one disk concurrently. >> >> The other cheap possibility is to use iSCSI (e.g. iet). Or NFS. >> > Doesn't really answer the "cluster FS" question, since that's just > shared storage. :) > > Good point and of course true. I skipped the "cluster fs" part completely. Now if the question were "What do you use for shared storage to be able to use Xen migration", then I'd be ok. Harald From cnegus at rucls.net Mon Sep 25 00:36:54 2006 From: cnegus at rucls.net (Chris Negus) Date: Sun, 24 Sep 2006 19:36:54 -0500 Subject: [Fedora-xen] Dbus problem with virt-manager Message-ID: <1159144614.2646.363.camel@einstein> I tried running virt-manager in FC6 T3 and got the following error message: dbus_bindings.DBusException Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help) Could not connection to session bus, disabling DBus service My kernel is 2.6.17-1.2647.fc6xen. All packages are up to date. Any suggestions? -- Chris Negus From cgs at ldsys.net Sun Sep 24 00:00:20 2006 From: cgs at ldsys.net (Christopher G. Stach II) Date: Sat, 23 Sep 2006 19:00:20 -0500 Subject: [Fedora-xen] Re: [Xen-users] what do you recommend for cluster fs ?? In-Reply-To: <45155D1D.8070804@gmx.net> References: <45155D1D.8070804@gmx.net> Message-ID: <4515CA94.6000109@ldsys.net> Harald Kubota wrote: > Anand Gupta wrote: >> I was wondering what people use / recommend for a cluster fs for use >> with xen ? > I'm currently using a firewire external hard disk. When used with the > correct IDE-FW-chipset (Oxford are the only ones working), 4 hosts can > connect to one disk concurrently. > > The other cheap possibility is to use iSCSI (e.g. iet). Or NFS. > > Harald Doesn't really answer the "cluster FS" question, since that's just shared storage. :) GNBD + CLVM + GFS here. -- Christopher G. Stach II From berrange at redhat.com Mon Sep 25 14:32:51 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 25 Sep 2006 15:32:51 +0100 Subject: [Fedora-xen] Dbus problem with virt-manager In-Reply-To: <1159144614.2646.363.camel@einstein> References: <1159144614.2646.363.camel@einstein> Message-ID: <20060925143251.GA16283@redhat.com> On Sun, Sep 24, 2006 at 07:36:54PM -0500, Chris Negus wrote: > I tried running virt-manager in FC6 T3 and got the following error > message: > > dbus_bindings.DBusException Unable to determine the address of the > message bus (try 'man dbus-launch' and 'man dbus-daemon' for help) > Could not connection to session bus, disabling DBus service > > My kernel is 2.6.17-1.2647.fc6xen. All packages are up to date. Any > suggestions? Don't worry this message is (mostly) harmless. Virt-manager will optionally register a DBus service which lets the VM Applet controls some of its UI functions. If it can't talk to DBus, virt-manager will simply not register this service, everything else will carry on as normal. I'm removing this scary logging error message from next release to avoid worrying people unneccessarily. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From kobkob at gmail.com Mon Sep 25 20:51:46 2006 From: kobkob at gmail.com (Orathai Sukwong) Date: Mon, 25 Sep 2006 16:51:46 -0400 Subject: [Fedora-xen] Cannot run WinXP on the Xen fedora core 6 Message-ID: <748f85310609251351h4cdf3928w112f5f80878763a0@mail.gmail.com> Hi, I've tried to bring the 32bit WinXP guest up on the Fedore Core 6-xen. My xen release is 2.6.17-1.2647.fc6xen and version #1 SMP Wed Sep 13 13:26:53 EDT 2006. xen_caps are xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p. My machine is running the Fedora Core 6 i686. The problem is that when I booted the WinXP guest, it crashed. Here are some debugging info: (XEN) (GUEST: 5) unsupported PCI BIOS function 0x0E (XEN) (GUEST: 5) int13_harddisk: function 15, unmapped device for ELDL=81 (XEN) 0f 6f, This opcode isn't handled yet (XEN) handle_mmio: failed to decode instruction (XEN) mmio opcode: va 0xf81393c0, gpa 0xf00783c0, len 3: 0f 6f 06 (XEN) domain_crash_sync called from platform.c:869 (XEN) Domain 5 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.0-unstable Not tainted ]---- (XEN) CPU: 0 (XEN) EIP: 0008:[] (XEN) EFLAGS: 00010202 CONTEXT: hvm (XEN) eax: f81393c0 ebx: e10875cc ecx: 0000002a edx: 00000008 (XEN) esi: f81393c0 edi: e10875d2 ebp: f86440d4 esp: f86440c8 (XEN) cr0: 80010031 cr3: 001f9ea0 (XEN) ds: 0023 es: 0023 fs: 0030 gs: 0000 ss: 0010 cs: 0008 (XEN) sh_update_paging_modes: postponing determination of shadow mode (XEN) (file=hvm.c, line=195) Allocated port 3 for hvm. (XEN) vmx_do_launch(): GUEST_CR3<=001f9ea0, HOST_CR3<=2bd03000 (XEN) (file=event_channel.c, line=176) EVTCHNOP failure: domain 0, error -22, line 176 domid: 6 qemu: the number of cpus is 1 shared page at pfn:1ffff, mfn: 21d54 buffered io page at pfn:1fffd, mfn: 21d56 char device redirected to /dev/pts/2 bind interdomain ioctl error 22 Any ideas what went wrong? Please help me. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Mon Sep 25 21:04:03 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 25 Sep 2006 22:04:03 +0100 Subject: [Fedora-xen] Cannot run WinXP on the Xen fedora core 6 In-Reply-To: <748f85310609251351h4cdf3928w112f5f80878763a0@mail.gmail.com> References: <748f85310609251351h4cdf3928w112f5f80878763a0@mail.gmail.com> Message-ID: <20060925210403.GC13054@redhat.com> On Mon, Sep 25, 2006 at 04:51:46PM -0400, Orathai Sukwong wrote: > Hi, > > I've tried to bring the 32bit WinXP guest up on the Fedore Core 6-xen. My > xen release is 2.6.17-1.2647.fc6xen and version #1 SMP Wed Sep 13 13:26:53 > EDT 2006. xen_caps are xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p. My > machine is running the Fedora Core 6 i686. The problem is that when I booted > the WinXP guest, it crashed. Here are some debugging info: > > (XEN) (GUEST: 5) unsupported PCI BIOS function 0x0E > (XEN) (GUEST: 5) int13_harddisk: function 15, unmapped device for ELDL=81 > (XEN) 0f 6f, This opcode isn't handled yet > (XEN) handle_mmio: failed to decode instruction > (XEN) mmio opcode: va 0xf81393c0, gpa 0xf00783c0, len 3: 0f 6f 06 > (XEN) domain_crash_sync called from platform.c:869 > (XEN) Domain 5 (vcpu#0) crashed on cpu#0: > (XEN) ----[ Xen-3.0-unstable Not tainted ]---- > (XEN) CPU: 0 > (XEN) EIP: 0008:[] > (XEN) EFLAGS: 00010202 CONTEXT: hvm > (XEN) eax: f81393c0 ebx: e10875cc ecx: 0000002a edx: 00000008 > (XEN) esi: f81393c0 edi: e10875d2 ebp: f86440d4 esp: f86440c8 > (XEN) cr0: 80010031 cr3: 001f9ea0 > (XEN) ds: 0023 es: 0023 fs: 0030 gs: 0000 ss: 0010 cs: 0008 > (XEN) sh_update_paging_modes: postponing determination of shadow mode > (XEN) (file=hvm.c, line=195) Allocated port 3 for hvm. > (XEN) vmx_do_launch(): GUEST_CR3<=001f9ea0, HOST_CR3<=2bd03000 > (XEN) (file=event_channel.c, line=176) EVTCHNOP failure: domain 0, error > -22, line 176 > > domid: 6 > qemu: the number of cpus is 1 > shared page at pfn:1ffff, mfn: 21d54 > buffered io page at pfn:1fffd, mfn: 21d56 > char device redirected to /dev/pts/2 > bind interdomain ioctl error 22 > > Any ideas what went wrong? Please help me. Thank you. This is a bug in the HVM emulation layer. In some cases it needs to emulate instructions, but it looks like WinXp issues one it was unable to emulate yet. I checked upstream xen-unstable.hg repository there's still no support for this. Please enter a bugzilla ticket with the details from this mail so the problem can be tracked. I'm afraid there's no immediate work around I can think of to make this work, so you might want to try Windows 2k instead which I believe has been getting more upstream testing than XP Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From acathrow at redhat.com Mon Sep 25 21:14:33 2006 From: acathrow at redhat.com (Andrew Cathrow) Date: Mon, 25 Sep 2006 17:14:33 -0400 Subject: [Fedora-xen] Cannot run WinXP on the Xen fedora core 6 In-Reply-To: <20060925210403.GC13054@redhat.com> References: <748f85310609251351h4cdf3928w112f5f80878763a0@mail.gmail.com> <20060925210403.GC13054@redhat.com> Message-ID: <1159218873.3517.10.camel@aic-laptop.cathrow.org> I've got WinXP running on the 2647 kernel on FC6. The guest runs well, but the install was more than a little challenging. I ended up installing the guest using QEMU (which was tremendously slow) but once the install had completed the guest runs well. On Mon, 2006-09-25 at 22:04 +0100, Daniel P. Berrange wrote: > On Mon, Sep 25, 2006 at 04:51:46PM -0400, Orathai Sukwong wrote: > > Hi, > > > > I've tried to bring the 32bit WinXP guest up on the Fedore Core 6-xen. My > > xen release is 2.6.17-1.2647.fc6xen and version #1 SMP Wed Sep 13 13:26:53 > > EDT 2006. xen_caps are xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p. My > > machine is running the Fedora Core 6 i686. The problem is that when I booted > > the WinXP guest, it crashed. Here are some debugging info: > > > > (XEN) (GUEST: 5) unsupported PCI BIOS function 0x0E > > (XEN) (GUEST: 5) int13_harddisk: function 15, unmapped device for ELDL=81 > > (XEN) 0f 6f, This opcode isn't handled yet > > (XEN) handle_mmio: failed to decode instruction > > (XEN) mmio opcode: va 0xf81393c0, gpa 0xf00783c0, len 3: 0f 6f 06 > > (XEN) domain_crash_sync called from platform.c:869 > > (XEN) Domain 5 (vcpu#0) crashed on cpu#0: > > (XEN) ----[ Xen-3.0-unstable Not tainted ]---- > > (XEN) CPU: 0 > > (XEN) EIP: 0008:[] > > (XEN) EFLAGS: 00010202 CONTEXT: hvm > > (XEN) eax: f81393c0 ebx: e10875cc ecx: 0000002a edx: 00000008 > > (XEN) esi: f81393c0 edi: e10875d2 ebp: f86440d4 esp: f86440c8 > > (XEN) cr0: 80010031 cr3: 001f9ea0 > > (XEN) ds: 0023 es: 0023 fs: 0030 gs: 0000 ss: 0010 cs: 0008 > > (XEN) sh_update_paging_modes: postponing determination of shadow mode > > (XEN) (file=hvm.c, line=195) Allocated port 3 for hvm. > > (XEN) vmx_do_launch(): GUEST_CR3<=001f9ea0, HOST_CR3<=2bd03000 > > (XEN) (file=event_channel.c, line=176) EVTCHNOP failure: domain 0, error > > -22, line 176 > > > > domid: 6 > > qemu: the number of cpus is 1 > > shared page at pfn:1ffff, mfn: 21d54 > > buffered io page at pfn:1fffd, mfn: 21d56 > > char device redirected to /dev/pts/2 > > bind interdomain ioctl error 22 > > > > Any ideas what went wrong? Please help me. Thank you. > > This is a bug in the HVM emulation layer. In some cases it needs to emulate > instructions, but it looks like WinXp issues one it was unable to emulate > yet. I checked upstream xen-unstable.hg repository there's still no support > for this. Please enter a bugzilla ticket with the details from this mail so > the problem can be tracked. I'm afraid there's no immediate work around I > can think of to make this work, so you might want to try Windows 2k instead > which I believe has been getting more upstream testing than XP > > Regards, > Dan. Andrew Cathrow Red Hat, Inc. (678) 733 0452 - Mobile (404) 437 6178 - Home Office acathrow at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From yongkang.you at intel.com Tue Sep 26 06:59:18 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Tue, 26 Sep 2006 14:59:18 +0800 Subject: [Fedora-xen] Re: [Xen-ia64-devel] FC6 Test3 Xentest result Message-ID: <094BCE01AFBE9646AF220B0B3F367AAB589032@pdsmsx413.ccr.corp.intel.com> Hi Aron and Akio, I reported a new bug about Xen0 crashing, when I try to insert xennet.ko in XenU. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208062 Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Aron Griffis >Sent: 2006?9?21? 22:45 >To: You, Yongkang >Cc: xen-ia64-devel at lists.xensource.com; fedora-xen at redhat.com >Subject: [Fedora-xen] Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 >Xentest result > >You, Yongkang wrote: [Wed Sep 20 2006, 01:46:22AM EDT] >> [Bug 207227] New: Xen0 reboot command can not reboot Tiger4 machine. > >I think this is a duplicate of bug 203032. >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203032 > >> [Bug 207241] New: XenU domain can not be created successfully. >> New xenU created failure serial log has been pasted to the bug. > >I think the front-end and back-end drivers aren't communicating. >I see the same problem with both network and block drivers when >attempting xenguest-install. > >Aron > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From takebe_akio at jp.fujitsu.com Tue Sep 26 11:46:16 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Tue, 26 Sep 2006 20:46:16 +0900 Subject: [Fedora-xen] Re: [Xen-ia64-devel] FC6 Test3 Xentest result In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AAB589032@pdsmsx413.ccr.corp.intel.com> References: <094BCE01AFBE9646AF220B0B3F367AAB589032@pdsmsx413.ccr.corp.intel.com> Message-ID: Hi, Yongkang Thank you for your report. I have the same bug. Aron reported the likely bug of xenguest-install.py. I try to debug this issue. Best Regards, Akio Takebe >Hi Aron and Akio, > >I reported a new bug about Xen0 crashing, when I try to insert xennet.ko in > XenU. >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208062 > > >Best Regards, >Yongkang (Kangkang) $B%b%?%=%*(B > >>-----Original Message----- >>From: fedora-xen-bounces at redhat.com >>[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Aron Griffis >>Sent: 2006$B%Hs%d%D(B21$B%M%f(B 22:45 >>To: You, Yongkang >>Cc: xen-ia64-devel at lists.xensource.com; fedora-xen at redhat.com >>Subject: [Fedora-xen] Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 >>Xentest result >> >>You, Yongkang wrote: [Wed Sep 20 2006, 01:46:22AM EDT] >>> [Bug 207227] New: Xen0 reboot command can not reboot Tiger4 machine. >> >>I think this is a duplicate of bug 203032. >>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203032 >> >>> [Bug 207241] New: XenU domain can not be created successfully. >>> New xenU created failure serial log has been pasted to the bug. >> >>I think the front-end and back-end drivers aren't communicating. >>I see the same problem with both network and block drivers when >>attempting xenguest-install. >> >>Aron >> >>-- >>Fedora-xen mailing list >>Fedora-xen at redhat.com >>https://www.redhat.com/mailman/listinfo/fedora-xen From paul at xelerance.com Tue Sep 26 15:04:39 2006 From: paul at xelerance.com (Paul Wouters) Date: Tue, 26 Sep 2006 17:04:39 +0200 (CEST) Subject: [Fedora-xen] %{_libdir} wrong on x86_64 xenU on FC5 from xenguest-install.py In-Reply-To: References: Message-ID: On Tue, 26 Sep 2006, Paul Wouters wrote: An update on this. It is not apache specific. It seems the stock FC5 xenguest-install.py on x86_64, despite running the proper 64bit kernel/userland, is somehow using /usr/lib as %{_libdir}. This is odd, as it is a virgin xenguest install from a x86_86 xen0, where the xen0 properly expands %{_libdir} to /usr/lib64, but the installed xenU does not. I've changed the bugzilla item to the xen component. Paul > Date: Tue, 26 Sep 2006 08:11:15 +0200 (CEST) > From: Paul Wouters > Cc: fedora-devel-list at redhat.com > To: Discussion related to Fedora Extras > Subject: multiple apache module packages fail on %{_libdir} on x86_64 on FC5 > > > ( filed as https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208059 but posting > here anyway, as it might cause faulty builds for extras apache modules as well) > > (someone prob needs to approve the fedora-devel-list CC:, if it doesnt' auto bounce) > > I was in the process of making a new apache module (mod_auth_radius). A problem I > ran into was that despite using %{_libdir}, the module would install in > /usr/lib/httpd/modules instead of /usr/lib64/httpd/modules. This is on an FC5 > xenu build with xenguest-install.py on a P4 with an x86_64 kernel. > > I checked what I could have done wrong by testing two random other modules from > extras, mod_cband and mod_security. They turned out to suffer from the same > problem, they also install in the wrong directory. > > So I decided to look at a core module, and picked mod_auth_mysql, which turns > out to not even build on x86_64, with a failure to link against libmysqlclient, > which is indeed a missing Require (which I bugzilla'ed), but after installing > both mysqlclient10 and mysqlclient14, it still couldnt't find the proper > library. > > So I picked mod_auth_pgsql. That compiled fine, but I already had it installed > from binary. I peeked: > > # rpm -ql mod_auth_pgsql > /etc/httpd/conf.d/auth_pgsql.conf > /usr/lib64/httpd/modules/mod_auth_pgsql.so > /usr/share/doc/mod_auth_pgsql-2.0.3 > /usr/share/doc/mod_auth_pgsql-2.0.3/INSTALL > /usr/share/doc/mod_auth_pgsql-2.0.3/README > /var/www/manual/mod/mod_auth_pgsql.html > > Then I checked my freshly build package: > > # rpm -qlp /usr/src/redhat/RPMS/x86_64/mod_auth_pgsql-2.0.3-2.3.x86_64.rpm > /usr/doc/mod_auth_pgsql-2.0.3 > /usr/doc/mod_auth_pgsql-2.0.3/INSTALL > /usr/doc/mod_auth_pgsql-2.0.3/README > /usr/etc/httpd/conf.d/auth_pgsql.conf > /usr/lib/httpd/modules/mod_auth_pgsql.so > /var/www/manual/mod/mod_auth_pgsql.html > > > This leads me to believe that the current apxs in httpd-devel is subtly > broken. Note this is a freshly installed FC5 with updates. > > Part of my spec file (which matches other mod_* packages) > > %build > /usr/sbin/apxs -Wc,"%{optflags}" -c mod_auth_radius-2.0.c > > %install > rm -rf %{buildroot} > mkdir -p %{buildroot}%{_libdir}/httpd/modules/ > mkdir -p %{buildroot}/%{_sysconfdir}/httpd/conf.d/ > install -p .libs/mod_auth_radius-2.0.so %{buildroot}/%{_libdir}/httpd/modules/ > install -m644 %{SOURCE1} %{buildroot}/%{_sysconfdir}/httpd/conf.d/ > > relevant bits of output: > > + cd /usr/src/redhat/BUILD > + cd mod_auth_radius-1.5.7 > + /usr/sbin/apxs '-Wc,-O2 -g' -c mod_auth_radius-2.0.c > /usr/lib64/apr-1/build/libtool --silent --mode=compile gcc -prefer-pic -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -pthread -I/usr/include/httpd -I/usr/include/apr-1 -I/usr/include/apr-1 -O2 -g -c -o mod_auth_radius-2.0.lo mod_auth_radius-2.0.c && touch mod_auth_radius-2.0.slo > > /usr/lib64/apr-1/build/libtool --silent --mode=link gcc -o mod_auth_radius-2.0.la -rpath /usr/lib64/httpd/modules -module -avoid-version mod_auth_radius-2.0.lo > + exit 0 > Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.599 > + umask 022 > + cd /usr/src/redhat/BUILD > + cd mod_auth_radius-1.5.7 > + rm -rf /var/tmp/mod_auth_radius-1.5.7-1-root- > + mkdir -p /var/tmp/mod_auth_radius-1.5.7-1-root-/usr/lib/httpd/modules/ > + mkdir -p /var/tmp/mod_auth_radius-1.5.7-1-root-//usr/etc/httpd/conf.d/ > + install -p .libs/mod_auth_radius-2.0.so /var/tmp/mod_auth_radius-1.5.7-1-root-//usr/lib/httpd/modules/ > + install -m644 /usr/src/redhat/SOURCES/mod_auth_radius.conf /var/tmp/mod_auth_radius-1.5.7-1-root-//usr/etc/httpd/conf.d/ > + exit 0 > > As can be seen, apxs seems to reference /usr/lib64/httpd/modules while building, but /var/tmp/mod_auth_radius-1.5.7-1-root-//usr/lib/httpd/modules/ when installing. > > Paul > > -- Building and integrating Virtual Private Networks with Openswan: http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155 From paul at xelerance.com Tue Sep 26 15:12:15 2006 From: paul at xelerance.com (Paul Wouters) Date: Tue, 26 Sep 2006 17:12:15 +0200 (CEST) Subject: [Fedora-xen] Re: rpmbuild environment issues for xen guest? In-Reply-To: <20060926145814.GA22096@redhat.com> References: <20060926145814.GA22096@redhat.com> Message-ID: On Tue, 26 Sep 2006, Joe Orton wrote: > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208059 > > This report has an x86_64 Xen guest where _libdir is expanding to > /usr/lib; perhaps /etc/rpm/platform needs to be set up by the Xen > guest-creating scripts? Is this a known issue? > > Paul, if you do: > > echo x86_64-redhat-linux > /etc/rpm/platform > > does that fix the problem? Hmm. # more /etc/rpm/platform ia32e-redhat-linux # echo x86_64-redhat-linux > /etc/rpm/platform # rpmbuild -bb /usr/src/redhat/SPECS/mod_auth_radius.spec [...] + install -p .libs/mod_auth_radius-2.0.so /var/tmp/mod_auth_radius-1.5.7-1-root-root//usr/lib64/httpd/modules/ It did! Thank you! I do notice that the xen0 has ia32e-redhat-linux as well, though it did not seem to suffer from this problem when building rpms - it used /usr/lib64 fine. Can you tell me more about this? Paul From jorton at redhat.com Tue Sep 26 14:58:14 2006 From: jorton at redhat.com (Joe Orton) Date: Tue, 26 Sep 2006 15:58:14 +0100 Subject: [Fedora-xen] rpmbuild environment issues for xen guest? Message-ID: <20060926145814.GA22096@redhat.com> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208059 This report has an x86_64 Xen guest where _libdir is expanding to /usr/lib; perhaps /etc/rpm/platform needs to be set up by the Xen guest-creating scripts? Is this a known issue? Paul, if you do: echo x86_64-redhat-linux > /etc/rpm/platform does that fix the problem? joe From elitescripts2000 at yahoo.com Tue Sep 26 16:48:08 2006 From: elitescripts2000 at yahoo.com (Matt) Date: Tue, 26 Sep 2006 09:48:08 -0700 (PDT) Subject: [Fedora-xen] xm vnet-list is not supported In-Reply-To: Message-ID: <20060926164808.77615.qmail@web31813.mail.mud.yahoo.com> Hello, I have an example xen domain running however I want to add virtual networks ( ip networks ) When I run: xm vnet-list It says: Error: method "xend_vnets" is not supported Does this mean I need a xen binary with this support? If so what is the RPM package name? regards, matt From berrange at redhat.com Tue Sep 26 17:13:33 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 26 Sep 2006 18:13:33 +0100 Subject: [Fedora-xen] xm vnet-list is not supported In-Reply-To: <20060926164808.77615.qmail@web31813.mail.mud.yahoo.com> References: <20060926164808.77615.qmail@web31813.mail.mud.yahoo.com> Message-ID: <20060926171333.GI8885@redhat.com> On Tue, Sep 26, 2006 at 09:48:08AM -0700, Matt wrote: > Hello, > > I have an example xen domain running however I want to add virtual networks ( > ip networks ) > > When I run: xm vnet-list > > It says: Error: method "xend_vnets" is not supported > > Does this mean I need a xen binary with this support? If so what is the RPM > package name? No, this means that the 'xm' client is trying to invoke a method in xend which does not exist. Looking at the mercurial changelogs upstream Xen development removed the xend_vnets method back in March 2006 $ hg log -r 5c9c44fc1c39 changeset: 9403:5c9c44fc1c39 parent: 9401:2c77d26871f7 user: anthony at rhesis.austin.ibm.com date: Thu Mar 23 11:25:37 2006 +0100 summary: Use XML-RPC as a transport for Xend instead of S-Expression/HTTP. $ hg log --patch -r 5c9c44fc1c39 | grep --after 2 xend_vnets - def xend_vnets(self): - return self.xendGet(self.vneturl()) - I don't see any obvious way to fix this, so it'll have to be reported bck to upstream Xen developers for resolution. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shobha_ranganathan at yahoo.com Tue Sep 26 22:31:03 2006 From: shobha_ranganathan at yahoo.com (shobha ranganathan) Date: Tue, 26 Sep 2006 15:31:03 -0700 (PDT) Subject: [Fedora-xen] "Import Error:No module named libvirt" while running xenguest-install.py in Fc5 x86 mode Message-ID: <20060926223103.16595.qmail@web55905.mail.re3.yahoo.com> I download xen3.0.2-23.src.rpm and build the dom0 Kernel in Fedora COre 5 in x86 mode. I did not build a domU kernel at all. I tried to run ./xenguest-install.py in dom0 kernel after booting into it.. I got this error "No module named libvirt". I then tried installing libvirt-0.0.6-1.i386.rpm using "rpm --install libvirt-0.0.6-1.i386.rpm" I get failed dependencies error such as "libxenstore.so is needed by libvirt-0.0.6-1.i386 xen is needed by libvirt-0.0.6-1.i386" what am I missing here ? I have libxenstore.so in /usr/lib. Commands like "xm list" works in dom0 kernel thanks for your help Shobha --------------------------------- Do you Yahoo!? Get on board. You're invited to try the new Yahoo! Mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From veillard at redhat.com Wed Sep 27 07:50:37 2006 From: veillard at redhat.com (Daniel Veillard) Date: Wed, 27 Sep 2006 03:50:37 -0400 Subject: [Fedora-xen] "Import Error:No module named libvirt" while running xenguest-install.py in Fc5 x86 mode In-Reply-To: <20060926223103.16595.qmail@web55905.mail.re3.yahoo.com> References: <20060926223103.16595.qmail@web55905.mail.re3.yahoo.com> Message-ID: <20060927075037.GB27354@redhat.com> On Tue, Sep 26, 2006 at 03:31:03PM -0700, shobha ranganathan wrote: > I download xen3.0.2-23.src.rpm and build the dom0 Kernel in Fedora COre 5 in x86 mode. I did not build a domU kernel at all. > I tried to run ./xenguest-install.py in dom0 kernel after booting into it.. I got this error > "No module named libvirt". > > I then tried installing libvirt-0.0.6-1.i386.rpm using > "rpm --install libvirt-0.0.6-1.i386.rpm" > > I get failed dependencies error such as > "libxenstore.so is needed by libvirt-0.0.6-1.i386 > xen is needed by libvirt-0.0.6-1.i386" > > what am I missing here ? I have libxenstore.so in /usr/lib. > Commands like "xm list" works in dom0 kernel There is a set of tightly interconnected packages that are needed. You cannot just upgrade one of them, especially the xen RPM. The set of source RPMs are kernel (-xen), xen, libvirt, python-xeninst (and virt-manager) . Don't try to upgrade one without upgrading the others. The RPM dependancies are here to express the tight coupling between those packages, don't try to --force or --nodeps you're nearly garanteed to have a not running Xen setup if you do. The best is to upgrade to FC6 test3 if you want to try a recent version, and to FC6 final when it's out. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From jorton at redhat.com Wed Sep 27 10:15:48 2006 From: jorton at redhat.com (Joe Orton) Date: Wed, 27 Sep 2006 11:15:48 +0100 Subject: [Fedora-xen] Re: rpmbuild environment issues for xen guest? In-Reply-To: References: <20060926145814.GA22096@redhat.com> Message-ID: <20060927101548.GA10178@redhat.com> On Tue, Sep 26, 2006 at 05:12:15PM +0200, Paul Wouters wrote: > On Tue, 26 Sep 2006, Joe Orton wrote: > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208059 > > > > This report has an x86_64 Xen guest where _libdir is expanding to > > /usr/lib; perhaps /etc/rpm/platform needs to be set up by the Xen > > guest-creating scripts? Is this a known issue? > > > > Paul, if you do: > > > > echo x86_64-redhat-linux > /etc/rpm/platform > > > > does that fix the problem? > > Hmm. > > # more /etc/rpm/platform > ia32e-redhat-linux Scary! I think this file is created by anaconda. So if it's wrong in your xen0 and just gets copied as-is to the guests, there is probably something very wrong elsewhere. (I don't claim to understand how or why this file is used or needed by rpmbuild, sorry) joe From berrange at redhat.com Wed Sep 27 12:13:56 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 27 Sep 2006 13:13:56 +0100 Subject: [Fedora-xen] Re: rpmbuild environment issues for xen guest? In-Reply-To: <20060927101548.GA10178@redhat.com> References: <20060926145814.GA22096@redhat.com> <20060927101548.GA10178@redhat.com> Message-ID: <20060927121356.GA20056@redhat.com> On Wed, Sep 27, 2006 at 11:15:48AM +0100, Joe Orton wrote: > On Tue, Sep 26, 2006 at 05:12:15PM +0200, Paul Wouters wrote: > > On Tue, 26 Sep 2006, Joe Orton wrote: > > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208059 > > > > > > This report has an x86_64 Xen guest where _libdir is expanding to > > > /usr/lib; perhaps /etc/rpm/platform needs to be set up by the Xen > > > guest-creating scripts? Is this a known issue? > > > > > > Paul, if you do: > > > > > > echo x86_64-redhat-linux > /etc/rpm/platform > > > > > > does that fix the problem? > > > > Hmm. > > > > # more /etc/rpm/platform > > ia32e-redhat-linux > > Scary! I think this file is created by anaconda. So if it's wrong in > your xen0 and just gets copied as-is to the guests, there is probably > something very wrong elsewhere. (I don't claim to understand how or why > this file is used or needed by rpmbuild, sorry) Yes, this is created by anaconda - it is, however, corect - ia32a is the canonical architecture for Intel's x86_64 CPUs. The problem is that the basic RPM / rpmbuild macros for some reason don't treat it as a 64-bit arch - redhat-rpm-config fixes it for reasons I don't understand, so I re-assigned it to rpm. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From xen.mails at gmail.com Wed Sep 27 19:53:21 2006 From: xen.mails at gmail.com (Anand Gupta) Date: Thu, 28 Sep 2006 01:23:21 +0530 Subject: [Fedora-xen] what do you recommend for cluster fs ?? In-Reply-To: <4515717E.4030605@redhat.com> References: <4515717E.4030605@redhat.com> Message-ID: Could you please direct me some documentation/howto where i can get a feel of it and see how to go about installing and using it ? I heard about the RH Cluster Suite, however wasn't able to find any documentation to use it. On 9/23/06, Rik van Riel wrote: > > Anand Gupta wrote: > > I was wondering what people use / recommend for a cluster fs for use > > with xen ? > > > > Also with this cluster fs, will the domU's be using flat files / lvm ? > > (it should be the former as per my guess since these flat files will be > > stored on the cluster fs, but then won't performance hit will be there > > for these domU's ? ) > > You could also use CLVM to have your guests living on logical > volumes that are visible on all cluster hosts. > > -- > "You don't have to be crazy to do this ... but it helps." -- Bob Ross > -- regards, Anand Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Wed Sep 27 19:58:04 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 27 Sep 2006 20:58:04 +0100 Subject: [Fedora-xen] what do you recommend for cluster fs ?? In-Reply-To: References: <4515717E.4030605@redhat.com> Message-ID: <20060927195804.GR20056@redhat.com> On Thu, Sep 28, 2006 at 01:23:21AM +0530, Anand Gupta wrote: > Could you please direct me some documentation/howto where i can get a feel > of it and see how to go about installing and using it ? I heard about the RH > Cluster Suite, however wasn't able to find any documentation to use it. There's some docs linked off the Clustersuite dev pages: http://sources.redhat.com/cluster/ Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From xen.mails at gmail.com Wed Sep 27 20:04:06 2006 From: xen.mails at gmail.com (Anand Gupta) Date: Thu, 28 Sep 2006 01:34:06 +0530 Subject: [Fedora-xen] what do you recommend for cluster fs ?? In-Reply-To: <20060927195804.GR20056@redhat.com> References: <4515717E.4030605@redhat.com> <20060927195804.GR20056@redhat.com> Message-ID: Thanks for the link. Already tried looking there, however was confused. I guess there is no other way then to try to find way in those docs itself. On 9/28/06, Daniel P. Berrange wrote: > > On Thu, Sep 28, 2006 at 01:23:21AM +0530, Anand Gupta wrote: > > Could you please direct me some documentation/howto where i can get a > feel > > of it and see how to go about installing and using it ? I heard about > the RH > > Cluster Suite, however wasn't able to find any documentation to use it. > > There's some docs linked off the Clustersuite dev pages: > > http://sources.redhat.com/cluster/ > > Regards, > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 > -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B > 9505 -=| > -- regards, Anand Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From acathrow at redhat.com Wed Sep 27 20:32:35 2006 From: acathrow at redhat.com (Andrew Cathrow) Date: Wed, 27 Sep 2006 16:32:35 -0400 Subject: [Fedora-xen] what do you recommend for cluster fs ?? In-Reply-To: References: <4515717E.4030605@redhat.com> Message-ID: <1159389155.21386.7.camel@amd.cathrow.org> All the documentation is available on line. http://www.redhat.com/docs/manuals/csgfs/ On Thu, 2006-09-28 at 01:23 +0530, Anand Gupta wrote: > Could you please direct me some documentation/howto where i can get a > feel of it and see how to go about installing and using it ? I heard > about the RH Cluster Suite, however wasn't able to find any > documentation to use it. > > > On 9/23/06, Rik van Riel wrote: > > Anand Gupta wrote: > > I was wondering what people use / recommend for a cluster fs > for use > > with xen ? > > > > Also with this cluster fs, will the domU's be using flat > files / lvm ? > > (it should be the former as per my guess since these flat > files will be > > stored on the cluster fs, but then won't performance hit > will be there > > for these domU's ? ) > > You could also use CLVM to have your guests living on logical > volumes that are visible on all cluster hosts. > > -- > "You don't have to be crazy to do this ... but it helps." -- > Bob Ross > > > > > -- > regards, > > Anand Gupta > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From xen.mails at gmail.com Wed Sep 27 20:34:39 2006 From: xen.mails at gmail.com (Anand Gupta) Date: Thu, 28 Sep 2006 02:04:39 +0530 Subject: [Fedora-xen] what do you recommend for cluster fs ?? In-Reply-To: <1159389155.21386.7.camel@amd.cathrow.org> References: <4515717E.4030605@redhat.com> <1159389155.21386.7.camel@amd.cathrow.org> Message-ID: On 9/28/06, Andrew Cathrow wrote: > > All the documentation is available on line. > > http://www.redhat.com/docs/manuals/csgfs/ > Thanks for the pointer Andrew. -- regards, Anand Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrian at creative.net.au Thu Sep 28 04:21:53 2006 From: adrian at creative.net.au (Adrian Chadd) Date: Thu, 28 Sep 2006 12:21:53 +0800 Subject: [Fedora-xen] Recurring Zombie (XenU used as a web server) In-Reply-To: <4512AF1A.7090606@flora.ca> References: <20060908223542.A95158B9A3@www1.email.si> <4512A68F.60107@flora.ca> <53094.12.43.115.17.1158851071.squirrel@digitalhermit.com> <4512AF1A.7090606@flora.ca> Message-ID: <20060928042153.GA1461@skywalker.creative.net.au> On Thu, Sep 21, 2006, Russell McOrmond wrote: > >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 > > Kwan Lowe wrote: > >This is the bug report I'd found... It looks like yours is the same issue: > > > >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204468 > > I've added a note there. If people can leave their consoles open and > see if there is a kernel panic similar to the one that I reported, it > may be the same xennet related bug. > > I've observed the same problem on a number of machines I administer > (Mixed Intel, AMD, etc), and each time it seems to come down to the same > xennet issue. Here's a recent crash. I can't run 2187 because it crashes almost straight away (and I think I emailed the crashdump to the list already.) Its still worrying that this oops takes out networking for all VMs.. Adrian BUG: unable to handle kernel NULL pointer dereference at virtual address 000000bc printing eip: c908e1ad *pde = ma 1509f067 pa 01ff3067 *pte = ma 00000000 pa fffff000 Oops: 0002 [#1] SMP Modules linked in: ipv6 xennet dm_snapshot dm_zero dm_mirror dm_mod raid1 CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00210046 (2.6.17-1.2157_FC5xenU #1) EIP is at network_tx_buf_gc+0xc4/0x1b7 [xennet] eax: 00000066 ebx: 00000032 ecx: c6540cfc edx: 00000000 esi: 00000001 edi: c6540400 ebp: 0000002c esp: c0651edc ds: 007b es: 007b ss: 0069 Process swapper (pid: 0, threadinfo=c0650000 task=c05f1800) Stack: <0>c6540cfc 00000000 00000000 00000004 c6540000 001ece31 001ece32 001ece12 00000000 c6540488 c6540400 c6540000 c908f150 c01b5e80 00000000 00000000 00000107 c043a57d 00000107 c6540000 c0651f88 c0651f88 00000107 c0643780 Call Trace: netif_int+0x24/0x66 [xennet] handle_IRQ_event+0x42/0x85 __do_IRQ+0x8d/0xdc do_IRQ+0x1a/0x25 evtchn_do_upcall+0x66/0x9f hypervisor_callback+0x3d/0x48 safe_halt+0x84/0xa7 xen_idle+0x46/0x4e cpu_idle+0x94/0xad start_kernel+0x346/0x34c Code: b4 9f 00 09 00 00 50 e8 9d c5 48 f7 c7 84 9f 00 09 00 00 00 00 00 00 8b 87 f4 00 00 00 89 84 9f f4 00 00 00 89 9f f4 00 00 00 90 8d 90 00 00 00 0f 94 c0 83 c4 10 84 c0 74 62 bb 00 e0 ff ff EIP: [] network_tx_buf_gc+0xc4/0x1b7 [xennet] SS:ESP 0069:c0651edc <0>Kernel panic - not syncing: Fatal exception in interrupt From berrange at redhat.com Wed Sep 27 19:58:04 2006 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 27 Sep 2006 20:58:04 +0100 Subject: [Xen-users] Re: [Fedora-xen] what do you recommend for cluster fs ?? In-Reply-To: References: <4515717E.4030605@redhat.com> Message-ID: <20060927195804.GR20056@redhat.com> On Thu, Sep 28, 2006 at 01:23:21AM +0530, Anand Gupta wrote: > Could you please direct me some documentation/howto where i can get a feel > of it and see how to go about installing and using it ? I heard about the RH > Cluster Suite, however wasn't able to find any documentation to use it. There's some docs linked off the Clustersuite dev pages: http://sources.redhat.com/cluster/ Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-users mailing list Xen-users at lists.xensource.com http://lists.xensource.com/xen-users From acathrow at redhat.com Wed Sep 27 20:32:35 2006 From: acathrow at redhat.com (Andrew Cathrow) Date: Wed, 27 Sep 2006 16:32:35 -0400 Subject: [Xen-users] Re: [Fedora-xen] what do you recommend for cluster fs ?? In-Reply-To: References: <4515717E.4030605@redhat.com> Message-ID: <1159389155.21386.7.camel@amd.cathrow.org> All the documentation is available on line. http://www.redhat.com/docs/manuals/csgfs/ On Thu, 2006-09-28 at 01:23 +0530, Anand Gupta wrote: > Could you please direct me some documentation/howto where i can get a > feel of it and see how to go about installing and using it ? I heard > about the RH Cluster Suite, however wasn't able to find any > documentation to use it. > > > On 9/23/06, Rik van Riel wrote: > > Anand Gupta wrote: > > I was wondering what people use / recommend for a cluster fs > for use > > with xen ? > > > > Also with this cluster fs, will the domU's be using flat > files / lvm ? > > (it should be the former as per my guess since these flat > files will be > > stored on the cluster fs, but then won't performance hit > will be there > > for these domU's ? ) > > You could also use CLVM to have your guests living on logical > volumes that are visible on all cluster hosts. > > -- > "You don't have to be crazy to do this ... but it helps." -- > Bob Ross > > > > > -- > regards, > > Anand Gupta > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Xen-users mailing list Xen-users at lists.xensource.com http://lists.xensource.com/xen-users From shobha_ranganathan at yahoo.com Fri Sep 29 17:16:19 2006 From: shobha_ranganathan at yahoo.com (shobha ranganathan) Date: Fri, 29 Sep 2006 10:16:19 -0700 (PDT) Subject: [Fedora-xen] xenguest-install.py - Error Bad file descriptor in FC6 Test2 DomU and Dom0 In-Reply-To: <200609291359.32516.joakley@solutioninc.com> Message-ID: <20060929171619.30572.qmail@web55902.mail.re3.yahoo.com> I have a Fedora COre 6 Test 2 dom0 built from xen-3.0.2 sources. That was succssful and "xm list "worked . I did not build a domU kernel though. I am trying to install FC6 Test2 as guest Os. I setup an http server in the same machine to grab the images of Fc6 TEst2 from a directory. When I did xenguest-install.py, I get this error. Please let me know what am I missing here. 1. Have I not setup my disks correctly ? 2. Is my http daemon configuration causing problems ? Starting install... libvir: Xen Daemon error : POST operation failed: No such domain xenbox_g1 Failed to get devices for domain xenbox_g1 Traceback (most recent call last): File "/usr/sbin/xenguest-install.py", line 476, in ? main() File "/usr/sbin/xenguest-install.py", line 467, in main start_paravirt_install(name, ram, disk, mac, uuid, bridge, src, options.extra) File "/usr/sbin/xenguest-install.py", line 344, in start_paravirt_install dom = conn.createLinux(cfgxml, 0) File "/usr/lib/python2.4/site-packages/libvirt.py", line 233, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed') libvirt.libvirtError: virDomainCreateLinux() failed The /var/log/xend.log shows as 2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG (XendDomainInfo:1217) XendDomainInfo.construct: None [2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG (XendDomainInfo:1249) XendDomainInfo.initDomain: 4 1.0 [2006-09-28 18:31:13 xend 3851] DEBUG (balloon:127) Balloon: 486224 KiB free; need 266240; done. [2006-09-28 18:31:13 xend 3851] INFO (image:134) buildDomain os=linux dom=4 vcpus=1 [2006-09-28 18:31:13 xend 3851] DEBUG (image:177) dom = 4 [2006-09-28 18:31:13 xend 3851] DEBUG (image:178) image = /var/lib/xen/vmlinuz.ypg7-X [2006-09-28 18:31:13 xend 3851] DEBUG (image:179) store_evtchn = 1 [2006-09-28 18:31:13 xend 3851] DEBUG (image:180) console_evtchn = 2 [2006-09-28 18:31:13 xend 3851] DEBUG (image:181) cmdline = root=/dev/xvd method=http://localhost [2006-09-28 18:31:13 xend 3851] DEBUG (image:182) ramdisk = /var/lib/xen/initrd.img.Y95dri [2006-09-28 18:31:13 xend 3851] DEBUG (image:183) vcpus = 1 [2006-09-28 18:31:13 xend 3851] DEBUG (image:184) features = [2006-09-28 18:31:13 xend.XendDomainInfo 3851] ERROR (XendDomainInfo:198) Domain construction failed Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 191, in create vm.initDomain() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1319, in initDomain raise VmError(str(exn)) VmError: (9, 'Bad file descriptor') [2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG (XendDomainInfo:1405) XendDomainInfo.destroy: domid=4 [2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG (XendDomainInfo:1413) XendDomainInfo.destroyDomain(4) [2006-09-28 18:31:13 xend 3851] ERROR (SrvBase:87) Request create 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/SrvDomainDir.py", line 82, in op_create raise XendError("Error creating domain: " + str(ex)) XendError: Error creating domain: (9, 'Bad file descriptor') thanks for your time --------------------------------- All-new Yahoo! Mail - Fire up a more powerful email and get things done faster. -------------- next part -------------- An HTML attachment was scrubbed... URL: From clalance at redhat.com Fri Sep 29 17:21:32 2006 From: clalance at redhat.com (Chris Lalancette) Date: Fri, 29 Sep 2006 13:21:32 -0400 Subject: [Fedora-xen] xenguest-install.py - Error Bad file descriptor in FC6 Test2 DomU and Dom0 In-Reply-To: <20060929171619.30572.qmail@web55902.mail.re3.yahoo.com> References: <20060929171619.30572.qmail@web55902.mail.re3.yahoo.com> Message-ID: <451D561C.6090602@redhat.com> shobha ranganathan wrote: > I have a Fedora COre 6 Test 2 dom0 built from xen-3.0.2 sources. That > was succssful and "xm list "worked . I did not build a domU kernel though. > > I am trying to install FC6 Test2 as guest Os. I setup an http server in > the same machine to grab the images of Fc6 TEst2 from a directory. > > When I did xenguest-install.py, I get this error. Please let me know > what am I missing here. > 1. Have I not setup my disks correctly ? > 2. Is my http daemon configuration causing problems ? > > > Starting install... > libvir: Xen Daemon error : POST operation failed: No such domain xenbox_g1 > Failed to get devices for domain xenbox_g1 > Traceback (most recent call last): > File "/usr/sbin/xenguest-install.py", line 476, in ? > main() > File "/usr/sbin/xenguest-install.py", line 467, in main > start_paravirt_install(name, ram, disk, mac, uuid, bridge, src, > options.extra) > File "/usr/sbin/xenguest-install.py", line 344, in start_paravirt_install > dom = conn.createLinux(cfgxml, 0) > File "/usr/lib/python2.4/site-packages/libvirt.py", line 233, in > createLinux > if ret is None:raise libvirtError('virDomainCreateLinux() failed') > libvirt.libvirtError: virDomainCreateLinux() failed > > > The /var/log/xend.log shows as > > 2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG > (XendDomainInfo:1217) XendDomainInfo.construct: None > [2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG > (XendDomainInfo:1249) XendDomainInfo.initDomain: 4 1.0 > [2006-09-28 18:31:13 xend 3851] DEBUG (balloon:127) Balloon: 486224 KiB > free; need 266240; done. > [2006-09-28 18:31:13 xend 3851] INFO (image:134) buildDomain os=linux > dom=4 vcpus=1 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:177) dom = 4 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:178) image = > /var/lib/xen/vmlinuz.ypg7-X > [2006-09-28 18:31:13 xend 3851] DEBUG (image:179) store_evtchn = 1 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:180) console_evtchn = 2 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:181) cmdline = > root=/dev/xvd method=http://localhost > [2006-09-28 18:31:13 xend 3851] DEBUG (image:182) ramdisk = > /var/lib/xen/initrd.img.Y95dri > [2006-09-28 18:31:13 xend 3851] DEBUG (image:183) vcpus = 1 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:184) features = > [2006-09-28 18:31:13 xend.XendDomainInfo 3851] ERROR > (XendDomainInfo:198) Domain construction failed > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 191, in create > vm.initDomain() > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 1319, in initDomain > raise VmError(str(exn)) > VmError: (9, 'Bad file descriptor') > [2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG > (XendDomainInfo:1405) XendDomainInfo.destroy: domid=4 > [2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG > (XendDomainInfo:1413) XendDomainInfo.destroyDomain(4) > [2006-09-28 18:31:13 xend 3851] ERROR (SrvBase:87) Request create 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/SrvDomainDir.py", line > 82, in op_create > raise XendError("Error creating domain: " + str(ex)) > XendError: Error creating domain: (9, 'Bad file descriptor') > > thanks for your time > > ------------------------------------------------------------------------ > All-new Yahoo! Mail > - > Fire up a more powerful email and get things done faster. > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen Hi there, Take a look at /var/log/xend-debug.log; is there something that talks about trying to run a PAE domU on a non-PAE hypervisor? If so, you need to recompile your dom0 to use pae (when you compile, put pae=y on the command-line). All of the FC6 paravirt kernels are PAE, and these need to match. Chris Lalancette From shobha_ranganathan at yahoo.com Fri Sep 29 17:35:52 2006 From: shobha_ranganathan at yahoo.com (shobha ranganathan) Date: Fri, 29 Sep 2006 10:35:52 -0700 (PDT) Subject: [Fedora-xen] xenguest-install.py - Error Bad file descriptor in FC6 Test2 DomU and Dom0 In-Reply-To: <451D561C.6090602@redhat.com> Message-ID: <20060929173552.95747.qmail@web55909.mail.re3.yahoo.com> Thanks a bunch. I see the ERROR in log as "PAE kernel on non PAE host" So I should do "make world pae=y" and "make install" ?? Shobha Chris Lalancette wrote: shobha ranganathan wrote: > I have a Fedora COre 6 Test 2 dom0 built from xen-3.0.2 sources. That > was succssful and "xm list "worked . I did not build a domU kernel though. > > I am trying to install FC6 Test2 as guest Os. I setup an http server in > the same machine to grab the images of Fc6 TEst2 from a directory. > > When I did xenguest-install.py, I get this error. Please let me know > what am I missing here. > 1. Have I not setup my disks correctly ? > 2. Is my http daemon configuration causing problems ? > > > Starting install... > libvir: Xen Daemon error : POST operation failed: No such domain xenbox_g1 > Failed to get devices for domain xenbox_g1 > Traceback (most recent call last): > File "/usr/sbin/xenguest-install.py", line 476, in ? > main() > File "/usr/sbin/xenguest-install.py", line 467, in main > start_paravirt_install(name, ram, disk, mac, uuid, bridge, src, > options.extra) > File "/usr/sbin/xenguest-install.py", line 344, in start_paravirt_install > dom = conn.createLinux(cfgxml, 0) > File "/usr/lib/python2.4/site-packages/libvirt.py", line 233, in > createLinux > if ret is None:raise libvirtError('virDomainCreateLinux() failed') > libvirt.libvirtError: virDomainCreateLinux() failed > > > The /var/log/xend.log shows as > > 2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG > (XendDomainInfo:1217) XendDomainInfo.construct: None > [2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG > (XendDomainInfo:1249) XendDomainInfo.initDomain: 4 1.0 > [2006-09-28 18:31:13 xend 3851] DEBUG (balloon:127) Balloon: 486224 KiB > free; need 266240; done. > [2006-09-28 18:31:13 xend 3851] INFO (image:134) buildDomain os=linux > dom=4 vcpus=1 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:177) dom = 4 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:178) image = > /var/lib/xen/vmlinuz.ypg7-X > [2006-09-28 18:31:13 xend 3851] DEBUG (image:179) store_evtchn = 1 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:180) console_evtchn = 2 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:181) cmdline = > root=/dev/xvd method=http://localhost > [2006-09-28 18:31:13 xend 3851] DEBUG (image:182) ramdisk = > /var/lib/xen/initrd.img.Y95dri > [2006-09-28 18:31:13 xend 3851] DEBUG (image:183) vcpus = 1 > [2006-09-28 18:31:13 xend 3851] DEBUG (image:184) features = > [2006-09-28 18:31:13 xend.XendDomainInfo 3851] ERROR > (XendDomainInfo:198) Domain construction failed > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 191, in create > vm.initDomain() > File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 1319, in initDomain > raise VmError(str(exn)) > VmError: (9, 'Bad file descriptor') > [2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG > (XendDomainInfo:1405) XendDomainInfo.destroy: domid=4 > [2006-09-28 18:31:13 xend.XendDomainInfo 3851] DEBUG > (XendDomainInfo:1413) XendDomainInfo.destroyDomain(4) > [2006-09-28 18:31:13 xend 3851] ERROR (SrvBase:87) Request create 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/SrvDomainDir.py", line > 82, in op_create > raise XendError("Error creating domain: " + str(ex)) > XendError: Error creating domain: (9, 'Bad file descriptor') > > thanks for your time > > ------------------------------------------------------------------------ > All-new Yahoo! Mail > - > Fire up a more powerful email and get things done faster. > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen Hi there, Take a look at /var/log/xend-debug.log; is there something that talks about trying to run a PAE domU on a non-PAE hypervisor? If so, you need to recompile your dom0 to use pae (when you compile, put pae=y on the command-line). All of the FC6 paravirt kernels are PAE, and these need to match. Chris Lalancette --------------------------------- Get your email and more, right on the new Yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From shobha_ranganathan at yahoo.com Fri Sep 29 19:50:46 2006 From: shobha_ranganathan at yahoo.com (shobha ranganathan) Date: Fri, 29 Sep 2006 12:50:46 -0700 (PDT) Subject: [Fedora-xen] Can I use Xen 3.0.2 Release 23 with Fc6 Test2 and PAE ? Message-ID: <20060929195046.58778.qmail@web55906.mail.re3.yahoo.com> Hi, I tried to compile xen 3.0.2 release 23 in Mac with Fc6 Test2. I did "make world pae=y" and "make install". "make install" gives me errors like the following. I checked in downloads website -- for FC6 Test2 , xen version is 3.0.2-23 and for Test3 it is xen-3.0.2-33. Am I missing patch ? /usr/src/redhat/BUILD/xen-unstable-10712/xen/common/built_in.o: In function `guest_physmap_add_page': /usr/src/redhat/BUILD/xen-unstable-10712/xen/include/asm/shadow.h:1538: undefined reference to `shadow_sync_and_drop_references' /usr/src/redhat/BUILD/xen-unstable-10712/xen/common/built_in.o: In function `guest_physmap_remove_page': /usr/src/redhat/BUILD/xen-unstable-10712/xen/include/asm/shadow.h:1558: undefined reference to `shadow_sync_and_drop_references' /usr/src/redhat/BUILD/xen-unstable-10712/xen/common/built_in.o: In function `guest_physmap_add_page': /usr/src/redhat/BUILD/xen-unstable-10712/xen/include/asm/shadow.h:1538: undefined reference to `shadow_sync_and_drop_references' /usr/src/redhat/BUILD/xen-unstable-10712/xen/common/built_in.o: In function `guest_physmap_remove_page': /usr/src/redhat/BUILD/xen-unstable-10712/xen/include/asm/shadow.h:1558: undefined reference to `shadow_sync_and_drop_references' /usr/src/redhat/BUILD/xen-unstable-10712/xen/common/built_in.o: In function `guest_physmap_add_page': /usr/src/redhat/BUILD/xen-unstable-10712/xen/include/asm/shadow.h:1538: undefined reference to `shadow_sync_and_drop_references' /usr/src/redhat/BUILD/xen-unstable-10712/xen/common/built_in.o: In function `free_domheap_pages': /usr/src/redhat/BUILD/xen-unstable-10712/xen/common/page_alloc.c:671: undefined reference to `shadow_drop_references' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `do_mmu_update': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/mm.c:2304: undefined reference to `shadow_l3_normal_pt_update' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `guest_physmap_add_page': /usr/src/redhat/BUILD/xen-unstable-10712/xen/include/asm/shadow.h:1538: undefined reference to `shadow_sync_and_drop_references' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `guest_physmap_remove_page': /usr/src/redhat/BUILD/xen-unstable-10712/xen/include/asm/shadow.h:1558: undefined reference to `shadow_sync_and_drop_references' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `hvm_copy': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/hvm.c:290: undefined reference to `gva_to_gpa' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `send_mmio_req': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/platform.c:761: undefined reference to `gva_to_gpa' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `send_pio_req': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/platform.c:705: undefined reference to `gva_to_gpa' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `svm_set_cr0': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/svm/svm.c:1557: undefined reference to `shadow_set_guest_paging_levels' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/svm/svm.c:1549: undefined reference to `shadow_set_guest_paging_levels' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `svm_vmexit_handler': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/svm/svm.c:2619: undefined reference to `gva_to_gpa' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/svm/svm.c:2621: undefined reference to `gva_to_gpa' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `svm_do_page_fault': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/svm/svm.c:851: undefined reference to `gva_to_gpa' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `vmx_set_cr0': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/vmx/vmx.c:1481: undefined reference to `shadow_set_guest_paging_levels' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/vmx/vmx.c:1473: undefined reference to `shadow_set_guest_paging_levels' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `mov_to_cr': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/vmx/vmx.c:1702: undefined reference to `shadow_set_guest_paging_levels' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/vmx/vmx.c:1751: undefined reference to `shadow_set_guest_paging_levels' /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/built_in.o: In function `vmx_do_page_fault': /usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86/hvm/vmx/vmx.c:801: undefined reference to `gva_to_gpa' make[3]: *** [/usr/src/redhat/BUILD/xen-unstable-10712/xen/xen-syms] Error 1 make[3]: Leaving directory `/usr/src/redhat/BUILD/xen-unstable-10712/xen/arch/x86' make[2]: *** [/usr/src/redhat/BUILD/xen-unstable-10712/xen/xen] Error 2 make[2]: Leaving directory `/usr/src/redhat/BUILD/xen-unstable-10712/xen' make[1]: *** [install] Error 2 make[1]: Leaving directory `/usr/src/redhat/BUILD/xen-unstable-10712/xen' make: *** [install-xen] Error 2 v --------------------------------- Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. -------------- next part -------------- An HTML attachment was scrubbed... URL: