similar to: My DomU can''t boot

Hi Pasi, if I don''t change the tty to hvc it will stopped on Kernel 2.6.31.13 on i686 (console) localhost login: root Kernel 2.6.31.13 on i686 (console) localhost login: root Kernel 2.6.31.13 on i686 (console) localhost login: root After I change it to hvc0 followed the twiki page the log is Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK

Hello xen-users ! I am coming for help concerning the just released 4.0 version. Install has worked rather well on my Debian Lenny. I have just had a few bugs for which I have found the answer looking around on this list. I have created a Debian Lenny domU which boots up just fine. The only problem is that I am unable to get a console prompt when using "xm console nameofdomU". I do see

I''m running Xen 3.2 on Debian 5.0 (Lenny) and am having trouble booting up a Debian Etch DomU. It hangs at the end when it says "Starting periodic command scheduler: cron." It''s just completely frozen. At one point I set it sit for a few hours and got back into the console and it said something about "time went backwards" but I used the

After startup of the DomU with xm create mydomu.cfg ­c The startup always stops, when starting the Cron-Daemon. [ 1.810477] EXT3 FS on xvda1, internal journal Loading kernel modules...done. Cleaning up ifupdown.... Setting up networking.... Activating lvm and md swap...done. Checking file systems...fsck from util-linux-ng 2.17.2 done. Mounting local filesystems...done. Activating swapfile

Hi, I've tried to setup a new DomU on Lenny and I'm a little bit confused on which device names I should use for disks and console in the various DomU-kernels? Is it correct that: 2.6.18-xen-kernel from Etch start with no "extra" tty1 in /etc/inittab /dev/sd for disks 2.6.26-xen-kernel from Lenny: start with no "extra" hvc0 in /etc/inittab /dev/xvd for disks

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I''m using VNC to show vm''s linux boot. I see lines like [ 1.053298] EXT3-fs: INFO: recovery required on readonly filesystem. [ 1.053686] EXT3-fs: write access will be enabled during recovery. [ 1.494490] kjournald starting. Commit interval 5 seconds etc. But à the end of booting, it stop. No prompt login. With "xm console vm" I have the boot login. I

Hi, currently i am using KVM, but i want to switch (back) to xen. All my VMs have a own partition inside a lvm. Inside of this partition are 2-3 own pratition. if i want to access them, i can do this by "kpartx -a /dev/vg/VM". Usually my domu configs look like this: bootloader=''/usr/bin/pygrub'' name="ipfire" memory=512 acpi=1 apic=1

Hi, I''m using Debian 5 (lenny) with Xen 3.2-1. When I try to start a Linux guest (installed with debootstrap like this <http://www.option-c.com/xwiki/Create_a_Debian_VM_with_debootstrap>), the VM hangs right after starting crond. This is exactly before the login prompt (which doesn''t come up). 1) In the internet, the solution is an /extra/ line in the configuration

I followed the book called "Professional Xen Virtualization" written by William von Hagen,and published by Wiley Publishing,Inc. Here are some configuration files: #cat /xen/ubuntu/ubuntu.xen3.cfg kernel = "/boot/vmlinuz-2.6.18-128.1.16.el5xen" ramdisk = "/boot/initrd-2.6.18-128.1.16.el5xen-no-scsi.img" memory = "512" name = "Ubuntu804" vif =

Hello everyone, I''m quite a newbie with Xen and I''m currently having an issue. I run Xen 4 on Debian Squeeze x64 and I''m trying to build an OpenFiler DomU from the Xen domU filesystem tarbal they provide (See http://www.openfiler.com/community/download/). I downloaded the tarball and run ''tar xzpvf /root/soft/openfiler-2.3-x86_64.tar.gz'' to extract

Hi all, I have a machine that won't boot syslinux 4.02 but will boot syslinux 3.53. We've installed syslinux 4.02 on a number of machines but only this one has a problem. The problem is that the machine hangs entirely after printing "boot:" on the tty. The stanza being booted in /boot/extlinux.conf is: label xe # XenServer kernel mboot.c32 append /boot/xen.gz

Hi list, I am running a virtualized server. Dom0 uses Xen 3.2.1 with Debian Etch and a custom kernel 2.6.21 created by my webhosting company. I install my domU using debootstrap for a Debian Etch with 2.6.18-6-xen-amd64 kernel. Everything works well except the fact that once the VM is started I cannot "xm console" into it. It only works while it is booting and while it is shutting

Are these the current functional procedures for dropping a dom0 on a jaunty 64 bit server? xen-tools: http://bderzhavets.wordpress.com/2009/08/14/attempt-of-prevu-xen-3-4-1-hypervisor-on-ubuntu-jaunty-server-64-bit/ kernel: http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/ Regarding the patches used in the above procedure from here:

I just installed xen-linux-system-2.6.26-1-xen-amd64 2.6.26-7 on a freshly installed Debian Lenny AMD64 system, and when I create a Debian Lenny DomU with xen-tools I cannot attach to a console nor log in with SSH. When running # xm create -c test.cfg the system starts booting, but it seems to "freeze" after the kernel has booted. Googling a bit, shows that I seem to have the problem

Hey, I''m experiencing strange problem: non-deterministic PV domain hang, only on some machines (with fast SSD drive). I''ve tried xen-4.1.0 and xen-4.1.1 with many kernels different kernels: VM: - 2.6.38.3 xenlinux based on SUSE package - vanilla 3.0.3 - vanilla 3.1 rc2 dom0: - 2.6.38.3 xenlinux based on SUSE package - vanilla 3.1 rc2 Result always the same: sometimes VM

Hi All, I am working on creating storage driver domain with xen-4.3.0 . I am referring this - http://wiki.xen.org/wiki?title=Storage_driver_domains&oldid=9371 I have created Storage domain with xl utility of xen, then followed above wiki for rest of the steps, additionally I did install blktap-dkms package also- Following xen processes are running on Domain 0:

Hi All, I am working on creating storage driver domain with xen-4.3.0 . I am referring this - http://wiki.xen.org/wiki?title=Storage_driver_domains&oldid=9371 I have created Storage domain with xl utility of xen, then followed above wiki for rest of the steps, additionally I did install blktap-dkms package also- Following xen processes are running on Domain 0:

Hi, I''m using a custom block script in my xen setup and when started, it creates a new device node pointing to some network resources. Now I noticed that the script is called twice for the root block, the first time for pygrub most likely, but is only stopped once ... I don''t mind creating two devices node, but then I need to destroy both ... Is this a known issue ? Cheers,