From berrange at redhat.com Tue Jan 2 09:36:31 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 2 Jan 2007 09:36:31 +0000 Subject: [Fedora-xen] starting a vm with virt-manager In-Reply-To: <5bb00b3f0612280714m66f7dd90x4de881644f55ed2a@mail.gmail.com> References: <5bb00b3f0612280714m66f7dd90x4de881644f55ed2a@mail.gmail.com> Message-ID: <20070102093631.GB3351@redhat.com> On Thu, Dec 28, 2006 at 04:14:03PM +0100, Henning Sprang wrote: > Hi, > Somehow I'd expect such a nice graphical tool as virt.manager, that, > if I can install, (and start the installed machine directly after > install), stop, restore, and do all the other nice things with a xen > vm, I must also be able to simply start a vm for which I have a config > lying around. > > But I see nowhere any "start a vm" option. The only thing that is > there is a "restore vm" option, but when I chose a normal vm config > file, it always says "error restring domain - is the domain already > running". > I assume, this function is really only for domains that I saved (not > the same as opposed to shut down, at leat in xen terminology). > > Is that right? Am I right that virt.manager has no functionality to > simply start a vm with it's config file, and I must do this manually? The problem is ultimately in XenD itself - the RPC protocol used for managing VMs has no spport for inactive guests - the 'xm' command line tool has this functionality hardcoded in itself so its not exposed to other tools via the API. The new Xen 3.0.4 released 2 weeks ago does now have inactive guest support, so Xen in Fedora 7 will likely support this. For the Xen 3.0.3 in Fedora Core 6, we have had to write some extra code in libvirt to manage inactive domains by bypassing XenD. This was just pushed to Fedora updates in libvirt 0.1.10 a few days back. Thus I will now be able to enable support for inactive domains in the next release of virt-manager - hopefully within the next couple of weeks. So, yes, you are right that there is no way to start an existing guest using virt-manager in Fedora today. We are actively implemnenting this so expect it to appear in the near future.... 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 ask at develooper.com Tue Jan 2 12:06:51 2007 From: ask at develooper.com (=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=) Date: Tue, 2 Jan 2007 04:06:51 -0800 Subject: [Fedora-xen] writegrub crash during xen install Message-ID: <4DEDDD20-BFBA-420C-8753-F7B78CF959AE@develooper.com> Hi, I am starting my install like this, virt-install -n cpansearch -r 768 -f /dev/vgmirror/xm-cpansearch -b xenbr1 -p -l http://mirrors.la.sol/fedora/install/x86_64/ --vnc -d -x ks=http://mirrors.la.sol/fedora/ks/xen.cfg -d My kickstart file is at http://tmp.askask.com/2007/01/xen.cfg After all the RPM are installed, I get the following crash. This is with the most recent fedora 6 updates on the Dom0 system. I've tried doing the install both with a "clean FC6" tree and with a tree that had the updates merged in. Traceback (most recent call first): File "/usr/lib/booty/bootloaderInfo.py", line 711, in writeGrub f = open(instRoot + cf, "w+") File "/usr/lib/booty/bootloaderInfo.py", line 1188, in write justConfig | (not self.useGrubVal)) File "/usr/lib/anaconda/bootloader.py", line 187, in writeBootloader justConfigFile, anaconda.intf) File "/usr/lib/anaconda/dispatch.py", line 199, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 122, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 923, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 950, in handleRenderCallback self.currentWindow.renderCallback() IOError: [Errno 30] Read-only file system: '/mnt/sysimage/boot/grub/ grub.conf' Any ideas? - ask -- http://develooper.com/ - http://askask.com/ From info at vsic.net Wed Jan 3 02:53:20 2007 From: info at vsic.net (Frank Morane) Date: Tue, 02 Jan 2007 20:53:20 -0600 Subject: [Fedora-xen] error mounting /proc: any solution ? Message-ID: <459B1AA0.8050009@vsic.net> Hi, This problem has been around since September 2006. The last working version I used was vmlinuz-2.6.16-1.2133_FC5xenU under vmlinuz-2.6.16-1.2133_FC5xen0. The domu I try to run is CentOs 4.4 which runs fine under FC5. The reason I want to make it work is that we have production servers and we wish to avoid having to re install everything and migrate a big bunch of domains and database etc. I am trying to run my existing domU with FC6 but I cannot get passed this root system problem. I tried with other distros and get the same problem, same thing with XenExpress. I am waiting from XenSource to find out if they can help but probably too much champagne on new year's day is delaying response. If possible I would rather stick with FCX as I had it running without too much problem for 18 months but the updates have become problematic since September. I have read many, many people talking about this over the last 4 months but not a single solution to the problem, has anyone a detailed howto to get it up and running? I tried the faq about initrd, I am no iniscript expert and I failed, I tried with binaries, I tried compiling from source with many variant, with and without modules (or builtin) etc. Alway the same result. All log simply confirms the problem below. Also, can it be run under a FC6 dom0 on a Opteron if the domU is i686? Finally, the doc on setting up a VMX is rather sparse, can someone point to a more detail howto? Regards, [root at localhost xen]# xm create -c thoreau Using config file "thoreau". Started domain thoreau Bootdata ok (command line is root=/dev/sda1 ro) Linux version 2.6.18-1.2868.fc6xen (brewbuilder at hs20-bc1-5.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Fri Dec 15 17:47:25 EST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) No mptable found. Built 1 zonelists. Total pages: 133120 Kernel command line: root=/dev/sda1 ro Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2010.298 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Software IO TLB disabled Memory: 504444k/532480k available (2321k kernel code, 19164k reserved, 1087k data, 172k init) Calibrating delay using timer specific routine.. 5027.54 BogoMIPS (lpj=10055097) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU: Physical Processor ID: 1 CPU: Processor Core ID: 1 (SMP-)alternatives turned off Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 6, 262144 bytes) TCP established hash table entries: 131072 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1167787607.766:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key DF110FCA12BBB71F - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Bootdata ok (command line is root=/dev/sda1 ro) Linux version 2.6.18-1.2868.fc6xen (brewbuilder at hs20-bc1-5.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Fri Dec 15 17:47:25 EST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) No mptable found. Built 1 zonelists. Total pages: 133120 Kernel command line: root=/dev/sda1 ro Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2010.298 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Software IO TLB disabled Memory: 504444k/532480k available (2321k kernel code, 19164k reserved, 1087k data, 172k init) Calibrating delay using timer specific routine.. 5027.54 BogoMIPS (lpj=10055097) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU: Physical Processor ID: 1 CPU: Processor Core ID: 1 (SMP-)alternatives turned off Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 6, 262144 bytes) TCP established hash table entries: 131072 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1167787607.766:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key DF110FCA12BBB71F - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new driver libusual usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2052 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vbd/2051 XENBUS: Device with no driver: device/vif/0 Write protecting the kernel read-only data: 440k Red Hat nash version 5.1.19.0.2 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading ohci-hcd.ko module Loading ehci-hcd.ko module Loading jbd.ko module Loading ext3.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading 3w-9xxx.ko module 3ware 9000 Storage Controller device driver for Linux v2.26.02.007. Loading shpchp.ko module shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Loading libata.ko module Loading sata_nv.ko module Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! -- Frank Morane (Free Thinker) http://www.adventuresinlegalland.com http://www.lysanderspooner.org http://thoreau.eserver.org From adrian at creative.net.au Wed Jan 3 02:05:02 2007 From: adrian at creative.net.au (Adrian Chadd) Date: Wed, 3 Jan 2007 10:05:02 +0800 Subject: [Fedora-xen] error mounting /proc: any solution ? In-Reply-To: <459B1AA0.8050009@vsic.net> References: <459B1AA0.8050009@vsic.net> Message-ID: <20070103020502.GC12569@skywalker.creative.net.au> On Tue, Jan 02, 2007, Frank Morane wrote: > Hi, > > This problem has been around since September 2006. The last working > version I used was vmlinuz-2.6.16-1.2133_FC5xenU under > vmlinuz-2.6.16-1.2133_FC5xen0. The domu I try to run is CentOs 4.4 which > runs fine under FC5. Could you paste the config file please? > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/2049 > XENBUS: Device with no driver: device/vbd/2052 > XENBUS: Device with no driver: device/vbd/2050 > XENBUS: Device with no driver: device/vbd/2051 > XENBUS: Device with no driver: device/vif/0 This is a big hint - if you were running PVM (which I can only guess at since you haven't provided a config file) then it sounds like you've not got the network and block device drivers loaded. The network side is easy - I have this trouble from time to time - just add 'xennet' in /etc/modules. This assumes the block device drivers are loaded and the system has mounted root. The block device is a bit more worrying - I'll wait until you've posted your config file so I can guess what kernel you're booting. Adrian From info at vsic.net Wed Jan 3 03:18:51 2007 From: info at vsic.net (Frank Morane) Date: Tue, 02 Jan 2007 21:18:51 -0600 Subject: [Fedora-xen] error mounting /proc: any solution ? In-Reply-To: <20070103020502.GC12569@skywalker.creative.net.au> References: <459B1AA0.8050009@vsic.net> <20070103020502.GC12569@skywalker.creative.net.au> Message-ID: <459B209B.5090803@vsic.net> Adrian Chadd wrote: > On Tue, Jan 02, 2007, Frank Morane wrote: > >> Hi, >> >> This problem has been around since September 2006. The last working >> version I used was vmlinuz-2.6.16-1.2133_FC5xenU under >> vmlinuz-2.6.16-1.2133_FC5xen0. The domu I try to run is CentOs 4.4 which >> runs fine under FC5. >> > > Could you paste the config file please? > > >> NET: Registered protocol family 17 >> XENBUS: Device with no driver: device/vbd/2049 >> XENBUS: Device with no driver: device/vbd/2052 >> XENBUS: Device with no driver: device/vbd/2050 >> XENBUS: Device with no driver: device/vbd/2051 >> XENBUS: Device with no driver: device/vif/0 >> > > This is a big hint - if you were running PVM (which I can only guess at since > you haven't provided a config file) then it sounds like you've not got the > network and block device drivers loaded. > > The network side is easy - I have this trouble from time to time - just > add 'xennet' in /etc/modules. This assumes the block device drivers > are loaded and the system has mounted root. > > The block device is a bit more worrying - I'll wait until you've posted > your config file so I can guess what kernel you're booting. > I used the original one and I get the same problem with the fc6xen: [root at localhost xen]# cat Cent kernel = "/boot/vmlinuz-2.6.16-1.2133_FC5xenU" #kernel = "/boot/vmlinuz-2.6.18-1.2869.fc6xen" memory = 512 name = "thoreau" ramdisk = "/boot/initrd-2.6.16-1.2133_FC5xenU.img" #ramdisk = "/boot/initrd-2.6.18-1.2869.fc6xen.img" #ip = "192.168.0.50" #netmask = "255.255.255.255" #gateway = "192.168.0.1" #hostname = "testing" vif = [ '' ] #dhcp = "dhcp" disk = ['phy:/dev/VSI/thoreau,sda1,w','phy:/dev/VSI/thoreauHS,sda4,w','phy:/dev/VSI/swap1G-1,sda2,w','phy:/dev/VSI/tmp1G-1,sda3,w'] #disk = ['file:/img/centos.4-3.VSI,sda1,w','phy:/dev/VolGroup00/swap1,sda2,w','file:/img/tmpfiles,sda3,w'] root = "/dev/sda1 ro" Thank you for your quick response. ++ > > > Adrian > > > -- Frank Morane (Free Thinker) http://www.adventuresinlegalland.com http://www.lysanderspooner.org http://thoreau.eserver.org From majulier at hotmail.com Wed Jan 3 20:30:26 2007 From: majulier at hotmail.com (Mike Julier) Date: Wed, 3 Jan 2007 12:30:26 -0800 Subject: [Fedora-xen] virt-install "ERROR: CD device must exist" Message-ID: I am: New to Linux New to Xen Working with new(er) motherboard (intel DG965SS). When running virt-install I get to the "what would you like to use for the virtual CD image?" question I get "ERROR: CD device must exist!" I have tried answering the question with: - nfs:192168.1.2:/tmp/LinuxInstallTree <-- a directory with the contents of the install DVD - nfs:192.168.1.2:/tmp/LinuxInstallDisk <-- a directory containing the .iso file of the install DVD - nfs:192.168.1.2:/tmp/LinuxInstallDisk/FC_6.x86_64.DVD.iso <-- the .iso file itself When I did the original install of the host (Dom0) I had to use the "linux all-generic-ide" command/option because of some sort of issue where the install script could not see the CD drive once it was ready to start actually installing. Unfortunately I have no idea if the CD error is saying that I haven't done something correctly on the host OS or if the install of the guest is barfing or obviously about to barf so the script is killing it early. I can't see the CD drive when running either the .fc6 or .fc6xen kernels. (I'm under the impression that would be hoping for too much given my inexperience and newness of the mobo.) Thanks for any help. Please feel free to ask any clarifying questions. -------------- next part -------------- An HTML attachment was scrubbed... URL: From webmaster at livebands.nl Thu Jan 4 03:13:33 2007 From: webmaster at livebands.nl (Jeroen Beerstra) Date: Thu, 4 Jan 2007 04:13:33 +0100 Subject: [Fedora-xen] problems with rhel4(clone) as DomainU on FC6 Xen host Message-ID: <200701040413.34235.webmaster@livebands.nl> hi there, I am currently playing around with the Xen support in FC6. Installation of Xen and FC6 Domain0, setting up a FC6 guest with virt-manager all went well, however I did not succeed in running a second RHEL4(clone) guest I prepped with Qemu. It took quite some time to figure things out, firstly the host is x86_64 and the guest is/was a 32 bit X/OS (Dutch RHEL clone) desktop , but if I understand things correctly there shouldn't be any problems when running a 64 bit kernel with 32 bit userland. Then I had to learn that a initrd for domain0 is not the same as one for a domainU :) After that the guest booted with the FC6 Xen kernel when I disabled SELinux , however udev fails to start which makes the bootup stop on filesystem check time because I used the default LVM setup and the LVM devices are not created, so the rootfs cannot be found. The repair shell however showed the rootfs is mounted on /dev/mapper/VolGroup00-LogVol00 ro and a remount rw does work even though /dev/mapper/VolGroup00-LogVol00 does not seem to exist :? So I decided I needed a Xen enabled RHEL4 x86_64 kernel and got it from http://people.redhat.com/~jbaron/rhel4/RPMS.kernel/. I could also convert the image to a non LVM one (the Centos4.4 guest from jailtime.org does bootup properly even though it has the same udev problem, because of this), but I rather have a fully functional X/OS. Ofcourse there were problems. I could not install the x86_64 kernel inside the X/OS guest booted with Qemu so I tried manually putting things in place. Running '/sbin/new-kernel-pkg --package kernel-xenU --mkinitrd --depmod --install 2.6.9-42.36.ELxenU' produced some errors related to strip and 64bit kernel modules, but the initrd got created. I'm sure I can work around this if needed, however Xen crashes on the RHEL4 Xen kernel right away: # xm create -c VirtualXOS4_test Using config file "VirtualXOS4_test". Started domain VirtualXOS4 xen_start_info @ffffffff8068a000 shared @m0000fc7000 @ffffffff80107000=@ffffffffff5fd000 [0x802] xen_start_info: @ffffffff8068a000 cr3 0000000000101000 pml4p ffffffff80101ff8 pml4e 0000000000103067 (real 0000000028292067) pgdp ffffff8000103ff0 pgde 0000000000105067 (real 00000000064cc067) pmdp ffffff8000105018 pmde 0000000000693067 (real 0000000066165067) ptep ffffff8000693450 pte 001000000068a027 (real 0010000006c13027) xen_shared_info: @ffffffffff5fd000 cr3 0000000000101000 pml4p ffffffff80101ff8 pml4e 0000000000103067 (real 0000000028292067) pgdp ffffff8000103ff8 pgde 0000000000000000 is none PAGE_OFFSET+1.2: @ffffff8000001000 cr3 0000000000101000 pml4p ffffffff80101ff8 pml4e 0000000000103067 (real 0000000028292067) pgdp ffffff8000103000 pgde 0000000000694067 (real 00000000567a2067) pmdp ffffff8000694000 pmde 0000000000695067 (real 0000000067e6c067) ptep ffffff8000695008 pte 0000000000001167 (real 0000000008709167) Is the RHEL4 Xen kernel incompatible with FC6 Xen? If so does anybody know if an updated version exists and were to get it? And then there is pygrub, with the FC6 guest created by virt-manager this works like a charm, however with the X/OS guest it just won't work: # xm create -c VirtualXOS4 Using config file "VirtualXOS4". Going to boot X/OS Linux (2.6.9-42.36.ELxenU) kernel: /vmlinuz-2.6.9-42.36.ELxenU initrd: /initrd-2.6.9-42.36.ELxenU.img Error: invalid literal for int(): gh I even tried copying over the grub installation from the FC6 x86_64 guest, but the problem remains. Anybody has any idea why pygrub is failing: Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 194, in create vm.construct() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1257, in construct handle = uuid.fromString(self.info['uuid'])) File "/usr/lib64/python2.4/site-packages/xen/xend/uuid.py", line 67, in fromString return [ int(s[i : i + 2], 16) for i in range(0, 32, 2) ] ValueError: invalid literal for int(): gh [2007-01-04 03:47:06 xend.XendDomainInfo 3323] DEBUG (XendDomainInfo:1449) XendDomainInfo.destroy: domid=None [2007-01-04 03:47:06 xend 3323] ERROR (xmlrpclib2:184) invalid literal for int(): gh Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/util/xmlrpclib2.py", line 162, in _marshaled_dispatch response = self._dispatch(method, params) File "/usr/lib64/python2.4/SimpleXMLRPCServer.py", line 406, in _dispatch return func(*params) File "/usr/lib64/python2.4/site-packages/xen/xend/server/XMLRPCServer.py", line 64, in domain_create info = XendDomain.instance().domain_create(config) File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 228, in domain_create dominfo = XendDomainInfo.create(config) File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 194, in create vm.construct() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1257, in construct handle = uuid.fromString(self.info['uuid'])) File "/usr/lib64/python2.4/site-packages/xen/xend/uuid.py", line 67, in fromString return [ int(s[i : i + 2], 16) for i in range(0, 32, 2) ] ValueError: invalid literal for int(): gh -- regards, Jeroen Beerstra From topgun.in at gmail.com Thu Jan 4 10:15:50 2007 From: topgun.in at gmail.com (Pushkar Pande) Date: Thu, 4 Jan 2007 15:45:50 +0530 Subject: [Fedora-xen] Xen error on FC 5, problem creating guest Message-ID: <4dee6a190701040215u10a034aakac865472d803d74f@mail.gmail.com> Hi, I am working on a P4, 2.4 GHz intel system with 512 MB of RAM. I installed the xen0 and the xenU kernel that comes along with the installation DVD. I am able to boot xen, and the 'xm list' command shows the Domain-0 running. I tried to build a guest with the following config file kernel="/usr/lib/xen/boot/hvmloader" name="FC5Guest" memory=256 root="/dev/hda1" disk=['phy:/root/temp/disk.img,hda1,w'] vif=[''] saved to fc5-inst when i tried to create the guest using 'xm create -c fc5-inst' , i get the following error 'Error creating Domain: (22, 'Invalid Argument') ' I am new to xen, please help me out. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.vonsteiger at bluewin.ch Thu Jan 4 10:44:07 2007 From: thomas.vonsteiger at bluewin.ch (Thomas von Steiger) Date: Thu, 4 Jan 2007 11:44:07 +0100 Subject: AW: [Fedora-xen] Xen error on FC 5, problem creating guest In-Reply-To: <4dee6a190701040215u10a034aakac865472d803d74f@mail.gmail.com> Message-ID: <00b801c72fed$42ee0c00$3201a8c0@athlon> If you use a image file for the guest you need "file" not "phy" in disk definition. Thomas _____ Von: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Im Auftrag von Pushkar Pande Gesendet: Donnerstag, 4. Januar 2007 11:16 An: fedora-xen at redhat.com Betreff: [Fedora-xen] Xen error on FC 5, problem creating guest Hi, I am working on a P4, 2.4 GHz intel system with 512 MB of RAM. I installed the xen0 and the xenU kernel that comes along with the installation DVD. I am able to boot xen, and the 'xm list' command shows the Domain-0 running. I tried to build a guest with the following config file kernel="/usr/lib/xen/boot/hvmloader" name="FC5Guest" memory=256 root="/dev/hda1" disk=['phy:/root/temp/disk.img,hda1,w'] vif=[''] saved to fc5-inst when i tried to create the guest using 'xm create -c fc5-inst' , i get the following error 'Error creating Domain: (22, 'Invalid Argument') ' I am new to xen, please help me out. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas.vonsteiger at bluewin.ch Thu Jan 4 10:53:58 2007 From: thomas.vonsteiger at bluewin.ch (Thomas von Steiger) Date: Thu, 4 Jan 2007 11:53:58 +0100 Subject: AW: [Fedora-xen] Xen error on FC 5, problem creating guest In-Reply-To: <00b801c72fed$42ee0c00$3201a8c0@athlon> Message-ID: <00c301c72fee$a2caf380$3201a8c0@athlon> Sorry, and there is more todo. Check this webpages for howto setup xen guests. http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 or http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 thomas _____ Von: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Im Auftrag von Thomas von Steiger Gesendet: Donnerstag, 4. Januar 2007 11:44 An: 'Pushkar Pande'; fedora-xen at redhat.com Betreff: AW: [Fedora-xen] Xen error on FC 5, problem creating guest If you use a image file for the guest you need "file" not "phy" in disk definition. Thomas _____ Von: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Im Auftrag von Pushkar Pande Gesendet: Donnerstag, 4. Januar 2007 11:16 An: fedora-xen at redhat.com Betreff: [Fedora-xen] Xen error on FC 5, problem creating guest Hi, I am working on a P4, 2.4 GHz intel system with 512 MB of RAM. I installed the xen0 and the xenU kernel that comes along with the installation DVD. I am able to boot xen, and the 'xm list' command shows the Domain-0 running. I tried to build a guest with the following config file kernel="/usr/lib/xen/boot/hvmloader" name="FC5Guest" memory=256 root="/dev/hda1" disk=['phy:/root/temp/disk.img,hda1,w'] vif=[''] saved to fc5-inst when i tried to create the guest using 'xm create -c fc5-inst' , i get the following error 'Error creating Domain: (22, 'Invalid Argument') ' I am new to xen, please help me out. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vehre at gmx.de Thu Jan 4 11:39:34 2007 From: vehre at gmx.de (Andre Vehreschild) Date: Thu, 4 Jan 2007 12:39:34 +0100 Subject: [Fedora-xen] System hang when starting cups in Xen Message-ID: <200701041239.34733.vehre@gmx.de> Hi, I installed the current xen-kernel on a FC6 and tried to boot it on my Intel Core 2 Duo. Everthing seems fine until the system tries to start the printer-service cups for a locally connect parallel port printer. It simply hangs forever. After a reboot, I checked if the non xen-kernel is able to boot: It is. Next I went into the interactive mode, when rebooting into xen. I neglected the start of cups and the system continued to start up upto the yum-updatesd. Then hanging again. Do I miss something? Do have to configure something before I am able to install the rpms as provided by Fedora? I use Fedora Core 6 with the most recent updates kernel-xen-2.6.18-1.2869.fc6 on an Intel Core 2 Duo E6600 1GB Ram on a Gigabyte 965G Board. Thanks in advance for any advices. Greetings, Andre -- Andre Vehreschild * Kreuzherrenstr. 8 * 52062 Aachen * Tel.: 0241/929 10 18 email: vehre at gmx.de oder vehre at freenet.de * Mobil: 0178/38 37 5 36 From kms at passback.co.uk Thu Jan 4 13:38:35 2007 From: kms at passback.co.uk (Keith Sharp) Date: Thu, 04 Jan 2007 13:38:35 +0000 Subject: [Fedora-xen] System hang when starting cups in Xen In-Reply-To: <200701041239.34733.vehre@gmx.de> References: <200701041239.34733.vehre@gmx.de> Message-ID: <1167917915.17019.6.camel@animal.passback.co.uk> On Thu, 2007-01-04 at 12:39 +0100, Andre Vehreschild wrote: > Hi, > > I installed the current xen-kernel on a FC6 and tried to boot it on my Intel > Core 2 Duo. Everthing seems fine until the system tries to start the > printer-service cups for a locally connect parallel port printer. It simply > hangs forever. After a reboot, I checked if the non xen-kernel is able to > boot: It is. Next I went into the interactive mode, when rebooting into xen. > I neglected the start of cups and the system continued to start up upto the > yum-updatesd. Then hanging again. > > Do I miss something? Do have to configure something before I am able to > install the rpms as provided by Fedora? > > I use Fedora Core 6 with the most recent updates kernel-xen-2.6.18-1.2869.fc6 > on an Intel Core 2 Duo E6600 1GB Ram on a Gigabyte 965G Board. I saw something similar a while back and opened Red Hat bug 151491: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151491 which led to Xen bug 13: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=13 The resolution for me was getting ACPI support into the Xen kernels. FC6 + Xen works fine on the same hardware. Keith. From davidsen at tmr.com Fri Jan 5 22:12:57 2007 From: davidsen at tmr.com (Bill Davidsen) Date: Fri, 05 Jan 2007 17:12:57 -0500 Subject: [Fedora-xen] System hang when starting cups in Xen In-Reply-To: <200701041239.34733.vehre@gmx.de> References: <200701041239.34733.vehre@gmx.de> Message-ID: <459ECD69.3040705@tmr.com> Andre Vehreschild wrote: > Hi, > > I installed the current xen-kernel on a FC6 and tried to boot it on my Intel > Core 2 Duo. Everthing seems fine until the system tries to start the > printer-service cups for a locally connect parallel port printer. It simply > hangs forever. After a reboot, I checked if the non xen-kernel is able to > boot: It is. Next I went into the interactive mode, when rebooting into xen. > I neglected the start of cups and the system continued to start up upto the > yum-updatesd. Then hanging again. > > Do I miss something? Do have to configure something before I am able to > install the rpms as provided by Fedora? > > I use Fedora Core 6 with the most recent updates kernel-xen-2.6.18-1.2869.fc6 > on an Intel Core 2 Duo E6600 1GB Ram on a Gigabyte 965G Board. I have a similar but not identical system, and no problem. You might try some acpi options at boot time, and see if there's a change. I read something about this, but I can't remember details as I didn't have the issue. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979 From justin.wickett at duke.edu Sat Jan 6 05:27:17 2007 From: justin.wickett at duke.edu (Justin Wickett) Date: Sat, 6 Jan 2007 00:27:17 -0500 Subject: [Fedora-xen] treating logical volumes as physical drives In-Reply-To: <6C87D792-F4C3-4EEB-B59E-C0F2DE5288DE@duke.edu> References: <6C87D792-F4C3-4EEB-B59E-C0F2DE5288DE@duke.edu> Message-ID: <76D55B5D-CF82-43CD-B0E3-382B6D9946C5@duke.edu> I decided to go with my third approach and ended up installing FC5 on an ext3 formatted logical volume within my LVM partition containing my host OS (FC6) and specified a FC5 xen PAE-supported kernel in my xen config file. The kernel seemed to load without any problems when I tried creating the xen config file while in FC6, but panicked since I failed to "append a correct "root=" boot option". From the console view, I noticed that my kernel command line was "root=/dev/hda2/dev/ VolGroup00/xm_fc5_001_lv ro 4", which obviously doesn't make any sense. I followed the basic install for FC6, with the addition of creating multiple logical volumes within my LVM partition. What would be the correct string to set the root variable found inside of the xen config files as? Here are the last couple of lines I get while in console view before the kernel panics... md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "hda2/dev/VolGroup00/xm_fc5_001_lv" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0,0) More of my system information can be viewed at http://www.duke.edu/ ~jyw2/xenerrors.html Justin Wickett Duke 2010 http://www.duke.edu/~jyw2 On Dec 30, 2006, at 4:07 PM, Justin Wickett wrote: > I would like to use a logical volume as a "physical" drive on which > I can install a fedora operating system. As of now, when I run > xenguest-installer, it treats the install location that I specified > ( which is an unformatted logical volume that I had just created ) > as a physical drive (named "xvda") and allows me to perform a basic > install on it. When I look at that logical volume, it comes up as a > "foreign" device, because it contains a /boot directory, and a > volume group consisting of a / directory and a swap directory. I > was wondering how to mimic that effect without using my xenguest- > installer program, so that when I pop a CD in and the installer > starts up, I can specify a logical volume and let the installer > treat it as a physical drive just like the xenguest-installer > program does. > > I am trying to accomplish this because I was unable to install FC4 > via the xenguest-installer. I had mounted the image as a loopback > device to /var/ftp/pub and specified the /pub directory in FTP > server's root folder as my "Installation source", and was greeted > by an error from my FTP server (vsftpd) saying "550 Failed to > change directory". When I do the exact same thing except mount the > FC6 iso instead of the FC4 iso, everything works fine. What could I > be doing wrong? > > If all else fails, I guess I can just specify in my /etc/xen/xm- > fc4-001 file the kernel and the ramdisk parameters, and install FC4 > on an ext3 formatted logical volume specified as the / directory, > and thus reuse my existing /boot directory instead of trying to use > the pygrub bootloader with a new /boot directory. In this case, > where could I find a compiled xenU kernel and an appropriate initrd > image for FC4? > > Thank you very much and happy new years to all! > > Justin Wickett > Duke 2010 > http://www.duke.edu/~jyw2 > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From acathrow at redhat.com Sat Jan 6 16:32:28 2007 From: acathrow at redhat.com (Andrew Cathrow) Date: Sat, 06 Jan 2007 11:32:28 -0500 Subject: [Fedora-xen] treating logical volumes as physical drives In-Reply-To: <76D55B5D-CF82-43CD-B0E3-382B6D9946C5@duke.edu> References: <6C87D792-F4C3-4EEB-B59E-C0F2DE5288DE@duke.edu> <76D55B5D-CF82-43CD-B0E3-382B6D9946C5@duke.edu> Message-ID: <1168101148.17678.6.camel@amd.cathrow.org> So looking at your xen config on your web page we see this kernel = "/boot/vmlinuz-2.6.18-1.2257.fc5xen" #initrd = "/boot/initrd-2.6.18-1.2257.fc5xen.img" memory = "400" name = "xm-fc5-001" disk = [ 'phy:/dev/VolGroup00/xm_fc5_001_lv,xvda,w' ] root = "/dev/hda2/dev/VolGroup00/xm_fc5_001_lv ro" vif = [ '' ] #vif = [ 'mac=00:17:3f:23:67:v2, bridge=xenbr0', ] uuid = "34998936-a8a1-4252-81cc-3109181e8111" #vnc = 1 #vncunused = 1 vcpus=4 extra = "4" on_reboot = 'restart' on_crash = 'restart' Looking at your disk configuration in that file disk = [ 'phy:/dev/VolGroup00/xm_fc5_001_lv,xvda,w' ] So you're using /dev/VolGroup00/xm_fc6_001_lv as your disk in your guest domain. and that will appear to the guest as /dev/xvda So the root line is wrong. After the kernel is loaded it'll look inside the guest domain for /dev/hda2/dev/VolGroup00/xm_fc5_001_lv which doesn't exist. Typically you'd not have the kernel, initrd and root lines in the xen config. You'd use a bootloader. Remove those lines and add the following bootloader="/usr/bin/pygrub" Then start the domain with xm create -c domain-name This will give you a console with a cut down version of grub (that reads /boot/grub/grub.conf from your guest's xvda device. This presumes that you've got the xenU kernel installed in the guest domain. On Sat, 2007-01-06 at 00:27 -0500, Justin Wickett wrote: > ~jyw2/xenerrors.html -- 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 jb at scorpion77.cjb.net Sun Jan 7 00:57:17 2007 From: jb at scorpion77.cjb.net (Jeroen Beerstra) Date: Sun, 7 Jan 2007 01:57:17 +0100 Subject: [Fedora-xen] problems with rhel4(clone) as DomainU on FC6 Xen host In-Reply-To: <200701040413.34235.webmaster@livebands.nl> References: <200701040413.34235.webmaster@livebands.nl> Message-ID: <200701070157.18281.jb@scorpion77.cjb.net> hi again, Op donderdag 4 januari 2007 04:13, schreef Jeroen Beerstra: > hi there, > Just to make sure nobody is wasting time on this ... so far you haven't but one never knows ;) or just to help out somebody with similar problems. I have given up and grabbed myself an X/OS 4 x86_64 iso and guess what it just worked (tm)! Actually that is a bit oversimplified, since RHEL4 (and clones) is not XEN enabled by default so it did required some manual labour, but basicly this time following the guidelines from http://people.redhat.com/riel/RHEL4-Xen-HOWTO produced a working xen guest. The problem was with the initrd: - an initrd created on i386 RHEL4 for the x86_64 RHEL4 kernel doesn't has any modules in it, hence (?) it doesn't boot at all. - an initrd created on a FC6 guest is incompatible with RHEL4 (nash consumes 100% CPU and the correct devices for lvm are not created so the system doesn't boot) - finally an initrd created on the RHEL4 x86_64 guest (booted with qemu) for the x86_64 RHEL4 kernel did work. So you need a working x86_64 RHEL4 (clone) setup to be able to build a working initrd for the RHEL4 x86_64 xen kernels. This then does boot i386 RHEL4, but why bother :D However pygrub still doesn't work, same problem as before :( I was kindoff hoping there was some problem with x86_64 versus i386, but apparently that isn't it either ... anybody any ideas why pygrub is baling out with 'Error: invalid literal for int(): gh'?? http://people.redhat.com/riel/RHEL4-Xen-HOWTO suggests pygrub should work with RHEL4 guests. > > And then there is pygrub, with the FC6 guest created by virt-manager this > works like a charm, however with the X/OS guest it just won't work: > > # xm create -c VirtualXOS4 > Using config file "VirtualXOS4". > Going to boot X/OS Linux (2.6.9-42.36.ELxenU) > kernel: /vmlinuz-2.6.9-42.36.ELxenU > initrd: /initrd-2.6.9-42.36.ELxenU.img > Error: invalid literal for int(): gh > > I even tried copying over the grub installation from the FC6 x86_64 guest, > but the problem remains. Anybody has any idea why pygrub is failing: > > Traceback (most recent call last): > File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 194, in create > vm.construct() > File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 1257, in construct > handle = uuid.fromString(self.info['uuid'])) > File "/usr/lib64/python2.4/site-packages/xen/xend/uuid.py", line 67, in > fromString > return [ int(s[i : i + 2], 16) for i in range(0, 32, 2) ] > ValueError: invalid literal for int(): gh > [2007-01-04 03:47:06 xend.XendDomainInfo 3323] DEBUG (XendDomainInfo:1449) > XendDomainInfo.destroy: domid=None > [2007-01-04 03:47:06 xend 3323] ERROR (xmlrpclib2:184) invalid literal for > int(): gh > Traceback (most recent call last): > File "/usr/lib64/python2.4/site-packages/xen/util/xmlrpclib2.py", line > 162, in _marshaled_dispatch > response = self._dispatch(method, params) > File "/usr/lib64/python2.4/SimpleXMLRPCServer.py", line 406, in _dispatch > return func(*params) > File > "/usr/lib64/python2.4/site-packages/xen/xend/server/XMLRPCServer.py", line > 64, in domain_create > info = XendDomain.instance().domain_create(config) > File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line > 228, in domain_create > dominfo = XendDomainInfo.create(config) > File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 194, in create > vm.construct() > File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", > line 1257, in construct > handle = uuid.fromString(self.info['uuid'])) > File "/usr/lib64/python2.4/site-packages/xen/xend/uuid.py", line 67, in > fromString > return [ int(s[i : i + 2], 16) for i in range(0, 32, 2) ] > ValueError: invalid literal for int(): gh -- Jeroen Beerstra From felix.schwarz at web.de Sun Jan 7 12:34:31 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Sun, 07 Jan 2007 13:34:31 +0100 Subject: [Fedora-xen] HVM guest does not start anymore (dma_timer_expiry) Message-ID: <45A0E8D7.30008@web.de> Hi, I'm using Xen on a FC6 (x86_64) system (Dell E521, AMD X2 4200 with Pacifica-Support) with a number of different guest systems (paravirtualized as well as fully virtualized ones). One of these is a FC6 (i386), running in HVM mode (because AFAIK x86_64 Xen does not support i386 paravirtualized guests). Everything worked fine so far. Today, I did a yum update in the guest machine, loading the updates of the last 2-3 weeks. This was okay to. Unfortunately, the guest won't start anymore. I'm getting these boot messages (manually typed in here, typing errors may be present): ... no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys ... wait for some time ... hda: DMA interrupt recovery hda: lost interrupt hda: dma_timer_expiry: dma status == 0x24 (again and again) My host system is fully patched as as of 01/06/2007 and so is the guest system. As a special exception, I am running kernel version 2.6.18-1.2857.4.2.fc6.0.2.sctxen on the host system in order to get my Broadcom network chipset working. I can boot the guest just fine using qemu from Fedora Extras. Other HVM guests (such as FC5 i386) are booting just fine. Any ideas? fs From vania.toma at neurolink.net Sun Jan 7 19:59:30 2007 From: vania.toma at neurolink.net (Vania Martino Toma) Date: Sun, 07 Jan 2007 20:59:30 +0100 Subject: [Fedora-xen] "No drive found, to create filesystem"...problem with fedora 6 paravirtualization Message-ID: <45A15122.4080402@neurolink.net> Hi, i've installed fc6xen, the service of XEN and the Domain0 starts correctly. I've tried to install another fedora6 paravirtualized and i've selected installation in 1 large file (xen1) with 5 GB of space limit in /home/b4y path. The installation in VNC starts correctly, but in the window to create the partition structure, not appears the virtual hard drive. The installation stops with the message " no drive found, to create filesystem...". Help me, please!!! Best regards Vania Toma From master at bradleyland.com Mon Jan 8 00:11:20 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Sun, 7 Jan 2007 16:11:20 -0800 (PST) Subject: [Fedora-xen] Kerner oops with FC6 and xen Message-ID: <4786.192.168.2.254.1168215080.squirrel@www.bradleyland.com> Anyone seen this? I can't keep my dom0 machine running for more than a couple of days before it crashes. Kernel 2868 also crashes. [master at zeus ~]$ uname -a Linux zeus.bradleyland.com 2.6.18-1.2869.fc6xen #1 SMP Wed Dec 20 15:28:06 EST 2006 i686 athlon i386 GNU/Linux BUG: soft lockup detected on CPU#0! [] dump_trace+0x69/0x1af [] show_trace_log_lvl+0x18/0x2c [] show_trace+0xf/0x11 [] dump_stack+0x15/0x17 [] softlockup_tick+0xad/0xc4 [] timer_interrupt+0x54b/0x593 [] handle_IRQ_event+0x27/0x51 [] __do_IRQ+0x96/0xf2 [] do_IRQ+0xab/0xbc [] evtchn_do_upcall+0x64/0x9b [] hypervisor_callback+0x3d/0x48 DWARF2 unwinder stuck at hypervisor_callback+0x3d/0x48 Leftover inexact backtrace: [] sis900_interrupt+0x42/0x6ab [sis900] [] ide_intr+0xfe/0x1ab [] handle_IRQ_event+0x27/0x51 [] __do_IRQ+0x96/0xf2 [] do_IRQ+0x9e/0xbc [] br_handle_frame_finish+0xb2/0xcf [bridge] [] evtchn_do_upcall+0x64/0x9b [] hypervisor_callback+0x3d/0x48 [] rtl8169_poll+0x77/0x1d4 [r8169] [] net_rx_action+0x96/0x18b [] __do_softirq+0x5e/0xc3 [] do_softirq+0x59/0xc6 [] ktime_get+0x12/0x34 [] do_IRQ+0xb0/0xbc [] evtchn_do_upcall+0x64/0x9b [] hypervisor_callback+0x3d/0x48 [] raw_safe_halt+0x8c/0xaf [] xen_idle+0x22/0x2e [] cpu_idle+0x91/0xab [] start_kernel+0x3aa/0x3b2 [] unknown_bootoption+0x0/0x204 ======================= From justin.wickett at duke.edu Tue Jan 9 10:37:36 2007 From: justin.wickett at duke.edu (Justin Wickett) Date: Tue, 9 Jan 2007 05:37:36 -0500 Subject: [Fedora-xen] treating logical volumes as physical drives In-Reply-To: <1168101148.17678.6.camel@amd.cathrow.org> References: <6C87D792-F4C3-4EEB-B59E-C0F2DE5288DE@duke.edu> <76D55B5D-CF82-43CD-B0E3-382B6D9946C5@duke.edu> <1168101148.17678.6.camel@amd.cathrow.org> Message-ID: Thank you Andrew for the response. I am taking the pygrub route, and have specified in my xen config file that "disk = [ 'phy:/dev/ hdc,xvda,w', 'phy:/dev/VolGroup00/xm_fc5_001_lv,xvda2,w' ]". The kernel starts up fine, but when Red Hat nash starts to run, no volume groups are found. When i mount /dev/VolGroup00/xm_fc5_001_lv and 'cd' into the /dev/ directory, the only files that appear when I do an 'ls' are mapper and VolGroup00, both of which are directories. I think that my problem has to do with specifying a correct value for my 'disk' variable in the xen config file. I have included all of the important information concerning this issue on my website. As always, thanks for the help! Also, if there was simply a way you could tell Anaconda to treat a logical volume as a partition on which to install a standard FC operating system all my problems would be solved. I just specified xm- fc5-001_lv as my root partition and used my existing FC6 boot partition for my /boot kernels+data. The errors and extra info can be found at http://www.duke.edu/~jyw2/ xenerrors.html Justin Wickett Duke 2010 http://www.duke.edu/~jyw2 On Jan 6, 2007, at 11:32 AM, Andrew Cathrow wrote: > > So looking at your xen config on your web page we see this > > kernel = "/boot/vmlinuz-2.6.18-1.2257.fc5xen" #initrd = "/boot/ > initrd-2.6.18-1.2257.fc5xen.img" memory = "400" name = "xm-fc5-001" > disk = [ 'phy:/dev/VolGroup00/xm_fc5_001_lv,xvda,w' ] root = "/dev/ > hda2/dev/VolGroup00/xm_fc5_001_lv ro" vif = [ '' ] #vif = > [ 'mac=00:17:3f:23:67:v2, bridge=xenbr0', ] uuid = "34998936- > a8a1-4252-81cc-3109181e8111" #vnc = 1 #vncunused = 1 vcpus=4 extra > = "4" on_reboot = 'restart' on_crash = 'restart' Looking at your > disk configuration in that file disk = [ 'phy:/dev/VolGroup00/ > xm_fc5_001_lv,xvda,w' ] So you're using /dev/VolGroup00/ > xm_fc6_001_lv as your disk in your guest domain. and that will > appear to the guest as /dev/xvda So the root line is wrong. After > the kernel is loaded it'll look inside the guest domain for /dev/ > hda2/dev/VolGroup00/xm_fc5_001_lv which doesn't exist. Typically > you'd not have the kernel, initrd and root lines in the xen config. > You'd use a bootloader. Remove those lines and add the following > bootloader="/usr/bin/pygrub" Then start the domain with xm create - > c domain-name This will give you a console with a cut down version > of grub (that reads /boot/grub/grub.conf from your guest's xvda > device. This presumes that you've got the xenU kernel installed in > the guest domain. On Sat, 2007-01-06 at 00:27 -0500, Justin Wickett > wrote: >> ~jyw2/xenerrors.html > -- Andrew Cathrow Red Hat, Inc. (678) 733 0452 - Mobile (404) 437 > 6178 - Home Office acathrow at redhat.com From chris at webarchitects.co.uk Tue Jan 9 15:27:19 2007 From: chris at webarchitects.co.uk (Chris Croome) Date: Tue, 9 Jan 2007 15:27:19 +0000 Subject: [Fedora-xen] Encrypted virtual machines on Fedora Core 6 Message-ID: <20070109152719.GA15033@webarchitects.co.uk> Hi If anyone ever wants to create virtual machines on an encrypted hard disk then the notes here might help: http://wiki.xensource.com/xenwiki/EncryptedPartitions Chris -- Chris Croome web design http://www.webarchitects.co.uk/ web content management http://mkdoc.com/ From berrange at redhat.com Tue Jan 9 15:52:20 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 9 Jan 2007 15:52:20 +0000 Subject: [Fedora-xen] Encrypted virtual machines on Fedora Core 6 In-Reply-To: <20070109152719.GA15033@webarchitects.co.uk> References: <20070109152719.GA15033@webarchitects.co.uk> Message-ID: <20070109155220.GH2269@redhat.com> On Tue, Jan 09, 2007 at 03:27:19PM +0000, Chris Croome wrote: > Hi > > If anyone ever wants to create virtual machines on an encrypted hard > disk then the notes here might help: > > http://wiki.xensource.com/xenwiki/EncryptedPartitions That is a nice guide ! One question - you did the encryption on the raw block device (/dev/md1) and then created LVM volumes within it. Any reason you didn't do it the other way around. Eg, make /dev/md1 the PV in a VG, and then encrypt individual LVM logical volumes. There shouldn't be any real difference in securitywith the latter way, and it would remove the need to run 'vgscan' after running the luksOpen command. It would also let you use difference LUKS passwords on a per-VM basis if desired. 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 oehmes at de.ibm.com Tue Jan 9 16:14:25 2007 From: oehmes at de.ibm.com (Sven Oehme) Date: Tue, 9 Jan 2007 17:14:25 +0100 Subject: [Fedora-xen] Encrypted virtual machines on Fedora Core 6 In-Reply-To: <20070109155220.GH2269@redhat.com> Message-ID: i did the same a few days ago and the whole system freezes after i copied a few mb into the encrypted volume (with the newest kernel) i have no idea if it is related to this Problem --> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213414 but i assume not .. Sven "Daniel P. Berrange" Sent by: fedora-xen-bounces at redhat.com 01/09/07 04:52 PM Please respond to "Daniel P. Berrange" To Chris Croome cc xen-users at lists.xensource.com, fedora-xen at redhat.com Subject Re: [Fedora-xen] Encrypted virtual machines on Fedora Core 6 On Tue, Jan 09, 2007 at 03:27:19PM +0000, Chris Croome wrote: > Hi > > If anyone ever wants to create virtual machines on an encrypted hard > disk then the notes here might help: > > http://wiki.xensource.com/xenwiki/EncryptedPartitions That is a nice guide ! One question - you did the encryption on the raw block device (/dev/md1) and then created LVM volumes within it. Any reason you didn't do it the other way around. Eg, make /dev/md1 the PV in a VG, and then encrypt individual LVM logical volumes. There shouldn't be any real difference in securitywith the latter way, and it would remove the need to run 'vgscan' after running the luksOpen command. It would also let you use difference LUKS passwords on a per-VM basis if desired. 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 -=| -- 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 chris at webarchitects.co.uk Tue Jan 9 16:21:57 2007 From: chris at webarchitects.co.uk (Chris Croome) Date: Tue, 9 Jan 2007 16:21:57 +0000 Subject: [Xen-users] Re: [Fedora-xen] Encrypted virtual machines on Fedora Core 6 In-Reply-To: <20070109155220.GH2269@redhat.com> References: <20070109152719.GA15033@webarchitects.co.uk> <20070109155220.GH2269@redhat.com> Message-ID: <20070109162157.GC15033@webarchitects.co.uk> Hi On Tue 09-Jan-2007 at 03:52:20PM +0000, Daniel P. Berrange wrote: > On Tue, Jan 09, 2007 at 03:27:19PM +0000, Chris Croome wrote: > > > > http://wiki.xensource.com/xenwiki/EncryptedPartitions > > That is a nice guide ! One question - you did the encryption on the > raw block device (/dev/md1) and then created LVM volumes within it. > Any reason you didn't do it the other way around. Eg, make /dev/md1 > the PV in a VG, and then encrypt individual LVM logical volumes. > There shouldn't be any real difference in securitywith the latter way, > and it would remove the need to run 'vgscan' after running the > luksOpen command. It would also let you use difference LUKS passwords > on a per-VM basis if desired. Urm, no good reason, though I did want to just have to type one passphrase once when Dom0 boots and then be able to create and resize partitions on top of the crypted one without bothering with any LUKs stuff... Also although I have been using LUKs for a while I'm not so experienced with LVM or Xen so it's been a learning curve and I didn't think of doing it the way you have suggested... ;-) Chris -- Chris Croome web design http://www.webarchitects.co.uk/ web content management http://mkdoc.com/ From tk at ncircle.com Tue Jan 9 22:24:03 2007 From: tk at ncircle.com (Timothy D. Keanini Sr.) Date: Tue, 9 Jan 2007 16:24:03 -0600 Subject: [Fedora-xen] NetBSD 3.1 on fc6 xen 3.0.3 Message-ID: <3D053E53-A5D8-47A0-A28D-E3450209742F@ncircle.com> Hello, I've been trying to setup a instance of NetBSD-3.1 on a fc6xen Dom-0 Linux testlab 2.6.18-1.2849.fc6xen #1 SMP Fri Nov 10 12:57:36 EST 2006 x86_64 x86_64 x86_64 GNU/Linux [root at testlab netbsd]# xm info host : testlab release : 2.6.18-1.2849.fc6xen version : #1 SMP Fri Nov 10 12:57:36 EST 2006 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2189 hw_caps : 178bfbff:e3d3fbff: 00000000:00000010:00000001:00000000:00000003 total_memory : 16319 free_memory : 512 xen_major : 3 xen_minor : 0 xen_extra : .3-rc5-1.2849.f xen_caps : xen-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30) cc_compile_by : brewbuilder cc_compile_domain : build.redhat.com cc_compile_date : Fri Nov 10 12:30:42 EST 2006 xend_config_format : 2 What follows is my process and at the end my errors when I go to 'xm create' the dom-U ## setup storage space for our new netbsd instance /usr/sbin/lvcreate -L4g -n lvnetbsd31 vg --- Logical volume --- LV Name /dev/vg/lvnetbsd31 [deleted] #### download the kernels ## I tried both the Oct 31 2006 build and the Jan 6 2007 build of 3.1 from HEAD ## First try at using NetBSD-3.1 distrubution ftp.netbsd.org:/pub/NetBSD/NetBSD-3.1/i386/binary/kernel> -rw-r--r-- 1 1369 netbsd 1762990 Oct 31 05:10 netbsd-XEN3_DOMU.gz -r--r--r-- 1 1369 netbsd 1673944 Oct 31 05:12 netbsd- INSTALL_XEN3_DOMU.gz [root at testlab netbsd]# openssl dgst md5 netb* MD5(netbsd-INSTALL_XEN3_DOMU)= 68f054de424d9f3b2151a28ab125fc92 MD5(netbsd-XEN3_DOMU)= 5c9c409593ed552e97853f7d34539623 ## Second Try at this using the HEAD distrubtion ftp.netbsd.org:/pub/NetBSD/NetBSD-daily/HEAD/200701040000Z/i386/ binary/kernel> MD5(netbsd-INSTALL_XEN3_DOMU)= c80ab0a7bda7617a936a3f3244b86a8a MD5(netbsd-XEN3_DOMU)= eb7483c4604c6c57615d94ce4b078d7f [root at testlab netbsd]# file * netbsd-INSTALL_XEN3_DOMU: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for NetBSD 4.99.7, not stripped netbsd-XEN3_DOMU: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for NetBSD 4.99.7, not stripped #### Simple configuration [root at testlab netbsd]# cat /etc/xen/netbsd.cfg # main configuration name = "netbsd31" kernel = "/data/xenimages/netbsd/netbsd-INSTALL_XEN3_DOMU" root="/dev/hda1" memory = 512 disk = [ 'phy:/dev/vg/lvnetbsd31,0x3,w' ] #network information ip = "10.10.80.60" netmask = "255.255.255.0" gateway = "10.10.80.1" ##### [root at testlab netbsd]# cp netbsd.cfg /etc/xen/netbsd.cfg [root at testlab netbsd]# xm create -c /etc/xen/netbsd.cfg Using config file "/etc/xen/netbsd.cfg". Error: (22, 'Invalid argument') ## xend.log output [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 190) XendDomainInfo.create(['vm', ['name', 'netbsd31'], ['memory', 512], ['vcpus', 1], ['image', ['linux', ['kernel', '/data/xenimages/ netbsd/netbsd-INSTALL_XEN3_DOMU'], ['ip', '10.10.80.60:1.2.3.4:10.10.80.1:255.255.255.0::eth0:off'], ['root', '/ dev/hda1'], ['vncunused', 1], ['xauthority', '/root/.Xauthority']]], ['device', ['vbd', ['uname', 'phy:/dev/vg/lvnetbsd31'], ['dev', '0x3'], ['mode', 'w']]]]) [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 296) parseConfig: config is ['vm', ['name', 'netbsd31'], ['memory', 512], ['vcpus', 1], ['image', ['linux', ['kernel', '/data/xenimages/ netbsd/netbsd-INSTALL_XEN3_DOMU'], ['ip', '10.10.80.60:1.2.3.4:10.10.80.1:255.255.255.0::eth0:off'], ['root', '/ dev/hda1'], ['vncunused', 1], ['xauthority', '/root/.Xauthority']]], ['device', ['vbd', ['uname', 'phy:/dev/vg/lvnetbsd31'], ['dev', '0x3'], ['mode', 'w']]]] [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 395) parseConfig: result is {'shadow_memory': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'localtime': None, 'image': ['linux', ['kernel', '/data/xenimages/netbsd/netbsd- INSTALL_XEN3_DOMU'], ['ip', '10.10.80.60:1.2.3.4:10.10.80.1:255.255.255.0::eth0:off'], ['root', '/ dev/hda1'], ['vncunused', 1], ['xauthority', '/root/.Xauthority']], 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 'netbsd31', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 512, 'device': [('vbd', ['vbd', ['uname', 'phy:/dev/vg/lvnetbsd31'], ['dev', '0x3'], ['mode', 'w']])], 'bootloader': None, 'cpu': None, 'maxmem': None} [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 1253) XendDomainInfo.construct: None [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 1285) XendDomainInfo.initDomain: 21 1.0 [2007-01-09 11:45:05 xend 2291] INFO (image:214) configuring linux guest [2007-01-09 11:45:06 xend 2291] DEBUG (balloon:127) Balloon: 525000 KiB free; need 524288; done. [2007-01-09 11:45:06 xend 2291] INFO (image:138) buildDomain os=linux dom=21 vcpus=1 [2007-01-09 11:45:06 xend 2291] DEBUG (image:193) dom = 21 [2007-01-09 11:45:06 xend 2291] DEBUG (image:194) image = / data/xenimages/netbsd/netbsd-INSTALL_XEN3_DOMU [2007-01-09 11:45:06 xend 2291] DEBUG (image:195) store_evtchn = 1 [2007-01-09 11:45:06 xend 2291] DEBUG (image:196) console_evtchn = 2 [2007-01-09 11:45:06 xend 2291] DEBUG (image:197) cmdline = ip=10.10.80.60:1.2.3.4:10.10.80.1:255.255.255.0::eth0:off root=/dev/hda1 [2007-01-09 11:45:06 xend 2291] DEBUG (image:198) ramdisk = [2007-01-09 11:45:06 xend 2291] DEBUG (image:199) vcpus = 1 [2007-01-09 11:45:06 xend 2291] DEBUG (image:200) features = [2007-01-09 11:45:06 xend.XendDomainInfo 2291] ERROR (XendDomainInfo: 202) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/ XendDomainInfo.py", line 195, in create vm.initDomain() File "/usr/lib64/python2.4/site-packages/xen/xend/ XendDomainInfo.py", line 1363, in initDomain raise VmError(str(exn)) VmError: (22, 'Invalid argument') ### xend-debug.log output ## ERROR: Kernel not a Xen-compatible Elf image. ERROR: Error constructing guest OS ERROR: Kernel not a Xen-compatible Elf image. ERROR: Error constructing guest OS ERROR: Kernel not a Xen-compatible Elf image. ERROR: Error constructing guest OS -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Tue Jan 9 22:30:03 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 9 Jan 2007 22:30:03 +0000 Subject: [Fedora-xen] NetBSD 3.1 on fc6 xen 3.0.3 In-Reply-To: <3D053E53-A5D8-47A0-A28D-E3450209742F@ncircle.com> References: <3D053E53-A5D8-47A0-A28D-E3450209742F@ncircle.com> Message-ID: <20070109223003.GA14242@redhat.com> On Tue, Jan 09, 2007 at 04:24:03PM -0600, Timothy D. Keanini Sr. wrote: > > Hello, > I've been trying to setup a instance of NetBSD-3.1 on a fc6xen Dom-0 > Linux testlab 2.6.18-1.2849.fc6xen #1 SMP Fri Nov 10 12:57:36 EST > 2006 x86_64 x86_64 x86_64 GNU/Linux > > # main configuration > name = "netbsd31" > kernel = "/data/xenimages/netbsd/netbsd-INSTALL_XEN3_DOMU" > root="/dev/hda1" > memory = 512 > disk = [ 'phy:/dev/vg/lvnetbsd31,0x3,w' ] > > #network information > ip = "10.10.80.60" > netmask = "255.255.255.0" > gateway = "10.10.80.1" > > ##### > > [root at testlab netbsd]# cp netbsd.cfg /etc/xen/netbsd.cfg > > [root at testlab netbsd]# xm create -c /etc/xen/netbsd.cfg > Using config file "/etc/xen/netbsd.cfg". > Error: (22, 'Invalid argument') This basically says your kernel image is invalid > ### xend-debug.log output > ## > ERROR: Kernel not a Xen-compatible Elf image. > ERROR: Error constructing guest OS > ERROR: Kernel not a Xen-compatible Elf image. > ERROR: Error constructing guest OS > ERROR: Kernel not a Xen-compatible Elf image. > ERROR: Error constructing guest OS This confirms that the kernel image you're trying to boot is incompatible with your host OS. Are you sure that /data/xenimages/netbsd/netbsd-INSTALL_XEN3_DOMU Is a kernel image, and not a virtual disk image ? If it really is a krenel image, make sure it is the same architecture as your dom0 - ie x86_64. 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 clalance at redhat.com Tue Jan 9 22:32:11 2007 From: clalance at redhat.com (Chris Lalancette) Date: Tue, 09 Jan 2007 17:32:11 -0500 Subject: [Fedora-xen] NetBSD 3.1 on fc6 xen 3.0.3 In-Reply-To: <3D053E53-A5D8-47A0-A28D-E3450209742F@ncircle.com> References: <3D053E53-A5D8-47A0-A28D-E3450209742F@ncircle.com> Message-ID: <45A417EB.6090004@redhat.com> Timothy D. Keanini Sr. wrote: > > > [root at testlab netbsd]# cp netbsd.cfg /etc/xen/netbsd.cfg > > [root at testlab netbsd]# xm create -c /etc/xen/netbsd.cfg > Using config file "/etc/xen/netbsd.cfg". > Error: (22, 'Invalid argument') > > > ### xend-debug.log output > ## > ERROR: Kernel not a Xen-compatible Elf image. > ERROR: Error constructing guest OS > ERROR: Kernel not a Xen-compatible Elf image. > ERROR: Error constructing guest OS > ERROR: Kernel not a Xen-compatible Elf image. > ERROR: Error constructing guest OS > Yes, I have run into the same thing. The problem is that NetBSD doesn't have a PAE enabled kernel available, and FC6 is compiled to use PAE. Unfortunately, you are probably out of luck unless: 1) You recompile the FC6 kernel and HV to be non-PAE. It's fairly straightforward, but the problem then is that your other FC6 guests won't work (because then you will have non-PAE dom0, but PAE guests). 2) Find someone willing to make NetBSD use PAE. There are also some bimodal (meaning that both PAE and non-PAE guests would work on a PAE dom0) patches going into upstream Xen, but I'm not sure if we would put those into FC6 (or they would wait for FC7 or later). Chris Lalancette From m3freak at rogers.com Wed Jan 10 21:44:07 2007 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Wed, 10 Jan 2007 16:44:07 -0500 Subject: [Fedora-xen] Internal and external domains on one host Message-ID: <1168465447.20064.12.camel@krs> Hi Everyone, Would I be crazy to use one physical box to run a few internal Xen domU (stuff for the LAN), and use the same host to run a few domU in a DMZ (website, mail, etc.)? Besides the fact that a DoS attack on the DMZ domU could slow the domU on the LAN side down to a crawl, is there anything else that I should be concerned about? I have a small home office, and want to consolidate my three servers to two. Besides saving some electricity, the box in the DMZ is old and slow - the one I want to consolidate to is _much_ better. The better server is already running Xen and a few domU, actually. Has anyone done this? A little part of me says it would be fool hardy, but I can be convinced otherwise! Thanks in advance, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.18-1.2869.fc6 i686 GNU/Linux 16:37:22 up 4 days, 5:24, 2 users, load average: 0.84, 0.71, 0.59 From ktanzer at desc.org Thu Jan 11 19:58:54 2007 From: ktanzer at desc.org (Ken Tanzer) Date: Thu, 11 Jan 2007 11:58:54 -0800 Subject: [Fedora-xen] Re: many many error messages in kernel log : 4gb seg fixup, process acroread In-Reply-To: <45A4F1A0.5090809@iinet.net.au> References: <45A44F1D.4000606@desc.org> <45A4F1A0.5090809@iinet.net.au> Message-ID: <45A696FE.2030600@desc.org> Thanks for the suggestions. I ended up rebooting into the non-xen kernel (2.6.18-1.2869), and these messages disappeared. Ken David Timms wrote: > Ken Tanzer wrote: >> John Q. reported this problem on 12/31, with no reply. We are seeing >> the same problem in our logs. Does anyone have an idea how to solve >> it, or even some suggestions for troubleshooting or investigating? >> Thanks in advance. >> >> Ken >> >>> Hello fedora-list, >>> >>> I have fedora FC6 on i386 machine with latest acroread. (7.0.8). >>> When starting acroerad and all the time it is opened I see many >>> many error messages in the kernel log: >>> >>> ... >>> Dec 31 12:27:47 rr kernel: printk: 7133 messages suppressed. >>> Dec 31 12:27:47 rr kernel: 4gb seg fixup, process acroread (pid >>> 14328), cs:ip 73:00d719f7 >>> Dec 31 12:27:52 rr kernel: printk: 2743 messages suppressed. >>> Dec 31 12:27:52 rr kernel: 4gb seg fixup, process acroread (pid >>> 14328), cs:ip 73:00d719f7 >>> >>> .... >>> This messages appear each second , which means thousands messages in a >>> second. >>> >>> At the second I close the app, these messages stop. >>> Any idea why ? > Maybe ps aux|grep acro and post that. > Are you displaying pdf file at the time you are seeing the message ? > This could be just with the firefox plugin as well ? > If you tail -f /var/log/messages and start/stop acrobat, do the > messages start / stop ? > > If you use the fc6 Evince 0.6.0 to view a pdf does the message continue ? > It seems to be a bug in the upstream acroread itself, and if so it > might be worth searching adobe's web site for faq/forums/bugzilla's, > and posting your experiences there. > > DaveT. > -------------- next part -------------- A non-text attachment was scrubbed... Name: ktanzer.vcf Type: text/x-vcard Size: 342 bytes Desc: not available URL: From Travis.Formoso at blueslate.net Thu Jan 11 21:00:16 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Thu, 11 Jan 2007 16:00:16 -0500 Subject: [Fedora-xen] Installing Xen in a low memory environment Message-ID: Hi guys, I am trying to set up Xen with a machine that has only 256 MB. I set up a NFS share and it does go to the install part, however it stops usually between 10-20% of the install. I was wondering if I could do anything to set this up with such low memory. Thanks This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. -------------- next part -------------- An HTML attachment was scrubbed... URL: From antonio.cecere.ext at siemens.com Fri Jan 12 08:30:12 2007 From: antonio.cecere.ext at siemens.com (Cecere, Antonio (EXT)) Date: Fri, 12 Jan 2007 09:30:12 +0100 Subject: [Fedora-Xen] Save&Restore VMs Message-ID: <1C798AB57865E043A82487E9DA4B47B7018196@MILVB534A.it001.siemens.net> Hi fedora-list, >From the terminal I have created a VM, four VM on FC6Xen, because the virt-manager [0.2.6] has a nice graphic, but the programme it's not complete. [root at localhost ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 418 4 r----- 10529.6 test01 13 256 1 -b---- 365.2 test02 3 256 1 -b---- 423.6 test03 11 512 2 ------ 379.8 test04 15 256 1 -b---- 348.3 The VMs run perfectly but when I try to save them whith # xm save Dom1 Dom1.chk an error is given on the /usr/lib/xen/bin/xc_save. Restoring the VMs is impossible. [root at localhost ~]# xm save test03 test03.chk Error: /usr/lib/xen/bin/xc_save 21 11 0 0 0 failed Usage: xm save Save a domain state to restore later. Do you have any idea??? Thi is my conf on a Intel i686: [root at localhost ~]# xm info host : localhost.localdomain release : 2.6.18-1.2798.fc6xen version : #1 SMP Mon Oct 16 15:11:19 EDT 2006 machine : i686 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1666 hw_caps : bfebfbff:00100000:00000000:00000140:0000c1a9 total_memory : 2047 free_memory : 258 xen_major : 3 xen_minor : 0 xen_extra : .3-rc3-1.2798.f xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30) cc_compile_by : brewbuilder cc_compile_domain : build.redhat.com cc_compile_date : Mon Oct 16 14:34:31 EDT 2006 xend_config_format : 2 Regards, Antonio Cecere -------------- next part -------------- An HTML attachment was scrubbed... URL: From oehmes at de.ibm.com Fri Jan 12 13:10:34 2007 From: oehmes at de.ibm.com (Sven Oehme) Date: Fri, 12 Jan 2007 14:10:34 +0100 Subject: [Fedora-xen] Network Problem after todays update In-Reply-To: <1138377808.6643.10.camel@bree.local.net> Message-ID: Hi , i did an update today from kernel-xen-2.6.18-1.2869.fc6 to kernel-xen-2.6.19-1.2895.fc6 and from xen-3.0.3-1.fc6 to xen-3.0.3-3.fc6 . the upgrade itself went fine, and all on dom_0 works as expected. But i have now trouble with my guetsts Network. All guests are connecting to the outside world over NAT. i can ssh between all guests as well as between dom_0 and all guests. i can ping each box outside the dom_0 (my dns server for insteance) but i can't ssh or ftp to any box outside my internal dom_0 network, it always timed out. looking at a tcp dump it marks the frames i send from the guests as Checksum Errors. any ideas ? should i open a bugzilla entry for this ? Sven -------------- next part -------------- An HTML attachment was scrubbed... URL: From oehmes at de.ibm.com Fri Jan 12 13:19:38 2007 From: oehmes at de.ibm.com (Sven Oehme) Date: Fri, 12 Jan 2007 14:19:38 +0100 Subject: [Fedora-xen] Network Problem after todays update In-Reply-To: Message-ID: sorry, there was a small typo in my mail, i upgraded from kernel-xen-2.6.18-1.2868.fc6 to kernel-xen-2.6.19-1.2895.fc6 not from -1.2869 .. btw. going back to kernel .2868 fixes it, so there must be a bug added between .2868 and .2895 i will test with .2869 later today .. Sven Sven Oehme/Germany/IBM at IBMDE Sent by: fedora-xen-bounces at redhat.com 01/12/07 02:10 PM To fedora-xen at redhat.com cc Subject [Fedora-xen] Network Problem after todays update Hi , i did an update today from kernel-xen-2.6.18-1.2869.fc6 to kernel-xen-2.6.19-1.2895.fc6 and from xen-3.0.3-1.fc6 to xen-3.0.3-3.fc6 . the upgrade itself went fine, and all on dom_0 works as expected. But i have now trouble with my guetsts Network. All guests are connecting to the outside world over NAT. i can ssh between all guests as well as between dom_0 and all guests. i can ping each box outside the dom_0 (my dns server for insteance) but i can't ssh or ftp to any box outside my internal dom_0 network, it always timed out. looking at a tcp dump it marks the frames i send from the guests as Checksum Errors. any ideas ? should i open a bugzilla entry for this ? Sven-- 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 antonio.cecere.ext at siemens.com Fri Jan 12 14:19:11 2007 From: antonio.cecere.ext at siemens.com (Cecere, Antonio (EXT)) Date: Fri, 12 Jan 2007 15:19:11 +0100 Subject: R: [Fedora-xen] Network Problem after todays update In-Reply-To: Message-ID: <1C798AB57865E043A82487E9DA4B47B701819D@MILVB534A.it001.siemens.net> Hi Sven, I should also update the kernel, but I'm waiting for the 2.6.20 that should be released in no time. I have 4 domains in 2.6.18-1.2798.fc6xen and xen-3.0.3, and they ping between them but I can't open an ftp transfer, though I can ping to the outside. Try to make a traceroute and see what ride they make. Let me know... Antonio antonio.cecere.ext at siemens.com ____________________________________________________________ -----Messaggio originale----- Da: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Per conto di Sven Oehme Inviato: venerd? 12 gennaio 2007 14.20 A: fedora-xen at redhat.com Oggetto: Re: [Fedora-xen] Network Problem after todays update sorry, there was a small typo in my mail, i upgraded from kernel-xen-2.6.18-1.2868.fc6 to kernel-xen-2.6.19-1.2895.fc6 not from -1.2869 .. btw. going back to kernel .2868 fixes it, so there must be a bug added between .2868 and .2895 i will test with .2869 later today .. Sven ______________________________________________________ Hi , i did an update today from kernel-xen-2.6.18-1.2869.fc6 to kernel-xen-2.6.19-1.2895.fc6 and from xen-3.0.3-1.fc6 to xen-3.0.3-3.fc6 . the upgrade itself went fine, and all on dom_0 works as expected. But i have now trouble with my guetsts Network. All guests are connecting to the outside world over NAT. i can ssh between all guests as well as between dom_0 and all guests. i can ping each box outside the dom_0 (my dns server for insteance) but i can't ssh or ftp to any box outside my internal dom_0 network, it always timed out. looking at a tcp dump it marks the frames i send from the guests as Checksum Errors. any ideas ? should i open a bugzilla entry for this ? Sven-- 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 daniel at velotype.nl Sat Jan 13 03:26:32 2007 From: daniel at velotype.nl (Daniel Tuijnman) Date: Sat, 13 Jan 2007 04:26:32 +0100 Subject: [Fedora-xen] No success installing Windows XP in fully-virtualized domain Message-ID: <20070113032632.GB15254@velotype.nl> Hi, I tried installing Windows XP in a fully-virtualized guest domain, using Fedora Core 6, but had no success. The installation would never proceed beyond the reboot halfway in the install process; sometimes even abort earlier. I tried this both with virt-manager, and with hand-crafted config files, fiddling with all possible variations of acpi and apic settings. Using a successfully installed Windows domain appears to be no problem, though - even with both acpi and apic turned on. I managed to create a Windows XP domain with the free version of XenEnterprise without any problems. Is there anything special about the Xen implementation in this product? I ask, because it struck me when I tried to install Windows 2000 - which they say they don't support - all went fine, except that all dialog texts in the installation process were blacked out.. Using it is no option for me, because I want to use the machine both for various servers and as my desktop machine. (I also tried Debian Etch, but wasn't successful either...) Does anyone have suggestions what I could do: - to be able to give a more meaningful report what goes wrong? - to create other Windows domains in the future? The hardware I'm using: - AMD 64X2 5000+ - Asus M2N-SLI deluxe motherboard (nVidia nForce 5 chipset) I also upgraded the BIOS to the latest version, just to be sure. - 2 Gb RAM Greetings, Daniel -- Dani?l Tuijnman phone: +31-24-377.7329 De Voorstenkamp 19-59 mobile: +31-6-4611.4589 NL-6545 GR Nijmegen fax: +31-24-373.3632 ======================================================================== There's an old story about the person who wished his computer were as easy to use as his telephone. That wish has come true, since I no longer know how to use my telephone. Bjarne Stroustrup ======================================================================== From macr111080 at yahoo.com.mx Sat Jan 13 14:40:14 2007 From: macr111080 at yahoo.com.mx (Rodolfo Martinez) Date: Sat, 13 Jan 2007 06:40:14 -0800 (PST) Subject: [Fedora-xen] No success installing Windows XP in fully-virtualized domain Message-ID: <20070113144015.5797.qmail@web51708.mail.yahoo.com> Hi Daniel, I found this workaround in the list archives... It worked for me. "I had this problem, too - the solution was re-installing WinXP, and, when the installer asks you to press 'F6' for addtional drivers, press 'F5' instead. Then select 'Standard PC ...'" https://www.redhat.com/archives/fedora-xen/2006-November/msg00158.html Regards, Rodolfo Marti?nez ----- Original Message ---- From: Daniel Tuijnman To: fedora-xen at redhat.com Sent: Friday, January 12, 2007 9:26:32 PM Subject: [Fedora-xen] No success installing Windows XP in fully-virtualized domain Hi, I tried installing Windows XP in a fully-virtualized guest domain, using Fedora Core 6, but had no success. The installation would never proceed beyond the reboot halfway in the install process; sometimes even abort earlier. I tried this both with virt-manager, and with hand-crafted config files, fiddling with all possible variations of acpi and apic settings. Using a successfully installed Windows domain appears to be no problem, though - even with both acpi and apic turned on. I managed to create a Windows XP domain with the free version of XenEnterprise without any problems. Is there anything special about the Xen implementation in this product? I ask, because it struck me when I tried to install Windows 2000 - which they say they don't support - all went fine, except that all dialog texts in the installation process were blacked out.. Using it is no option for me, because I want to use the machine both for various servers and as my desktop machine. (I also tried Debian Etch, but wasn't successful either...) Does anyone have suggestions what I could do: - to be able to give a more meaningful report what goes wrong? - to create other Windows domains in the future? The hardware I'm using: - AMD 64X2 5000+ - Asus M2N-SLI deluxe motherboard (nVidia nForce 5 chipset) I also upgraded the BIOS to the latest version, just to be sure. - 2 Gb RAM Greetings, Daniel -- Dani?l Tuijnman phone: +31-24-377.7329 De Voorstenkamp 19-59 mobile: +31-6-4611.4589 NL-6545 GR Nijmegen fax: +31-24-373.3632 ======================================================================== There's an old story about the person who wished his computer were as easy to use as his telephone. That wish has come true, since I no longer know how to use my telephone. Bjarne Stroustrup ======================================================================== -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen ____________________________________________________________________________________ Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 From sjafri at purdue.edu Sat Jan 13 23:29:57 2007 From: sjafri at purdue.edu (sjafri at purdue.edu) Date: Sat, 13 Jan 2007 18:29:57 -0500 Subject: [Fedora-xen] Vanishing Harddisk Message-ID: <1168730997.45a96b75b68c9@webmail.purdue.edu> Hello All, I hope some one can help me. I have xen running on Fedora Core 6, now when I try to add a guest os using virt-manager there are no hard disks detected. the whole process goes fine until I have to pick a partition for installation. I tried using both a file as avirtual disk and also a partition, in both cases I come to stop because no hard disks or partitions are selected. Ali From berrange at redhat.com Sun Jan 14 16:22:14 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 14 Jan 2007 16:22:14 +0000 Subject: [Fedora-xen] Vanishing Harddisk In-Reply-To: <1168730997.45a96b75b68c9@webmail.purdue.edu> References: <1168730997.45a96b75b68c9@webmail.purdue.edu> Message-ID: <20070114162214.GC973@redhat.com> On Sat, Jan 13, 2007 at 06:29:57PM -0500, sjafri at purdue.edu wrote: > > > Hello All, I hope some one can help me. I have xen running on Fedora Core 6, now > when I try to add a guest os using virt-manager there are no hard disks > detected. the whole process goes fine until I have to pick a partition for > installation. I tried using both a file as avirtual disk and also a partition, > in both cases I come to stop because no hard disks or partitions are selected. Run through the install again, and when you get to the partition stage of the install, take a copy of /root/.virt-manager/virt-manager.log and also the /etc/xen/ config file & post it to the list. Alternatively create a BZ report for the issue attaching those two files and the logs from /var/log/xen 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 phil at pricom.com.au Mon Jan 15 14:23:17 2007 From: phil at pricom.com.au (Phil Rhoades) Date: Tue, 16 Jan 2007 01:23:17 +1100 Subject: [Fedora-xen] Using a FC6 Guest as Internet gateway, proxy etc Message-ID: <1168870997.10412.10.camel@prix.pricom.com.au> People, Now that I can create FC6 Guests running on FC6 quite happily I am thinking of using a very stripped down, minimal Guest as the Internet gateway, proxy etc for the host machine such that the Guest has the real IP address and the host machine is using a typical private IP address eg 192.168.0.10 - is anyone else doing this successfully? Thanks, Phil. -- Philip Rhoades Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Fax: +61:(0)2-8221-9599 E-mail: phil at pricom.com.au From john.mizell at tch.com Mon Jan 15 12:58:49 2007 From: john.mizell at tch.com (John Mizell) Date: Mon, 15 Jan 2007 07:58:49 -0500 Subject: [Fedora-xen] Xen vm install Message-ID: <1168865929.23614.3.camel@lucky7> I am trying to install fedora 6 64 guest on top of a fedora 6 64 host with xen. I have tried using nfs and ftp. Both methods stall during the package install and never complete. Is there a work around for this or a fix on the way? John Mizell From master at bradleyland.com Mon Jan 15 17:14:17 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Mon, 15 Jan 2007 09:14:17 -0800 (PST) Subject: [Fedora-xen] Using a FC6 Guest as Internet gateway, proxy etc In-Reply-To: <1168870997.10412.10.camel@prix.pricom.com.au> References: <1168870997.10412.10.camel@prix.pricom.com.au> Message-ID: <45499.192.168.3.1.1168881257.squirrel@www.bradleyland.com> > People, > > Now that I can create FC6 Guests running on FC6 quite happily I am > thinking of using a very stripped down, minimal Guest as the Internet > gateway, proxy etc for the host machine such that the Guest has the real > IP address and the host machine is using a typical private IP address eg > 192.168.0.10 - is anyone else doing this successfully? > > Thanks, > > Phil. > -- > Philip Rhoades > > Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) > GPO Box 3411 > Sydney NSW 2001 > Australia > Fax: +61:(0)2-8221-9599 > E-mail: phil at pricom.com.au > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > I'm running a domU firewall as described in: http://www.shorewall.net/XenMyWay.html works just like any other machine. Also for running the firewall in dom0, http://www.shorewall.net/Xen.html From karl at guentherk.net Mon Jan 15 20:12:40 2007 From: karl at guentherk.net (Karl Guenther) Date: Mon, 15 Jan 2007 14:12:40 -0600 Subject: [Fedora-xen] 4gb seg fixup, process on FC6 domU Message-ID: <45ABE038.8000802@guentherk.net> Hi, I have read through the threads on the 4gb seg fixup. Both Xen and beagle are important to me for day to day use. I boot into FC6 Xen and beagle seems to work but I am not sure what the 4gb seg fixup messages are all about. Are they just warning messages? Is anything failing that I should know about as a user of both Xen and beagle? Thank You Karl Guenther From jklein at saugus.k12.ca.us Mon Jan 15 20:14:11 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Mon, 15 Jan 2007 12:14:11 -0800 (PST) Subject: [Fedora-xen] Re: Using a FC6 Guest as Internet gateway, proxy etc Message-ID: <15655978.846001168892051056.JavaMail.root@do8> We are doing this now and have been very happy with it. In fact, we have a VM that is NAT routing from a private to a public subnet, which is forwarding to another VM that is routing/transparent proxy to the internet, all through bridged interfaces. All of our host systems are blades on the private subnet. -- Jim Klein Director Information Services & Technology LPIC1, CNA/CNE 4-6, RHCT/RHCE Saugus Union School District http://www.saugus.k12.ca.us "Finis Origine Pendet" Date: Tue, 16 Jan 2007 01:23:17 +1100 From: Phil Rhoades < phil at pricom.com.au > Subject: [Fedora-xen] Using a FC6 Guest as Internet gateway, proxy etc To: fedora-xen at redhat.com Message-ID: < 1168870997.10412.10.camel at prix.pricom.com.au > Content-Type: text/plain People, Now that I can create FC6 Guests running on FC6 quite happily I am thinking of using a very stripped down, minimal Guest as the Internet gateway, proxy etc for the host machine such that the Guest has the real IP address and the host machine is using a typical private IP address eg 192.168.0.10 - is anyone else doing this successfully? Thanks, Phil. -- Philip Rhoades Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Fax: +61:(0)2-8221-9599 E-mail: phil at pricom.com.au -------------- next part -------------- An HTML attachment was scrubbed... URL: From master at bradleyland.com Mon Jan 15 20:24:24 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Mon, 15 Jan 2007 12:24:24 -0800 (PST) Subject: [Fedora-xen] More Xen/FC6 crashing Message-ID: <46959.192.168.3.1.1168892664.squirrel@www.bradleyland.com> Anyone have any ideas on this one? I can't keep my main dom0 machine running for more than 5-8 days before I get a crash. I turned ACPI on and it seemed to get the machine to run longer, but who knows? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (32 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (33 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (32 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (45 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (59 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (47 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (52 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (26 of 40) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (60 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (44 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (54 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (43 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (40 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (38 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (56 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (56 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (62 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (63 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (61 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (50 of 64) (XEN) (file=memory.c, line=66) Could not allocate order=0 extent: id=0 memflags=0 (60 of 64) list_del corruption. prev->next should be d08d9280, but was d08d0080 ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:65! invalid opcode: 0000 [#1] SMP last sysfs file: /devices/platform/i2c-9191/9191-0290/temp3_max Modules linked in: nls_utf8 cifs netloop netbk blktap blkbk ipv6 autofs4 it87 hwmon_vid hwmon i2c_isa hidp l2cap bluetooth iptable_raw xt_policy xt_multiport ipt_ULOG ipt_TTL ipt_ttl ipt_TOS ipt_tos ipt_TCPMSS ipt_SAME ipt_REJECT ipt_REDIRECT ipt_recent ipt_owner ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_iprange ipt_hashlimit ipt_ECN ipt_ecn ipt_DSCP ipt_dscp ipt_CLUSTERIP ipt_ah ipt_addrtype ip_nat_tftp ip_nat_snmp_basic ip_nat_pptp ip_nat_irc ip_nat_ftp ip_nat_amanda ip_conntrack_tftp ip_conntrack_pptp ip_conntrack_netbios_ns ip_conntrack_irc ip_conntrack_ftp ts_kmp ip_conntrack_amanda xt_tcpmss xt_pkttype xt_physdev bridge xt_NFQUEUE xt_MARK xt_mark xt_mac xt_limit xt_length xt_helper xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat ip_nat ip_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables sunrpc video sbs i2c_ec button battery asus_acpi ac parport_pc lp parport floppy ide_cd serio_raw cdrom pcspkr r8169 sis900 mii i2c_sis630 i2c_core dm_snapshot dm_zero dm_mirror dm_mod raid456 xor ext3 jbd ehci_hcd CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010086 (2.6.18-1.2869.fc6xen #1) EIP is at list_del+0x23/0x6c eax: 00000048 ebx: d08d9280 ecx: c066d030 edx: f5416000 esi: c0ca3e20 edi: e7a9b000 ebp: c185c520 esp: c0cd5efc ds: 007b es: 007b ss: 0069 Process events/0 (pid: 5, ti=c0cd5000 task=ed7c0030 task.ti=c0cd5000) Stack: c0631e24 d08d9280 d08d0080 d08d9280 c046223d c0416178 00000006 00000004 c0739030 c0739020 00000006 c0739000 00000000 c0462340 00000000 00000000 c185c520 c0ca3e44 c0ca3e20 c185c520 c0fdd2a0 00000000 c04637e0 00000000 Call Trace: [] free_block+0x63/0xdc [] drain_array+0x8a/0xb5 [] cache_reap+0x85/0x117 [] run_workqueue+0x83/0xc5 [] worker_thread+0xd9/0x10d [] kthread+0xc0/0xed [] kernel_thread_helper+0x5/0xb DWARF2 unwinder stuck at kernel_thread_helper+0x5/0xb Leftover inexact backtrace: ======================= Code: 00 00 89 c3 eb e8 90 90 53 89 c3 83 ec 0c 8b 40 04 8b 00 39 d8 74 1c 89 5c 24 04 89 44 24 08 c7 04 24 24 1e 63 c0 e8 28 c3 f3 ff <0f> 0b 41 00 61 1e 63 c0 8b 03 8b 40 04 39 d8 74 1c 89 5c 24 04 EIP: [] list_del+0x23/0x6c SS:ESP 0069:c0cd5efc <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20 in_atomic():0, irqs_disabled():1 [] dump_trace+0x69/0x1af [] show_trace_log_lvl+0x18/0x2c [] show_trace+0xf/0x11 [] dump_stack+0x15/0x17 [] down_read+0x12/0x20 [] blocking_notifier_call_chain+0xe/0x29 [] do_exit+0x1b/0x776 [] die+0x289/0x2ae [] do_invalid_op+0xa2/0xab [] error_code+0x2b/0x30 DWARF2 unwinder stuck at error_code+0x2b/0x30 Leftover inexact backtrace: [] list_del+0x23/0x6c [] free_block+0x63/0xdc [] dequeue_task+0x13/0x26 [] drain_array+0x8a/0xb5 [] cache_reap+0x85/0x117 [] run_workqueue+0x83/0xc5 [] _spin_lock_irqsave+0x12/0x17 [] cache_reap+0x0/0x117 [] worker_thread+0xd9/0x10d [] default_wake_function+0x0/0xc [] worker_thread+0x0/0x10d [] kthread+0xc0/0xed [] kthread+0x0/0xed [] kernel_thread_helper+0x5/0xb ======================= BUG: spinlock lockup on CPU#0, events/0/5, c0ca3e44 (Not tainted) [] dump_trace+0x69/0x1af [] show_trace_log_lvl+0x18/0x2c [] show_trace+0xf/0x11 [] dump_stack+0x15/0x17 [] _raw_spin_lock+0xbf/0xdc [] cache_alloc_refill+0x60/0x478 [] kmem_cache_alloc+0x54/0x6d [] alloc_skb_from_cache+0x48/0x112 [] __dev_alloc_skb+0x4e/0x64 [] sis900_interrupt+0x278/0x6ab [sis900] [] handle_IRQ_event+0x27/0x51 [] __do_IRQ+0x96/0xf2 [] do_IRQ+0x9e/0xbc ======================= From master at bradleyland.com Mon Jan 15 20:29:48 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Mon, 15 Jan 2007 12:29:48 -0800 (PST) Subject: [Fedora-xen] More Xen/FC6 crashing In-Reply-To: <46959.192.168.3.1.1168892664.squirrel@www.bradleyland.com> References: <46959.192.168.3.1.1168892664.squirrel@www.bradleyland.com> Message-ID: <50456.192.168.3.1.1168892988.squirrel@www.bradleyland.com> Version info... [root at zeus ~]# rpm -q xen xen-3.0.3-1.fc6 [root at zeus ~]# uname -a Linux zeus.bradleyland.com 2.6.18-1.2869.fc6xen #1 SMP Wed Dec 20 15:28:06 EST 2006 i686 athlon i386 GNU/Linux [root at zeus ~]# From itamar at ispbrasil.com.br Tue Jan 16 04:31:58 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Tue, 16 Jan 2007 02:31:58 -0200 Subject: [Fedora-xen] 4gb seg fixup, process on FC6 domU References: <45ABE038.8000802@guentherk.net> Message-ID: <008301c73927$44fdcce0$0a00000a@ispbrasil> install kernel-xen on domU using a RPMS, will fix your problem. -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 ----- Original Message ----- From: "Karl Guenther" To: "Fedora-xen" Sent: Monday, January 15, 2007 6:12 PM Subject: [Fedora-xen] 4gb seg fixup, process on FC6 domU > Hi, > > I have read through the threads on the 4gb seg fixup. Both Xen and > beagle are important to me for day to day use. > > I boot into FC6 Xen and beagle seems to work but I am not sure what the > 4gb seg fixup messages are all about. Are they just warning messages? > > Is anything failing that I should know about as a user of both Xen and > beagle? > > Thank You > > Karl Guenther > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From gary at primeexalia.com Tue Jan 16 05:20:54 2007 From: gary at primeexalia.com (Gary W. Smith) Date: Mon, 15 Jan 2007 21:20:54 -0800 Subject: [Fedora-xen] DomU problem with tap:aio and xvdN. Message-ID: <57F9959B46E0FA4D8BA88AEDFBE5829024EFA3@pxtbenexd01.pxt.primeexalia.com> Hello, In a nutshell, I can't get DomU's to work with xvdN and tap:aio under FC6.2869. I have also tried to get them to work with XenSource 3.0.4. I've been asking this in the xen-users group but I haven't had any positive response. I have the following DomU's that I'm testing with: FC4/5/6, CentOS4. In general, they all seem to have the same problems. The problem is that when I reference the FC6 Xen boot kernel in the kernel config line for the DomU it kernel panics. I have copied /lib/modules/* (FC6 and XenSource) to the DomU as well for testing. If I do sdN and file it all works fine, but only for XenSource kernel. At the Dom0 level we are booting to FC.2869 and only referencing the XenSource 3.0.4 images at the DomU config file level. Am I missing something fundamental? I have also ran into this problem with the jailtime.org images as well. FC6 kernel: (kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen') XENBUS: Device with no driver: device/vbd/51713 XENBUS: Device with no driver: device/vbd/51714 XENBUS: Device with no driver: device/vif/0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "xvda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) XenSource 3.0.4 kernel: (kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen') md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. WARNING: g.e. still in use! WARNING: leaking g.e. and page still in use! end_request: I/O error, dev xvda1, sector 2 EXT2-fs: unable to read superblock Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(202,1) Overall config file: name = 'fedora4' memory = '256' disk = [ 'file:/xen-build/fedora4/xen-D0.img,xvda1,w' , 'file:/xen-build/fedora4/xen-swap.img,xvda2,w' ] #disk = [ 'tap:aio:/xen-build/fedora4/xen-D0.img,xvda1,w','tap:aio:/xen-build/fedo ra4/xen-swap.img,xvda2,w' ] root = '/dev/xvda1 ro' vif = [ 'mac=00:16:e6:CD:49:5B' ] kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen' #kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen' on_reboot = 'restart' on_crash = 'restart' extras = 'console=xvc0' From xenguy at gmail.com Tue Jan 16 05:35:29 2007 From: xenguy at gmail.com (Sadique Puthen) Date: Tue, 16 Jan 2007 11:05:29 +0530 Subject: [Fedora-xen] DomU problem with tap:aio and xvdN. In-Reply-To: <57F9959B46E0FA4D8BA88AEDFBE5829024EFA3@pxtbenexd01.pxt.primeexalia.com> References: <57F9959B46E0FA4D8BA88AEDFBE5829024EFA3@pxtbenexd01.pxt.primeexalia.com> Message-ID: <45AC6421.7030803@gmail.com> Gary W. Smith wrote: > Hello, > > In a nutshell, I can't get DomU's to work with xvdN and tap:aio under > FC6.2869. I have also tried to get them to work with XenSource 3.0.4. > > I've been asking this in the xen-users group but I haven't had any > positive response. I have the following DomU's that I'm testing with: > FC4/5/6, CentOS4. In general, they all seem to have the same problems. > > The problem is that when I reference the FC6 Xen boot kernel in the > kernel config line for the DomU it kernel panics. I have copied > /lib/modules/* (FC6 and XenSource) to the DomU as well for testing. If > I do sdN and file it all works fine, but only for XenSource kernel. > > At the Dom0 level we are booting to FC.2869 and only referencing the > XenSource 3.0.4 images at the DomU config file level. > > Am I missing something fundamental? I have also ran into this problem > with the jailtime.org images as well. > > FC6 kernel: > (kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen') > > XENBUS: Device with no driver: device/vbd/51713 > XENBUS: Device with no driver: device/vbd/51714 > XENBUS: Device with no driver: device/vif/0 > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > VFS: Cannot open root device "xvda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > > XenSource 3.0.4 kernel: > (kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen') > > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > WARNING: g.e. still in use! > WARNING: leaking g.e. and page still in use! > end_request: I/O error, dev xvda1, sector 2 > EXT2-fs: unable to read superblock > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(202,1) > > > Overall config file: > > name = 'fedora4' > memory = '256' > disk = [ 'file:/xen-build/fedora4/xen-D0.img,xvda1,w' , > 'file:/xen-build/fedora4/xen-swap.img,xvda2,w' ] > #disk = [ > 'tap:aio:/xen-build/fedora4/xen-D0.img,xvda1,w','tap:aio:/xen-build/fedo > ra4/xen-swap.img,xvda2,w' ] > root = '/dev/xvda1 ro' > vif = [ 'mac=00:16:e6:CD:49:5B' ] > kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen' > Why don't use bootloader = "/usr/bin/pygrub" and load a modified kernel from domU itself? > #kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen' > on_reboot = 'restart' > on_crash = 'restart' > extras = 'console=xvc0' > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > From gary at primeexalia.com Tue Jan 16 06:10:40 2007 From: gary at primeexalia.com (Gary W. Smith) Date: Mon, 15 Jan 2007 22:10:40 -0800 Subject: [Fedora-xen] DomU problem with tap:aio and xvdN. In-Reply-To: <45AC6421.7030803@gmail.com> References: <57F9959B46E0FA4D8BA88AEDFBE5829024EFA3@pxtbenexd01.pxt.primeexalia.com> <45AC6421.7030803@gmail.com> Message-ID: <57F9959B46E0FA4D8BA88AEDFBE5829024EFA6@pxtbenexd01.pxt.primeexalia.com> Sadique, Can you explain how to do this in each environment? I've been down that road with limited success as grub worked different in each environment. Installing grub usually requires me to hack quick a bit of stuff. OTOH the people on the xen-users at lists.xensource.com said just the opposite when I was looking for help getting the kernel to boot using grub (/usr/bin/pygrub). As for the modified kernels per OS I've been having bad luck with getting things like FC4 working under 3.0.4. > -----Original Message----- > From: Sadique Puthen [mailto:xenguy at gmail.com] > Sent: Monday, January 15, 2007 9:35 PM > To: Gary W. Smith > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] DomU problem with tap:aio and xvdN. > > Gary W. Smith wrote: > > Hello, > > > > In a nutshell, I can't get DomU's to work with xvdN and tap:aio under > > FC6.2869. I have also tried to get them to work with XenSource 3.0.4. > > > > I've been asking this in the xen-users group but I haven't had any > > positive response. I have the following DomU's that I'm testing with: > > FC4/5/6, CentOS4. In general, they all seem to have the same problems. > > > > The problem is that when I reference the FC6 Xen boot kernel in the > > kernel config line for the DomU it kernel panics. I have copied > > /lib/modules/* (FC6 and XenSource) to the DomU as well for testing. If > > I do sdN and file it all works fine, but only for XenSource kernel. > > > > At the Dom0 level we are booting to FC.2869 and only referencing the > > XenSource 3.0.4 images at the DomU config file level. > > > > Am I missing something fundamental? I have also ran into this problem > > with the jailtime.org images as well. > > > > FC6 kernel: > > (kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen') > > > > XENBUS: Device with no driver: device/vbd/51713 > > XENBUS: Device with no driver: device/vbd/51714 > > XENBUS: Device with no driver: device/vif/0 > > md: Autodetecting RAID arrays. > > md: autorun ... > > md: ... autorun DONE. > > VFS: Cannot open root device "xvda1" or unknown-block(0,0) > > Please append a correct "root=" boot option > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(0,0) > > > > XenSource 3.0.4 kernel: > > (kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen') > > > > md: Autodetecting RAID arrays. > > md: autorun ... > > md: ... autorun DONE. > > WARNING: g.e. still in use! > > WARNING: leaking g.e. and page still in use! > > end_request: I/O error, dev xvda1, sector 2 > > EXT2-fs: unable to read superblock > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(202,1) > > > > > > Overall config file: > > > > name = 'fedora4' > > memory = '256' > > disk = [ 'file:/xen-build/fedora4/xen-D0.img,xvda1,w' , > > 'file:/xen-build/fedora4/xen-swap.img,xvda2,w' ] > > #disk = [ > > 'tap:aio:/xen-build/fedora4/xen-D0.img,xvda1,w','tap:aio:/xen-build/fedo > > ra4/xen-swap.img,xvda2,w' ] > > root = '/dev/xvda1 ro' > > vif = [ 'mac=00:16:e6:CD:49:5B' ] > > kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen' > > > Why don't use bootloader = "/usr/bin/pygrub" and load a modified kernel > from domU itself? > > #kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen' > > on_reboot = 'restart' > > on_crash = 'restart' > > extras = 'console=xvc0' > > > > > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > From xenguy at gmail.com Tue Jan 16 11:09:16 2007 From: xenguy at gmail.com (Sadique Puthen) Date: Tue, 16 Jan 2007 16:39:16 +0530 Subject: [Fedora-xen] DomU problem with tap:aio and xvdN. In-Reply-To: <57F9959B46E0FA4D8BA88AEDFBE5829024EFA6@pxtbenexd01.pxt.primeexalia.com> References: <57F9959B46E0FA4D8BA88AEDFBE5829024EFA3@pxtbenexd01.pxt.primeexalia.com> <45AC6421.7030803@gmail.com> <57F9959B46E0FA4D8BA88AEDFBE5829024EFA6@pxtbenexd01.pxt.primeexalia.com> Message-ID: <45ACB25C.70508@gmail.com> Gary W. Smith wrote: > Sadique, > > Can you explain how to do this in each environment? One example: http://people.redhat.com/riel/RHEL4-Xen-HOWTO > I've been down that > road with limited success as grub worked different in each environment. > Installing grub usually requires me to hack quick a bit of stuff. > > OTOH the people on the xen-users at lists.xensource.com said just the > opposite when I was looking for help getting the kernel to boot using > grub (/usr/bin/pygrub). > > As for the modified kernels per OS I've been having bad luck with > getting things like FC4 working under 3.0.4. > > > > >> -----Original Message----- >> From: Sadique Puthen [mailto:xenguy at gmail.com] >> Sent: Monday, January 15, 2007 9:35 PM >> To: Gary W. Smith >> Cc: fedora-xen at redhat.com >> Subject: Re: [Fedora-xen] DomU problem with tap:aio and xvdN. >> >> Gary W. Smith wrote: >> >>> Hello, >>> >>> In a nutshell, I can't get DomU's to work with xvdN and tap:aio >>> > under > >>> FC6.2869. I have also tried to get them to work with XenSource >>> > 3.0.4. > >>> I've been asking this in the xen-users group but I haven't had any >>> positive response. I have the following DomU's that I'm testing >>> > with: > >>> FC4/5/6, CentOS4. In general, they all seem to have the same >>> > problems. > >>> The problem is that when I reference the FC6 Xen boot kernel in the >>> kernel config line for the DomU it kernel panics. I have copied >>> /lib/modules/* (FC6 and XenSource) to the DomU as well for testing. >>> > If > >>> I do sdN and file it all works fine, but only for XenSource kernel. >>> >>> At the Dom0 level we are booting to FC.2869 and only referencing the >>> XenSource 3.0.4 images at the DomU config file level. >>> >>> Am I missing something fundamental? I have also ran into this >>> > problem > >>> with the jailtime.org images as well. >>> >>> FC6 kernel: >>> (kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen') >>> >>> XENBUS: Device with no driver: device/vbd/51713 >>> XENBUS: Device with no driver: device/vbd/51714 >>> XENBUS: Device with no driver: device/vif/0 >>> md: Autodetecting RAID arrays. >>> md: autorun ... >>> md: ... autorun DONE. >>> VFS: Cannot open root device "xvda1" or unknown-block(0,0) >>> Please append a correct "root=" boot option >>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>> unknown-block(0,0) >>> >>> XenSource 3.0.4 kernel: >>> (kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen') >>> >>> md: Autodetecting RAID arrays. >>> md: autorun ... >>> md: ... autorun DONE. >>> WARNING: g.e. still in use! >>> WARNING: leaking g.e. and page still in use! >>> end_request: I/O error, dev xvda1, sector 2 >>> EXT2-fs: unable to read superblock >>> Kernel panic - not syncing: VFS: Unable to mount root fs on >>> unknown-block(202,1) >>> >>> >>> Overall config file: >>> >>> name = 'fedora4' >>> memory = '256' >>> disk = [ 'file:/xen-build/fedora4/xen-D0.img,xvda1,w' , >>> 'file:/xen-build/fedora4/xen-swap.img,xvda2,w' ] >>> #disk = [ >>> >>> > 'tap:aio:/xen-build/fedora4/xen-D0.img,xvda1,w','tap:aio:/xen-build/fedo > >>> ra4/xen-swap.img,xvda2,w' ] >>> root = '/dev/xvda1 ro' >>> vif = [ 'mac=00:16:e6:CD:49:5B' ] >>> kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen' >>> >>> >> Why don't use bootloader = "/usr/bin/pygrub" and load a modified >> > kernel > >> from domU itself? >> >>> #kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen' >>> on_reboot = 'restart' >>> on_crash = 'restart' >>> extras = 'console=xvc0' >>> >>> >>> >>> -- >>> Fedora-xen mailing list >>> Fedora-xen at redhat.com >>> https://www.redhat.com/mailman/listinfo/fedora-xen >>> >>> >>> > > > From ppavliks at gmail.com Tue Jan 16 11:40:38 2007 From: ppavliks at gmail.com (Andrew Avramenko) Date: Tue, 16 Jan 2007 14:40:38 +0300 Subject: [Fedora-xen] Installing RHEL5 as a guest OS Message-ID: <1e0deccb0701160340i7c4220fcra71b8379dc3283e1@mail.gmail.com> Hello! I have RHEL 5 beta 2 installed as OS of domain0. Now I'm trying to install the same OS as guest. In the middle of installing RPMs anaconda crashed with "install exited abnormally". In some cases it crashed with errors in rpm locks. Could you help me? I'm new for Xen, sorry if something wrong :) Here is information about hardware and soft: Memory for guest domain: 192 Mb CPU: 1 VCPU ============================================== [root at localhost ~]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) 4 CPU 3.00GHz stepping : 3 cpu MHz : 2992.658 cache size : 2048 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr bogomips : 7485.54 processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) 4 CPU 3.00GHz stepping : 3 cpu MHz : 2992.658 cache size : 2048 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc up pni monitor ds_cpl est cid cx16 xtpr bogomips : 7485.54 =========================================== -- With Best Regards, RHCE, Avramenko Andrew R-Style. Technical support. From suyashjape at gmail.com Tue Jan 16 16:35:30 2007 From: suyashjape at gmail.com (suyash jape) Date: Tue, 16 Jan 2007 22:05:30 +0530 Subject: [Fedora-xen] Fwd: %post doubts In-Reply-To: <16314edc0701160806n35b09880yefab2d5ab6fe3b51@mail.gmail.com> References: <16314edc0701160806n35b09880yefab2d5ab6fe3b51@mail.gmail.com> Message-ID: <16314edc0701160835q6ed95a7cx5a13d7979f1f2a06@mail.gmail.com> ---------- Forwarded message ---------- From: suyash jape Date: Jan 16, 2007 9:36 PM Subject: %post doubts To: xen-users at lists.xensource.com Hello ,I 'm a newbie Linux and i'm trying to use Xen and Linux together. I'm facing few problens with %post in kickstart in FC5. 1)Copying of files during post is failing inspite of having Static IP.( resolv.conf must have been ready.So dunno why.). 2)Other than /usr/share/doc/anaconda-11.1.1.3/kickstart-docs.txt file, Could you suggest some documents which could tell me "how flexible is %post and what all are the thigns we can do with it" 3)Also i'm a little confused about the state of the file system when anaconda is running %post.Could you shed some light on that and what things like /mnt/sysimage corresponds to? will be eternally grateful Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gary at primeexalia.com Tue Jan 16 16:51:44 2007 From: gary at primeexalia.com (Gary W. Smith) Date: Tue, 16 Jan 2007 08:51:44 -0800 Subject: [Fedora-xen] DomU problem with tap:aio and xvdN. In-Reply-To: <45ACB25C.70508@gmail.com> References: <57F9959B46E0FA4D8BA88AEDFBE5829024EFA3@pxtbenexd01.pxt.primeexalia.com> <45AC6421.7030803@gmail.com> <57F9959B46E0FA4D8BA88AEDFBE5829024EFA6@pxtbenexd01.pxt.primeexalia.com> <45ACB25C.70508@gmail.com> Message-ID: <57F9959B46E0FA4D8BA88AEDFBE5829024EFA9@pxtbenexd01.pxt.primeexalia.com> Been down that road as well. The problem here is that not all of the OS's I'm playing with have a xenified kernel. I had seen this article before though. I haven't tested it as of yet. The problem is the destination machine for some of these VM's isn't VT enabled. > -----Original Message----- > From: Sadique Puthen [mailto:xenguy at gmail.com] > Sent: Tuesday, January 16, 2007 3:09 AM > To: Gary W. Smith > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] DomU problem with tap:aio and xvdN. > > Gary W. Smith wrote: > > Sadique, > > > > Can you explain how to do this in each environment? > > One example: > > http://people.redhat.com/riel/RHEL4-Xen-HOWTO > > > I've been down that > > road with limited success as grub worked different in each environment. > > Installing grub usually requires me to hack quick a bit of stuff. > > > > OTOH the people on the xen-users at lists.xensource.com said just the > > opposite when I was looking for help getting the kernel to boot using > > grub (/usr/bin/pygrub). > > > > As for the modified kernels per OS I've been having bad luck with > > getting things like FC4 working under 3.0.4. > > > > > > > > > >> -----Original Message----- > >> From: Sadique Puthen [mailto:xenguy at gmail.com] > >> Sent: Monday, January 15, 2007 9:35 PM > >> To: Gary W. Smith > >> Cc: fedora-xen at redhat.com > >> Subject: Re: [Fedora-xen] DomU problem with tap:aio and xvdN. > >> > >> Gary W. Smith wrote: > >> > >>> Hello, > >>> > >>> In a nutshell, I can't get DomU's to work with xvdN and tap:aio > >>> > > under > > > >>> FC6.2869. I have also tried to get them to work with XenSource > >>> > > 3.0.4. > > > >>> I've been asking this in the xen-users group but I haven't had any > >>> positive response. I have the following DomU's that I'm testing > >>> > > with: > > > >>> FC4/5/6, CentOS4. In general, they all seem to have the same > >>> > > problems. > > > >>> The problem is that when I reference the FC6 Xen boot kernel in the > >>> kernel config line for the DomU it kernel panics. I have copied > >>> /lib/modules/* (FC6 and XenSource) to the DomU as well for testing. > >>> > > If > > > >>> I do sdN and file it all works fine, but only for XenSource kernel. > >>> > >>> At the Dom0 level we are booting to FC.2869 and only referencing the > >>> XenSource 3.0.4 images at the DomU config file level. > >>> > >>> Am I missing something fundamental? I have also ran into this > >>> > > problem > > > >>> with the jailtime.org images as well. > >>> > >>> FC6 kernel: > >>> (kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen') > >>> > >>> XENBUS: Device with no driver: device/vbd/51713 > >>> XENBUS: Device with no driver: device/vbd/51714 > >>> XENBUS: Device with no driver: device/vif/0 > >>> md: Autodetecting RAID arrays. > >>> md: autorun ... > >>> md: ... autorun DONE. > >>> VFS: Cannot open root device "xvda1" or unknown-block(0,0) > >>> Please append a correct "root=" boot option > >>> Kernel panic - not syncing: VFS: Unable to mount root fs on > >>> unknown-block(0,0) > >>> > >>> XenSource 3.0.4 kernel: > >>> (kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen') > >>> > >>> md: Autodetecting RAID arrays. > >>> md: autorun ... > >>> md: ... autorun DONE. > >>> WARNING: g.e. still in use! > >>> WARNING: leaking g.e. and page still in use! > >>> end_request: I/O error, dev xvda1, sector 2 > >>> EXT2-fs: unable to read superblock > >>> Kernel panic - not syncing: VFS: Unable to mount root fs on > >>> unknown-block(202,1) > >>> > >>> > >>> Overall config file: > >>> > >>> name = 'fedora4' > >>> memory = '256' > >>> disk = [ 'file:/xen-build/fedora4/xen-D0.img,xvda1,w' , > >>> 'file:/xen-build/fedora4/xen-swap.img,xvda2,w' ] > >>> #disk = [ > >>> > >>> > > 'tap:aio:/xen-build/fedora4/xen-D0.img,xvda1,w','tap:aio:/xen-build/fedo > > > >>> ra4/xen-swap.img,xvda2,w' ] > >>> root = '/dev/xvda1 ro' > >>> vif = [ 'mac=00:16:e6:CD:49:5B' ] > >>> kernel = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen' > >>> > >>> > >> Why don't use bootloader = "/usr/bin/pygrub" and load a modified > >> > > kernel > > > >> from domU itself? > >> > >>> #kernel = '/boot/vmlinuz-2.6.18-1.2869.fc6xen' > >>> on_reboot = 'restart' > >>> on_crash = 'restart' > >>> extras = 'console=xvc0' > >>> > >>> > >>> > >>> -- > >>> Fedora-xen mailing list > >>> Fedora-xen at redhat.com > >>> https://www.redhat.com/mailman/listinfo/fedora-xen > >>> > >>> > >>> > > > > > > From ktanzer at desc.org Tue Jan 16 20:30:52 2007 From: ktanzer at desc.org (Ken Tanzer) Date: Tue, 16 Jan 2007 12:30:52 -0800 Subject: [Fedora-xen] 4gb seg fixup, process on FC6 domU In-Reply-To: <008301c73927$44fdcce0$0a00000a@ispbrasil> References: <45ABE038.8000802@guentherk.net> <008301c73927$44fdcce0$0a00000a@ispbrasil> Message-ID: <45AD35FC.2080607@desc.org> > install kernel-xen on domU using a RPMS, will fix your problem. Can you explain why this would fix the problem, or what the problem is? IIRC, domU is terminology for a guest Xen machine (with dom0 being the host). In my case, I was running a xen kernel (dom0), but not running any guest machines, so I don't have a domU that would come into play. Thanks! Ken -------------- next part -------------- A non-text attachment was scrubbed... Name: ktanzer.vcf Type: text/x-vcard Size: 342 bytes Desc: not available URL: From berrange at redhat.com Tue Jan 16 20:39:59 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 16 Jan 2007 20:39:59 +0000 Subject: [Fedora-xen] 4gb seg fixup, process on FC6 domU In-Reply-To: <45ABE038.8000802@guentherk.net> References: <45ABE038.8000802@guentherk.net> Message-ID: <20070116203959.GC10619@redhat.com> On Mon, Jan 15, 2007 at 02:12:40PM -0600, Karl Guenther wrote: > Hi, > > I have read through the threads on the 4gb seg fixup. Both Xen and > beagle are important to me for day to day use. > > I boot into FC6 Xen and beagle seems to work but I am not sure what the > 4gb seg fixup messages are all about. Are they just warning messages? Yes, there're merely warnings. They indicate that the Mono virtual machine is using -ve segment addressing, which forces Xen to jump through some nasty hoops. This in turn causes bad performance for the app in question. GLibC used to have the same problem, but has been fixed to not do this kind of -ve segment addressing when run on Xen. Mono is still using the slow way :-( 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 itamar at ispbrasil.com.br Wed Jan 17 02:16:44 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Wed, 17 Jan 2007 00:16:44 -0200 Subject: [Fedora-xen] 4gb seg fixup, process on FC6 domU References: <45ABE038.8000802@guentherk.net> <008301c73927$44fdcce0$0a00000a@ispbrasil> <45AD35FC.2080607@desc.org> Message-ID: <005701c739dd$8a9e3c10$0a00000a@ispbrasil> this is a warning about glibc to stop messages on console echo "hwcap 0 nosegneg" > /etc/ld.so.conf.d/nosegneg.conf or install kernel-xen on domU -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 ----- Original Message ----- From: "Ken Tanzer" To: "Itamar Reis Peixoto" Cc: "Karl Guenther" ; "Fedora-xen" Sent: Tuesday, January 16, 2007 6:30 PM Subject: Re: [Fedora-xen] 4gb seg fixup, process on FC6 domU > >> install kernel-xen on domU using a RPMS, will fix your problem. > > Can you explain why this would fix the problem, or what the problem is? > IIRC, domU is terminology for a guest Xen machine (with dom0 being the > host). In my case, I was running a xen kernel (dom0), but not running > any guest machines, so I don't have a domU that would come into play. > > Thanks! > > Ken > > From netwiz at crc.id.au Wed Jan 17 11:12:32 2007 From: netwiz at crc.id.au (Steven Haigh) Date: Wed, 17 Jan 2007 22:12:32 +1100 Subject: [Fedora-xen] Asterisk and passing a TDM400P card to a DomU Message-ID: Hi guys, I'm trying to use a TDM400P PCI card in a DomU host however when I insert the modules for the PCI card to the asterisk DomU, I get the following: Jan 17 22:13:48 asterisk kernel: Zapata Telephony Interface Registered on major 196 Jan 17 22:13:48 asterisk kernel: Zaptel Version: 1.4.0 Echo Canceller: MG2 Jan 17 22:13:53 asterisk kernel: PCI: Enabling device 0000:00:00.0 (0000 -> 0003) Jan 17 22:13:53 asterisk kernel: Freshmaker version: 73 Jan 17 22:13:53 asterisk kernel: Freshmaker passed register test Jan 17 22:13:54 asterisk kernel: Module 0: Not installed Jan 17 22:13:54 asterisk kernel: Module 1: Not installed Jan 17 22:13:54 asterisk kernel: Module 2: Not installed Jan 17 22:13:54 asterisk kernel: Module 3: Installed -- AUTO FXO (AUSTRALIA mode) Jan 17 22:13:54 asterisk kernel: Found a Wildcard TDM: Wildcard TDM400P REV I (1 modules) Jan 17 22:13:54 asterisk kernel: Registered tone zone 1 (Australia) Jan 17 22:13:54 asterisk kernel: TDM PCI Master abort Jan 17 22:13:54 asterisk last message repeated 3100 times Jan 17 22:13:54 asterisk kernel: TDM Pr ar abort Jan 17 22:13:54 asterisk kernel: r abort Jan 17 22:13:54 asterisk kernel: >> This seems to happen until I unload the module. I have passed the PCI card through successfully, as I see this on the DomU: # lspci 00:00.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface Anyone have any ideas on this? -- Steven Haigh Email: netwiz at crc.id.au Web: http://www.crc.id.au Phone: (03) 9017 0597 - 0412 935 897 From andreground at gmail.com Wed Jan 17 10:32:36 2007 From: andreground at gmail.com (AndreGround) Date: Wed, 17 Jan 2007 11:32:36 +0100 Subject: [Fedora-xen] Unable to start a FC3 domU under FC6 using Fedora bundled Xen packages Message-ID: Hi, this is the error I get when I try to start my FC3 domU. exec of init (/sbin/init) failed!!!: No such file or directory Kernel panic - not syncing: Attempted to kill init! I can share any config if you need to check something. Any help/idea is *REALLY* appreciated. Thanks in advance, Andrea From netwiz at crc.id.au Wed Jan 17 22:33:37 2007 From: netwiz at crc.id.au (Steven Haigh) Date: Thu, 18 Jan 2007 09:33:37 +1100 Subject: [Fedora-xen] Asterisk and passing a TDM400P card to a DomU In-Reply-To: References: Message-ID: <6D556902-F53C-4FF3-8FFE-B431FB3E364A@crc.id.au> Further to this, It seems to happen when I have more than one PCI device accessing the PCI bus at once... I have a sound card passed to another DomU which is recording audio from the Line In. If I shut this down, the asterisk module for the wctdm card does not produce these errors. Could this be a bug in the hypervisor wrt PCI access? On 17/01/2007, at 10:12 PM, Steven Haigh wrote: > Hi guys, > > I'm trying to use a TDM400P PCI card in a DomU host however when I > insert the modules for the PCI card to the asterisk DomU, I get the > following: > > Jan 17 22:13:48 asterisk kernel: Zapata Telephony Interface > Registered on major 196 > Jan 17 22:13:48 asterisk kernel: Zaptel Version: 1.4.0 Echo > Canceller: MG2 > Jan 17 22:13:53 asterisk kernel: PCI: Enabling device 0000:00:00.0 > (0000 -> 0003) > Jan 17 22:13:53 asterisk kernel: Freshmaker version: 73 > Jan 17 22:13:53 asterisk kernel: Freshmaker passed register test > Jan 17 22:13:54 asterisk kernel: Module 0: Not installed > Jan 17 22:13:54 asterisk kernel: Module 1: Not installed > Jan 17 22:13:54 asterisk kernel: Module 2: Not installed > Jan 17 22:13:54 asterisk kernel: Module 3: Installed -- AUTO FXO > (AUSTRALIA mode) > Jan 17 22:13:54 asterisk kernel: Found a Wildcard TDM: Wildcard > TDM400P REV I (1 modules) > Jan 17 22:13:54 asterisk kernel: Registered tone zone 1 (Australia) > Jan 17 22:13:54 asterisk kernel: TDM PCI Master abort > Jan 17 22:13:54 asterisk last message repeated 3100 times > Jan 17 22:13:54 asterisk kernel: TDM Pr ar abort > Jan 17 22:13:54 asterisk kernel: r abort > Jan 17 22:13:54 asterisk kernel: Jan 17 22:13:54 asterisk kernel: r abort > Jan 17 22:13:54 asterisk kernel: Jan 17 22:13:54 asterisk kernel: r abort > Jan 17 22:13:54 asterisk kernel: r abort > Jan 17 22:13:54 asterisk kernel: > <<< repeated many, many times >>> > > This seems to happen until I unload the module. > > I have passed the PCI card through successfully, as I see this on > the DomU: > # lspci > 00:00.0 Communication controller: Tiger Jet Network Inc. Tiger3XX > Modem/ISDN interface > > Anyone have any ideas on this? > > -- > Steven Haigh > > Email: netwiz at crc.id.au > Web: http://www.crc.id.au > Phone: (03) 9017 0597 - 0412 935 897 > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Steven Haigh Email: netwiz at crc.id.au Web: http://www.crc.id.au Phone: (03) 9017 0597 - 0412 935 897 From andreground at gmail.com Thu Jan 18 10:01:55 2007 From: andreground at gmail.com (AndreGround) Date: Thu, 18 Jan 2007 11:01:55 +0100 Subject: [Fedora-xen] Unable to start a FC3 domU under FC6 using Fedora bundled Xen packages In-Reply-To: References: Message-ID: Andrew, Ninny, thanks a lot for your reply! I'm collecting data (configurations and logs) from different tests I've made and then I'll post everything in order to let you better analyze my issue. Thanks again, Andrea On 1/18/07, ninny issac wrote: > Hi, > The error is probably due to incorrect root partition for your guest domain. > The kernel will start /sbin/init after mounting the root partion. > Could you provide more details like what is the root partion for FC3 domU , > whether it is a partition or file and also your configuration file for domU, > so people can easily figure it out. > > > > > On 1/17/07, AndreGround wrote: > > > > Hi, > > this is the error I get when I try to start my FC3 domU. > > > > exec of init (/sbin/init) failed!!!: No such file or directory > > Kernel panic - not syncing: Attempted to kill init! > > > > I can share any config if you need to check something. > > > > Any help/idea is *REALLY* appreciated. > > > > Thanks in advance, > > Andrea > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > From andreground at gmail.com Thu Jan 18 14:34:14 2007 From: andreground at gmail.com (AndreGround) Date: Thu, 18 Jan 2007 15:34:14 +0100 Subject: [Fedora-xen] Unable to start a FC3 domU under FC6 using Fedora bundled Xen packages In-Reply-To: References: Message-ID: Hi, here are all my config files & logs taken from my test: Please note that the kernel used is the one provided by Fedora RPM Packages. The initrd (initrd-2.6.18-1.2869.fc6xenU.img) has been generated using the mkinitrd syntax listed below. - Test 1) Xen config file: #kernel ="/boot/vmlinuz-2.6.18-1.2869.fc6xen" #ramdisk = "/boot/initrd-2.6.18-1.2869.fc6xenU.img" memory = 256 name = "mail" bootloader="/usr/bin/pygrub" #vif = ['mac=aa:00:00:00:00:01'] disk = ['tap:aio:/xen/mail/fedora.img,xvda1,w','tap:aio:/xen/mail/swap1.img,xvda2,w'] #root = "/dev/sda1 ro" #extra = "ro selinux=0 3" DomU grub: title Fedora Core 3 root (hd0,0) kernel /boot/vmlinuz-2.6.18-1.2869.fc6xen root=/dev/xvda1 initrd /boot/initrd-2.6.18-1.2869.fc6xenU.img DomU fstab: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/xvda1 / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/xvda2 swap swap defaults 0 0 Initrd creation script: mkinitrd -f --with=xennet --preload=xenblk /xen/mnt/boot/initrd-2.6.18-1.2869.fc6xenU.img --fstab=/xen/mnt/etc/fstab 2.6.18-1.2869.fc6xen Initrd: [root at hulk initrd]# cat init #!/bin/nash mount -t proc /proc /proc setquiet echo Mounting proc filesystem echo Mounting sysfs filesystem mount -t sysfs /sys /sys echo Creating /dev mount -o mode=0755 -t tmpfs /dev /dev mkdir /dev/pts mount -t devpts -o gid=5,mode=620 /dev/pts /dev/pts mkdir /dev/shm mkdir /dev/mapper echo Creating initial device nodes mknod /dev/null c 1 3 mknod /dev/zero c 1 5 mknod /dev/systty c 4 0 mknod /dev/tty c 5 0 mknod /dev/console c 5 1 mknod /dev/ptmx c 5 2 mknod /dev/rtc c 10 135 mknod /dev/tty0 c 4 0 mknod /dev/tty1 c 4 1 mknod /dev/tty2 c 4 2 mknod /dev/tty3 c 4 3 mknod /dev/tty4 c 4 4 mknod /dev/tty5 c 4 5 mknod /dev/tty6 c 4 6 mknod /dev/tty7 c 4 7 mknod /dev/tty8 c 4 8 mknod /dev/tty9 c 4 9 mknod /dev/tty10 c 4 10 mknod /dev/tty11 c 4 11 mknod /dev/tty12 c 4 12 mknod /dev/ttyS0 c 4 64 mknod /dev/ttyS1 c 4 65 mknod /dev/ttyS2 c 4 66 mknod /dev/ttyS3 c 4 67 echo Setting up hotplug. hotplug echo Creating block device nodes. mkblkdevs echo "Loading xenblk.ko module" insmod /lib/xenblk.ko echo "Loading uhci-hcd.ko module" insmod /lib/uhci-hcd.ko echo "Loading ohci-hcd.ko module" 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" insmod /lib/scsi_mod.ko echo "Loading sd_mod.ko module" insmod /lib/sd_mod.ko echo "Loading 3w-xxxx.ko module" insmod /lib/3w-xxxx.ko echo "Loading xennet.ko module" insmod /lib/xennet.ko mkblkdevs resume /dev/xvda2 echo Creating root device. mkrootdev -t ext3 -o defaults,ro /dev/xvda1 echo Mounting root filesystem. mount /sysroot echo Setting up other filesystems. setuproot echo Switching to new root and running init. switchroot Result: exec of init (/sbin/init) failed!!!: No such file or directory Kernel panic - not syncing: Attempted to kill init! Log: [root at hulk ~]# xm create -c mail Using config file "/etc/xen/mail". Going to boot Fedora Core 3 kernel: /boot/vmlinuz-2.6.18-1.2869.fc6xen initrd: /boot/initrd-2.6.18-1.2869.fc6xenU.img Started domain mail Linux version 2.6.18-1.2869.fc6xen (brewbuilder at ls20-bc2-14.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Wed Dec 20 15:28:06 EST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Using x86 segment limits to approximate NX protection ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 67584 Kernel command line: root=/dev/xvda1 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c078b000 soft=c076b000 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 1800.059 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB disabled vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000 Memory: 250940k/270336k available (2099k kernel code, 10876k reserved, 842k data, 180k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4503.36 BogoMIPS (lpj=9006734) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 3324k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 6, 327680 bytes) TCP bind hash table entries: 8192 (order: 5, 163840 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1169130101.084:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 1E0E64C0A8BD9F26 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.18-1.2869.fc6xen (brewbuilder at ls20-bc2-14.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Wed Dec 20 15:28:06 EST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Using x86 segment limits to approximate NX protection ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 67584 Kernel command line: root=/dev/xvda1 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c078b000 soft=c076b000 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 1800.059 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB disabled vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000 Memory: 250940k/270336k available (2099k kernel code, 10876k reserved, 842k data, 180k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4503.36 BogoMIPS (lpj=9006734) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 3324k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 6, 327680 bytes) TCP bind hash table entries: 8192 (order: 5, 163840 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1169130101.084:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 1E0E64C0A8BD9F26 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new driver libusual usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51713 XENBUS: Device with no driver: device/vbd/51714 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 357k Red Hat nash version 5.1.19.0.2 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading xenblk.ko module Registering block device major 202 Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading ohci-hcd.ko module Loading ehci-hcd.ko module Loading jbd.ko module Loading ext3.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading 3w-xxxx.ko module 3ware Storage Controller device driver for Linux v1.26.02.001. Loading xennet.ko module netfront: Initialising virtual ethernet driver. Creating root device. Mounting root filesystem. EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys exec of init (/sbin/init) failed!!!: No such file or directory Kernel panic - not syncing: Attempted to kill init! Other test reports will follow. Let me have your thoughts. Thanks in advance, Andrea Maurizio Gnerre On 1/18/07, AndreGround wrote: > Andrew, Ninny, > thanks a lot for your reply! > > I'm collecting data (configurations and logs) from different tests > I've made and then I'll post everything in order to let you better > analyze my issue. > > Thanks again, > Andrea > > On 1/18/07, ninny issac wrote: > > Hi, > > The error is probably due to incorrect root partition for your guest domain. > > The kernel will start /sbin/init after mounting the root partion. > > Could you provide more details like what is the root partion for FC3 domU , > > whether it is a partition or file and also your configuration file for domU, > > so people can easily figure it out. > > > > > > > > > > On 1/17/07, AndreGround wrote: > > > > > > Hi, > > > this is the error I get when I try to start my FC3 domU. > > > > > > exec of init (/sbin/init) failed!!!: No such file or directory > > > Kernel panic - not syncing: Attempted to kill init! > > > > > > I can share any config if you need to check something. > > > > > > Any help/idea is *REALLY* appreciated. > > > > > > Thanks in advance, > > > Andrea > > > > > > -- > > > Fedora-xen mailing list > > > Fedora-xen at redhat.com > > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > From m3freak at rogers.com Fri Jan 19 05:54:02 2007 From: m3freak at rogers.com (Kanwar Ranbir Sandhu) Date: Fri, 19 Jan 2007 00:54:02 -0500 Subject: [Fedora-xen] Internal and external domains on one host In-Reply-To: <1168465447.20064.12.camel@krs> References: <1168465447.20064.12.camel@krs> Message-ID: <1169186042.17319.20.camel@krs> On Wed, 2007-01-10 at 16:44 -0500, Kanwar Ranbir Sandhu wrote: > Would I be crazy to use one physical box to run a few internal Xen domU > (stuff for the LAN), and use the same host to run a few domU in a DMZ > (website, mail, etc.)? Besides the fact that a DoS attack on the DMZ > domU could slow the domU on the LAN side down to a crawl, is there > anything else that I should be concerned about? > > I have a small home office, and want to consolidate my three servers to > two. Besides saving some electricity, the box in the DMZ is old and > slow - the one I want to consolidate to is _much_ better. The better > server is already running Xen and a few domU, actually. > > Has anyone done this? A little part of me says it would be fool hardy, > but I can be convinced otherwise! Does anyone have an opinion on this? I'm still wondering if it's wise to use one Xen box for domUs in a DMZ and domUs in a trusted network. Thanks, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.18-1.2869.fc6 i686 GNU/Linux 00:51:33 up 1 day, 2:15, 2 users, load average: 0.52, 0.34, 0.32 From fedora-xen at j.jimmc.org Fri Jan 19 06:48:08 2007 From: fedora-xen at j.jimmc.org (Jim McBeath) Date: Thu, 18 Jan 2007 22:48:08 -0800 Subject: [Fedora-xen] "4gb seg fixup, process X" on FC6 dom0 Message-ID: <20070119064808.GA5407@nwlink.com> I am running a stock FC6 xen, with all yum updates through today, on a Shuttle box with a Core 2 Duo and 2GB of memory. I am getting "4gb seg fixup" for plenty of programs, including X, sh, ls, date, grep, less, ssh, su and vim. This is in dom0, with no domU running. The worst offender is X: in /var/log/messages, every five seconds it consistently logs something like this: Jan 18 19:34:59 gumby kernel: printk: 30302 messages suppressed. Jan 18 19:34:59 gumby kernel: 4gb seg fixup, process X (pid 4383), cs:ip 73:47150f2a 20,000 is typical for the number of messages suppressed. It varies in different five-second intervals from about 10,000 to 89,000. I have poked around on the net and searched through the archives for this group, without finding an answer. I have seen a few posts about 4gb-seg-fixup messages in domU, or from mono programs, or from older OSs that needed a "nosegneg" file in /etc/ld.so.conf.d, but none of those seem to apply here. Any suggestions? -- Jim McBeath [root at gumby ~]# uname -a Linux gumby.local 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 19:47:12 EST 2007 i686 i686 i386 GNU/Linux [root at gumby ~]# ls /etc/ld.so.conf.d kernelcap-2.6.18-1.2869.fc6.conf mysql-i386.conf kernelcap-2.6.19-1.2895.fc6.conf qt-i386.conf [root at gumby ~]# cat /etc/ld.so.conf.d/kernelcap-2.6.19-1.2895.fc6.conf # This directive teaches ldconfig to search in nosegneg subdirectories # and cache the DSOs there with extra bit 0 set in their hwcap match # fields. In Xen guest kernels, the vDSO tells the dynamic linker to # search in nosegneg subdirectories and to match this extra hwcap bit # in the ld.so.cache file. hwcap 0 nosegneg [root at gumby ~]# From mario at verbelen.org Fri Jan 19 07:48:26 2007 From: mario at verbelen.org (Mario Verbelen) Date: Fri, 19 Jan 2007 08:48:26 +0100 Subject: [Fedora-xen] Internal and external domains on one host In-Reply-To: <1169186042.17319.20.camel@krs> References: <1168465447.20064.12.camel@krs> <1169186042.17319.20.camel@krs> Message-ID: <1169192906.5698.16.camel@leo> On Fri, 2007-01-19 at 00:54 -0500, Kanwar Ranbir Sandhu wrote: > On Wed, 2007-01-10 at 16:44 -0500, Kanwar Ranbir Sandhu wrote: > > Would I be crazy to use one physical box to run a few internal Xen domU > > (stuff for the LAN), and use the same host to run a few domU in a DMZ > > (website, mail, etc.)? Besides the fact that a DoS attack on the DMZ > > domU could slow the domU on the LAN side down to a crawl, is there > > anything else that I should be concerned about? > > > > I have a small home office, and want to consolidate my three servers to > > two. Besides saving some electricity, the box in the DMZ is old and > > slow - the one I want to consolidate to is _much_ better. The better > > server is already running Xen and a few domU, actually. > > > > Has anyone done this? A little part of me says it would be fool hardy, > > but I can be convinced otherwise! > > Does anyone have an opinion on this? I'm still wondering if it's wise > to use one Xen box for domUs in a DMZ and domUs in a trusted network. > > Thanks, > > Ranbir > My opinion of this, Well If you configure it well I don't see a problem (as far as I known xen) Make shore the can't hack dom0 keep this ip internal and place only domU's in dmz (best via other network card or via vlan's) I don't think that bridging only is save enough when someone hacks a domU Mario, From asraikhn at gmail.com Sun Jan 21 16:20:02 2007 From: asraikhn at gmail.com (Asrai khn) Date: Sun, 21 Jan 2007 21:20:02 +0500 Subject: [Fedora-xen] "4gb seg fixup, process X" on FC6 dom0 In-Reply-To: <20070119064808.GA5407@nwlink.com> References: <20070119064808.GA5407@nwlink.com> Message-ID: <5f0f8dba0701210820v113e0004k8636223f4891dc4c@mail.gmail.com> Yes there is a fix for this you can find the solution in the archives http://www.mail-archive.com/fedora-xen at redhat.com/msg00053.html Thanks. Askar On 1/19/07, Jim McBeath wrote: > > I am running a stock FC6 xen, with all yum updates through today, on a > Shuttle box with a Core 2 Duo and 2GB of memory. I am getting "4gb seg > fixup" for plenty of programs, including X, sh, ls, date, grep, less, > ssh, su and vim. This is in dom0, with no domU running. > > The worst offender is X: in /var/log/messages, every five seconds > it consistently logs something like this: > > Jan 18 19:34:59 gumby kernel: printk: 30302 messages suppressed. > Jan 18 19:34:59 gumby kernel: 4gb seg fixup, process X (pid 4383), cs:ip > 73:47150f2a > > 20,000 is typical for the number of messages suppressed. It varies in > different five-second intervals from about 10,000 to 89,000. > > I have poked around on the net and searched through the archives > for this group, without finding an answer. I have seen a few posts > about 4gb-seg-fixup messages in domU, or from mono programs, or from > older OSs that needed a "nosegneg" file in /etc/ld.so.conf.d, but > none of those seem to apply here. > > Any suggestions? > > -- > Jim McBeath > > > [root at gumby ~]# uname -a > Linux gumby.local 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 19:47:12 EST 2007 > i686 i686 i386 GNU/Linux > [root at gumby ~]# ls /etc/ld.so.conf.d > kernelcap-2.6.18-1.2869.fc6.conf mysql-i386.conf > kernelcap-2.6.19-1.2895.fc6.conf qt-i386.conf > [root at gumby ~]# cat /etc/ld.so.conf.d/kernelcap-2.6.19-1.2895.fc6.conf > # This directive teaches ldconfig to search in nosegneg subdirectories > # and cache the DSOs there with extra bit 0 set in their hwcap match > # fields. In Xen guest kernels, the vDSO tells the dynamic linker to > # search in nosegneg subdirectories and to match this extra hwcap bit > # in the ld.so.cache file. > hwcap 0 nosegneg > [root at gumby ~]# > > -- > 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 fedora-xen at j.jimmc.org Sun Jan 21 20:49:51 2007 From: fedora-xen at j.jimmc.org (Jim McBeath) Date: Sun, 21 Jan 2007 12:49:51 -0800 Subject: [Fedora-xen] "4gb seg fixup, process X" on FC6 dom0 In-Reply-To: <5f0f8dba0701210820v113e0004k8636223f4891dc4c@mail.gmail.com> References: <20070119064808.GA5407@nwlink.com> <5f0f8dba0701210820v113e0004k8636223f4891dc4c@mail.gmail.com> Message-ID: <20070121204950.GA16518@nwlink.com> Thanks for responding, Askar. I saw that thread, and those fixes are not working for me. My system already had the nosegneg file in /etc/ld.so.conf.d (it was installed there along with the kernel, so that issue has been fixed in the sources), and ldconfig shows that the system knows about it: # ldconfig -N -X -p | grep libc.so libc.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) => /lib/i686/nosegneg/libc.so.6 libc.so.6 (libc6, OS ABI: Linux 2.6.9) => /lib/libc.so.6 The messages are coming from non-mono processes, so that's not it either. Perhaps a problem with dual cpu being used with Xen and FC6? Is there anyone else out there running Xen and FC6 on a Core 2 Duo who can report not having this problem? -- Jim On Sun, Jan 21, 2007 at 09:20:02PM +0500, Asrai khn wrote: > Date: Sun, 21 Jan 2007 21:20:02 +0500 > From: "Asrai khn" > To: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] "4gb seg fixup, process X" on FC6 dom0 > > > Yes there is a fix for this you can find the solution in the archives > http://www.mail-archive.com/fedora-xen at redhat.com/msg00053.html > Thanks. Askar > > On 1/19/07, Jim McBeath wrote: > > I am running a stock FC6 xen, with all yum updates through today, on a > Shuttle box with a Core 2 Duo and 2GB of memory. I am getting "4gb seg > fixup" for plenty of programs, including X, sh, ls, date, grep, less, > ssh, su and vim. This is in dom0, with no domU running. > The worst offender is X: in /var/log/messages, every five seconds > it consistently logs something like this: > Jan 18 19:34:59 gumby kernel: printk: 30302 messages suppressed. > Jan 18 19:34:59 gumby kernel: 4gb seg fixup, process X (pid 4383), cs:ip > 73:47150f2a > 20,000 is typical for the number of messages suppressed. It varies in > different five-second intervals from about 10,000 to 89,000. > I have poked around on the net and searched through the archives > for this group, without finding an answer. I have seen a few posts > about 4gb-seg-fixup messages in domU, or from mono programs, or from > older OSs that needed a "nosegneg" file in /etc/ld.so.conf.d, but > none of those seem to apply here. > Any suggestions? > -- > Jim McBeath > [root at gumby ~]# uname -a > Linux gumby.local 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 19:47:12 EST 2007 > i686 i686 i386 GNU/Linux > [root at gumby ~]# ls /etc/ld.so.conf.d > kernelcap-2.6.18-1.2869.fc6.conf mysql-i386.conf > kernelcap-2.6.19-1.2895.fc6.conf qt-i386.conf > [root at gumby ~]# cat /etc/ld.so.conf.d/kernelcap-2.6.19-1.2895.fc6.conf > # This directive teaches ldconfig to search in nosegneg subdirectories > # and cache the DSOs there with extra bit 0 set in their hwcap match > # fields. In Xen guest kernels, the vDSO tells the dynamic linker to > # search in nosegneg subdirectories and to match this extra hwcap bit > # in the ld.so.cache file. > hwcap 0 nosegneg > [root at gumby ~]# From mfreemon at ncsa.uiuc.edu Mon Jan 22 17:13:41 2007 From: mfreemon at ncsa.uiuc.edu (Mike Freemon) Date: Mon, 22 Jan 2007 11:13:41 -0600 Subject: [Fedora-xen] "4gb seg fixup, process X" on FC6 dom0 In-Reply-To: <20070121204950.GA16518@nwlink.com> References: <20070119064808.GA5407@nwlink.com> <5f0f8dba0701210820v113e0004k8636223f4891dc4c@mail.gmail.com> <20070121204950.GA16518@nwlink.com> Message-ID: <6.0.0.22.2.20070122111336.028e17f0@pop.ncsa.uiuc.edu> At 1/21/2007 02:49 PM Sunday, Jim McBeath wrote: >Thanks for responding, Askar. I saw that thread, and those fixes >are not working for me. My system already had the nosegneg file in >/etc/ld.so.conf.d (it was installed there along with the kernel, so that >issue has been fixed in the sources), and ldconfig shows that the system >knows about it: > ># ldconfig -N -X -p | grep libc.so > libc.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) => > /lib/i686/nosegneg/libc.so.6 > libc.so.6 (libc6, OS ABI: Linux 2.6.9) => /lib/libc.so.6 > >The messages are coming from non-mono processes, so that's not it either. > >Perhaps a problem with dual cpu being used with Xen and FC6? > >Is there anyone else out there running Xen and FC6 on a Core 2 Duo who >can report not having this problem? > >-- >Jim > >On Sun, Jan 21, 2007 at 09:20:02PM +0500, Asrai khn wrote: > > Date: Sun, 21 Jan 2007 21:20:02 +0500 > > From: "Asrai khn" > > To: fedora-xen at redhat.com > > Subject: Re: [Fedora-xen] "4gb seg fixup, process X" on FC6 dom0 > > > > > > Yes there is a fix for this you can find the solution in the archives > > http://www.mail-archive.com/fedora-xen at redhat.com/msg00053.html > > Thanks. Askar > > > > On 1/19/07, Jim McBeath wrote: > > > > I am running a stock FC6 xen, with all yum updates through today, on a > > Shuttle box with a Core 2 Duo and 2GB of memory. I am getting > "4gb seg > > fixup" for plenty of programs, including X, sh, ls, date, grep, less, > > ssh, su and vim. This is in dom0, with no domU running. > > The worst offender is X: in /var/log/messages, every five seconds > > it consistently logs something like this: > > Jan 18 19:34:59 gumby kernel: printk: 30302 messages suppressed. > > Jan 18 19:34:59 gumby kernel: 4gb seg fixup, process X (pid > 4383), cs:ip > > 73:47150f2a > > 20,000 is typical for the number of messages suppressed. It varies in > > different five-second intervals from about 10,000 to 89,000. > > I have poked around on the net and searched through the archives > > for this group, without finding an answer. I have seen a few posts > > about 4gb-seg-fixup messages in domU, or from mono programs, or from > > older OSs that needed a "nosegneg" file in /etc/ld.so.conf.d, but > > none of those seem to apply here. > > Any suggestions? > > -- > > Jim McBeath > > [root at gumby ~]# uname -a > > Linux gumby.local 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 19:47:12 > EST 2007 > > i686 i686 i386 GNU/Linux > > [root at gumby ~]# ls /etc/ld.so.conf.d > > kernelcap-2.6.18-1.2869.fc6.conf mysql-i386.conf > > kernelcap-2.6.19-1.2895.fc6.conf qt-i386.conf > > [root at gumby ~]# cat /etc/ld.so.conf.d/kernelcap-2.6.19-1.2895.fc6.conf > > # This directive teaches ldconfig to search in nosegneg subdirectories > > # and cache the DSOs there with extra bit 0 set in their hwcap match > > # fields. In Xen guest kernels, the vDSO tells the dynamic linker to > > # search in nosegneg subdirectories and to match this extra hwcap bit > > # in the ld.so.cache file. > > hwcap 0 nosegneg > > [root at gumby ~]# > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From mfreemon at ncsa.uiuc.edu Mon Jan 22 17:18:16 2007 From: mfreemon at ncsa.uiuc.edu (Mike Freemon) Date: Mon, 22 Jan 2007 11:18:16 -0600 Subject: [Fedora-xen] xm list broken in xen 3.0.3-3 In-Reply-To: <20070121204950.GA16518@nwlink.com> References: <20070119064808.GA5407@nwlink.com> <5f0f8dba0701210820v113e0004k8636223f4891dc4c@mail.gmail.com> <20070121204950.GA16518@nwlink.com> Message-ID: <6.0.0.22.2.20070122111407.028eb370@pop.ncsa.uiuc.edu> When upgrading from xen-3.0.3-2 to xen-3.0.3-3, the xm list command breaks with the following error: # xm list Name ID Mem(MiB) VCPUs State Time(s) Error: method "xend.domain.getSysMem" is not supported Usage: xm list [options] [Domain, ...] List information about all/some domains. -l, --long Output all VM details in SXP --label Include security labels It looks like the getSysMem functionality changed. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=649 Is there a new version of the xen-3.0.3 package in updates-testing planned? # rpm -qa|grep xen kernel-xen0-2.6.18-1.2239.fc5 kernel-xen0-2.6.18-1.2257.fc5 xen-3.0.3-3.fc5 # rpm -qa|grep libvirt libvirt-python-0.1.7-3.FC5 libvirt-0.1.7-3.FC5 # dmesg|head Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb quiet) Linux version 2.6.18-1.2257.fc5xen0 (brewbuilder at ls20-bc1-13.build.redhat.com) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)) #1 SMP Fri Dec 15 17:06:13 EST 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 00000001f0e11000 (usable) On node 0 totalpages: 2035217 DMA zone: 2035217 pages, LIFO batch:31 DMI 2.4 present. ACPI: RSDP (v002 DELL ) @ 0x00000000000f2a00 ACPI: XSDT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x00000000000f2a80 ACPI: FADT (v003 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x00000000000f2b88 TIA, - Mike From berrange at redhat.com Mon Jan 22 17:26:40 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 22 Jan 2007 17:26:40 +0000 Subject: [Fedora-xen] xm list broken in xen 3.0.3-3 In-Reply-To: <6.0.0.22.2.20070122111407.028eb370@pop.ncsa.uiuc.edu> References: <20070119064808.GA5407@nwlink.com> <5f0f8dba0701210820v113e0004k8636223f4891dc4c@mail.gmail.com> <20070121204950.GA16518@nwlink.com> <6.0.0.22.2.20070122111407.028eb370@pop.ncsa.uiuc.edu> Message-ID: <20070122172640.GH7153@redhat.com> On Mon, Jan 22, 2007 at 11:18:16AM -0600, Mike Freemon wrote: > When upgrading from xen-3.0.3-2 to xen-3.0.3-3, the xm list command breaks > with the following error: You need to restart XenD (or reboot the host). We didn't automatically resart XenD in the %post script because that doesn't play nicely if you have any fullvirt guests running :-( > Name ID Mem(MiB) VCPUs State Time(s) > Error: method "xend.domain.getSysMem" is not supported > Usage: xm list [options] [Domain, ...] > > List information about all/some domains. > -l, --long Output all VM details in SXP > --label Include security labels > > It looks like the getSysMem functionality changed. Its a new function actually - previous 'xm list' just reported what you'd told XenD to give the guest - this was not the same as what the guest was actually allocated by the HV. The new getSysMem function is used to make xm list show the correct (actual) allocation 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 naoki at valuecommerce.com Tue Jan 23 09:52:51 2007 From: naoki at valuecommerce.com (Naoki) Date: Tue, 23 Jan 2007 18:52:51 +0900 Subject: [Fedora-xen] xen images gone from rawhide. Message-ID: <1169545971.24378.91.camel@dragon.valuecommerce.ne.jp> http://redhat.download.fedoraproject.org/pub/fedora/linux/core/development/x86_64//os/images/xen doesn't exist. Is he coming back? Sorry I had a flick through devel-list archives but didn't see a matching subject and fedora-devel suggested asking the xen maintainer.. To be honest I don't know who that is. From thomas.vonsteiger at bluewin.ch Tue Jan 23 13:25:22 2007 From: thomas.vonsteiger at bluewin.ch (Thomas von Steiger) Date: Tue, 23 Jan 2007 14:25:22 +0100 Subject: [Fedora-xen] FC6: guest's with link in /etc/xen/auto not startet after xen update Message-ID: <004201c73ef1$ef503500$3201a8c0@athlon> Hello, I have updated fc6 to xen-3.0.3-3 and kernel-xen 2.6.19-1.2895 without any problem. After reboot all the guest's with a link in /etc/xen/auto don't start automatically. How I can autostart the guest with this xen releases ? If I try to start the guest's with "xm create rhel41" for example, all the guest's are running without problem. Many Thanks for any Tips, Thomas -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.6/646 - Release Date: 23.01.2007 03:36 From quintela at redhat.com Tue Jan 23 11:26:27 2007 From: quintela at redhat.com (Juan Quintela) Date: Tue, 23 Jan 2007 12:26:27 +0100 Subject: [Fedora-xen] xen images gone from rawhide. In-Reply-To: <1169545971.24378.91.camel@dragon.valuecommerce.ne.jp> References: <1169545971.24378.91.camel@dragon.valuecommerce.ne.jp> Message-ID: <1169551587.12919.11.camel@Chuck.local> On Tue, 2007-01-23 at 18:52 +0900, Naoki wrote: Hi > http://redhat.download.fedoraproject.org/pub/fedora/linux/core/development/x86_64//os/images/xen doesn't exist. > > Is he coming back? > > Sorry I had a flick through devel-list archives but didn't see a > matching subject and fedora-devel suggested asking the xen maintainer.. To be honest I don't know who that is. It is comming back. Problem is that there is still not 2.6.20-rcX xen kernel around :( I am finishing it, but it will take still anouther week (and I am known to be one optimist). As an interim solution, there are going to be linuyx-2.6.19.2, xen-3.0.4 kernels around while I finish the 2.6.20 kernels. Later, Juan. From quintela at redhat.com Tue Jan 23 16:18:44 2007 From: quintela at redhat.com (Juan Quintela) Date: Tue, 23 Jan 2007 17:18:44 +0100 Subject: [Fwd: Re: [Fedora-xen] xen images gone from rawhide.] Message-ID: <1169569124.12919.14.camel@Chuck.local> [ Sending also to the mailing list] -------------- next part -------------- An embedded message was scrubbed... From: Juan Quintela Subject: Re: [Fedora-xen] xen images gone from rawhide. Date: Tue, 23 Jan 2007 12:26:27 +0100 Size: 1251 URL: From master at bradleyland.com Tue Jan 23 17:21:36 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Tue, 23 Jan 2007 09:21:36 -0800 (PST) Subject: [Fedora-xen] FC6/Xen crash -- isolated to rsnapshot job Message-ID: <48005.192.168.3.1.1169572896.squirrel@www.bradleyland.com> I've isolated my FC6/xen crashing problems to cron backup jobs that were running in my dom0. I have moved the jobs into a domU and now observe the crashing behavior in the domU. At least the entire environment doesn't come down when it's in a domU. In my crontab, I have a series of rsnapshot backup jobs to backup a handful of windows and linux servers. For windows machines, the script mounts a share on the windows machine using CIFS (samba). It seems only the Windows backup jobs crash the machine and then only crash when two are scheduled to start at exactly the same time. I can replicate the problem by running the crontab command from the command line. If I run the commands one at a time, no crash. If I start them both back to back, the crash occurs within 30 seconds or so. Under FC4, these scripts/backup jobs worked fine for almost a year without intervention. I've read there have been a host of problems with CIFS in FC6, but I thought they had been resolved. As a workaround, I can change the job schedule for now, but something is still broken in the kernel, samba or both. Here's a trace: list_del corruption. prev->next should be c2f5c640, but was c2f50080 ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:65! invalid opcode: 0000 [#1] SMP last sysfs file: /block/ram0/range Modules linked in: nls_utf8 cifs ipv6 autofs4 hidp l2cap bluetooth iptable_raw xt_policy xt_multiport ipt_ULOG ipt_TTL ipt_ttl ipt_TOS ipt_tos ipt_TCPMSS ipt_SAME ipt_REJECT ipt_REDIRECT ipt_recent ipt_owner ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_iprange ipt_hashlimit ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype ip_nat_tftp ip_nat_snmp_basic ip_nat_pptp ip_nat_irc ip_nat_ftp ip_nat_amanda ip_conntrack_tftp ip_conntrack_pptp ip_conntrack_netbios_ns ip_conntrack_irc ip_conntrack_ftp ts_kmp ip_conntrack_amanda xt_tcpmss xt_pkttype xt_physdev bridge xt_NFQUEUE xt_MARK xt_mark xt_mac xt_limit xt_length xt_helper xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat ip_nat ip_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables tun sunrpc xennet parport_pc lp parport pcspkr dm_snapshot dm_zero dm_mirror dm_mod raid456 xor ext3 jbd xenblk CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010082 (2.6.19-1.2895.fc6xen #1) EIP is at list_del+0x23/0x6c eax: 00000048 ebx: c2f5c640 ecx: c0683b30 edx: f5416000 esi: c117a7c0 edi: c32af000 ebp: c117eda0 esp: c0d2def0 ds: 007b es: 007b ss: 0069 Process events/0 (pid: 5, ti=c0d2d000 task=c006e030 task.ti=c0d2d000) Stack: c0646145 c2f5c640 c2f50080 c2f5c640 c0467706 c078afc0 c028c980 c0619b9d 00000014 00000002 c1176228 c1176220 00000014 c1176200 00000000 c0467809 00000000 00000000 c117eda0 c117a7e4 c117a7c0 c117eda0 c0d404a0 00000000 Call Trace: [] free_block+0x77/0xf0 [] drain_array+0x8a/0xb5 [] cache_reap+0x85/0x117 [] run_workqueue+0x97/0xdd [] worker_thread+0xd9/0x10d [] kthread+0xc0/0xec [] kernel_thread_helper+0x7/0x10 ======================= Code: 00 00 89 c3 eb e8 90 90 53 89 c3 83 ec 0c 8b 40 04 8b 00 39 d8 74 1c 89 5c 24 04 89 44 24 08 c7 04 24 45 61 64 c0 e8 9a 4b f3 ff <0f> 0b 41 00 82 61 64 c0 8b 03 8b 40 04 39 d8 74 1c 89 5c 24 04 EIP: [] list_del+0x23/0x6c SS:ESP 0069:c0d2def0 <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20 in_atomic():0, irqs_disabled():1 [] dump_trace+0x69/0x1b6 [] show_trace_log_lvl+0x18/0x2c [] show_trace+0xf/0x11 [] dump_stack+0x15/0x17 [] down_read+0x12/0x28 [] blocking_notifier_call_chain+0xe/0x29 [] do_exit+0x1b/0x787 [] die+0x2af/0x2d4 [] do_invalid_op+0xa2/0xab [] error_code+0x2b/0x30 [] list_del+0x23/0x6c [] free_block+0x77/0xf0 [] drain_array+0x8a/0xb5 [] cache_reap+0x85/0x117 [] run_workqueue+0x97/0xdd [] worker_thread+0xd9/0x10d [] kthread+0xc0/0xec [] kernel_thread_helper+0x7/0x10 ======================= BUG: spinlock lockup on CPU#0, rsync/11148, c117a7e4 (Not tainted) [] dump_trace+0x69/0x1b6 [] show_trace_log_lvl+0x18/0x2c [] show_trace+0xf/0x11 [] dump_stack+0x15/0x17 [] _raw_spin_lock+0xbf/0xdc [] cache_alloc_refill+0x74/0x4dc [] kmem_cache_alloc+0x54/0x6d [] pgd_alloc+0x54/0x230 [] mm_init+0x94/0xb9 [] do_execve+0x6f/0x1f5 [] sys_execve+0x2f/0x4f [] syscall_call+0x7/0xb [<00b98402>] 0xb98402 ======================= From pasik at iki.fi Tue Jan 23 20:05:36 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 23 Jan 2007 22:05:36 +0200 Subject: [Fedora-xen] xen images gone from rawhide. In-Reply-To: <1169551587.12919.11.camel@Chuck.local> References: <1169545971.24378.91.camel@dragon.valuecommerce.ne.jp> <1169551587.12919.11.camel@Chuck.local> Message-ID: <20070123200536.GH7120@edu.joroinen.fi> On Tue, Jan 23, 2007 at 12:26:27PM +0100, Juan Quintela wrote: > On Tue, 2007-01-23 at 18:52 +0900, Naoki wrote: > > Hi > > > http://redhat.download.fedoraproject.org/pub/fedora/linux/core/development/x86_64//os/images/xen doesn't exist. > > > > Is he coming back? > > > > Sorry I had a flick through devel-list archives but didn't see a > > matching subject and fedora-devel suggested asking the xen maintainer.. To be honest I don't know who that is. > > It is comming back. Problem is that there is still not 2.6.20-rcX xen > kernel around :( > > I am finishing it, but it will take still anouther week (and I am known > to be one optimist). As an interim solution, there are going to be > linuyx-2.6.19.2, xen-3.0.4 kernels around while I finish the 2.6.20 > kernels. > Hi! Any idea when xen 3.0.4 packages will hit rawhide ? Based on that reply I would guess in a couple of days.. ? Thanks! -- Pasi > Later, Juan. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From berrange at redhat.com Tue Jan 23 20:08:51 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 23 Jan 2007 20:08:51 +0000 Subject: [Fedora-xen] xen images gone from rawhide. In-Reply-To: <20070123200536.GH7120@edu.joroinen.fi> References: <1169545971.24378.91.camel@dragon.valuecommerce.ne.jp> <1169551587.12919.11.camel@Chuck.local> <20070123200536.GH7120@edu.joroinen.fi> Message-ID: <20070123200851.GJ19805@redhat.com> On Tue, Jan 23, 2007 at 10:05:36PM +0200, Pasi K?rkk?inen wrote: > On Tue, Jan 23, 2007 at 12:26:27PM +0100, Juan Quintela wrote: > > On Tue, 2007-01-23 at 18:52 +0900, Naoki wrote: > > > > Hi > > > > > http://redhat.download.fedoraproject.org/pub/fedora/linux/core/development/x86_64//os/images/xen doesn't exist. > > > > > > Is he coming back? > > > > > > Sorry I had a flick through devel-list archives but didn't see a > > > matching subject and fedora-devel suggested asking the xen maintainer.. To be honest I don't know who that is. > > > > It is comming back. Problem is that there is still not 2.6.20-rcX xen > > kernel around :( > > > > I am finishing it, but it will take still anouther week (and I am known > > to be one optimist). As an interim solution, there are going to be > > linuyx-2.6.19.2, xen-3.0.4 kernels around while I finish the 2.6.20 > > kernels. > > > > Hi! > > Any idea when xen 3.0.4 packages will hit rawhide ? Based on that reply I > would guess in a couple of days.. ? About 4 days ago - i built xen 3.0.4 into rawhide on friday in anticipation of Juan having a kernel ready... 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 quintela at redhat.com Tue Jan 23 20:30:49 2007 From: quintela at redhat.com (Juan Quintela) Date: Tue, 23 Jan 2007 21:30:49 +0100 Subject: [Fedora-xen] xen images gone from rawhide. In-Reply-To: <20070123200536.GH7120@edu.joroinen.fi> References: <1169545971.24378.91.camel@dragon.valuecommerce.ne.jp> <1169551587.12919.11.camel@Chuck.local> <20070123200536.GH7120@edu.joroinen.fi> Message-ID: <1169584249.31128.0.camel@Chuck.local> On Tue, 2007-01-23 at 22:05 +0200, Pasi K?rkk?inen wrote: > On Tue, Jan 23, 2007 at 12:26:27PM +0100, Juan Quintela wrote: > > On Tue, 2007-01-23 at 18:52 +0900, Naoki wrote: > > > > Hi > > > > > http://redhat.download.fedoraproject.org/pub/fedora/linux/core/development/x86_64//os/images/xen doesn't exist. > > > > > > Is he coming back? > > > > > > Sorry I had a flick through devel-list archives but didn't see a > > > matching subject and fedora-devel suggested asking the xen maintainer.. To be honest I don't know who that is. > > > > It is comming back. Problem is that there is still not 2.6.20-rcX xen > > kernel around :( > > > > I am finishing it, but it will take still anouther week (and I am known > > to be one optimist). As an interim solution, there are going to be > > linuyx-2.6.19.2, xen-3.0.4 kernels around while I finish the 2.6.20 > > kernels. > > > > Hi! > > Any idea when xen 3.0.4 packages will hit rawhide ? Based on that reply I > would guess in a couple of days.. ? I hate rpm packaging. I hate rpm packaging. .... I hope to get something later today/tomorrow. But getting it through brew is getting _interesting_. Later, Juan. From asraikhn at gmail.com Wed Jan 24 14:08:23 2007 From: asraikhn at gmail.com (Asrai khn) Date: Wed, 24 Jan 2007 19:08:23 +0500 Subject: [Fedora-xen] FC6: guest's with link in /etc/xen/auto not startet after xen update In-Reply-To: <004201c73ef1$ef503500$3201a8c0@athlon> References: <004201c73ef1$ef503500$3201a8c0@athlon> Message-ID: <5f0f8dba0701240608h40f413a3jc3f43c27d7c8a68e@mail.gmail.com> Hi, Are you sture xend and xendomains services running when you start xen dom0? , also before rebooting host shutdown all VMs and see it start it or not. Thanks. Askar On 1/23/07, Thomas von Steiger wrote: > > Hello, > > I have updated fc6 to xen-3.0.3-3 and kernel-xen 2.6.19-1.2895 without any > problem. > After reboot all the guest's with a link in /etc/xen/auto don't start > automatically. > How I can autostart the guest with this xen releases ? > > If I try to start the guest's with "xm create rhel41" for example, all the > guest's are running without problem. > > Many Thanks for any Tips, > > Thomas > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.432 / Virus Database: 268.17.6/646 - Release Date: 23.01.2007 > 03:36 > > > -- > 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 asraikhn at gmail.com Wed Jan 24 14:04:20 2007 From: asraikhn at gmail.com (Asrai khn) Date: Wed, 24 Jan 2007 19:04:20 +0500 Subject: [Fedora-xen] xm list broken in xen 3.0.3-3 In-Reply-To: <20070122172640.GH7153@redhat.com> References: <20070119064808.GA5407@nwlink.com> <5f0f8dba0701210820v113e0004k8636223f4891dc4c@mail.gmail.com> <20070121204950.GA16518@nwlink.com> <6.0.0.22.2.20070122111407.028eb370@pop.ncsa.uiuc.edu> <20070122172640.GH7153@redhat.com> Message-ID: <5f0f8dba0701240604u6d6047cm8fc940a0298616c7@mail.gmail.com> Exactly need to reboot xend service, this happend to me also but when i ... service xend restart xm list starting working fine Thanks. Askar On 1/22/07, Daniel P. Berrange wrote: > > On Mon, Jan 22, 2007 at 11:18:16AM -0600, Mike Freemon wrote: > > When upgrading from xen-3.0.3-2 to xen-3.0.3-3, the xm list command > breaks > > with the following error: > > You need to restart XenD (or reboot the host). We didn't automatically > resart > XenD in the %post script because that doesn't play nicely if you have any > fullvirt guests running :-( > > > Name ID Mem(MiB) VCPUs State > Time(s) > > Error: method "xend.domain.getSysMem" is not supported > > Usage: xm list [options] [Domain, ...] > > > > List information about all/some domains. > > -l, --long Output all VM details in SXP > > --label Include security labels > > > > It looks like the getSysMem functionality changed. > > Its a new function actually - previous 'xm list' just reported what you'd > told XenD to give the guest - this was not the same as what the guest was > actually allocated by the HV. The new getSysMem function is used to make > xm list show the correct (actual) allocation > > 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 -=| > > -- > 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 benjhenrion at gmail.com Thu Jan 25 10:43:01 2007 From: benjhenrion at gmail.com (benjamin henrion) Date: Thu, 25 Jan 2007 11:43:01 +0100 Subject: [Fedora-xen] guest debian on fedora host with virt-manager Message-ID: Hello every body! I have installed Xen on fedora to try virt-manager. All is allright to install an fedora guest. But now i want to install an debian guest . And i don't find the address to have the debian medium. I'have tried this one " http://ftp2.fr.debian.org/debian/" and this one " http://ftp2.de.debian.org/debian/" but it doesn't match... I just know the Fedora medium: http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/ So, please i need the address of the debian medium ... Thanks ! benjamin -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Thu Jan 25 12:25:15 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 25 Jan 2007 12:25:15 +0000 Subject: [Fedora-xen] guest debian on fedora host with virt-manager In-Reply-To: References: Message-ID: <20070125122515.GD15872@redhat.com> On Thu, Jan 25, 2007 at 11:43:01AM +0100, benjamin henrion wrote: > Hello every body! > > I have installed Xen on fedora to try virt-manager. > All is allright to install an fedora guest. But now i want to install an > debian guest . > And i don't find the address to have the debian medium. I'have tried this > one " > http://ftp2.fr.debian.org/debian/" and this one " > http://ftp2.de.debian.org/debian/" but it doesn't match... > > I just know the Fedora medium: > http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/ > > So, please i need the address of the debian medium ... Unfortunately the Debian trees are not setup in a way which allows us to do paravirtualized Xen installs from virt-manager[1]. So for Debian you'll have to use full-virt instead, or run the Debian bootstrap scripts to manually create a DomU image. Not much help for your situation, but we're prototyping support for installing SuSE paravirt guests from virt-manager, now we've identified how their installer can be booted under Xen. Regards, Dan. [1] virt-manager requires a vmlinuz & initrd file for Xen kernel which is able to boot straight into the installer. -- |=- 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 master at bradleyland.com Thu Jan 25 17:58:14 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Thu, 25 Jan 2007 09:58:14 -0800 (PST) Subject: [Fedora-xen] FC6/Xen/CIFS mount broken Message-ID: <35894.192.168.3.1.1169747894.squirrel@www.bradleyland.com> With further narrowing down, I've isolated my FC6/xen crashes to mounting a CIFS volume. A single mount is all that is required to cause the kernel oops. Please see fedora bugzilla # 214622. It looks as though the base kernel has been patched, but the xenified kernel has not. (?) If the xen kernels have been patched, then the problem still exists. Doesn't matter whether the Windows share is mounted rw or ro. Same behavior. No IO required. After the mount, the machine will crash within a minute or so, virtually every time so it should be easy to test. Can anyone tell me when the non-xen CIFS kernel patch will make it into the xen kernels? This bug has been driving me crazy. Thanks, Dave [root at firewall2 ~]# uname -a Linux firewall2.xxxxxxx.com 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 19:47:12 EST 2007 i686 athlon i386 GNU/Linux From jerutley at gmail.com Thu Jan 25 21:30:11 2007 From: jerutley at gmail.com (Jeremy Utley) Date: Thu, 25 Jan 2007 13:30:11 -0800 Subject: [Fedora-xen] FC6/Xen/CIFS mount broken In-Reply-To: <35894.192.168.3.1.1169747894.squirrel@www.bradleyland.com> References: <35894.192.168.3.1.1169747894.squirrel@www.bradleyland.com> Message-ID: On 1/25/07, master at bradleyland.com wrote: > With further narrowing down, I've isolated my FC6/xen crashes to mounting > a CIFS volume. A single mount is all that is required to cause the kernel > oops. > > Please see fedora bugzilla # 214622. > > It looks as though the base kernel has been patched, but the xenified > kernel has not. (?) If the xen kernels have been patched, then the problem > still exists. > > Doesn't matter whether the Windows share is mounted rw or ro. Same > behavior. No IO required. After the mount, the machine will crash within a > minute or so, virtually every time so it should be easy to test. > > Can anyone tell me when the non-xen CIFS kernel patch will make it into > the xen kernels? This bug has been driving me crazy. > > Thanks, > > Dave > > [root at firewall2 ~]# uname -a > Linux firewall2.xxxxxxx.com 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 > 19:47:12 EST 2007 i686 athlon i386 GNU/Linux I have this exact same kernel, but in the amd64 variant, and am mounting a CIFS filesystem exported from another Fedora 6 box without difficulty. No crashes or anything. Is this i386-specific? Jeremy [jeremy at vulcan ~]$ uname -a Linux vulcan.internal.jutley.org 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 19:09:13 EST 2007 x86_64 x86_64 x86_64 GNU/Linux [jeremy at vulcan ~]$ mount | grep cifs //hurricane/storage on /mnt/storage type cifs (rw,mand) From master at bradleyland.com Thu Jan 25 21:56:41 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Thu, 25 Jan 2007 13:56:41 -0800 (PST) Subject: [Fedora-xen] FC6/Xen/CIFS mount broken In-Reply-To: References: <35894.192.168.3.1.1169747894.squirrel@www.bradleyland.com> Message-ID: <46919.192.168.3.1.1169762201.squirrel@www.bradleyland.com> > > I have this exact same kernel, but in the amd64 variant, and am > mounting a CIFS filesystem exported from another Fedora 6 box without > difficulty. No crashes or anything. Is this i386-specific? > > Jeremy > > [jeremy at vulcan ~]$ uname -a > Linux vulcan.internal.jutley.org 2.6.19-1.2895.fc6xen #1 SMP Wed Jan > 10 19:09:13 EST 2007 x86_64 x86_64 x86_64 GNU/Linux > [jeremy at vulcan ~]$ mount | grep cifs > //hurricane/storage on /mnt/storage type cifs (rw,mand) > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > Hmmm, interesting. I don't know as I'm not running any 64bit hardware. I can bring down either dom0 or domU with a single mount. Have you tried mounting a "real" Windows share? Probably doesn't make any difference though... The patch exists. If I get tired of waiting, I'll get the kernel sources, put in the patch and compile it myself. Just a hassle. From jerutley at gmail.com Thu Jan 25 22:47:17 2007 From: jerutley at gmail.com (Jeremy Utley) Date: Thu, 25 Jan 2007 14:47:17 -0800 Subject: [Fedora-xen] FC6/Xen/CIFS mount broken In-Reply-To: <46919.192.168.3.1.1169762201.squirrel@www.bradleyland.com> References: <35894.192.168.3.1.1169747894.squirrel@www.bradleyland.com> <46919.192.168.3.1.1169762201.squirrel@www.bradleyland.com> Message-ID: On 1/25/07, master at bradleyland.com wrote: > Hmmm, interesting. I don't know as I'm not running any 64bit hardware. I > can bring down either dom0 or domU with a single mount. > > Have you tried mounting a "real" Windows share? Probably doesn't make any > difference though... > > The patch exists. If I get tired of waiting, I'll get the kernel sources, > put in the patch and compile it myself. Just a hassle. > > Just on a whim, I tried mounting a share on my Windows 2003 server box here at home, and it mounted just fine as well. Unfortunately, I don't have any regular X86 boxes here running the Xen kernel, so I can't really tell for sure what would happen doing this on a normal X86 machine. It's strange, but even using older Fedora 6 kernels on X86, I haven't had any issues *MOUNTING* a cifs partition - but I would find that I couldn't read those files properly at one time. Jeremy From andreground at gmail.com Fri Jan 26 12:44:36 2007 From: andreground at gmail.com (AndreGround) Date: Fri, 26 Jan 2007 13:44:36 +0100 Subject: [Fedora-xen] Unable to start a FC3 domU under FC6 using Fedora bundled Xen packages In-Reply-To: References: Message-ID: Hi Ninny, thanks for your help. Here's what I get without using the initrd: VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Please let me have your considerations. Thanks again, Andrea On 1/25/07, ninny issac wrote: > Hi, > Could you try to use sda1/sda2 instead of xvda1/2. > ie, disk = > ['tap:aio:/xen/mail/fedora.img,sda1,w','tap:aio:/xen/mail/swap1.img,sda2,w'] > Also can you comment out the initrd line from DomU grub: > title Fedora Core 3 > root (hd0,0) > kernel /boot/vmlinuz-2.6.18-1.2869.fc6xen root=/dev/sda1 > # initrd /boot/initrd-2.6.18-1.2869.fc6xenU.img > > The error says that kernel could not find /sbin/init , so just try with the > above configuration. > > > > > > On 1/18/07, AndreGround wrote: > > Hi, > > here are all my config files & logs taken from my test: > > > > Please note that the kernel used is the one provided by Fedora RPM > Packages. > > The initrd (initrd-2.6.18-1.2869.fc6xenU.img) has been > generated using > > the mkinitrd syntax listed below. > > > > - Test 1) > > > > Xen config file: > > #kernel ="/boot/vmlinuz-2.6.18-1.2869.fc6xen" > > #ramdisk = "/boot/initrd-2.6.18-1.2869.fc6xenU.img" > > memory = 256 > > name = "mail" > > bootloader="/usr/bin/pygrub" > > #vif = ['mac=aa:00:00:00:00:01'] > > disk = > ['tap:aio:/xen/mail/fedora.img,xvda1,w','tap:aio:/xen/mail/swap1.img,xvda2,w'] > > #root = "/dev/sda1 ro" > > #extra = "ro selinux=0 3" > > > > DomU grub: > > title Fedora Core 3 > > root (hd0,0) > > kernel /boot/vmlinuz-2.6.18-1.2869.fc6xen root=/dev/xvda1 > > initrd /boot/initrd-2.6.18-1.2869.fc6xenU.img > > > > DomU fstab: > > # This file is edited by fstab-sync - see 'man fstab-sync' for details > > /dev/xvda1 / ext3 > defaults 1 1 > > none /dev/pts devpts > gid=5,mode=620 0 0 > > none /dev/shm tmpfs > defaults 0 0 > > none /proc proc > defaults 0 0 > > none /sys sysfs > defaults 0 0 > > /dev/xvda2 swap swap > defaults 0 0 > > > > Initrd creation script: > > mkinitrd -f --with=xennet --preload=xenblk > > /xen/mnt/boot/initrd-2.6.18-1.2869.fc6xenU.img > > --fstab=/xen/mnt/etc/fstab 2.6.18-1.2869.fc6xen > > > > Initrd: > > [root at hulk initrd]# cat init > > #!/bin/nash > > > > mount -t proc /proc /proc > > setquiet > > echo Mounting proc filesystem > > echo Mounting sysfs filesystem > > mount -t sysfs /sys /sys > > echo Creating /dev > > mount -o mode=0755 -t tmpfs /dev /dev > > mkdir /dev/pts > > mount -t devpts -o gid=5,mode=620 /dev/pts /dev/pts > > mkdir /dev/shm > > mkdir /dev/mapper > > echo Creating initial device nodes > > mknod /dev/null c 1 3 > > mknod /dev/zero c 1 5 > > mknod /dev/systty c 4 0 > > mknod /dev/tty c 5 0 > > mknod /dev/console c 5 1 > > mknod /dev/ptmx c 5 2 > > mknod /dev/rtc c 10 135 > > mknod /dev/tty0 c 4 0 > > mknod /dev/tty1 c 4 1 > > mknod /dev/tty2 c 4 2 > > mknod /dev/tty3 c 4 3 > > mknod /dev/tty4 c 4 4 > > mknod /dev/tty5 c 4 5 > > mknod /dev/tty6 c 4 6 > > mknod /dev/tty7 c 4 7 > > mknod /dev/tty8 c 4 8 > > mknod /dev/tty9 c 4 9 > > mknod /dev/tty10 c 4 10 > > mknod /dev/tty11 c 4 11 > > mknod /dev/tty12 c 4 12 > > mknod /dev/ttyS0 c 4 64 > > mknod /dev/ttyS1 c 4 65 > > mknod /dev/ttyS2 c 4 66 > > mknod /dev/ttyS3 c 4 67 > > echo Setting up hotplug. > > hotplug > > echo Creating block device nodes. > > mkblkdevs > > echo "Loading xenblk.ko module" > > insmod /lib/xenblk.ko > > echo "Loading uhci-hcd.ko module" > > insmod /lib/uhci-hcd.ko > > echo "Loading ohci-hcd.ko module" > > 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" > > insmod /lib/scsi_mod.ko > > echo "Loading sd_mod.ko module" > > insmod /lib/sd_mod.ko > > echo "Loading 3w-xxxx.ko module" > > insmod /lib/3w- xxxx.ko > > echo "Loading xennet.ko module" > > insmod /lib/xennet.ko > > mkblkdevs > > resume /dev/xvda2 > > echo Creating root device. > > mkrootdev -t ext3 -o defaults,ro /dev/xvda1 > > echo Mounting root filesystem. > > mount /sysroot > > echo Setting up other filesystems. > > setuproot > > echo Switching to new root and running init. > > switchroot > > > > Result: > > exec of init (/sbin/init) failed!!!: No such file or directory > > Kernel panic - not syncing: Attempted to kill init! > > > > Log: > > [root at hulk ~]# xm create -c mail > > Using config file "/etc/xen/mail". > > Going to boot Fedora Core 3 > > kernel: /boot/vmlinuz-2.6.18-1.2869.fc6xen > > initrd: /boot/initrd-2.6.18-1.2869.fc6xenU.img > > Started domain mail > > Linux version 2.6.18-1.2869.fc6xen > > (brewbuilder at ls20-bc2-14.build.redhat.com ) (gcc version > 4.1.1 20061011 > > (Red Hat 4.1.1-30)) #1 SMP Wed Dec 20 15:28:06 EST 2006 > > BIOS-provided physical RAM map: > > Xen: 0000000000000000 - 0000000010800000 (usable) > > 0MB HIGHMEM available. > > 264MB LOWMEM available. > > Using x86 segment limits to approximate NX protection > > ACPI in unprivileged domain disabled > > Built 1 zonelists. Total pages: 67584 > > Kernel command line: root=/dev/xvda1 > > Enabling fast FPU save and restore... done. > > Enabling unmasked SIMD FPU exception support... done. > > Initializing CPU#0 > > CPU 0 irqstacks, hard=c078b000 soft=c076b000 > > PID hash table entries: 2048 (order: 11, 8192 bytes) > > Xen reported: 1800.059 MHz processor. > > Console: colour dummy device 80x25 > > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > > Software IO TLB disabled > > vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000 > > Memory: 250940k/270336k available (2099k kernel code, 10876k reserved, > > 842k data, 180k init, 0k highmem) > > Checking if this processor honours the WP bit even in supervisor mode... > Ok. > > Calibrating delay using timer specific routine.. 4503.36 BogoMIPS > (lpj=9006734) > > Security Framework v1.0.0 initialized > > SELinux: Initializing. > > SELinux: Starting in permissive mode > > selinux_register_security: Registering secondary module > capability > > Capability LSM initialized as secondary > > Mount-cache hash table entries: 512 > > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > > CPU: L2 Cache: 256K (64 bytes/line) > > Checking 'hlt' instruction... OK. > > SMP alternatives: switching to UP code > > Freeing SMP alternatives: 12k freed > > Brought up 1 CPUs > > checking if image is initramfs... it is > > Freeing initrd memory: 3324k freed > > Grant table initialized > > NET: Registered protocol family 16 > > Brought up 1 CPUs > > PCI: setting up Xen PCI frontend stub > > ACPI: Interpreter disabled. > > Linux Plug and Play Support v0.97 (c) Adam Belay > > pnp: PnP ACPI: disabled > > xen_mem: Initialising balloon driver. > > usbcore: registered new driver usbfs > > usbcore: registered new driver hub > > PCI: System does not support PCI > > PCI: System does not support PCI > > NetLabel: Initializing > > NetLabel: domain hash size = 128 > > NetLabel: protocols = UNLABELED CIPSOv4 > > NetLabel: unlabeled traffic allowed by default > > NET: Registered protocol family 2 > > IP route cache hash table entries: 4096 (order: 2, 16384 bytes) > > TCP established hash table entries: 16384 (order: 6, 327680 bytes) > > TCP bind hash table entries: 8192 (order: 5, 163840 bytes) > > TCP: Hash tables configured (established 16384 bind 8192) > > TCP reno registered > > IA-32 Microcode Update Driver: v1.14-xen < tigran at veritas.com> > > audit: initializing netlink socket (disabled) > > audit(1169130101.084:1): initialized > > VFS: Disk quotas dquot_6.5.1 > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > > SELinux: Registering netfilter hooks > > Initializing Cryptographic API > > ksign: Installing public key data > > Loading keyring > > - Added public key 1E0E64C0A8BD9F26 > > - User ID: Red Hat, Inc. (Kernel Module GPG key) > > io scheduler noop registered > > io scheduler anticipatory registered > > io scheduler deadline registered > > io scheduler cfq registered (default) > > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > > rtc: IRQ 8 is not free. > > Non-volatile memory driver v1.2 > > Linux agpgart interface v0.101 (c) Dave Jones > > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > > Xen virtual console successfully installed as xvc0 > > Linux version 2.6.18-1.2869.fc6xen > > ( brewbuilder at ls20-bc2-14.build.redhat.com) (gcc version > 4.1.1 20061011 > > (Red Hat 4.1.1-30)) #1 SMP Wed Dec 20 15:28:06 EST 2006 > > BIOS-provided physical RAM map: > > Xen: 0000000000000000 - 0000000010800000 (usable) > > 0MB HIGHMEM available. > > 264MB LOWMEM available. > > Using x86 segment limits to approximate NX protection > > ACPI in unprivileged domain disabled > > Built 1 zonelists. Total pages: 67584 > > Kernel command line: root=/dev/xvda1 > > Enabling fast FPU save and restore... done. > > Enabling unmasked SIMD FPU exception support... done. > > Initializing CPU#0 > > CPU 0 irqstacks, hard=c078b000 soft=c076b000 > > PID hash table entries: 2048 (order: 11, 8192 bytes) > > Xen reported: 1800.059 MHz processor. > > Console: colour dummy device 80x25 > > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > > Software IO TLB disabled > > vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000 > > Memory: 250940k/270336k available (2099k kernel code, 10876k reserved, > > 842k data, 180k init, 0k highmem) > > Checking if this processor honours the WP bit even in supervisor mode... > Ok. > > Calibrating delay using timer specific routine.. 4503.36 BogoMIPS > (lpj=9006734) > > Security Framework v1.0.0 initialized > > SELinux: Initializing. > > SELinux: Starting in permissive mode > > selinux_register_security: Registering secondary module > capability > > Capability LSM initialized as secondary > > Mount-cache hash table entries: 512 > > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > > CPU: L2 Cache: 256K (64 bytes/line) > > Checking 'hlt' instruction... OK. > > SMP alternatives: switching to UP code > > Freeing SMP alternatives: 12k freed > > Brought up 1 CPUs > > checking if image is initramfs... it is > > Freeing initrd memory: 3324k freed > > Grant table initialized > > NET: Registered protocol family 16 > > Brought up 1 CPUs > > PCI: setting up Xen PCI frontend stub > > ACPI: Interpreter disabled. > > Linux Plug and Play Support v0.97 (c) Adam Belay > > pnp: PnP ACPI: disabled > > xen_mem: Initialising balloon driver. > > usbcore: registered new driver usbfs > > usbcore: registered new driver hub > > PCI: System does not support PCI > > PCI: System does not support PCI > > NetLabel: Initializing > > NetLabel: domain hash size = 128 > > NetLabel: protocols = UNLABELED CIPSOv4 > > NetLabel: unlabeled traffic allowed by default > > NET: Registered protocol family 2 > > IP route cache hash table entries: 4096 (order: 2, 16384 bytes) > > TCP established hash table entries: 16384 (order: 6, 327680 bytes) > > TCP bind hash table entries: 8192 (order: 5, 163840 bytes) > > TCP: Hash tables configured (established 16384 bind 8192) > > TCP reno registered > > IA-32 Microcode Update Driver: v1.14-xen < tigran at veritas.com> > > audit: initializing netlink socket (disabled) > > audit(1169130101.084:1): initialized > > VFS: Disk quotas dquot_6.5.1 > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > > SELinux: Registering netfilter hooks > > Initializing Cryptographic API > > ksign: Installing public key data > > Loading keyring > > - Added public key 1E0E64C0A8BD9F26 > > - User ID: Red Hat, Inc. (Kernel Module GPG key) > > io scheduler noop registered > > io scheduler anticipatory registered > > io scheduler deadline registered > > io scheduler cfq registered (default) > > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > > rtc: IRQ 8 is not free. > > Non-volatile memory driver v1.2 > > Linux agpgart interface v0.101 (c) Dave Jones > > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > > Xen virtual console successfully installed as xvc0 > > Event-channel device installed. > > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > > ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > > ide-floppy driver 0.99.newide > > usbcore: registered new driver libusual > > usbcore: registered new driver hiddev > > usbcore: registered new driver usbhid > > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > > PNP: No PS/2 controller found. Probing ports directly. > > i8042.c: No controller found. > > mice: PS/2 mouse device common for all mice > > md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 > > md: bitmap version 4.39 > > TCP bic registered > > Initializing IPsec netlink socket > > NET: Registered protocol family 1 > > NET: Registered protocol family 17 > > Using IPI No-Shortcut mode > > XENBUS: Device with no driver: device/vbd/51713 > > XENBUS: Device with no driver: device/vbd/51714 > > Freeing unused kernel memory: 180k freed > > Write protecting the kernel read-only data: 357k > > Red Hat nash version 5.1.19.0.2 starting > > Mounting proc filesystem > > Mounting sysfs filesystem > > Creating /dev > > Creating initial device nodes > > Setting up hotplug. > > Creating block device nodes. > > Loading xenblk.ko module > > Registering block device major 202 > > Loading uhci-hcd.ko module > > USB Universal Host Controller Interface driver v3.0 > > Loading ohci-hcd.ko module > > Loading ehci-hcd.ko module > > Loading jbd.ko module > > Loading ext3.ko module > > Loading scsi_mod.ko module > > SCSI subsystem initialized > > Loading sd_mod.ko module > > Loading 3w-xxxx.ko module > > 3ware Storage Controller device driver for Linux v1.26.02.001. > > Loading xennet.ko module > > netfront: Initialising virtual ethernet driver. > > Creating root device. > > Mounting root filesystem. > > EXT3-fs: INFO: recovery required on readonly filesystem. > > EXT3-fs: write access will be enabled during recovery. > > kjournald starting. Commit interval 5 seconds > > EXT3-fs: recovery complete. > > EXT3-fs: mounted filesystem with ordered data mode. > > Setting up other filesystems. > > Setting up new root fs > > no fstab.sys, mounting internal defaults > > Switching to new root and running init. > > unmounting old /dev > > unmounting old /proc > > unmounting old /sys > > exec of init (/sbin/init) failed!!!: No such file or directory > > Kernel panic - not syncing: Attempted to kill init! > > > > Other test reports will follow. > > > > Let me have your thoughts. > > > > Thanks in advance, > > Andrea Maurizio Gnerre > > > > On 1/18/07, AndreGround wrote: > > > Andrew, Ninny, > > > thanks a lot for your reply! > > > > > > I'm collecting data (configurations and logs) from different tests > > > I've made and then I'll post everything in order to let you better > > > analyze my issue. > > > > > > Thanks again, > > > Andrea > > > > > > On 1/18/07, ninny issac wrote: > > > > Hi, > > > > The error is probably due to incorrect root partition for your guest > domain. > > > > The kernel will start /sbin/init after mounting the root partion. > > > > Could you provide more details like what is the root partion for FC3 > domU , > > > > whether it is a partition or file and also your configuration file for > domU, > > > > so people can easily figure it out. > > > > > > > > > > > > > > > > > > > > On 1/17/07, AndreGround < andreground at gmail.com > wrote: > > > > > > > > > > Hi, > > > > > this is the error I get when I try to start my FC3 domU. > > > > > > > > > > exec of init (/sbin/init) failed!!!: No such file or directory > > > > > Kernel panic - not syncing: Attempted to kill init! > > > > > > > > > > I can share any config if you need to check something. > > > > > > > > > > Any help/idea is *REALLY* appreciated. > > > > > > > > > > Thanks in advance, > > > > > Andrea > > > > > > > > > > -- > > > > > Fedora-xen mailing list > > > > > Fedora-xen at redhat.com > > > > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > > > > > > > > > > > > > -- > Please avoid sending me Word or PowerPoint attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > > thanks... > niny... From dhanks at corp.untd.com Fri Jan 26 18:41:07 2007 From: dhanks at corp.untd.com (Hanks, Dan) Date: Fri, 26 Jan 2007 10:41:07 -0800 Subject: [Fedora-xen] Can't boot RH7.2 fully-virtualized guest Message-ID: <37CA9FAB24D3A74B97E93B82BD04D39517462FEB@LAXEVS01.lax.corp.int.untd.com> Hi folks, I'm using FC6 (kernel 2.6.19-1.2895.fc6xen), with SELinux disabled. I'm running on a Dell D820 laptop with vmx extensions enabled (confirmed by looking for vmx in /proc/cpuinfo), trying to boot a RH7.2 (uh, yeah, don't ask...) fully-virtualized guest. I used virt-manager to successfully install RH7.2 on a disk image. However when I then try to boot from the image, on the console I see: MXT page nr start=ffffffff len=ffffffff Ooops! Too many entries in the memory map" Spewed out a lot of times, followed by some kernel information, ending up with: "Unable to handle kernel paging request at virtual address ffffffff" This ends in a kernel panic, complaining: "<0> Kernel panic: Attempted to kill the idle task! In idle task - not syncing" Here's my config file: # Automatically generated xen config file name = "rh72a" builder = "hvm" memory = "500" disk = [ 'file:/home/user/rh72.xen.img,hda,w', ] vif = [ 'type=ioemu, mac=00:16:3e:57:24:2a, bridge=xenbr0', ] uuid = "c77c61e4-3294-2bc2-7005-92b92d3191d2" device_model = "/usr/lib/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 vncunused=1 apic=1 acpi=1 pae=1 vcpus=1 serial = "pty" # enable serial console on_reboot = 'restart' on_crash = 'restart' Am I missing something obvious? Any more info I can provide that would be helpful? Thanks for any help you might offer. -- Dan Hanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From karl at athabascau.ca Fri Jan 26 18:52:11 2007 From: karl at athabascau.ca (Karl Stevens) Date: Fri, 26 Jan 2007 11:52:11 -0700 Subject: [Fedora-xen] Can't boot RH7.2 fully-virtualized guest In-Reply-To: <37CA9FAB24D3A74B97E93B82BD04D39517462FEB@LAXEVS01.lax.corp.int.untd.com> References: <37CA9FAB24D3A74B97E93B82BD04D39517462FEB@LAXEVS01.lax.corp.int.untd.com> Message-ID: <45BA4DDB.3040006@athabascau.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanks, Dan wrote: > MXT page nr start=ffffffff len=ffffffff > Ooops! Too many entries in the memory map? > This ends in a kernel panic, complaining: > ?<0> Kernel panic: Attempted to kill the idle task! In idle task ? not > syncing? We ran into the same problem. The default kernel for RH7.2 is patched to support "MXT" (automatic compression to/from RAM), and the HVM bios confuses it. Upgrade the kernel to one that doesn't have MXT (such as kernel-smp-2.4.20-28.7) and you'll be fine. There may also be a boot param to tell the kernel to ignore MXT, which would likely have the same effect. - -Karl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFuk3br6qWhNgoahURAvavAKCL9t/j6dcHlwZo5du234NhQafMwACgo6y3 SkCuujIBapk0QSy0w2Ezdpk= =pSUF -----END PGP SIGNATURE----- __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- From Darrell.Frazier at crc.army.mil Fri Jan 26 21:10:14 2007 From: Darrell.Frazier at crc.army.mil (Frazier, Darrell USA CRC (Contractor)) Date: Fri, 26 Jan 2007 15:10:14 -0600 Subject: [Fedora-xen] Cannot get xen on RHEL5 to use a RHEL4 repository Message-ID: I am running xen on a Dell 2850/ 3.0Ghz/ 12GB RAM/ RHEL5 Beta2 system. I am attempting to create a rhel4 guest. I have copied the rhel4 packages from cd into a directory (/var/www/html/rhel4) and enabled http. I created a repository on the host machine and updated yum to look at that repository using createrepo under /var/www/html/rhel4. I am able to see the repository with a web browser on another machine. My issue comes when I use the http://myhost/rhel4 in the configuration window asking where it asks where the installation media resides. I get the following error: Guest Install Error ERROR: Invalid URL location given: [Errno:14] HTTP Error 404: Not found. I am about at my wits end on how to rectify this issue. Any help would be greatly appreciated. Thanx in advance Darrell J. Frazier Unix System Administrator US Army Combat Readiness Center CAUTION: This electronic transmission may contain information protected by deliberative process or other privilege, which is protected from disclosure under the Freedom of Information Act, 5 U.S.C. ? 552. The information is intended for the use of the individual or agency to which it was sent. If you are not the intended recipient, be aware that any disclosure, distribution or use of the contents of this information is prohibited. Do not release outside of DoD channels without prior authorization from the sender. The sender provides no assurance as to the integrity of the content of this electronic transmission after it has been sent and received by the intended email recipient. -------------- next part -------------- An HTML attachment was scrubbed... URL: From acathrow at redhat.com Fri Jan 26 21:25:20 2007 From: acathrow at redhat.com (Andrew Cathrow) Date: Fri, 26 Jan 2007 16:25:20 -0500 Subject: [Fedora-xen] Cannot get xen on RHEL5 to use a RHEL4 repository In-Reply-To: References: Message-ID: <1169846720.12585.32.camel@desktop.cathrow.org> You're on a 2850 so I guess that means that you don't have VT support on your cpu Check this with $ egrep ?svm|vmx? /proc/cpuinfo flags : fpu tsc msr pae vmx mce cx8 .. which will check for VMX (intel) or SVM (amd) support. if You don't get vmx or svm in the output then you don't have the cpu extensions for full virtualization. So you'll have to use a para-virt install - today RHEL4 does not include PV support - but RHEL4.5 (due feb/march) will include that support. So probably what you're seeing is the install looking for the pv install kernel - which should be in /images/xen/vmlinuz and since it's not there you're getting a http error. On Fri, 2007-01-26 at 15:10 -0600, Frazier, Darrell USA CRC (Contractor) wrote: > > I am running xen on a Dell 2850/ 3.0Ghz/ 12GB RAM/ RHEL5 Beta2 system. > I am attempting to create a rhel4 guest. I have copied the rhel4 > packages from cd into a directory (/var/www/html/rhel4) and enabled > http. I created a repository on the host machine and updated yum to > look at that repository using createrepo under /var/www/html/rhel4. I > am able to see the repository with a web browser on another machine. > > My issue comes when I use the http://myhost/rhel4 in the > configuration window asking where it asks where the installation media > resides. I get the following error: > > Guest Install Error > > ERROR: Invalid URL location given: [Errno:14] HTTP Error 404: Not > found. > > I am about at my wits end on how to rectify this issue. Any help would > be greatly appreciated. > > Thanx in advance > > Darrell J. Frazier > Unix System Administrator > US Army Combat Readiness Center > > CAUTION: This electronic transmission may contain information > protected by deliberative process or other privilege, which is > protected from disclosure under the Freedom of Information Act, 5 > U.S.C. ? 552. The information is intended for the use of the > individual or agency to which it was sent. If you are not the intended > recipient, be aware that any disclosure, distribution or use of the > contents of this information is prohibited. Do not release outside of > DoD channels without prior authorization from the sender. The sender > provides no assurance as to the integrity of the content of this > electronic transmission after it has been sent and received by the > intended email recipient. > > > > -- > 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 dhanks at corp.untd.com Fri Jan 26 21:37:56 2007 From: dhanks at corp.untd.com (Hanks, Dan) Date: Fri, 26 Jan 2007 13:37:56 -0800 Subject: [Fedora-xen] Can't boot RH7.2 fully-virtualized guest Message-ID: <37CA9FAB24D3A74B97E93B82BD04D39517462FEC@LAXEVS01.lax.corp.int.untd.com> > > Hanks, Dan wrote: > > MXT page nr start=ffffffff len=ffffffff > > Ooops! Too many entries in the memory map" > > This ends in a kernel panic, complaining: > > "<0> Kernel panic: Attempted to kill the idle task! In idle task - not > > syncing" > > We ran into the same problem. The default kernel for RH7.2 is patched > to support "MXT" (automatic compression to/from RAM), and the HVM bios > confuses it. > > Upgrade the kernel to one that doesn't have MXT (such as > kernel-smp-2.4.20-28.7) and you'll be fine. > > There may also be a boot param to tell the kernel to ignore MXT, which > would likely have the same effect. Dr. Google indicated that setting mem=NNN in the kernel args effectively disables MXT, however when I tried that, I got no kernel panics, but the VM hung shortly after "Uncompressing the kernel" So, I went out and snagged an old kernel SRPM for RH72 from the RedHat archives, added one line to the spec file to swap CONFIG_MXT=y with CONFIG_MXT=n in the kernel configs, rebuilt, mounted up the RH72 disk image, chrooted to it, installed my new rpm in place of the existing rpm, fired it up, and voila, it appears to be working. Thanks much for your help, it pointed me in the right direction! -- Dan From riel at redhat.com Fri Jan 26 22:04:49 2007 From: riel at redhat.com (Rik van Riel) Date: Fri, 26 Jan 2007 17:04:49 -0500 Subject: [Fedora-xen] Cannot get xen on RHEL5 to use a RHEL4 repository In-Reply-To: References: Message-ID: <45BA7B01.50607@redhat.com> Frazier, Darrell USA CRC (Contractor) wrote: > > I am running xen on a Dell 2850/ 3.0Ghz/ 12GB RAM/ RHEL5 Beta2 system. I > am attempting to create a rhel4 guest. The paravirtualized Xen kernel, glibc and installer support for RHEL4 will only be released with RHEL 4.5. -- Politics is the struggle between those who want to make their country the best in the world, and those who believe it already is. Each group calls the other unpatriotic. From felix.schwarz at web.de Fri Jan 26 22:42:07 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Fri, 26 Jan 2007 23:42:07 +0100 Subject: [Fedora-xen] HVM guests: Cannot allocate memory Message-ID: <45BA83BF.7010206@web.de> Hi, my Dom0 is running with Fedora Core 6 and overall I would say it works. But I have a problem with HVM guests: I can start them just after system reboot but they won't start after I worked some time. "xm create" just gives me the error message "VmError: (12, 'Cannot allocate memory')". The error does always appear when my "free" memory (as shown by top) is lower than the amount required by my HVM guest. What I do not understand is why Xen is not able to use memory which is used as cache by the Kernel. It is not uncommon for me to have 2-3 GB memory used as cache but only 20-30 MB free. Furthermore I expected that even SWAP can be used for my Xen guest which are another 2 GB. Is there a workaround/bugreport for this behavior? Is there any hope it can be fixed? fs From thomas.vonsteiger at bluewin.ch Sun Jan 28 09:06:05 2007 From: thomas.vonsteiger at bluewin.ch (Thomas von Steiger) Date: Sun, 28 Jan 2007 10:06:05 +0100 Subject: AW: [Fedora-xen] FC6: guest's with link in /etc/xen/auto not startetafter xen update In-Reply-To: <5f0f8dba0701240608h40f413a3jc3f43c27d7c8a68e@mail.gmail.com> Message-ID: <01e301c742bb$8b53a1e0$3201a8c0@athlon> Hi, xend and xendomains are chkconfig on. This was the same settings bevor I have done the update. Bevor I have done the update all guest?s are starting automaticly. I found in /etc/sysconfig/xendomains ?XENDOMAINS_AUTO=/etc/xen/auto?. From this point it looks ok. If I change XENDOMAINS_RESTOR to ?false?, service xendomains start startup all the guest?s. For me it means, ?xm save guest? is not running well on my dom0, becose ?xm restore guest? does not start any guest ? I have now the same effect on two dom0 Hosts. Regards, Thomas _____ Von: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Im Auftrag von Asrai khn Gesendet: Mittwoch, 24. Januar 2007 15:08 An: fedora-xen at redhat.com Betreff: Re: [Fedora-xen] FC6: guest's with link in /etc/xen/auto not startetafter xen update Hi, Are you sture xend and xendomains services running when you start xen dom0? , also before rebooting host shutdown all VMs and see it start it or not. Thanks. Askar On 1/23/07, Thomas von Steiger wrote: Hello, I have updated fc6 to xen-3.0.3-3 and kernel-xen 2.6.19-1.2895 without any problem. After reboot all the guest's with a link in /etc/xen/auto don't start automatically. How I can autostart the guest with this xen releases ? If I try to start the guest's with "xm create rhel41" for example, all the guest's are running without problem. Many Thanks for any Tips, Thomas -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.6/646 - Release Date: 23.01.2007 03:36 -- Fedora-xen mailing list HYPERLINK "mailto:Fedora-xen at redhat.com"Fedora-xen at redhat.com HYPERLINK "https://www.redhat.com/mailman/listinfo/fedora-xen"https://www.redhat.com/m ailman/listinfo/fedora-xen -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.10/651 - Release Date: 24.01.2007 18:48 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.12/654 - Release Date: 27.01.2007 17:02 -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Sun Jan 28 16:50:48 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 28 Jan 2007 16:50:48 +0000 Subject: [Fedora-xen] HVM guests: Cannot allocate memory In-Reply-To: <45BA83BF.7010206@web.de> References: <45BA83BF.7010206@web.de> Message-ID: <20070128165048.GA470@redhat.com> On Fri, Jan 26, 2007 at 11:42:07PM +0100, Felix Schwarz wrote: > Hi, > > my Dom0 is running with Fedora Core 6 and overall I would say it works. But > I have a problem with HVM guests: I can start them just after system reboot > but they won't start after I worked some time. "xm create" just gives me > the error message "VmError: (12, 'Cannot allocate memory')". > > The error does always appear when my "free" memory (as shown by top) is > lower than the amount required by my HVM guest. What I do not understand is > why Xen is not able to use memory which is used as cache by the Kernel. It > is not uncommon for me to have 2-3 GB memory used as cache but only 20-30 > MB free. Furthermore I expected that even SWAP can be used for my Xen guest > which are another 2 GB. Unfortunately the 'Cannot allocate memory' error message is caused by a bug in the Xen 3.0.3 hypervisor for HVM. It has nothing todo with the amount of free memory in either dom0, or the host, and so there's no easy way to avoid it / workaround it. > Is there a workaround/bugreport for this behavior? Is there any hope it can > be fixed? We've been trying a number of ways to fix it - the upstream patch from xen-unstable is too invasive to easily apply to Xen 3.0.3, so we need an alternate approach. Herbert Xu has just yesterday come up with an alternate fix which can be done entirely in the userspace tools which we're trying in the RHEL-5 branch of Xen. If it passes testing, then I'll apply the patch to FC6 Xen as well & push out an updated RPM at the soonest possible opportunity (hopefully within next few days). 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 Sun Jan 28 21:06:32 2007 From: henning_sprang at gmx.de (Henning Sprang) Date: Sun, 28 Jan 2007 22:06:32 +0100 Subject: [Fedora-xen] guest debian on fedora host with virt-manager In-Reply-To: <20070125122515.GD15872@redhat.com> References: <20070125122515.GD15872@redhat.com> Message-ID: <5bb00b3f0701281306l61a85f04r613015a206c50f34@mail.gmail.com> On 1/25/07, Daniel P. Berrange wrote: > Unfortunately the Debian trees are not setup in a way which allows us to do > paravirtualized Xen installs from virt-manager[1]. So for Debian you'll have to > use full-virt instead, or run the Debian bootstrap scripts to manually create > a DomU image. Just for the records, also on this list(same question came to xen-users): one cannot throw just any mirror in any installer and hope it works. Different distributions do not only have a different mirror setup, these two don't even use the same package type. So it's really asking too much to just feed the mirror address in. But I think saying "the debian mirror is not set up right" is a bit short sighted, and has the tendency to sound like "debian is wrong", while one could also argue "virt-manager is not good enough to handle debian" - both are wrong, because from both sides, these things cannot be easily expected - bootstraping is complex. For those who want to bootstrap Debian VMs on Fedora: I was quite successful running debootstrap and xen-tools installed from sources, or with an rpm created with alien, (which is unforunately only available in Debian and SuSE) Still, one problem remains unsolved, it is described in the thread "Getting Debian domU running on fedora with fedora-native packages (works with xensource binaries) " And it basically means, you can create the system image, but with the Fedora Xen packages, it just doesn't boot, while the exact same image runs 100% flawless with Xensource Xen binaries on fedora. > Not much help for your situation, but we're prototyping support for installing > SuSE paravirt guests from virt-manager, now we've identified how their installer > can be booted under Xen. It's quite simply documented in some blog on the net - didn't try it and don't have that link at hand, but I think anyway that running these full fledged manual installers is not really the best way to go. Better look at something simple like debootstrap. For example, yum installs of SuSE on Fedora also work well, the only problem that keeps coming up is that Fedora kernel is incompatible with most other distributions's images - only for SuSE at least it works after some tweaking while the debian problem mentioned above is, at least for me, still unsolved. Henning From felix.schwarz at web.de Sun Jan 28 21:09:53 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Sun, 28 Jan 2007 22:09:53 +0100 Subject: [Fedora-xen] HVM guests: Cannot allocate memory In-Reply-To: <20070128165048.GA470@redhat.com> References: <45BA83BF.7010206@web.de> <20070128165048.GA470@redhat.com> Message-ID: <45BD1121.40707@web.de> Daniel P. Berrange wrote: > Unfortunately the 'Cannot allocate memory' error message is caused by a bug > in the Xen 3.0.3 hypervisor for HVM. It has nothing todo with the amount of > free memory in either dom0, or the host, and so there's no easy way to avoid > it / workaround it. Thank you very much for your detailled answer :-) At least, the problem is already fixed in upstream so I'll get rid of the bug with FC7 at the lastest. fs From henning_sprang at gmx.de Mon Jan 29 12:59:45 2007 From: henning_sprang at gmx.de (Henning Sprang) Date: Mon, 29 Jan 2007 13:59:45 +0100 Subject: [Fedora-xen] NetBSD 3.1 on fc6 xen 3.0.3 In-Reply-To: <45A417EB.6090004@redhat.com> References: <3D053E53-A5D8-47A0-A28D-E3450209742F@ncircle.com> <45A417EB.6090004@redhat.com> Message-ID: <5bb00b3f0701290459q3bd6e835t2e17b7470069ad1e@mail.gmail.com> On 1/9/07, Chris Lalancette wrote: > > 1) You recompile the FC6 kernel and HV to be non-PAE. It's fairly straightforward, but the problem then is that your other FC6 guests won't work (because then you will have non-PAE dom0, but PAE guests). > > 2) Find someone willing to make NetBSD use PAE. > > There are also some bimodal (meaning that both PAE and non-PAE guests would work on a PAE dom0) patches going into upstream Xen, but I'm not sure if we would put those into FC6 (or they would wait for FC7 or later). 3) Use Xen Binaries from XenSource, which provide a selection. 4) Use another distribution as dom0 - SuSE and Debian let you chose if you want PAE or not. This is for sure only a solution when you don't need PAE :) Best solution would be really if the NetBSD team could upload two versions of their kernels, so everybody can use them... I also had this problem, but I remember in one of the logfiles there was actually an error message telling something useful like "non-PAE kernel on PAE host" something like that. Henning From thomas.vonsteiger at bluewin.ch Mon Jan 29 19:40:20 2007 From: thomas.vonsteiger at bluewin.ch (Thomas von Steiger) Date: Mon, 29 Jan 2007 20:40:20 +0100 Subject: AW: [Fedora-xen] FC5/FC6 "xm save...." failed for FV In-Reply-To: <01e301c742bb$8b53a1e0$3201a8c0@athlon> Message-ID: <00b501c743dd$4fffb520$3201a8c0@athlon> Hi all, Can this be true that "xm save..." are not working for fullvirtualisation guests ? Becose "xm migrate..." are not available for fullvirtualisation. Many Thanks Thomas ________________________________________ Von: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Gesendet: Sonntag, 28. Januar 2007 10:06 An: fedora-xen at redhat.com Betreff: AW: [Fedora-xen] FC6: guest's with link in /etc/xen/auto notstartetafter xen update Hi, xend and xendomains are chkconfig on. This was the same settings bevor I have done the update. Bevor I have done the update all guest?s are starting automaticly. I found in /etc/sysconfig/xendomains ?XENDOMAINS_AUTO=/etc/xen/auto?. From this point it looks ok. If I change XENDOMAINS_RESTORE to ?false?, service xendomains start startup all the guest?s. For me it means, ?xm save guest? is not running well on my dom0, becose ?xm restore guest? does not start any guest ? I have now the same effect on two dom0 Hosts. Regards, Thomas ________________________________________ Von: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] Im Auftrag von Asrai khn Gesendet: Mittwoch, 24. Januar 2007 15:08 An: fedora-xen at redhat.com Betreff: Re: [Fedora-xen] FC6: guest's with link in /etc/xen/auto not startetafter xen update Hi, Are you sture xend and xendomains services running when you start xen dom0? , also before rebooting host shutdown all VMs and see it start it or not. Thanks. Askar On 1/23/07, Thomas von Steiger wrote: Hello, I have updated fc6 to xen-3.0.3-3 and kernel-xen 2.6.19-1.2895 without any problem. After reboot all the guest's with a link in /etc/xen/auto don't start automatically. How I can autostart the guest with this xen releases ? If I try to start the guest's with "xm create rhel41" for example, all the guest's are running without problem. Many Thanks for any Tips, Thomas -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.6/646 - Release Date: 23.01.2007 03:36 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.10/651 - Release Date: 24.01.2007 18:48 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.12/655 - Release Date: 28.01.2007 13:12 From berrange at redhat.com Mon Jan 29 19:45:32 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 29 Jan 2007 19:45:32 +0000 Subject: [Fedora-xen] FC5/FC6 "xm save...." failed for FV In-Reply-To: <00b501c743dd$4fffb520$3201a8c0@athlon> References: <01e301c742bb$8b53a1e0$3201a8c0@athlon> <00b501c743dd$4fffb520$3201a8c0@athlon> Message-ID: <20070129194532.GM21100@redhat.com> On Mon, Jan 29, 2007 at 08:40:20PM +0100, Thomas von Steiger wrote: > Hi all, > > Can this be true that "xm save..." are not working for fullvirtualisation > guests ? > Becose "xm migrate..." are not available for fullvirtualisation. Correct - there is no support for save/restore/migrate for any fullvirt HVM guests. Upstream xen project is working on this, but don't expect to see if available anytime in the near future - xen 3.0.5 at the earliest. 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 naoki at valuecommerce.com Tue Jan 30 03:16:37 2007 From: naoki at valuecommerce.com (Naoki) Date: Tue, 30 Jan 2007 12:16:37 +0900 Subject: [Fedora-xen] Broadcom Ethernet interface broken under kernel-xen (module issue?) Message-ID: <1170126997.3289.170.camel@dragon.valuecommerce.ne.jp> I just noticed this (and I think reported in fedora-devel) that under a new FC6 install using kernel-xen-2.6.18-1.2798.fc6 the 'eth0' device would DHCP and obtain an IP address, but then would be unable to ping even the default route, and would not respond to 'ethtool' commands, only stating "Link: Yes". 'mii-tool' just barfs saying "Operation not supported". Problem also seems to be in kernel-xen-2.6.19-1.2895.fc6 although I have some problems blocking testing there. I have seen this on an IBM server and a Dell desktop, both using Broadcom adaptors. Sounds to be the same issues as http://lists.xensource.com/archives/html/xen-users/2006-07/msg00599.html http://lists.xensource.com/archives/html/xen-users/2006-08/msg00553.html Working (until IRQ bug kills it) 2.6.19-1.2895.fc6 alias eth0 tg3 # lspci |grep -i eth 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01) Working 2.6.18-1.2798.fc6 alias eth0 bnx2 # lspci |grep -i eth 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) 06:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) And this BZ looks like the same problem, I'll add my info there unless anybody tells me I'm on the wrong track.. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213991 From schwier at rvs.uni-hannover.de Tue Jan 30 12:37:39 2007 From: schwier at rvs.uni-hannover.de (Harald Schwier) Date: Tue, 30 Jan 2007 13:37:39 +0100 Subject: [Fedora-xen] Poor Network Performance between dom-0 and dom-u Message-ID: <45BF3C13.7020707@rvs.uni-hannover.de> Hi, i have problems concerning the network performance between dom-0 and a dom-u host. Messurement using iperf show [ 4] 1.0- 2.0 sec 7.85 MBytes 65.8 Mbits/sec Network performance between dom-0 and an external maschine shows gigabit speed. [ 5] 0.0- 1.0 sec 112 MBytes 938 Mbits/sec i am using Fedora core 6 on the dom-0 host and redhat 4.4 on the dom-u guest. Dom-u is fully virtualized. (Dual Xeon 5150 2.66GHz.) Any hints that could help to improve the performance are greatly appreciated. -- Harald From jprats at cesca.es Tue Jan 30 21:28:32 2007 From: jprats at cesca.es (Jordi Prats) Date: Tue, 30 Jan 2007 22:28:32 +0100 Subject: [Fedora-xen] destroydevice Message-ID: <45BFB880.1060409@cesca.es> Hi, It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm tool: creating a new VM it aborts showing this error: [root at inf16 ~]# xm create /etc/xen/rata.cfg Using config file "/etc/xen/rata.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given) [root at inf16 ~]# Anyone knows what is causing this? On the xen-users list there's some other messages related to this isue (one mine). Mats Petersson say that this may be causes by a backport. There's something broken on the package? There's any easy workarround? Thank you, -- ...................................................................... __ / / Jordi Prats Catal? C E / S / C A Departament de Sistemes /_/ Centre de Supercomputaci? de Catalunya Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es ...................................................................... pgp:0x5D0D1321 ...................................................................... From berrange at redhat.com Tue Jan 30 21:36:52 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 30 Jan 2007 21:36:52 +0000 Subject: [Fedora-xen] destroydevice In-Reply-To: <45BFB880.1060409@cesca.es> References: <45BFB880.1060409@cesca.es> Message-ID: <20070130213652.GN18642@redhat.com> On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote: > Hi, > It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm > tool: creating a new VM it aborts showing this error: > > [root at inf16 ~]# xm create /etc/xen/rata.cfg > Using config file "/etc/xen/rata.cfg". > Error: destroyDevice() takes exactly 3 arguments (2 given) > [root at inf16 ~]# > > Anyone knows what is causing this? On the xen-users list there's some > other messages related to this isue (one mine). Mats Petersson say that > this may be causes by a backport. Its a bug in one of the other patches we applied to the Xen RPM. I'll fix it in the next release. > There's something broken on the package? There's any easy workarround? The error above isn't actually the root cause of your problems. What's happened is that the hotplug scripts for your domain failed to complete for some reason. Then when XenD is cleaning up from that failure, we hit the bug above. So wrt to debugging your actual problems, ignore the error message above. Instead look for a mis-configuration in either your virtual network card or virtual disk config params. 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 jprats at cesca.es Tue Jan 30 22:04:45 2007 From: jprats at cesca.es (Jordi Prats) Date: Tue, 30 Jan 2007 23:04:45 +0100 Subject: [Fedora-xen] destroydevice In-Reply-To: <20070130213652.GN18642@redhat.com> References: <45BFB880.1060409@cesca.es> <20070130213652.GN18642@redhat.com> Message-ID: <45BFC0FD.3060503@cesca.es> Ok, thank you! How long will take for the next release? On the other hand, I can't ignore that error because I can't create any virtual machine, so Xen does nothing. On redhat 5 b2 it happens the same. I've changed my servers to FC6 because of this. Daniel P. Berrange wrote: > On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote: >> Hi, >> It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm >> tool: creating a new VM it aborts showing this error: >> >> [root at inf16 ~]# xm create /etc/xen/rata.cfg >> Using config file "/etc/xen/rata.cfg". >> Error: destroyDevice() takes exactly 3 arguments (2 given) >> [root at inf16 ~]# >> >> Anyone knows what is causing this? On the xen-users list there's some >> other messages related to this isue (one mine). Mats Petersson say that >> this may be causes by a backport. > > Its a bug in one of the other patches we applied to the Xen RPM. I'll fix > it in the next release. > >> There's something broken on the package? There's any easy workarround? > > The error above isn't actually the root cause of your problems. What's > happened is that the hotplug scripts for your domain failed to complete > for some reason. Then when XenD is cleaning up from that failure, we > hit the bug above. So wrt to debugging your actual problems, ignore the > error message above. Instead look for a mis-configuration in either your > virtual network card or virtual disk config params. > > Regards, > Dan. -- ...................................................................... __ / / Jordi Prats Catal? C E / S / C A Departament de Sistemes /_/ Centre de Supercomputaci? de Catalunya Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es ...................................................................... pgp:0x5D0D1321 ...................................................................... From berrange at redhat.com Tue Jan 30 22:05:39 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 30 Jan 2007 22:05:39 +0000 Subject: [Fedora-xen] destroydevice In-Reply-To: <45BFC0FD.3060503@cesca.es> References: <45BFB880.1060409@cesca.es> <20070130213652.GN18642@redhat.com> <45BFC0FD.3060503@cesca.es> Message-ID: <20070130220539.GP18642@redhat.com> On Tue, Jan 30, 2007 at 11:04:45PM +0100, Jordi Prats wrote: > Ok, thank you! > > How long will take for the next release? Probably a few days before it goes to updates-testing, so don't expect it to go to updates for at least a week > On the other hand, I can't ignore that error because I can't create any > virtual machine, so Xen does nothing. On redhat 5 b2 it happens the > same. I've changed my servers to FC6 because of this. Urm - read my explanation below again.... The 'Error: destroyDevice() takes exactly 3 arguments (2 given)' problem is *NOT* what is causing your guest to fail. It is merely obscuring the underlying failure - an updated RPM will remove up the 'destroyDevice' misleading message, but it won't magically make your guest work again. The fundamental problem is a configuration issue with your guest's virtual disk or networking. Once you fix the config problem, the guest will work just fine, with or without an updated RPM for the 'destroyDevice' issue > Daniel P. Berrange wrote: > > On Tue, Jan 30, 2007 at 10:28:32PM +0100, Jordi Prats wrote: > >> Hi, > >> It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm > >> tool: creating a new VM it aborts showing this error: > >> > >> [root at inf16 ~]# xm create /etc/xen/rata.cfg > >> Using config file "/etc/xen/rata.cfg". > >> Error: destroyDevice() takes exactly 3 arguments (2 given) > >> [root at inf16 ~]# > >> > >> Anyone knows what is causing this? On the xen-users list there's some > >> other messages related to this isue (one mine). Mats Petersson say that > >> this may be causes by a backport. > > > > Its a bug in one of the other patches we applied to the Xen RPM. I'll fix > > it in the next release. > > > >> There's something broken on the package? There's any easy workarround? > > > > The error above isn't actually the root cause of your problems. What's > > happened is that the hotplug scripts for your domain failed to complete > > for some reason. Then when XenD is cleaning up from that failure, we > > hit the bug above. So wrt to debugging your actual problems, ignore the > > error message above. Instead look for a mis-configuration in either your > > virtual network card or virtual disk config params. 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 ligesh at lxlabs.com Wed Jan 31 13:58:25 2007 From: ligesh at lxlabs.com (Ligesh) Date: Wed, 31 Jan 2007 19:28:25 +0530 Subject: [Fedora-xen] DomU boot on Fedora 6 fails with 'no root found' error. Message-ID: <20070131135825.GA7179@lxlabs.com> I am trying to get Xen running on Fedora 6, which I thought would be easy, but I guess not. I am using the standard image from jailtime.org and my domU configuration file is below. I am using the same kernel of the host itself. ------------ kernel = '/boot/vmlinuz-2.6.19-1.2895.fc6xen' ramdisk = '/boot/initrd-2.6.19-1.2895.fc6xen.img' memory = 512 name = 'test.vm' vif = ['vifname=vif-test0, mac=aa:00:f6:f4:06:1a'] vnc = 0 vncviewer = 0 serial = 'pty' disk = ['file:/home/test.vm//root.img,sda1,w', 'file:/home/test.vm//vm.swap,sda2,w'] root = '/dev/sda1 ro' ------------------ ------------------- Loading dm-zero.ko module Loading dm-snapshot.ko module Making device-mapper control node Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! -------------------------- The above is the error I got. It seems the initrd is searching for volGroup00, which is how the '/' of the HOST is mounted, but I have explicitly given 'root =' in the config file. So I am confused. Is there anyone here who has experienced this beforehand? Thanks in advance. From berrange at redhat.com Wed Jan 31 14:01:20 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 31 Jan 2007 14:01:20 +0000 Subject: [Fedora-xen] DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131135825.GA7179@lxlabs.com> References: <20070131135825.GA7179@lxlabs.com> Message-ID: <20070131140120.GB9168@redhat.com> On Wed, Jan 31, 2007 at 07:28:25PM +0530, Ligesh wrote: > > I am trying to get Xen running on Fedora 6, which I thought would be easy, but I guess not. I am using the standard image from jailtime.org and my domU configuration file is below. I am using the same kernel of the host itself. > > ------------ > kernel = '/boot/vmlinuz-2.6.19-1.2895.fc6xen' > ramdisk = '/boot/initrd-2.6.19-1.2895.fc6xen.img' > memory = 512 > name = 'test.vm' > vif = ['vifname=vif-test0, mac=aa:00:f6:f4:06:1a'] > vnc = 0 > vncviewer = 0 > serial = 'pty' > disk = ['file:/home/test.vm//root.img,sda1,w', 'file:/home/test.vm//vm.swap,sda2,w'] > root = '/dev/sda1 ro' > ------------------ Xen filesystem images should be kept in /xen (legacy location) or /var/lib/xen/images (recommended location) otherwise SELinux will deny the VM access to the files & the guest will be unable to mount its filesystem. I suspect this could be what's causing your VM to not find its root filesystem. > Volume group "VolGroup00" not found > mount: could not find filesystem '/dev/root' 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 sakaia at jp.fujitsu.com Wed Jan 31 14:12:10 2007 From: sakaia at jp.fujitsu.com (Atsushi SAKAI) Date: Wed, 31 Jan 2007 23:12:10 +0900 Subject: [Fedora-xen] DomU boot on Fedora 6 fails with 'no root found'error. In-Reply-To: <20070131140120.GB9168@redhat.com> References: <20070131140120.GB9168@redhat.com> Message-ID: <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> Hi,?Dan ?It seems to be initrd is not configured for DomU. Is my guess wrong? or currently initrd is shared by domU and Dom0 on FC6? Thanks Atsushi Sakai "Daniel P. Berrange" wrote: > On Wed, Jan 31, 2007 at 07:28:25PM +0530, Ligesh wrote: > > > > I am trying to get Xen running on Fedora 6, which I thought would be easy, but I guess not. I am using the standard image from jailtime.org and my domU configuration file is below. I am using the same kernel of the host itself. > > > > ------------ > > kernel = '/boot/vmlinuz-2.6.19-1.2895.fc6xen' > > ramdisk = '/boot/initrd-2.6.19-1.2895.fc6xen.img' > > memory = 512 > > name = 'test.vm' > > vif = ['vifname=vif-test0, mac=aa:00:f6:f4:06:1a'] > > vnc = 0 > > vncviewer = 0 > > serial = 'pty' > > disk = ['file:/home/test.vm//root.img,sda1,w', 'file:/home/test.vm//vm.swap,sda2,w'] > > root = '/dev/sda1 ro' > > ------------------ > > Xen filesystem images should be kept in /xen (legacy location) or > /var/lib/xen/images (recommended location) otherwise SELinux will > deny the VM access to the files & the guest will be unable to > mount its filesystem. I suspect this could be what's causing your > VM to not find its root filesystem. > > > Volume group "VolGroup00" not found > > mount: could not find filesystem '/dev/root' > > > > 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 -=| > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From ligesh at lxlabs.com Wed Jan 31 14:20:54 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Wed, 31 Jan 2007 19:50:54 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found'error. In-Reply-To: <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> References: <20070131140120.GB9168@redhat.com> <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> Message-ID: <20070131142054.GA7434@lxlabs.com> On Wed, Jan 31, 2007 at 11:12:10PM +0900, Atsushi SAKAI wrote: > Hi,?$B!!Dan > > ?$B!!It seems to be initrd is not configured for DomU. > Is my guess wrong? > or currently initrd is shared by domU and Dom0 on FC6? > Yes, I think that's the issue. Do you need separate initrds for each ostemplate? How do I create an initrd for a specific template? Does the initrd contain the fstab info? Thanks a lot. From ligesh at lxlabs.com Wed Jan 31 14:21:36 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Wed, 31 Jan 2007 19:51:36 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131140120.GB9168@redhat.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> Message-ID: <20070131142136.GB7434@lxlabs.com> On Wed, Jan 31, 2007 at 02:01:20PM +0000, Daniel P. Berrange wrote: > On Wed, Jan 31, 2007 at 07:28:25PM +0530, Ligesh wrote: > > Xen filesystem images should be kept in /xen (legacy location) or > /var/lib/xen/images (recommended location) otherwise SELinux will > deny the VM access to the files & the guest will be unable to > mount its filesystem. I suspect this could be what's causing your > VM to not find its root filesystem. > I did a setenforce 0 and tried again but got the same error. Shouldn't that be enough to disable selinux? Thanks. From ligesh at lxlabs.com Wed Jan 31 14:35:36 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Wed, 31 Jan 2007 20:05:36 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found'error. In-Reply-To: <20070131142054.GA7434@lxlabs.com> References: <20070131140120.GB9168@redhat.com> <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> <20070131142054.GA7434@lxlabs.com> Message-ID: <20070131143536.GA7844@lxlabs.com> I found the problem. It is with the initrd. It contains the 'init' program which seems to be trying to use LVM to do everything because host is configured on LVM, and since the guest doesn't have lvm configured it fails. So from where do I get a simple initrd image, that will not attempt to do acrobatics with the lvm? Thanks. From ligesh at lxlabs.com Wed Jan 31 14:40:52 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Wed, 31 Jan 2007 20:10:52 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found'error. In-Reply-To: <20070131143536.GA7844@lxlabs.com> References: <20070131140120.GB9168@redhat.com> <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> <20070131142054.GA7434@lxlabs.com> <20070131143536.GA7844@lxlabs.com> Message-ID: <20070131144052.GA7997@lxlabs.com> I would say that the fedora xen is broken, since I don't think we can use it easily to create a domU using pre-built templates. The initrd for the xen kernel seems to be built to use features that are not at all available on the domU, and there are no simple initrds available either. This is on 32 bit. On 64 bit, the initrd fails to even recognize the xen vbd devices and fails miserably. Is there a tutorial on how to create domUs using pre-built templates from jailtime.org? Thanks. From master at bradleyland.com Wed Jan 31 14:54:34 2007 From: master at bradleyland.com (master at bradleyland.com) Date: Wed, 31 Jan 2007 06:54:34 -0800 (PST) Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found'error. In-Reply-To: <20070131144052.GA7997@lxlabs.com> References: <20070131140120.GB9168@redhat.com> <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> <20070131142054.GA7434@lxlabs.com> <20070131143536.GA7844@lxlabs.com> <20070131144052.GA7997@lxlabs.com> Message-ID: <4144.192.168.2.92.1170255274.squirrel@www.bradleyland.com> I would agree it's broken as I've also been unable to get guests to work "out of the box". I've found the problem to be a missing kernel module in the initrd, required for disk access (xenblk.ko). If I build an initrd with xenblk.ko included, guests boot fine. I just make an initrd this command: mkinitrd --with=xenblk.ko /boot/your_image_name.img your_kernelname Just use the kernel name from uname -a mkinitrd --with=xenblk.ko /boot/initrd_test.img 2.6.19-prepcifs_fix From ligesh at lxlabs.com Wed Jan 31 15:43:35 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Wed, 31 Jan 2007 21:13:35 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found'error. In-Reply-To: <4144.192.168.2.92.1170255274.squirrel@www.bradleyland.com> References: <20070131140120.GB9168@redhat.com> <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> <20070131142054.GA7434@lxlabs.com> <20070131143536.GA7844@lxlabs.com> <20070131144052.GA7997@lxlabs.com> <4144.192.168.2.92.1170255274.squirrel@www.bradleyland.com> Message-ID: <20070131154335.GA9499@lxlabs.com> On Wed, Jan 31, 2007 at 06:54:34AM -0800, master at bradleyland.com wrote: > I would agree it's broken as I've also been unable to get guests to work > "out of the box". I've found the problem to be a missing kernel module in > the initrd, required for disk access (xenblk.ko). If I build an initrd > with xenblk.ko included, guests boot fine. > > I just make an initrd this command: > > mkinitrd --with=xenblk.ko /boot/your_image_name.img your_kernelname > > Just use the kernel name from uname -a > > mkinitrd --with=xenblk.ko /boot/initrd_test.img 2.6.19-prepcifs_fix Thanks, but my problem is that the 'init' inside the initrd is runing lvm commands, probably because it was built on a host that has LVM, and I need to remove these lvm commands from the init inside the initrd. How do I do that? Your above solution would have solved my problem yesterday when I ran into this, but now I have reimaged the server using LVM, and I am facing yet another problem. thanks. From ligesh at lxlabs.com Wed Jan 31 16:27:27 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Wed, 31 Jan 2007 21:57:27 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found'error. In-Reply-To: <20070131154335.GA9499@lxlabs.com> References: <20070131140120.GB9168@redhat.com> <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> <20070131142054.GA7434@lxlabs.com> <20070131143536.GA7844@lxlabs.com> <20070131144052.GA7997@lxlabs.com> <4144.192.168.2.92.1170255274.squirrel@www.bradleyland.com> <20070131154335.GA9499@lxlabs.com> Message-ID: <20070131162727.GA11443@lxlabs.com> On Wed, Jan 31, 2007 at 09:13:35PM +0530, K T Ligesh wrote: > On Wed, Jan 31, 2007 at 06:54:34AM -0800, master at bradleyland.com wrote: > > I would agree it's broken as I've also been unable to get guests to work > > "out of the box". I've found the problem to be a missing kernel module in > > the initrd, required for disk access (xenblk.ko). If I build an initrd > > with xenblk.ko included, guests boot fine. > > > > I just make an initrd this command: > > > > mkinitrd --with=xenblk.ko /boot/your_image_name.img your_kernelname > > > > Just use the kernel name from uname -a > > > > mkinitrd --with=xenblk.ko /boot/initrd_test.img 2.6.19-prepcifs_fix > This is the actual error, the LVM errors turned out to be a red herring. --------- XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 -------- You were actually right. It appears the LVm errors were non-critical and the critical error is the lack of xen device drivers in the kernel or the initrd. I tried with --with=xenblk.ko, but didn't work. I will try once more and report back. Thanks for the solution. From davidsen at tmr.com Wed Jan 31 18:40:58 2007 From: davidsen at tmr.com (Bill Davidsen) Date: Wed, 31 Jan 2007 13:40:58 -0500 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131142136.GB7434@lxlabs.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> Message-ID: <45C0E2BA.8000605@tmr.com> K T Ligesh wrote: > On Wed, Jan 31, 2007 at 02:01:20PM +0000, Daniel P. Berrange wrote: > >> On Wed, Jan 31, 2007 at 07:28:25PM +0530, Ligesh wrote: >> >> Xen filesystem images should be kept in /xen (legacy location) or >> /var/lib/xen/images (recommended location) otherwise SELinux will >> deny the VM access to the files & the guest will be unable to >> mount its filesystem. I suspect this could be what's causing your >> VM to not find its root filesystem. >> >> > > I did a setenforce 0 and tried again but got the same error. Shouldn't that be enough to disable selinux? > > And at some point will xen and selinux be compatible? I have everything in the "right" place, but it still doesn't work. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979 From berrange at redhat.com Wed Jan 31 18:44:44 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 31 Jan 2007 18:44:44 +0000 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <45C0E2BA.8000605@tmr.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> Message-ID: <20070131184444.GC9956@redhat.com> On Wed, Jan 31, 2007 at 01:40:58PM -0500, Bill Davidsen wrote: > K T Ligesh wrote: > >On Wed, Jan 31, 2007 at 02:01:20PM +0000, Daniel P. Berrange wrote: > > > >>On Wed, Jan 31, 2007 at 07:28:25PM +0530, Ligesh wrote: > >> > >>Xen filesystem images should be kept in /xen (legacy location) or > >>/var/lib/xen/images (recommended location) otherwise SELinux will > >>deny the VM access to the files & the guest will be unable to > >>mount its filesystem. I suspect this could be what's causing your > >>VM to not find its root filesystem. > >> > >> > > > > I did a setenforce 0 and tried again but got the same error. Shouldn't > > that be enough to disable selinux? > > > > > > And at some point will xen and selinux be compatible? I have everything > in the "right" place, but it still doesn't work. Xen is already SELinux compatible if you have images in /var/lib/xen/images If it is still not working, then it is most likely not an SELinux problem. If it was, then you would see AVC denials in the system/audit logs describing the problem 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 ligesh at lxlabs.com Wed Jan 31 18:46:15 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Thu, 1 Feb 2007 00:16:15 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <45C0E2BA.8000605@tmr.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> Message-ID: <20070131184615.GA23327@lxlabs.com> On Wed, Jan 31, 2007 at 01:40:58PM -0500, Bill Davidsen wrote: > > And at some point will xen and selinux be compatible? I have everything > in the "right" place, but it still doesn't work. > Forget selinux. Just disable it. I mean, you think of security only after the bleeding stops, your wounds have healed. (The bleeding that comes from banging your head on the keyboard in frustration). Since this is xen only mailinglist, I think we can talk about the situation with selinux disabled. Anyway, won't a setenforce 0, completely disable the damn thing? At least it says so as the output of the command. Thanks. From ligesh at lxlabs.com Wed Jan 31 18:52:28 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Thu, 1 Feb 2007 00:22:28 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131184444.GC9956@redhat.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184444.GC9956@redhat.com> Message-ID: <20070131185228.GA23660@lxlabs.com> mkinitrd has a major issue. It doesn't give error if the module we specify in the --with= doesn't exist. I gave mkintrd --with=gobble.kkk and it accepted it very happily and proceeded to create a initrd. What kind of initrd does this create? In fact, the initrd has no error checking whatsoever. The problem is that the xenblk.ko is not there in the initrd. It should actually be compiled into the kernel, at least the xen kernel. And I am completely confused why it isn't done so. Anyway, is there any place I can get a sane xen kernel for fc6? I checked the xensource, but they have it only for fc5. Thanks. From ligesh at lxlabs.com Wed Jan 31 18:57:40 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Thu, 1 Feb 2007 00:27:40 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found'error. In-Reply-To: <4144.192.168.2.92.1170255274.squirrel@www.bradleyland.com> References: <20070131140120.GB9168@redhat.com> <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> <20070131142054.GA7434@lxlabs.com> <20070131143536.GA7844@lxlabs.com> <20070131144052.GA7997@lxlabs.com> <4144.192.168.2.92.1170255274.squirrel@www.bradleyland.com> Message-ID: <20070131185740.GB23660@lxlabs.com> On Wed, Jan 31, 2007 at 06:54:34AM -0800, master at bradleyland.com wrote: > I would agree it's broken as I've also been unable to get guests to work > "out of the box". I've found the problem to be a missing kernel module in > the initrd, required for disk access (xenblk.ko). If I build an initrd > with xenblk.ko included, guests boot fine. > > I just make an initrd this command: > > mkinitrd --with=xenblk.ko /boot/your_image_name.img your_kernelname > > Just use the kernel name from uname -a > > mkinitrd --with=xenblk.ko /boot/initrd_test.img 2.6.19-prepcifs_fix Did you get an image from jailtime.org work with the default fedora 2.6.19 kernel and custom initrd? Then you are my hero. Could you be a bit more specific? Did you use the fedora default 2.6.19-1.2895.fc6xen kernel? Thanks. From berrange at redhat.com Wed Jan 31 19:01:50 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 31 Jan 2007 19:01:50 +0000 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131185228.GA23660@lxlabs.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184444.GC9956@redhat.com> <20070131185228.GA23660@lxlabs.com> Message-ID: <20070131190150.GD9956@redhat.com> On Thu, Feb 01, 2007 at 12:22:28AM +0530, K T Ligesh wrote: > > mkinitrd has a major issue. It doesn't give error if the module we > specify in the --with= doesn't exist. I gave mkintrd --with=gobble.kkk > and it accepted it very happily and proceeded to create a initrd. > What kind of initrd does this create? In fact, the initrd has no error > checking whatsoever. The problem is that the xenblk.ko is not there > in the initrd. It should actually be compiled into the kernel, at > least the xen kernel. And I am completely confused why it isn't done so. The xenblk driver is perfectly capable of living as a kernel module. All standard FC6 guest installs will have an initrd with xenblk as a module # cd /tmp # mkdir initrd # cd initrd # gunzip -c < /boot/initrd-2.6.18-1.2849.1dan2tbxen.img | cpio -idmv # find | grep xenblk ./lib/xenblk.ko 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 ligesh at lxlabs.com Wed Jan 31 19:19:28 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Thu, 1 Feb 2007 00:49:28 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131190150.GD9956@redhat.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184444.GC9956@redhat.com> <20070131185228.GA23660@lxlabs.com> <20070131190150.GD9956@redhat.com> Message-ID: <20070131191928.GA24206@lxlabs.com> On Wed, Jan 31, 2007 at 07:01:50PM +0000, Daniel P. Berrange wrote: > On Thu, Feb 01, 2007 at 12:22:28AM +0530, K T Ligesh wrote: > > # cd /tmp > # mkdir initrd > # cd initrd > # gunzip -c < /boot/initrd-2.6.18-1.2849.1dan2tbxen.img | cpio -idmv > # find | grep xenblk > ./lib/xenblk.ko > Nah. Its not there. This is the content of the initrd that comes with fedora. What you forget is that initrd seems to generated on the fly, because that's the only way it could have had all those silly lvm commands. So that's the basic issue. Fedora generates initrd dynamically, and that has no xenblk.ko inside. Let me see if the ones I have manually created have them. ----------------------------- bin bin/lvm bin/insmod bin/modprobe bin/nash etc etc/lvm etc/lvm/lvm.conf lib lib/dm-mod.ko lib/scsi_mod.ko lib/sd_mod.ko lib/dm-snapshot.ko lib/ehci-hcd.ko lib/ohci-hcd.ko lib/dm-mirror.ko lib/dm-zero.ko lib/jbd.ko lib/uhci-hcd.ko lib/sata_nv.ko lib/libata.ko lib/ext3.ko ------------------------------------ From ligesh at lxlabs.com Wed Jan 31 19:22:44 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Thu, 1 Feb 2007 00:52:44 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131191928.GA24206@lxlabs.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184444.GC9956@redhat.com> <20070131185228.GA23660@lxlabs.com> <20070131190150.GD9956@redhat.com> <20070131191928.GA24206@lxlabs.com> Message-ID: <20070131192244.GB24206@lxlabs.com> Ok, I zeroed in on my problem. Even with --with=xenblk.ko, mkinitrd is not adding the xenblk.ko to the initrd. And since mkinitrd seems to be lacking in any error messages, I have no clue what the heck is happening there either. The xenblk.ko is present on the host lib/modules though. I verified that. So anyway, the issue is with mkinitrd and its inability to add xenblk.ko to the initrd. Any suggestions? Thanks. From ligesh at lxlabs.com Wed Jan 31 19:23:55 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Thu, 1 Feb 2007 00:53:55 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131192244.GB24206@lxlabs.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184444.GC9956@redhat.com> <20070131185228.GA23660@lxlabs.com> <20070131190150.GD9956@redhat.com> <20070131191928.GA24206@lxlabs.com> <20070131192244.GB24206@lxlabs.com> Message-ID: <20070131192355.GC24206@lxlabs.com> Ah, maybe I shouldn't give the .ko? So it should be --with=xenblk? Thanks. From ligesh at lxlabs.com Wed Jan 31 19:27:11 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Thu, 1 Feb 2007 00:57:11 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131192355.GC24206@lxlabs.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184444.GC9956@redhat.com> <20070131185228.GA23660@lxlabs.com> <20070131190150.GD9956@redhat.com> <20070131191928.GA24206@lxlabs.com> <20070131192244.GB24206@lxlabs.com> <20070131192355.GC24206@lxlabs.com> Message-ID: <20070131192711.GA24445@lxlabs.com> On Thu, Feb 01, 2007 at 12:53:55AM +0530, K T Ligesh wrote: > Ah, maybe I shouldn't give the .ko? > > So it should be --with=xenblk? > > Thanks. Yeah, that was the issue. You have to use xenblk and not xenblk.ko. SO that solved the first part. I got the xenblk into the initrd.img which I think solves the major issue, but all is still not well. I am getting this error now. ---------------- insmod: error inserting '/lib/dm-snapshot.ko': -1 Required key not available Loading xenblk.ko module ksign: module signed with unknown public key - signature keyid: 8bdc589434dbc709 ver=3 Module signed with unknown public key =-------------------- Any ideas? Thanks. From ligesh at lxlabs.com Wed Jan 31 19:29:38 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Thu, 1 Feb 2007 00:59:38 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found'error. In-Reply-To: <4144.192.168.2.92.1170255274.squirrel@www.bradleyland.com> References: <20070131140120.GB9168@redhat.com> <200701311412.l0VECG8t024226@fjmscan501.ms.jp.fujitsu.com> <20070131142054.GA7434@lxlabs.com> <20070131143536.GA7844@lxlabs.com> <20070131144052.GA7997@lxlabs.com> <4144.192.168.2.92.1170255274.squirrel@www.bradleyland.com> Message-ID: <20070131192938.GB24445@lxlabs.com> On Wed, Jan 31, 2007 at 06:54:34AM -0800, master at bradleyland.com wrote: > > mkinitrd --with=xenblk.ko /boot/your_image_name.img your_kernelname This is actually not correct, and mkinitrd will fail silently and will not give any error, leading to lot confusion. The actual command is: mkinitrd --with=xenblk /boot/img.name kernel-version And actually this works, but I am stuck due to some other error. Thanks a lot. From davidsen at tmr.com Wed Jan 31 20:39:08 2007 From: davidsen at tmr.com (Bill Davidsen) Date: Wed, 31 Jan 2007 15:39:08 -0500 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <20070131184615.GA23327@lxlabs.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184615.GA23327@lxlabs.com> Message-ID: <45C0FE6C.9060102@tmr.com> K T Ligesh wrote: > On Wed, Jan 31, 2007 at 01:40:58PM -0500, Bill Davidsen wrote: > >> And at some point will xen and selinux be compatible? I have everything >> in the "right" place, but it still doesn't work. >> >> > > Forget selinux. Just disable it. I mean, you think of security only after the bleeding stops, your wounds have healed. (The bleeding that comes from banging your head on the keyboard in frustration). Since this is xen only mailinglist, I think we can talk about the situation with selinux disabled. > I bet you have the same eye-level bloody dent in your wall that I do ;-) > Anyway, won't a setenforce 0, completely disable the damn thing? At least it says so as the output of the command. That's true, but I regard "turn off security" in the same light as "run setuid root so you bypass all that permissions stuff." And at least some of the places I could use this require selinux. setenforce doesn't disable it, just sets it advisory, which means it still fails and tells you there's no such file as when there is, just where it should be. Daniel keeps telling me it works for him, so it's some failure of understanding. I'll write a detailed post later with exactly my xen experiences, right now I have to test and evaluate kvm for someone. I will test with selinux if it works without. There isn't a kvm list yet, but I won't burden this list with off-topic posts. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979 From berrange at redhat.com Wed Jan 31 20:42:57 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 31 Jan 2007 20:42:57 +0000 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <45C0FE6C.9060102@tmr.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184615.GA23327@lxlabs.com> <45C0FE6C.9060102@tmr.com> Message-ID: <20070131204257.GG9956@redhat.com> On Wed, Jan 31, 2007 at 03:39:08PM -0500, Bill Davidsen wrote: > K T Ligesh wrote: > >On Wed, Jan 31, 2007 at 01:40:58PM -0500, Bill Davidsen wrote: > > > >>And at some point will xen and selinux be compatible? I have everything > >>in the "right" place, but it still doesn't work. > >> > >> > > > > Forget selinux. Just disable it. I mean, you think of security only after > > the bleeding stops, your wounds have healed. (The bleeding that comes > > from banging your head on the keyboard in frustration). Since this is xen > > only mailinglist, I think we can talk about the situation with selinux > > disabled. > I bet you have the same eye-level bloody dent in your wall that I do ;-) > > Anyway, won't a setenforce 0, completely disable the damn thing? At least > > it says so as the output of the command. > > That's true, but I regard "turn off security" in the same light as "run > setuid root so you bypass all that permissions stuff." And at least some > of the places I could use this require selinux. setenforce doesn't > disable it, just sets it advisory, which means it still fails and tells > you there's no such file as when there is, just where it > should be. Daniel keeps telling me it works for him, so it's some > failure of understanding. If you see 'AVC' denial messages in /var/log/messages or /var/log/audit/audit.log when creating your Xen guest, do file them in BugZilla against Xen. If it does turn out to be a SELinux policy problem, we can usually get very fast turn around on policy updates, because as you say - being able to run with SELinux enabled is a very valuable security measure. 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 davidsen at tmr.com Wed Jan 31 20:43:54 2007 From: davidsen at tmr.com (Bill Davidsen) Date: Wed, 31 Jan 2007 15:43:54 -0500 Subject: [Fedora-xen] xm list broken in xen 3.0.3-3 In-Reply-To: <20070122172640.GH7153@redhat.com> References: <20070119064808.GA5407@nwlink.com> <5f0f8dba0701210820v113e0004k8636223f4891dc4c@mail.gmail.com> <20070121204950.GA16518@nwlink.com> <6.0.0.22.2.20070122111407.028eb370@pop.ncsa.uiuc.edu> <20070122172640.GH7153@redhat.com> Message-ID: <45C0FF8A.2040208@tmr.com> Daniel P. Berrange wrote: > On Mon, Jan 22, 2007 at 11:18:16AM -0600, Mike Freemon wrote: > >> When upgrading from xen-3.0.3-2 to xen-3.0.3-3, the xm list command breaks >> with the following error: >> > Its a new function actually - previous 'xm list' just reported what you'd > told XenD to give the guest - this was not the same as what the guest was > actually allocated by the HV. The new getSysMem function is used to make > xm list show the correct (actual) allocation > Dan, thanks much for the reason behind the solution. "Just reboot" is so Windows, it's nice to understand why in this case it really is needed. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979 From ligesh at lxlabs.com Wed Jan 31 21:05:15 2007 From: ligesh at lxlabs.com (K T Ligesh) Date: Thu, 1 Feb 2007 02:35:15 +0530 Subject: [Fedora-xen] Re: DomU boot on Fedora 6 fails with 'no root found' error. In-Reply-To: <45C0FE6C.9060102@tmr.com> References: <20070131135825.GA7179@lxlabs.com> <20070131140120.GB9168@redhat.com> <20070131142136.GB7434@lxlabs.com> <45C0E2BA.8000605@tmr.com> <20070131184615.GA23327@lxlabs.com> <45C0FE6C.9060102@tmr.com> Message-ID: <20070131210515.GA6605@lxlabs.com> On Wed, Jan 31, 2007 at 03:39:08PM -0500, Bill Davidsen wrote: > K T Ligesh wrote: > >On Wed, Jan 31, 2007 at 01:40:58PM -0500, Bill Davidsen wrote: > > > >>And at some point will xen and selinux be compatible? I have everything > >>in the "right" place, but it still doesn't work. > >> > >> > > That's true, but I regard "turn off security" in the same light as "run > setuid root so you bypass all that permissions stuff." And at least some > of the places I could use this require selinux. setenforce doesn't > disable it, just sets it advisory, which means it still fails and tells > you there's no such file as when there is, just where it > should be. Daniel keeps telling me it works for him, so it's some > failure of understanding. > The initrd on fc6 is fucking broken. It doesn't have xenblk or xennet added. The reason I think is that initrd is created dynamically and the code doesn't have the --preload=xenblk. This is the actual command you have to run to get a proper initrd. echo "/dev/sda1 / ext3 defaults 1 1" > myfstab mkinitrd -f --with=xennet --builtin=aic7xxx --builtin=serverworks --preload=xenblk --omit-raid-modules --omit-lvm-modules --fstab=myfstab /boot/xen-initrd.img 2.6.19-1.2895.fc6xen (Command courtesy of Jerry from xen-users, slightly modified by me). This will fix everything. Thanks.