Bug#472584: marked as done (linux-image-2.6.24-1-xen-686: Doesn't work as DomU)
Your message dated Sun, 14 Sep 2008 01:35:34 +0200 with message-id [EMAIL PROTECTED] and subject line user error has caused the Debian Bug report #472584, regarding linux-image-2.6.24-1-xen-686: Doesn't work as DomU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 472584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472584 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-xen-686 Version: 2.6.24-4 Severity: important When I try to use it as a DomU (with 2.6.18-6-xen-686 from Etch as Dom0) it doesn't boot. Nothing is displayed on the console and nothing appears to happen, it uses a small amount of CPU time and does nothing else. I have a DomU that I have tested with both 2.6.18-6-xen-686 and linux-image-2.6.24-1-xen-686 as the kernel, with 2.6.18-6-xen-686 it works but with linux-image-2.6.24-1-xen-686 it doesn't. The command xm dmesg includes the following in it's output, not sure if it's relevant: (XEN) traps.c:1946:d12 Domain attempted WRMSR 0404 from :0001 to :. (XEN) traps.c:1946:d12 Domain attempted WRMSR 0408 from 00344600:00344600 to :. (XEN) traps.c:1946:d12 Domain attempted WRMSR 040c from :0001 to :. (XEN) traps.c:1946:d12 Domain attempted WRMSR 0410 from 0008:0008 to :. (XEN) traps.c:1946:d12 Domain attempted WRMSR 0401 from 1000: to :. (XEN) traps.c:1946:d12 Domain attempted WRMSR 0411 from 2200:0011 to :. Here is the xm info output: host : unstable0 release: 2.6.18-6-xen-686 version: #1 SMP Sun Feb 10 22:43:13 UTC 2008 machine: i686 nr_cpus: 1 nr_nodes : 1 cores_per_socket : 1 threads_per_core : 1 cpu_mhz: 1102 hw_caps: 0383fbff:::0040 total_memory : 503 free_memory: 162 node_to_cpu: node0:0 xen_major : 3 xen_minor : 2 xen_extra : -1 xen_caps : xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0xf580 xen_changeset : unavailable cc_compiler: gcc version 4.2.3 (Debian 4.2.3-1) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date: Tue Feb 19 00:26:54 UTC 2008 xend_config_format : 4 ---End Message--- ---BeginMessage--- We found all problems as user error. Closing. Bastian -- You're too beautiful to ignore. Too much woman. -- Kirk to Yeoman Rand, The Enemy Within, stardate unknown ---End Message---
Bug#472584:
Dear Bastian: Many thanks for responding to the sketchy bug reports. Thanks to your help here, I have managed to get the linux-image-2.6.24-1-xen-686 kernel running as a domU kernel. The only remaining issue seems to be that, for me, the domU console (from xmcreate -c or from xm console) does not accept input; but that is bearable. I have listed the changes I made in a brief form below. I wonder whether it might be worth making something like this available, perhaps as a README.debian in /usr/share/doc/linux-image-2.6.24-N-xen-686 ? It could (judging by quite a few mailing list posts) be of some use to those who, like me, prefer to use testing (lenny) as their dom0, for reasons of security and relative stability. Thanks again for your help, and for all your debian efforts. Barry Tennison *** The following may be needed to convert a debian installation using 2.6.18 kernels to use a 2.6.24 kernel. (a) use a 2.6.18 xen kernel in the dom0 (see bug#466492) (b) modify the relevant xen domU .cfg files by: * changing entries like root=/dev/hdaN ro to root=/dev/xvdaN ro * adding (or expanding) a line to read: extra=console=hvc0 * possibly adding to the extra= line something like rootdelay=5 (increase or decrease the 5 seconds according to what works) (c) in the domU rootfs, aptitude install linux-modules-2.6.24-1-xen-686 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472584:
On Mon, Mar 31, 2008 at 09:11:38AM +1100, Russell Coker wrote: I think it's reasonable to expect a Lenny kernel to work in the same manner as an Etch kernel and to consider any failure to do so to be a bug. Well, this is not possible in this case because they added code to hijack other devices _and_ proposed the usage by default with the knowledge that Linus won't ever accept this. The above is what I was using. I added the console=hvc0 bit as you suggested (why is that needed?) and it displayed some console messages, Because there is not code which overrides the default console. Fedora have a patch, maybe I'll pull them in for now. mount: Mounting /dev/xvda on /root failed: No such device Contents of /dev? /sys/block? Bastian -- Get back to your stations! We're beaming down to the planet, sir. -- Kirk and Mr. Leslie, This Side of Paradise, stardate 3417.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472584:
On Mon, Mar 31, 2008 at 09:26:32PM +0200, Bastian Blank wrote: Contents of /dev? /sys/block? Oh, and xenstore-ls /local/domain/$domid. Bastian -- A little suffering is good for the soul. -- Kirk, The Corbomite Maneuver, stardate 1514.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472584:
On Tuesday 01 April 2008 06:26, Bastian Blank [EMAIL PROTECTED] wrote: On Mon, Mar 31, 2008 at 09:11:38AM +1100, Russell Coker wrote: I think it's reasonable to expect a Lenny kernel to work in the same manner as an Etch kernel and to consider any failure to do so to be a bug. Well, this is not possible in this case because they added code to hijack other devices _and_ proposed the usage by default with the knowledge that Linus won't ever accept this. Do we have people with enough spare time to fix this foolishness? The above is what I was using. I added the console=hvc0 bit as you suggested (why is that needed?) and it displayed some console messages, Because there is not code which overrides the default console. Fedora have a patch, maybe I'll pull them in for now. Fedora also messes things up. /dev/tty0 doesn't work for a getty with a Fedora/RHEL/CentOS kernel in a DomU. mount: Mounting /dev/xvda on /root failed: No such device Contents of /dev? /sys/block? (initramfs) ls -l /sys/block/xvda -r--r--r--1 004096 Mar 31 21:55 capability -r--r--r--1 004096 Mar 31 21:55 dev lrwxrwxrwx1 00 0 Mar 31 21:55 device - ../../devices/vbd-51712 drwxr-xr-x2 00 0 Mar 31 21:55 holders drwxr-xr-x3 00 0 Mar 31 21:55 queue -r--r--r--1 004096 Mar 31 21:55 range -r--r--r--1 004096 Mar 31 21:55 removable -r--r--r--1 004096 Mar 31 21:55 size drwxr-xr-x2 00 0 Mar 31 21:55 slaves -r--r--r--1 004096 Mar 31 21:55 stat lrwxrwxrwx1 00 0 Mar 31 21:55 subsystem - ../../block --w---1 004096 Mar 31 21:55 uevent (initramfs) ls -l /dev/xvda brw-rw1 00202, 0 Mar 31 21:55 /dev/xvda xenstore-ls /local/domain/$domid gives the following: vm = /vm/5787f4aa-a61e-c6b7-ce50-6a507cc9233c device = vbd = 51712 = virtual-device = 51712 device-type = disk protocol = x86_32-abi backend-id = 0 state = 4 backend = /local/domain/0/backend/vbd/23/51712 ring-ref = 8 event-channel = 6 vif = 0 = mac = 00:16:3e:66:66:69 handle = 0 protocol = x86_32-abi backend-id = 0 state = 4 backend = /local/domain/0/backend/vif/23/0 tx-ring-ref = 768 rx-ring-ref = 769 event-channel = 7 request-rx-copy = 1 feature-rx-notify = 1 feature-sg = 1 feature-gso-tcpv4 = 1 console = 0 = protocol = x86_32-abi state = 1 backend-id = 0 backend = /local/domain/0/backend/console/23/0 device-misc = vif = nextDeviceID = 1 console = nextDeviceID = 1 console = ring-ref = 77958 port = 2 limit = 1048576 type = xenconsoled tty = /dev/pts/2 image = entry = 3224522752 pae-mode = yes loader = generic virt-base = 3221225472 features = pae-pgdir-above-4gb = 1 writable-page-tables = 0 xen-version = xen-3.0 guest-os = linux hypercall-page = 3224731648 guest-version = 2.6 store = ring-ref = 77959 port = 1 cpu = 0 = availability = online control = platform-feature-multiprocessor-suspend = 1 name = play-test domid = 23 memory = target = 102400 serial = 0 = tty = /dev/pts/2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472584:
On Tue, Apr 01, 2008 at 09:00:57AM +1100, Russell Coker wrote: Fedora also messes things up. /dev/tty0 doesn't work for a getty with a Fedora/RHEL/CentOS kernel in a DomU. /dev/tty0 is a virtual console. A DomU have no virtual consoles except with a framebuffer. mount: Mounting /dev/xvda on /root failed: No such device (initramfs) ls -l /dev/xvda brw-rw1 00202, 0 Mar 31 21:55 /dev/xvda Okay, so this is the old race condition. Use rootdelay=X for now. Bastian -- A little suffering is good for the soul. -- Kirk, The Corbomite Maneuver, stardate 1514.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#472584
Processing commands for [EMAIL PROTECTED]: severity 472584 normal Bug#472584: linux-image-2.6.24-1-xen-686: Doesn't work as DomU Severity set to `normal' from `important' tags 472584 moreinfo Bug#472584: linux-image-2.6.24-1-xen-686: Doesn't work as DomU There were no tags set. Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472584:
severity 472584 normal tags 472584 moreinfo thanks I think you know how to report bugs. Pardon, this does not even include the minimal information to say anything, e.g. the kernel command line as specified in the xen config file. From the symptoms I would say you want to check that command line, it needs to include console=hvc0. Bastian -- The man on tops walks a lonely street; the chain of command is often a noose. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#472584:
On Monday 31 March 2008 04:57, Bastian Blank [EMAIL PROTECTED] wrote: I think you know how to report bugs. Pardon, this does not even include the minimal information to say anything, e.g. the kernel command line as specified in the xen config file. From the symptoms I would say you want to check that command line, it needs to include console=hvc0. I think it's reasonable to expect a Lenny kernel to work in the same manner as an Etch kernel and to consider any failure to do so to be a bug. kernel = /boot/vmlinuz-2.6.24-1-xen-686 ramdisk = /boot/initrd.img-2.6.24-1-xen-686 memory = 100 name = play-test vif = [ 'mac=00:16:3e:66:66:69, bridge=xenbr0' ] disk = [ 'phy:/dev/play0/play-snap,hda,w' ] root = /dev/hda ro extra = 2 audit=1 selinux=1 enforcing=1 The above is what I was using. I added the console=hvc0 bit as you suggested (why is that needed?) and it displayed some console messages, but couldn't find /dev/hda. I changed it to /dev/xvda with the following and it still didn't work: disk = [ 'phy:/dev/play0/play-snap,xvda,w' ] root = /dev/xvda ro extra = 2 audit=1 selinux=1 enforcing=1 console=hvc0 Here is the last section of the console output: mount: Mounting /dev/xvda on /root failed: No such device Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory Done. mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init. No init found. Try passing init= bootarg. BusyBox v1.1.3 (Debian 1:1.1.3-5) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned off (initramfs) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
