similar to: Reboot instead of dom0 starupt

    Question: can dom0 in Xen4.0 be rebooted (from domU or from within dom0) anytime without loosing anything ? If so, please provide details. If not, does Xen.org have this in roadmap ? The closest posting I found (old one) is: http://lists.xensource.com/archives/html/xen-devel/2005-07/msg00885.html The option is parameter as below (but this grub conf) noreboot Debugging Requests that

Hello, I have a big startproblem with the dom0 kernel. I use the latest stable xen with the 2.6.10 kernel. menu.lst: --- title Xen 2.05 / XenLinux 2.6.10 kernel /boot/xen.gz dom0_mem=512M noreboot module /boot/vmlinuz-2.6.10-xen0 root=/dev/sda1 ro console=tty0 --- Starterror: --- (XEN) Initial guest OS requires too much space (XEN) (8MB is greater than 0MB limit) --- System: I use an fresh

If I (for example) pass a wrong "root=" option to a dom0-linux kernel, it panics. so far, mkay a linux way. Now, different from other panics, there is a counter (of one second!) and then it reboots. I needed to make it panic three times till I could read the error message. Why has that been done this way? _______________________________________________ Xen-users mailing list

I''m experimenting with xen + iscsi, and I founded that under heavy stress domU''s can crash entire system, I''ve reproduced this many many times. My system is like this Software: - iSCSI Enterprise Target v0.4.13 - RedHat AS4 update 4 64bit + Xen 3.0.3-0 Kernel 2.6.16.29 + Open iSCSI v2.0.730 (Initiator) - Bonnie++ v1.03a VM: - Debian 3.1r3 + Open iSCSI v2.0.730

On Debian Squeeze (2.6.32-5) running Xen 4.0, I have created 2 Ubuntu Lucid Lynx (Ubuntu 10.04) vms. The vms, in a stress test, pass a large file between them via nfs file sharing. A previous entry in this forum helped to establish that some ethernet cards improve VM IO performance. However, our box installed with better intel nics is still rebooting under heavy VM IO loads. The kernel call

Hello list, I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this mission failed.. Hope you can help me by finding the reason for my problem. I downloaded the xen sources from http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz and compiled them by running "make" and "./install.sh". This seemed to work. After setting up grub like this,

Hi, Ive been using Xen2 for ages, and it great, but ive decided to go to Xen 3. Ive got it working, but I want to ask a couple of questions about it. 1. There no longer seems to be a seperate DomU and Dom0 built when I build from source. Is this the new policy? this would suit me, as I always used Xen0 kernels in my guest domains anyway. 2. Ive got me a vmx (vanderpool / intel virtualization

I have the following message while trying to boot xenlinux: ----------------------------------------------------- >Kernel Panic : Syncing no init found try passing init= option to kernel ------------------------------------------------------ My grub.conf is ------------------------------------------------------- title Xen 2.0 / XenLinux 2.6- 1th test root (hd0,1) kernel

Hi all, my main xen test system is a pizza box, simply standard. The kernel of stable debian sarge can shut it down/restart it correctly. My own xen kernel (based on debians inofficial xen kernel) cannot. I do not know much of kernels and hardware yet, so please help me to understand: Is shutting down (as opposed to writing "power down" to the screen) or restarting based on APM or

I am currently using a Dell PowerEdge server R610 with Xen 4.0 installed and the 2.6.31.13 pvops kernel. I am accessing the server console using the iDRAC KVM feature of the dell management console. Does anyone know how to configure the console option in the grub menu so that all the boot messages can be seen on the mgmt console? Currently I can view only the Xen bootup messages if I dont specify

Hi, how could I get better debugging output from the dom0 kernel? The kernel crashes after some time and debugging output to the console is being scrolled off by messages about NMI stuff trying to do something. I'm using Debian stable and would like to make a bug report, but without any useful information there's no point. So far, all I can say is that it seems to take over 12 and less

Hi, i have a problem with xen. the output of uname is:Linux xen 2.6.12-gentoo-r6 #9 SMP Mon Jan 23 18:13:25 CET 2006 i686 AMD Opteron(tm) Processor 844 AuthenticAMD GNU/Linux i user the SAME config of the kernel, for xen0 domain, and when i boot with xen0 kernel it reboots after this output... . . . ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.

Hi, I recently compiled a Xen-4.0.1 and pv-ops Dom0 2.6.32.27 kernel from JF''s tree.Where my hypervisor could not boot and unfortunately the system is rebooting so frequently that I am not able to note down the error messages on a paper and pencil.So now I am planning to go for a non pv-ops Dom0.I am not clear as what should be the approach? I have been Googling it every now and then and

Ian Campbell <ijc at hellion.org.uk> writes: > On Sun, 2014-06-15 at 11:03 +0200, lee wrote: >> Hi, >> >> how could I get better debugging output from the dom0 kernel? > > Either configure a serial console [0] or add "noreboot" to your > *hypervisor* command line, so you can see (and perhaps > transcribe/photograph) the crash before manually

I''m continuing to work on making a new XenCD as previously discussed here. In the course of that work, I''ve generated (actually, currently stuck on) the enclosed crash dump. Thought I''d forward it for interest. To head off questions, you''ll see references to a very large initrd (~114 Mb). The Xen dump may or not be related to this unusual usage.

On 03/21/2017 07:48 AM, PJ Welsh wrote: > On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis > <ricardo at palmtx.com.ar <mailto:ricardo at palmtx.com.ar>> wrote: > > El Lunes 20/03/2017, PJ Welsh escribi?: > > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > > Thanks > > PJ > > Edit grub's entry

El Lunes 20/03/2017, PJ Welsh escribi?: > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > Thanks > PJ Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it. > On Mon, Mar 20, 2017 at 2:23 PM, Johnny Hughes <johnny at centos.org> wrote: > > On

On Sun, 2014-06-15 at 11:03 +0200, lee wrote: > Hi, > > how could I get better debugging output from the dom0 kernel? Either configure a serial console [0] or add "noreboot" to your *hypervisor* command line, so you can see (and perhaps transcribe/photograph) the crash before manually rebooting. [0] http://wiki.xen.org/wiki/Xen_Serial_Console Ian.

Hello, my name is Viktor. I use kernel-2.6.38.5 as dom0. I can''t get access to console dom0. There is a blank screen after xen-4.1.0.gz loading. But dom0 is loaded and I have got it from ssh and it works fine. I just see nothing at monitor screen. Why? May be I have error in my grub.conf settings, please help! My video card: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series]

On Sun, 2014-06-15 at 13:35 +0200, lee wrote: > Ian Campbell <ijc at hellion.org.uk> writes: > > > On Sun, 2014-06-15 at 11:03 +0200, lee wrote: > >> Hi, > >> > >> how could I get better debugging output from the dom0 kernel? > > > > Either configure a serial console [0] or add "noreboot" to your > > *hypervisor* command