M.Wuerthele
2007-Jun-25 07:17 UTC
[Xen-users] Console hangs on Xen 3.1 Ubuntu Feisty Server
Hi,
i just installed Xen 3.1 in ubuntu feisty server. I created a
paravirtualized domU using debootstrap scripts.
Now i can boot this new feisty domU and connect to it using ''xm
console''. My problem is that the console stops working during bootup.
The last message i see is ''lo: Disabled Privacy Extensions''
and then
nothing. The domU is running anyhow. I can connect to it using ssh and i
can ping it but the xm console is dead.
What could be the problem ?
Thank you
Matthias
console output until it dies:
----------------snip--------------------------
root@xencube:/# xm create /etc/xen/vm/nas.pv -c
Using config file "/etc/xen/vm/nas.pv".
Started domain nas
[ 0.000000] Linux version 2.6.20-100-server-amd64
(root@palmier) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sat
Jun 2 10:53:09 UTC 2007 (Ubuntu Unofficial)
[ 0.000000] Command line: root=/dev/sda2 ro 3
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 0000000008800000 (usable)
[ 0.000000] end_pfn_map = 34816
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 34816
[ 0.000000] DMA32 34816 -> 34816
[ 0.000000] Normal 34816 -> 34816
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 34816
[ 5984.810484] No mptable found.
[ 5984.810928] PERCPU: Allocating 25600 bytes of per cpu data
[ 5984.810957] Built 1 zonelists. Total pages: 33200
[ 5984.810961] Kernel command line: root=/dev/sda2 ro 3
[ 5984.811713] Initializing CPU#0
[ 5984.811880] PID hash table entries: 1024 (order: 10, 8192 bytes)
[ 5984.811898] Xen reported: 1908.652 MHz processor.
[ 5984.811919] Console: colour dummy device 80x25
[ 5984.812142] Dentry cache hash table entries: 32768 (order: 6, 262144
bytes)
[ 5984.812284] Inode-cache hash table entries: 16384 (order: 5, 131072
bytes)
[ 5984.812328] Software IO TLB disabled
[ 5984.813760] Memory: 101112k/139264k available (2279k kernel code,
29796k reserved, 1243k data, 196k init)
[ 5984.937442] Calibrating delay using timer specific routine.. 3818.21
BogoMIPS (lpj=19091083)
[ 5984.937493] Security Framework v1.0.0 initialized
[ 5984.937502] SELinux: Disabled at boot.
[ 5984.937523] Mount-cache hash table entries: 256
[ 5984.937665] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
[ 5984.937673] CPU: L2 Cache: 512K (64 bytes/line)
[ 5984.937679] CPU: Physical Processor ID: 0
[ 5984.937683] CPU: Processor Core ID: 0
[ 5984.937686] (SMP-)alternatives turned off
[ 5984.937782] Early unpacking initramfs... done
[ 5984.966456] Brought up 1 CPUs
[ 5984.967279] Grant table initialized
[ 5984.967350] NET: Registered protocol family 16
[ 5984.968384] Brought up 1 CPUs
[ 5984.968401] PCI: Fatal: No config space access function found
[ 5984.968405] PCI: setting up Xen PCI frontend stub
[ 5984.968995] ACPI: Interpreter disabled.
[ 5984.969005] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 5984.969018] pnp: PnP ACPI: disabled
[ 5984.969787] xen_mem: Initialising balloon driver.
[ 5984.971007] PCI: System does not support PCI
[ 5984.971014] PCI: System does not support PCI
[ 5984.971043] NET: Registered protocol family 8
[ 5984.971049] NET: Registered protocol family 20
[ 5984.971060] NetLabel: Initializing
[ 5984.971064] NetLabel: domain hash size = 128
[ 5984.971068] NetLabel: protocols = UNLABELED CIPSOv4
[ 5984.971084] NetLabel: unlabeled traffic allowed by default
[ 5984.971436] NET: Registered protocol family 2
[ 5985.057457] IP route cache hash table entries: 2048 (order: 2, 16384
bytes)
[ 5985.057551] TCP established hash table entries: 8192 (order: 5,
131072 bytes)
[ 5985.057636] TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
[ 5985.057680] TCP: Hash tables configured (established 8192 bind 4096)
[ 5985.057687] TCP reno registered
[ 5985.087389] checking if image is initramfs... it is
[ 5985.118050] Freeing initrd memory: 22228k freed
[ 5985.131690] audit: initializing netlink socket (disabled)
[ 5985.131715] audit(1182717017.591:1): initialized
[ 5985.131877] VFS: Disk quotas dquot_6.5.1
[ 5985.131898] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 5985.131954] io scheduler noop registered
[ 5985.131961] io scheduler anticipatory registered
[ 5985.131966] io scheduler deadline registered (default)
[ 5985.131982] io scheduler cfq registered
[ 5985.153401] rtc: IRQ 8 is not free.
[ 5985.153492] Linux agpgart interface v0.102 (c) Dave Jones
[ 5985.153550] mice: PS/2 mouse device common for all mice
[ 5985.154077] RAMDISK driver initialized: 16 RAM disks of 65536K size
1024 blocksize
[ 5985.154276] input: Macintosh mouse button emulation as
/class/input/input0
[ 5985.154495] Xen virtual console successfully installed as xvc0
[ 5985.154568] Event-channel device installed.
[ 5985.170068] netfront: Initialising virtual ethernet driver.
[ 5985.172988] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 5985.172997] ide: Assuming 50MHz system bus speed for PIO modes;
override with idebus=xx
[ 5985.173141] PNP: No PS/2 controller found. Probing ports directly.
[ 5985.173963] i8042.c: No controller found.
[ 5985.174040] TCP cubic registered
[ 5985.174052] NET: Registered protocol family 1
[ 5985.174562] Registering block device major 8
[ 5985.174580] blkfront: sda1: barriers enabled
[ 5985.175358] blkfront: sda2: barriers enabled
[ 5985.178948] netfront: device eth0 has copying receive path.
[ 5985.267287] XENBUS: Device with no driver: device/console/0
[ 5985.267300] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 5985.549168] Capability LSM initialized
[ 5985.574161] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12)
initialised: dm-devel@redhat.com <mailto:dm-devel@redhat.com>
[ 5985.697998] thermal: Unknown symbol acpi_processor_set_thermal_limit
[ 5985.813562] md: raid1 personality registered for level 1
[ 5985.832768] md: md1 stopped.
[ 5985.934545] md: md1 stopped.
[ 5986.395311] EXT3-fs: INFO: recovery required on readonly filesystem.
[ 5986.395328] EXT3-fs: write access will be enabled during recovery.
[ 5986.500204] kjournald starting. Commit interval 5 seconds
[ 5986.500236] EXT3-fs: recovery complete.
[ 5986.517561] EXT3-fs: mounted filesystem with ordered data mode.
[ 5988.803359] NET: Registered protocol family 10
[ 5988.803472] lo: Disabled Privacy Extensions
---------------------snap--------------------
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Matthias Wuerthele
2007-Jun-25 12:16 UTC
[Xen-users] Console hangs on Xen 3.1 Ubuntu Feisty Server
Hi,
i just installed Xen 3.1 in ubuntu feisty server. I created a
paravirtualized domU using debootstrap scripts.
Now i can boot this new feisty domU and connect to it using ''xm
console''. My problem is that the console stops working during bootup.
The last message i see is ''lo: Disabled Privacy Extensions''
and then
nothing. The domU is running anyhow. I can connect to it using ssh and i
can ping it but the xm console is dead.
What could be the problem ?
Thank you
Matthias
console output until it dies:
----------------snip--------------------------
root@xencube:/# xm create /etc/xen/vm/nas.pv -c
Using config file "/etc/xen/vm/nas.pv".
Started domain nas
[ 0.000000] Linux version 2.6.20-100-server-amd64
(root@palmier) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sat
Jun 2 10:53:09 UTC 2007 (Ubuntu Unofficial)
[ 0.000000] Command line: root=/dev/sda2 ro 3
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 0000000008800000 (usable)
[ 0.000000] end_pfn_map = 34816
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 34816
[ 0.000000] DMA32 34816 -> 34816
[ 0.000000] Normal 34816 -> 34816
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 34816
[ 5984.810484] No mptable found.
[ 5984.810928] PERCPU: Allocating 25600 bytes of per cpu data
[ 5984.810957] Built 1 zonelists. Total pages: 33200
[ 5984.810961] Kernel command line: root=/dev/sda2 ro 3
[ 5984.811713] Initializing CPU#0
[ 5984.811880] PID hash table entries: 1024 (order: 10, 8192 bytes)
[ 5984.811898] Xen reported: 1908.652 MHz processor.
[ 5984.811919] Console: colour dummy device 80x25
[ 5984.812142] Dentry cache hash table entries: 32768 (order: 6, 262144
bytes)
[ 5984.812284] Inode-cache hash table entries: 16384 (order: 5, 131072
bytes)
[ 5984.812328] Software IO TLB disabled
[ 5984.813760] Memory: 101112k/139264k available (2279k kernel code,
29796k reserved, 1243k data, 196k init)
[ 5984.937442] Calibrating delay using timer specific routine.. 3818.21
BogoMIPS (lpj=19091083)
[ 5984.937493] Security Framework v1.0.0 initialized
[ 5984.937502] SELinux: Disabled at boot.
[ 5984.937523] Mount-cache hash table entries: 256
[ 5984.937665] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
[ 5984.937673] CPU: L2 Cache: 512K (64 bytes/line)
[ 5984.937679] CPU: Physical Processor ID: 0
[ 5984.937683] CPU: Processor Core ID: 0
[ 5984.937686] (SMP-)alternatives turned off
[ 5984.937782] Early unpacking initramfs... done
[ 5984.966456] Brought up 1 CPUs
[ 5984.967279] Grant table initialized
[ 5984.967350] NET: Registered protocol family 16
[ 5984.968384] Brought up 1 CPUs
[ 5984.968401] PCI: Fatal: No config space access function found
[ 5984.968405] PCI: setting up Xen PCI frontend stub
[ 5984.968995] ACPI: Interpreter disabled.
[ 5984.969005] Linux Plug and Play Support v0.97 (c) Adam Belay
[ 5984.969018] pnp: PnP ACPI: disabled
[ 5984.969787] xen_mem: Initialising balloon driver.
[ 5984.971007] PCI: System does not support PCI
[ 5984.971014] PCI: System does not support PCI
[ 5984.971043] NET: Registered protocol family 8
[ 5984.971049] NET: Registered protocol family 20
[ 5984.971060] NetLabel: Initializing
[ 5984.971064] NetLabel: domain hash size = 128
[ 5984.971068] NetLabel: protocols = UNLABELED CIPSOv4
[ 5984.971084] NetLabel: unlabeled traffic allowed by default
[ 5984.971436] NET: Registered protocol family 2
[ 5985.057457] IP route cache hash table entries: 2048 (order: 2, 16384
bytes)
[ 5985.057551] TCP established hash table entries: 8192 (order: 5,
131072 bytes)
[ 5985.057636] TCP bind hash table entries: 4096 (order: 4, 65536 bytes)
[ 5985.057680] TCP: Hash tables configured (established 8192 bind 4096)
[ 5985.057687] TCP reno registered
[ 5985.087389] checking if image is initramfs... it is
[ 5985.118050] Freeing initrd memory: 22228k freed
[ 5985.131690] audit: initializing netlink socket (disabled)
[ 5985.131715] audit(1182717017.591:1): initialized
[ 5985.131877] VFS: Disk quotas dquot_6.5.1
[ 5985.131898] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 5985.131954] io scheduler noop registered
[ 5985.131961] io scheduler anticipatory registered
[ 5985.131966] io scheduler deadline registered (default)
[ 5985.131982] io scheduler cfq registered
[ 5985.153401] rtc: IRQ 8 is not free.
[ 5985.153492] Linux agpgart interface v0.102 (c) Dave Jones
[ 5985.153550] mice: PS/2 mouse device common for all mice
[ 5985.154077] RAMDISK driver initialized: 16 RAM disks of 65536K size
1024 blocksize
[ 5985.154276] input: Macintosh mouse button emulation as
/class/input/input0
[ 5985.154495] Xen virtual console successfully installed as xvc0
[ 5985.154568] Event-channel device installed.
[ 5985.170068] netfront: Initialising virtual ethernet driver.
[ 5985.172988] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 5985.172997] ide: Assuming 50MHz system bus speed for PIO modes;
override with idebus=xx
[ 5985.173141] PNP: No PS/2 controller found. Probing ports directly.
[ 5985.173963] i8042.c: No controller found.
[ 5985.174040] TCP cubic registered
[ 5985.174052] NET: Registered protocol family 1
[ 5985.174562] Registering block device major 8
[ 5985.174580] blkfront: sda1: barriers enabled
[ 5985.175358] blkfront: sda2: barriers enabled
[ 5985.178948] netfront: device eth0 has copying receive path.
[ 5985.267287] XENBUS: Device with no driver: device/console/0
[ 5985.267300] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 5985.549168] Capability LSM initialized
[ 5985.574161] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12)
initialised: dm-devel@redhat.com <mailto:dm-devel@redhat.com>
[ 5985.697998] thermal: Unknown symbol acpi_processor_set_thermal_limit
[ 5985.813562] md: raid1 personality registered for level 1
[ 5985.832768] md: md1 stopped.
[ 5985.934545] md: md1 stopped.
[ 5986.395311] EXT3-fs: INFO: recovery required on readonly filesystem.
[ 5986.395328] EXT3-fs: write access will be enabled during recovery.
[ 5986.500204] kjournald starting. Commit interval 5 seconds
[ 5986.500236] EXT3-fs: recovery complete.
[ 5986.517561] EXT3-fs: mounted filesystem with ordered data mode.
[ 5988.803359] NET: Registered protocol family 10
[ 5988.803472] lo: Disabled Privacy Extensions
---------------------snap--------------------
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Paul Waldo
2007-Jun-25 12:45 UTC
Re: [Xen-users] Console hangs on Xen 3.1 Ubuntu Feisty Server
Matthias Wuerthele wrote:> Hi, > i just installed Xen 3.1 in ubuntu feisty server. I created a > paravirtualized domU using debootstrap scripts. > Now i can boot this new feisty domU and connect to it using ''xm > console''. My problem is that the console stops working during bootup. > The last message i see is ''lo: Disabled Privacy Extensions'' and then > nothing. The domU is running anyhow. I can connect to it using ssh and i > can ping it but the xm console is dead. > What could be the problem ? > > Thank you > MatthiasMatthias, I ran into this problem also. See attached email for my solution. HTH! Paul _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matthias Wuerthele
2007-Jun-25 13:15 UTC
Re: [Xen-users] Console hangs on Xen 3.1 Ubuntu Feisty Server
Hi Paul, i already found your posting. In my case your solution did not work. When i use debootstrap to install feisty i have /etc/event.d/tty 1-6. I copied tty2 into tty0 and changed everything in it referencing to tty2 to tty0 but i have still the same issue. The console gets stuck during bootup. I can close console (Ctrl5) and open it again. There are no errors or something but a black screen. Matthias Paul Waldo schrieb:> Matthias Wuerthele wrote: >> Hi, >> i just installed Xen 3.1 in ubuntu feisty server. I created a >> paravirtualized domU using debootstrap scripts. >> Now i can boot this new feisty domU and connect to it using ''xm >> console''. My problem is that the console stops working during bootup. >> The last message i see is ''lo: Disabled Privacy Extensions'' and then >> nothing. The domU is running anyhow. I can connect to it using ssh and i >> can ping it but the xm console is dead. >> What could be the problem ? >> >> Thank you >> Matthias > Matthias, > > I ran into this problem also. See attached email for my solution. HTH! > > Paul > > ------------------------------------------------------------------------ > > Betreff: > Re: [Xen-users] Problem connecting to console > Von: > Paul Waldo <pwaldo@waldoware.com> > Datum: > Thu, 21 Jun 2007 09:37:58 -0400 > An: > Marcel Schroers <schroers@physik.uni-wuppertal.de> > > An: > Marcel Schroers <schroers@physik.uni-wuppertal.de> > CC: > xen-users@lists.xensource.com > > > Marcel Schroers wrote: >> >> Hi Paul, >> >> I''m not sure, but maybe you have the same problem I had a cupple of >> days ago. >> Here''s the solution which actually worked fine for me. >> Hope it will help you also... > Hi Marcel, > > This did help! Ubuntu has no /etc/inittab, so it took me a while to > figure it out. Ubuntu uses files in /etc/event.d to spawn ttys. There > were entries for tty[2-6], but none for tty[0-1] :-O. I don''t know > why... I had to make a copy of /etc/event.d/tty2, name it tty0, and > change all occurrences of tty2 to tty0. A reboot later, I had a > console. Thanks so much! > > Paul >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Paul Waldo
2007-Jun-25 13:33 UTC
Re: [Xen-users] Console hangs on Xen 3.1 Ubuntu Feisty Server
Matthias Wuerthele wrote:> Hi Paul, > i already found your posting. > In my case your solution did not work. When i use debootstrap to > install feisty i have /etc/event.d/tty 1-6. I copied tty2 into tty0 > and changed everything in it referencing to tty2 to tty0 but i have > still the same issue. The console gets stuck during bootup. I can > close console (Ctrl5) and open it again. There are no errors or > something but a black screen. > MatthiasCan you ssh into the DomU? You can also try shutting down the DomU and mounting the filesystem. Anything odd in /var/log/syslog? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Matthias Wuerthele
2007-Jun-25 14:39 UTC
Re: [Xen-users] Console hangs on Xen 3.1 Ubuntu Feisty Server
I installed ssh using chroot so i can access the domU. /var/log/syslog does not contain any special errors The last line i can see in the console (using xm console...) is: lo: Disabled Privacy Extensions In syslog however there are 2 more lines but nothing interesting: ----snip---- Adding 524280k swap on /dev/sda1. Priority:-1 extents:1 across:524280k EXT3 FS on sda2, internal journal eth0: no IPv6 routers present ----snap---- The system can be used without problems. I can install software using apt-get or ping my network... I just noticed one more thing. If i am going to reboot the domU using the ssh connection and a simple ''reboot'' my xen console shows one more thing: ''Restarting system.'' So its not really dead its just like its not connected to the domU standard tty anymore. Maybe i have to specify this somewhere. This is something i will have to google for because i am not familiar with this part of linux yet. (still learning :-) Matthias Paul Waldo schrieb:> Matthias Wuerthele wrote: >> Hi Paul, >> i already found your posting. >> In my case your solution did not work. When i use debootstrap to >> install feisty i have /etc/event.d/tty 1-6. I copied tty2 into tty0 >> and changed everything in it referencing to tty2 to tty0 but i have >> still the same issue. The console gets stuck during bootup. I can >> close console (Ctrl5) and open it again. There are no errors or >> something but a black screen. >> Matthias > Can you ssh into the DomU? You can also try shutting down the DomU > and mounting the filesystem. Anything odd in /var/log/syslog?_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien CRAMATTE
2007-Jul-26 18:21 UTC
Re: [Xen-users] Console hangs on Xen 3.1 Ubuntu Feisty Server
Hello I''ve got the same issue with etch o feisty domU ! My hardware is E6600 core duo + P35 motherboard + Xen 3.1 + Ubuntu feisty server 64 bits Any tips to resolve the problem ...? Matthias Wuerthele escribió:> I installed ssh using chroot so i can access the domU. /var/log/syslog > does not contain any special errors > The last line i can see in the console (using xm console...) is: lo: > Disabled Privacy Extensions > In syslog however there are 2 more lines but nothing interesting: > ----snip---- > Adding 524280k swap on /dev/sda1. Priority:-1 extents:1 across:524280k > EXT3 FS on sda2, internal journal > eth0: no IPv6 routers present > ----snap---- > The system can be used without problems. I can install software using > apt-get or ping my network... > I just noticed one more thing. If i am going to reboot the domU using > the ssh connection and a simple ''reboot'' my > xen console shows one more thing: ''Restarting system.'' So its not > really dead its just like its not connected to the domU standard tty > anymore. Maybe i have to specify this somewhere. This is something i > will have to google for because i am not familiar with this part of > linux yet. (still learning :-) > Matthias > > Paul Waldo schrieb: >> Matthias Wuerthele wrote: >>> Hi Paul, >>> i already found your posting. >>> In my case your solution did not work. When i use debootstrap to >>> install feisty i have /etc/event.d/tty 1-6. I copied tty2 into tty0 >>> and changed everything in it referencing to tty2 to tty0 but i have >>> still the same issue. The console gets stuck during bootup. I can >>> close console (Ctrl5) and open it again. There are no errors or >>> something but a black screen. >>> Matthias >> Can you ssh into the DomU? You can also try shutting down the DomU >> and mounting the filesystem. Anything odd in /var/log/syslog? > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien CRAMATTE
2007-Jul-27 11:41 UTC
Re: [Xen-users] RESOLVED !!!! Console hangs on Xen 3.1 Ubuntu Feisty Server
Hello, I''ve found a solution to the Console Hangs on Feisty ... Many thanks to JuanJo''s BLOG (http://juanjosec.blogspot.com/2007/06/migrating-xen-installation-from-fc5-to.html) For a "feisty" DomU you must create /etc/event.d/xvc0 file -------- # xvc0 - getty # # This service maintains a getty on xvc0 from the point the system is # started until it is shut down again. start on runlevel 2 start on runlevel 3 stop on runlevel 0 stop on runlevel 1 stop on runlevel 4 stop on runlevel 5 stop on runlevel 6 respawn exec /sbin/getty 38400 xvc0 ------- For an "etch" domU you must edit /etc/inittab -------- ... x0:2345:respawn:/sbin/getty 38400 xvc0 ... -------- I believe that you must install udev inside etch domU ... To finish in "/etc/securetty" you should add a line with "xvc0" -------- # /etc/securetty: list of terminals on which root is allowed to login. # See securetty(5) and login(1). console # for people with serial port consoles ttyS0 # for devfs tts/0 # for xen console xvc0 # Standard console tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 ------- Hope that help ;) Regards _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steve Kemp
2007-Jul-27 11:57 UTC
Re: [Xen-users] RESOLVED !!!! Console hangs on Xen 3.1 Ubuntu Feisty Server
On Fri Jul 27, 2007 at 13:41:43 +0200, S?bastien CRAMATTE wrote:> I''ve found a solution to the Console Hangs on Feisty ...[using xvc0 instead of ttyS0, etc] I''ve seen this reported as a bug against xen-tools but I''ve never known why. <http://bugs.debian.org/423389> When, specifically, is xvc0 used? Steve -- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien CRAMATTE
2007-Jul-27 12:02 UTC
Re: [Xen-users] RESOLVED !!!! Console hangs on Xen 3.1 Ubuntu Feisty Server
Steve Kemp escribió:> On Fri Jul 27, 2007 at 13:41:43 +0200, S?bastien CRAMATTE wrote: > > >> I''ve found a solution to the Console Hangs on Feisty ... >> > > [using xvc0 instead of ttyS0, etc] > > I''ve seen this reported as a bug against xen-tools but I''ve never > known why. <http://bugs.debian.org/423389> > > When, specifically, is xvc0 used? > > Steve >Seems that is problem with xen 3.1 only ... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Rafał Kupka
2007-Jul-27 15:03 UTC
Re: [Xen-users] RESOLVED !!!! Console hangs on Xen 3.1 Ubuntu Feisty Server
On Fri, Jul 27, 2007 at 02:02:34PM +0200, Sébastien CRAMATTE wrote:> Steve Kemp escribió:Hello,> > When, specifically, is xvc0 used? > > > > Steve > > > Seems that is problem with xen 3.1 only ...It depends on DomU kernel. Newer ones do use xvc0. I have Xen 3.0.3-1 and 2.6.20 kernel[1] (with fedora-2.6.20-48670.patch) and DomUs have console on /dev/xvc0 (major 204, minor 191). Patch fragment about file drivers/xen/console/console.c says: * Modes: * ''xencons=off'' [XC_OFF]: Console is disabled. * ''xencons=tty'' [XC_TTY]: Console attached to ''/dev/tty[0-9]+''. * ''xencons=ttyS'' [XC_SERIAL]: Console attached to ''/dev/ttyS[0-9]+''. * ''xencons=xvc'' [XC_XVC]: Console attached to ''/dev/xvc0''. * [XC_DEFAULT]: DOM0 -> XC_SERIAL ; all others -> XC_TTY. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ but on my system default on DomUs is xvc (no xencons= kernel parameter) Kupson [1] Old debian sid kernel, last one with Xen patch included. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users