similar to: ''ser_baud=xxx'' option gone away

Hi, I am trying to install Xen/Xenolinux v1.1 on my workstation which has 2 SCSI disks. The first disk has WinXP installed, and the second disk has Redhat 8.0. I copied the images into /boot and modified grub.conf accordingly: title Xen / XenoLinux 2.4.22 root (hd1,0) kernel /xen.gz dom0_mem=131072 ser_baud=115200 noht noreboot module /xenolinux.gz root=/dev/sdb2 ro

I am trying to write a script to handle setup of domains using virtual block devices for their root FS and have been unable to get the virtual devices to work with any sort of consistency. This is using xen-1.1.bk on Redhat 7.3 (I had to rebuild all the tool binaries to run on 7.3). Anyway, I would first like to make sure I am using the vd/vbd stuff correctly. Here is an example of the problem I

Maybe this question is a little stupid, but please help me. I am a newbie to Xen. When I tried to create a new domain "domain 1", I followed the Yan-Ching CHU''s guide on :installing quick file systems for new domains in Xen 1.2". But when I do "xc_dom_create.py -Dvmid=1", Xen seems to start to boot with some normal bootup information, but right after several

it''s a good idea to do this: wget --passive-ftp for more and more sites. Probably a good default. ron ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking

Am I correct in reading the code that there is no "noht" (turn off hyperthreading) option in Xen (except in powerpc)? This was a surprise to me as I've seen it documented in various places and I recently suggested it as a diagnostic to a customer. =================================== If Xen could save time in a bottle / then clocks wouldn't virtually skew / It would save every

Whilst tinkering with lvm (which now works great - thanks!), I made a typo which caused the domain to stop booting. I think it was just that I got the config file wrong in terms of which device mapped to which. Anyway, I had specified ''restart=True'' and so the domain was starting to boot, failing, then restarting again. This was the expected behaviour, but it was a pain to kill.

Hi all, I am running the current xen-unstable and had the following error message when trying to create domain1. # ./xenctl script -f/etc/xen-mynewdom Domain defaults: name XenoLinux size 98304 vifs 1 domainImage /boot/xenolinux.gz domainInitRD null rootDevice /dev/hda5 rootArgs rw usrDevice null NWIP

The system is Mandrake-9.1 Linux wih gcc-3.2.2. I am trying to compile xenolinux-2.4.24 (with vanilla sources from ftp.kernel.org for linux-2.4.24). The steps of mkbuildtree ARCH=xeno make menuconfig ARCH=xeno make dep produce no errors, but ARCH=xeno make bzImage results in following error messages. Any pointers will be appreciated. -ishwar --- gcc -D__KERNEL__

I know you Xen developers are beginning to hate me ;) but... While trying to compile 2.4.24 under DOM0, quickly after issuing ''make dep'' I got: Kernel panic: Failed mmu update: c015bf80, 4 I suspect this address probably isn''t to helpful but this is all I have. I am currently booted in 2.4.21-SuSE and compiling the 2.4.24 regarding another thread here. Regarding

I''ve been recently testing the Xendemo CD and I can say that Xen is awesome. I''d like to start deploying it initially in some development/testing servers. However the limitation of the max memory of 800MB or so per virtual machine is a show stopper for many applications. Are there plans to raise the limit to something higher (like 2GB or so)? How difficult would it be?

Has anyone got Xen working with say, SELinux? Or vserver? Wesley Parish -- Clinesterton Beademung - in all of love. Mau e ki, "He aha te mea nui?" You ask, "What is the most important thing?" Maku e ki, "He tangata, he tangata, he tangata." I reply, "It is people, it is people, it is people." ------------------------------------------------------- This

Hi all, I have another problem with starting domainU (xenolinux). I took me pretty much quite some time and i can not figure out why starting a new domain is failing. I will really appreciate if somebody can help me with this error. The error I get when booting xen-domainU is: /======================= Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev

I know I have asked this before, but I am having trouble understanding the role of each component in the new 1.3 world: In 1.3 networking if Xen has no devices, and domain 0 owns and operates the NIC - does Xen have any role at all in networking for the guest OS''s? Which network device driver will a guest OS use? Do all the vnetif rules defined in Domain 0 now get interpreted by

Excuse me, what did you mean by "certainly wrong: you''re ... to make real physical partition hda1 visible to the domain"? Can we use real physical partition in vbd_list? And what the "cmdline_root" should be? Thanks. Xiaofang > vbd_list = [ (''phy:hda1'',''sda1'',''w''),

resend to larger group: which one is the right one? I''m going thru some merge hell and a need some newer PPC code from kernel.org. is it: http://xenbits.xensource.com/linux-2.6-xen.hg (worked on) --or-- http://xenbits.xensource.com/ext/linux-2.6-merge.hg (six weeks of nothing) there is also linux-2.6.rc-xen.hg, linux-2.6.tip-xen.hg, linux-2.6- patchqueue.hg the PPC team

Hi all I am in the process of upgrading my XEN servers from 2.4 to 2.6 kernels as I am having better results on 2.6. However one machine (the big daddy) refuses to boot a 2.6.9 xenolinux kernel. It''s an IBM eSeries xServer x205. I have selected what i think are the appropriate options in menuconfig but it refuses to boot into dom0. By refuse I mean it initialises the hypervisor,

Hi All, I''ve been looking through the code and list archives but haven''t found this yet... From dom0, how do you cause a virtual domain to gracefully shutdown? It seems like the machinery is there somewhere, because the hypervisor can do it to dom0... For reference, in UML you do this by putting this in /etc/inittab: ca:12345:ctrlaltdel:/sbin/shutdown -h now ...and then

Is there a particular reason for doing this unconditionally on both 32- and 64-bits in xenolinux? It would seem to me that this feature should be disabled at most in unprivileged kernels... Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

The attached re-enables the pygrub build and fixes the build with older e2fsprogs (tested on RHEL4 with e2fsprogs-1.35 and rawhide with e2fsprogs-1.38) Signed-off-by: Jeremy Katz <katzj@redhat.com> Jeremy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I'm having trouble with IBM xseries 345/dual Xeon 2.66GHz showing only one processor. At boot I see "SMP motherboard not recognized". Using title CentOS (2.6.18-8.1.8.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-8.1.8.el5 module /vmlinuz-2.6.18-8.1.8.el5xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet module /initrd-2.6.18-8.1.8.el5xen.img have