Hi,
I installed Xen3.3 on a Debian (etch) system. My DomU is also a Debian
(etch) system on a logical volume. I populated the volume by mounting it
from the Dom0 and used debootstrap. The config file for the DomU is:
kernel = "/boot/vmlinuz-2.6.18.8-xen"
ramdisk = "/boot/initrd.img-2.6.18.8-xen"
memory = 32
root = "/dev/xvda1 ro"
disk = [''phy:xenix-lvm/obelix_root,xvda1,w'',
''phy:xenix-lvm/obelix_swap,xvda2,w'']
vif = [ '''' ]
The kernel for the DomU is the kernel I get from the Xen3.3 build
process. Starting the DomU seems to work, at least I get no error from
xm create. When I want to switch the console to the DomU with XM console
the DomU seems to hang during boot. I get the following and then the
output stops. Nothing happens anymore. No login prompt. The only thing I
can do is to shutdown the DomU again.
Can someone please help?
Thanx
Martin
Oct 10 15:28:46 xenix kernel: Linux version 2.6.18.8-xen (root@xenix)
(gcc versi
on 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Thu Oct 9
17:03:20 CEST
2008
Oct 10 15:28:46 xenix kernel: BIOS-provided physical RAM map:
Oct 10 15:28:46 xenix kernel: Xen: 0000000000000000 - 0000000002800000
(usable)
Oct 10 15:28:46 xenix kernel: 0MB HIGHMEM available.
Oct 10 15:28:46 xenix kernel: 40MB LOWMEM available.
Oct 10 15:28:46 xenix kernel: ACPI in unprivileged domain disabled
Oct 10 15:28:46 xenix kernel: Allocating PCI resources starting at
10000000 (gap
: 02800000:fd800000)
Oct 10 15:28:46 xenix kernel: Detected 463.729 MHz processor.
Oct 10 15:28:46 xenix kernel: Built 1 zonelists. Total pages: 10240
Oct 10 15:28:46 xenix kernel: Kernel command line: root=/dev/xvda1 ro
Oct 10 15:28:46 xenix kernel: Enabling fast FPU save and restore... done.
Oct 10 15:28:46 xenix kernel: Initializing CPU#0
Oct 10 15:28:46 xenix kernel: PID hash table entries: 256 (order: 8,
1024 bytes)
Oct 10 15:28:46 xenix kernel: Xen reported: 348.203 MHz processor.
Oct 10 15:28:46 xenix kernel: Console: colour dummy device 80x25
Oct 10 15:28:46 xenix kernel: Dentry cache hash table entries: 8192
(order: 3, 3
2768 bytes)
Oct 10 15:28:46 xenix kernel: Inode-cache hash table entries: 4096
(order: 2, 16
384 bytes)
Oct 10 15:28:46 xenix kernel: Software IO TLB disabled
...
Oct 10 15:28:46 xenix kernel: RAMDISK driver initialized: 16 RAM disks
of 16384K
size 1024 blocksize
Oct 10 15:28:46 xenix kernel: loop: loaded (max 8 devices)
Oct 10 15:28:46 xenix kernel: Xen virtual console successfully installed
as xvc0
Oct 10 15:28:46 xenix kernel: Event-channel device installed.
Oct 10 15:28:46 xenix kernel: netfront: Initialising virtual ethernet
driver.
Oct 10 15:28:46 xenix kernel: xen-vbd: registered block device major 202
Oct 10 15:28:46 xenix kernel: blkfront: xvda1: barriers enabled
Oct 10 15:28:46 xenix kernel: blkfront: xvda2: barriers enabled
Oct 10 15:28:46 xenix kernel: Uniform Multi-Platform E-IDE driver
Revision: 7.00
alpha2
Oct 10 15:28:46 xenix kernel: ide: Assuming 50MHz system bus speed for
PIO modes
; override with idebus=xx
Oct 10 15:28:46 xenix kernel: PNP: No PS/2 controller found. Probing
ports direc
tly.
Oct 10 15:28:46 xenix kernel: mice: PS/2 mouse device common for all mice
Oct 10 15:28:46 xenix kernel: md: md driver 0.90.3 MAX_MD_DEVS=256,
MD_SB_DISKS27
Oct 10 15:28:46 xenix kernel: md: bitmap version 4.39
Oct 10 15:28:46 xenix kernel: NET: Registered protocol family 1
Oct 10 15:28:46 xenix kernel: md: md driver 0.90.3 MAX_MD_DEVS=256,
MD_SB_DISKS27
Oct 10 15:28:46 xenix kernel: md: bitmap version 4.39
Oct 10 15:28:46 xenix kernel: NET: Registered protocol family 1
Oct 10 15:28:46 xenix kernel: NET: Registered protocol family 17
Oct 10 15:28:46 xenix kernel: Using IPI No-Shortcut mode
Oct 10 15:28:46 xenix kernel: XENBUS: Device with no driver:
device/console/0
Oct 10 15:28:46 xenix kernel: BIOS EDD facility v0.16 2004-Jun-25, 0
devices fou
nd
Oct 10 15:28:46 xenix kernel: EDD information not available.
Oct 10 15:28:46 xenix kernel: Freeing unused kernel memory: 192k freed
Oct 10 15:28:46 xenix kernel: device-mapper: ioctl: 4.7.0-ioctl
(2006-06-24) ini
tialised: dm-devel@redhat.com
Oct 10 15:28:46 xenix kernel: kjournald starting. Commit interval 5 seconds
Oct 10 15:28:46 xenix kernel: EXT3-fs: mounted filesystem with ordered
data mode
.
Oct 10 15:28:46 xenix kernel:
Pausing... 5
Pausing... 4
Pausing... 3
Pausing... 2
Pausing... 1
Continuing...
Oct 10 15:28:46 xenix kernel:
Oct 10 15:28:46 xenix kernel: Adding 262136k swap on /dev/xvda2.
Priority:-1 ex
tents:1 across:262136k
Oct 10 15:28:46 xenix kernel: EXT3 FS on xvda1, internal journal
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi,
I installed Xen3.3 on a Debian (etch) system. My DomU is also a Debian
(etch) system on a logical volume. I populated the volume by mounting it
from the Dom0 and used debootstrap. The config file for the DomU is:
kernel = "/boot/vmlinuz-2.6.18.8-xen"
ramdisk = "/boot/initrd.img-2.6.18.8-xen"
memory = 32
root = "/dev/xvda1 ro"
disk = [''phy:xenix-lvm/obelix_root,xvda1,w'',
''phy:xenix-lvm/obelix_swap,xvda2,w'']
vif = [ '''' ]
The kernel for the DomU is the kernel I get from the Xen3.3 build
process. Starting the DomU seems to work, at least I get no error from
xm create. When I want to switch the console to the DomU with XM console
the DomU seems to hang during boot. I get the following and then the
output stops. Nothing happens anymore. No login prompt. The only thing I
can do is to shutdown the DomU again.
Can someone please help?
Thanx
Martin
Oct 10 15:28:46 xenix kernel: Linux version 2.6.18.8-xen (root@xenix)
(gcc versi
on 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Thu Oct 9
17:03:20 CEST
2008
Oct 10 15:28:46 xenix kernel: BIOS-provided physical RAM map:
Oct 10 15:28:46 xenix kernel: Xen: 0000000000000000 - 0000000002800000
(usable)
Oct 10 15:28:46 xenix kernel: 0MB HIGHMEM available.
Oct 10 15:28:46 xenix kernel: 40MB LOWMEM available.
Oct 10 15:28:46 xenix kernel: ACPI in unprivileged domain disabled
Oct 10 15:28:46 xenix kernel: Allocating PCI resources starting at
10000000 (gap
: 02800000:fd800000)
Oct 10 15:28:46 xenix kernel: Detected 463.729 MHz processor.
Oct 10 15:28:46 xenix kernel: Built 1 zonelists. Total pages: 10240
Oct 10 15:28:46 xenix kernel: Kernel command line: root=/dev/xvda1 ro
Oct 10 15:28:46 xenix kernel: Enabling fast FPU save and restore... done.
Oct 10 15:28:46 xenix kernel: Initializing CPU#0
Oct 10 15:28:46 xenix kernel: PID hash table entries: 256 (order: 8,
1024 bytes)
Oct 10 15:28:46 xenix kernel: Xen reported: 348.203 MHz processor.
Oct 10 15:28:46 xenix kernel: Console: colour dummy device 80x25
Oct 10 15:28:46 xenix kernel: Dentry cache hash table entries: 8192
(order: 3, 3
2768 bytes)
Oct 10 15:28:46 xenix kernel: Inode-cache hash table entries: 4096
(order: 2, 16
384 bytes)
Oct 10 15:28:46 xenix kernel: Software IO TLB disabled
...
Oct 10 15:28:46 xenix kernel: RAMDISK driver initialized: 16 RAM disks
of 16384K
size 1024 blocksize
Oct 10 15:28:46 xenix kernel: loop: loaded (max 8 devices)
Oct 10 15:28:46 xenix kernel: Xen virtual console successfully installed
as xvc0
Oct 10 15:28:46 xenix kernel: Event-channel device installed.
Oct 10 15:28:46 xenix kernel: netfront: Initialising virtual ethernet
driver.
Oct 10 15:28:46 xenix kernel: xen-vbd: registered block device major 202
Oct 10 15:28:46 xenix kernel: blkfront: xvda1: barriers enabled
Oct 10 15:28:46 xenix kernel: blkfront: xvda2: barriers enabled
Oct 10 15:28:46 xenix kernel: Uniform Multi-Platform E-IDE driver
Revision: 7.00
alpha2
Oct 10 15:28:46 xenix kernel: ide: Assuming 50MHz system bus speed for
PIO modes
; override with idebus=xx
Oct 10 15:28:46 xenix kernel: PNP: No PS/2 controller found. Probing
ports direc
tly.
Oct 10 15:28:46 xenix kernel: mice: PS/2 mouse device common for all mice
Oct 10 15:28:46 xenix kernel: md: md driver 0.90.3 MAX_MD_DEVS=256,
MD_SB_DISKS27
Oct 10 15:28:46 xenix kernel: md: bitmap version 4.39
Oct 10 15:28:46 xenix kernel: NET: Registered protocol family 1
Oct 10 15:28:46 xenix kernel: md: md driver 0.90.3 MAX_MD_DEVS=256,
MD_SB_DISKS27
Oct 10 15:28:46 xenix kernel: md: bitmap version 4.39
Oct 10 15:28:46 xenix kernel: NET: Registered protocol family 1
Oct 10 15:28:46 xenix kernel: NET: Registered protocol family 17
Oct 10 15:28:46 xenix kernel: Using IPI No-Shortcut mode
Oct 10 15:28:46 xenix kernel: XENBUS: Device with no driver:
device/console/0
Oct 10 15:28:46 xenix kernel: BIOS EDD facility v0.16 2004-Jun-25, 0
devices fou
nd
Oct 10 15:28:46 xenix kernel: EDD information not available.
Oct 10 15:28:46 xenix kernel: Freeing unused kernel memory: 192k freed
Oct 10 15:28:46 xenix kernel: device-mapper: ioctl: 4.7.0-ioctl
(2006-06-24) ini
tialised: dm-devel@redhat.com
Oct 10 15:28:46 xenix kernel: kjournald starting. Commit interval 5 seconds
Oct 10 15:28:46 xenix kernel: EXT3-fs: mounted filesystem with ordered
data mode
.
Oct 10 15:28:46 xenix kernel:
Pausing... 5
Pausing... 4
Pausing... 3
Pausing... 2
Pausing... 1
Continuing...
Oct 10 15:28:46 xenix kernel:
Oct 10 15:28:46 xenix kernel: Adding 262136k swap on /dev/xvda2.
Priority:-1 ex
tents:1 across:262136k
Oct 10 15:28:46 xenix kernel: EXT3 FS on xvda1, internal journal
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Anton wrote:> 2008/10/11 Martin Lang <mlg-hessigheim@gmx.de>: > >> Hi, >> >> I installed Xen3.3 on a Debian (etch) system. My DomU is also a Debian >> (etch) system on a logical volume. I populated the volume by mounting it >> from the Dom0 and used debootstrap. The config file for the DomU is: >> >> kernel = "/boot/vmlinuz-2.6.18.8-xen" >> ramdisk = "/boot/initrd.img-2.6.18.8-xen" >> memory = 32 >> root = "/dev/xvda1 ro" >> disk = [''phy:xenix-lvm/obelix_root,xvda1,w'', >> ''phy:xenix-lvm/obelix_swap,xvda2,w''] >> vif = [ '''' ] >> >> The kernel for the DomU is the kernel I get from the Xen3.3 build >> process. Starting the DomU seems to work, at least I get no error from >> xm create. When I want to switch the console to the DomU with XM console >> the DomU seems to hang during boot. I get the following and then the >> output stops. Nothing happens anymore. No login prompt. The only thing I >> can do is to shutdown the DomU again. >> >> Can someone please help? >> > > Just a guess, but try adding: > > extra = "xencons=tty" > > to the domU config file. > > I had similar baffling symptoms with 3.3 on Debian, and that fixed it for me. > >That solved the problem. Thanx again _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
How can such a stupid problem still exist in 2008? Can''t Xen handle some kind of misconfiguration detection? I remember struggling for days just because I had to change 1 character or 1 word in my Xen configuration files, that''s not a very good selling point. Moreover from one version to another, the configuration file can also completely fail. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Oct 12, 2008 at 7:40 AM, Thomas <iamkenzo@gmail.com> wrote:> How can such a stupid problem still exist in 2008? Can''t Xen handle > some kind of misconfiguration detection? I remember struggling for > days just because I had to change 1 character or 1 word in my Xen > configuration files, that''s not a very good selling point. Moreover > from one version to another, the configuration file can also > completely fail. >This particular problem is not a xen one, it is distribution and also kernel specific. The distros (if they do a good job), make the appropriate changes in their xen-related packages before they ship. Different kernels use different virtual consoles, so based on the kernel version different consoles need to be setup. This is also handled by distros as they ship. For those that compile their own, they should expect to have to do some customizations for their setup. This list has always been a good place to ask questions and learn from those that have the experience. When Xen support hits the mainline Linux kernel, hopefully things like consoles will stabilize/standardize. Until that point, people can come to this list and/or search places like xen.markmail.org for help/solutions. If you feel that there is a better solution, you should suggest the appropriate patches on xen-devel. Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Oct 10, 2008 at 11:59 PM, Martin Lang <mlg-hessigheim@gmx.de> wrote:> Hi, > > I installed Xen3.3 on a Debian (etch) system. My DomU is also a Debian > (etch) system on a logical volume. I populated the volume by mounting it > from the Dom0 and used debootstrap. The config file for the DomU is: > > kernel = "/boot/vmlinuz-2.6.18.8-xen" > ramdisk = "/boot/initrd.img-2.6.18.8-xen" > memory = 32 > root = "/dev/xvda1 ro" > disk = [''phy:xenix-lvm/obelix_root,xvda1,w'', > ''phy:xenix-lvm/obelix_swap,xvda2,w''] > vif = [ '''' ]In your domU config file, did you have such xencons=tty1 or something in extra? Mine is something like below: extra = "3 selinux=0 xencons=tty1" Kindest regards, Giam Teck Choon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users