[Bug 708025] New: xm console <domain> does not work: xenconsole: Could not read tty from store: No such file or directory
https://bugzilla.novell.com/show_bug.cgi?id=708025 https://bugzilla.novell.com/show_bug.cgi?id=708025#c0 Summary: xm console <domain> does not work: xenconsole: Could not read tty from store: No such file or directory Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas@novell.com ReportedBy: heigu@gmx.de QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=442080) --> (http://bugzilla.novell.com/attachment.cgi?id=442080) xm dmesg User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 I have running two (productive) paravirtualized domU on Xen version 4.0.2_02-4.9.2. My first problem is that I cannot get into the console anymore: # xm console os111-mailserver xenconsole: Could not read tty from store: No such file or directory but xenconsoled and xenstored are running: # ps -efl ... 5 S root 2123 1 0 80 0 - 5680 futex_ Jul23 ? 00:00:00 xenconsoled --pid-file=/var/run/xenconsoled.pid 4 S root 2133 1 0 80 0 - 15791 - Jul23 ? 00:00:00 /usr/sbin/cupsd -C /etc/cups/cupsd.conf 1 S root 2135 1 0 80 0 - 19069 353875 Jul23 ? 00:00:09 /usr/bin/perl /usr/libexec/webmin/miniserv.pl /etc/webmin/miniserv.conf 5 S ntp 2175 1 0 80 0 - 7093 - Jul23 ? 00:00:05 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf 1 S root 2202 1 0 80 0 - 992 3 Jul23 ? 00:00:04 /usr/sbin/nscd 1 S root 2213 2 0 80 0 - 0 netbk_ Jul23 ? 00:17:04 [netback/0] 1 S root 2214 2 0 80 0 - 0 netbk_ Jul23 ? 00:18:06 [netback/1] 1 S root 2215 2 0 80 0 - 0 netbk_ Jul23 ? 00:00:00 [netback/2] 1 S root 2216 2 0 80 0 - 0 netbk_ Jul23 ? 00:00:00 [netback/3] 4 S root 2298 1 0 80 0 - 5142 140221 Jul23 ? 00:00:00 /usr/lib/postfix/master 1 S root 2323 1 0 80 0 - 3347 - Jul23 ? 00:00:00 /usr/sbin/cron 4 S postfix 2329 2298 0 80 0 - 5228 184466 Jul23 ? 00:00:00 qmgr -l -t fifo -u 5 S nagios 2358 1 0 80 0 - 4121 214816 Jul23 ? 00:00:09 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d 5 S root 2370 1 0 80 0 - 4651 - Jul23 ? 00:00:00 /usr/sbin/smartd 5 S root 2377 1 0 80 0 - 2122 - Jul23 ? 00:00:03 xenstored --pid-file /var/run/xenstore.pid 1 S root 2384 1 0 80 0 - 29698 wait Jul23 ? 00:00:00 /usr/bin/python /usr/sbin/xend start 1 S root 2385 1 0 80 0 - 29346 429496 Jul23 ? 00:00:05 blktapctrl 5 S root 2386 2384 0 80 0 - 68092 184466 Jul23 ? 00:03:38 /usr/bin/python /usr/sbin/xend start 1 S root 3000 2 0 60 -20 - 0 loop_t Jul23 ? 00:00:00 [loop0] 1 S root 3030 2 0 80 0 - 0 blkif_ Jul23 ? 00:00:17 [blkback.1.xvda] 1 S root 3032 2 0 80 0 - 0 blkif_ Jul23 ? 00:00:00 [blkback.1.xvdb] 1 S root 3033 2 0 80 0 - 0 blkif_ Jul23 ? 00:00:01 [blkback.1.xvdc] 1 S root 3290 2 0 60 -20 - 0 loop_t Jul23 ? 00:00:00 [loop1] 1 S root 3303 2 0 80 0 - 0 blkif_ Jul23 ? 00:00:04 [blkback.2.xvda] 1 S root 3304 2 0 80 0 - 0 blkif_ Jul23 ? 00:00:00 [blkback.2.xvdb] 4 S postfix 3703 2298 0 80 0 - 5133 140105 11:45 ? 00:00:00 pickup -l -t fifo -u 4 S root 4040 1 0 80 0 - 990 - Jul23 tty1 00:00:00 /sbin/mingetty --noclear tty1 4 S root 4041 1 0 80 0 - 990 - Jul23 tty2 00:00:00 /sbin/mingetty tty2 4 S root 4042 1 0 80 0 - 990 - Jul23 tty3 00:00:00 /sbin/mingetty tty3 4 S root 4043 1 0 80 0 - 990 - Jul23 tty4 00:00:00 /sbin/mingetty tty4 4 S root 4044 1 0 80 0 - 990 - Jul23 tty5 00:00:00 /sbin/mingetty tty5 4 S root 4045 1 0 80 0 - 990 - Jul23 tty6 00:00:00 /sbin/mingetty tty6 5 S root 4108 567 0 78 -2 - 5323 - 11:46 ? 00:00:00 /sbin/udevd --daemon 5 S root 4163 567 0 78 -2 - 5323 - 11:46 ? 00:00:00 /sbin/udevd --daemon 1 S root 4334 2 0 60 -20 - 0 loop_t 11:46 ? 00:00:00 [loop2] 1 S root 4422 2 0 80 0 - 0 blkif_ 11:46 ? 00:00:00 [blkback.13.xvda] 1 S root 4423 2 0 80 0 - 0 blkif_ 11:46 ? 00:00:00 [blkback.13.xvdb] 1 S root 4424 2 0 80 0 - 0 blkif_ 11:46 ? 00:00:00 [blkback.13.xvdc] 1 S root 4893 2 0 80 0 - 0 bdi_wr 12:00 ? 00:00:00 [flush-253:2] 4 R root 5059 31498 0 80 0 - 1156 - 12:13 pts/1 00:00:00 ps -efl 1 S root 8016 2 0 80 0 - 0 worker Jul24 ? 00:00:00 [kworker/4:2] 1 S root 11682 2 0 80 0 - 0 worker Jul24 ? 00:00:00 [kworker/0:2] 1 S root 30591 1 0 80 0 - 25632 429496 08:44 ? 00:00:02 4 S root 31490 2109 0 80 0 - 19314 - 09:12 ? 00:00:00 sshd: root@pts/1 4 S root 31498 31490 0 80 0 - 3746 - 09:12 pts/1 00:00:00 -bash Rebooting the server didn't change anything. The second problem is that vm-install does not work anymore because it has also no access to the console. After answering all questions the following appears: "Installation wird vorbereitet ... Installation ... Konnte die Konsole der VM nicht anzeigen. Bitte verbinden Sie sich mit einem manuellen Viewer." After that vm-install hangs until i destroyed the domain in a new putty session. The problems were starting with the fact that i could not create a new domain with vm-install with a certain dvd-iso file (openSUSE 11.1) which was not a problem before different times. Maybe it was a mistake i made before, that i mounted (and umounted) xvdb (the iso file in the domain config) in a domU. Later i was reading that this shouldn't be done in a paravirtualized guest. I didn't try restart xend until now because i fear that the guests will not start properly. However, i don't know if it is a bug or something is getting corrupt in the xen system. Reproducible: Always Steps to Reproduce: 1.1 xm console <domain> 2.1 vm-install Actual Results: as described above Expected Results: as described above -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c1
Charles Arnold
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c2
Frank Frewer
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c3
Preston Millett
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c4
--- Comment #4 from Frank Frewer
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c5
--- Comment #5 from Preston Millett
I just added the ip to the file and changed maxmem:
name="os111-mailserver" description="None" uuid="f5a0ea0c-43b0-77af-fc24-301f6e2413f5" memory=512 maxmem=1024 vcpus=1 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 keymap="de" builder="linux" bootloader="/usr/bin/pygrub" bootargs="" extra="xencons=tty " disk=[ 'phy:/dev/vg0base/xen-2,xvda,w', 'file:/images/openSUSE-11.1-DVD-i586.iso,xvdb:cdrom,r', 'phy:/dev/vg0base/xen-2-add,xvdc,w', ] vif=[ 'mac=00:16:3e:5d:32:47,ip=178.63.xxx.xx' ] nographic=1
Did you try to mount and umount xvdb (the iso file in the domain config) in the guest?
Yes I did mount and unmount the disk. It seemed to have no effect on the guest or my ability to attach to the console. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c6
Jon Schewe
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c7
--- Comment #7 from Jon Schewe
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c
James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c8
--- Comment #8 from Preston Millett
I too have seen this problem. It typically occurs after the vm reboots. When I initially start up the vm I'm able to connect with "xm console <domain>", however after the vm reboots and definitely if the vm is saved and then restored I can no longer connect to the console. This worked under opensuse 11.2 and the xen 3.x version that was shipped with it. This problem only occurred once I upgraded to opensuse 11.4 and xen 4.x.
Was the VM created using vm-install using os11.4, or was it created using os11.2 and then upgraded to 11.4 with the issue appearing after the upgrade? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c9
--- Comment #9 from Jon Schewe
(In reply to comment #6)
I too have seen this problem. It typically occurs after the vm reboots. When I initially start up the vm I'm able to connect with "xm console <domain>", however after the vm reboots and definitely if the vm is saved and then restored I can no longer connect to the console. This worked under opensuse 11.2 and the xen 3.x version that was shipped with it. This problem only occurred once I upgraded to opensuse 11.4 and xen 4.x.
Was the VM created using vm-install using os11.4, or was it created using os11.2 and then upgraded to 11.4 with the issue appearing after the upgrade?
The VM was created in 11.2 manually (not using vm-install) and then upgraded to 11.4 and the issue appeared after the upgrade. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c10
--- Comment #10 from James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c11
James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c12
Jon Schewe
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c13
--- Comment #13 from James Fehlig
I'm not building from source, so these paths aren't very helpful. Where do these patches apply on a live system?
You can patch the python code directly with no need to build packages. Save /usr/lib64/python/site-packages/xen/xend/XendCheckpoint.py and /usr/lib64/python/site-packages/xen/xend/XendDomainInfo.py before applying the patch and then e.g. # cd /usr/lib64/python/site-packages/ # patch -p3 < /path/to/patch # rcxend restart
If this fixed bugs in SLES, any particular reason that it's not being pushed to opensuse?
It was just reported in SLES, with customer providing positive feedback on the patch. The fix will be pushed in next SLES update, and next openSUSE one if the patch fixes your problem :-). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c14
--- Comment #14 from Jon Schewe
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c15
--- Comment #15 from James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c16
--- Comment #16 from James Fehlig
Hmm, I think you'll need this patch as well. I've tested it, along with patch in #14,
Err, I meant patch in comment #10... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c17
--- Comment #17 from Frank Frewer
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c18
--- Comment #18 from Frank Frewer
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c19
Jon Schewe
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c20
James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c21
--- Comment #21 from Frank Frewer
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c22
--- Comment #22 from James Fehlig
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c23
--- Comment #23 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c24
--- Comment #24 from Frank Frewer
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c25
--- Comment #25 from James Fehlig
After updating and rebooting the dom0 (without shutting down the guests) I had no access to the console again. But rebooting the guests "repairs" it.
What do you mean by "rebooting the dom0 without shutting down guests"? Guests have to get shutdown, saved, or migrated away on dom0 shutdown or reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c26
--- Comment #26 from Frank Frewer
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c27
--- Comment #27 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c28
--- Comment #28 from James Fehlig
I mean that I didn't shutdown the guests before I were rebooting the dom0.
OK, so xendomains script shutdown the guests when dom0 was rebooted.
Do you mean that I have to shutdown the guests manually? Or is there a possibility to configure xen to shutdown all guests automatically on shutdown of the dom0?
The xendomains init scripts handles shutdown of guests when dom0 is shutdown. It can also be configured to start guests when dom0 is started. Or to save guests on dom0 shutdown and restore when dom0 is started. Or to migrate the guests to another machine when dom0 is shutdown. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c29
--- Comment #29 from Frank Frewer
Does this issue happen also with the updated packages, or did you see it only once while dom0 ran the broken tools and thus created kind-of broken guests?
I will test it this night and will give you feedback if it happens again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c30
--- Comment #30 from Olaf Hering
The xendomains init scripts handles shutdown of guests when dom0 is shutdown. It can also be configured to start guests when dom0 is started. Or to save guests on dom0 shutdown and restore when dom0 is started. Or to migrate the guests to another machine when dom0 is shutdown.
However, with ${xm_cmd} being xl now, that does not really work because it lacks the --force knob. sigh... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c31
--- Comment #31 from James Fehlig
However, with ${xm_cmd} being xl now, that does not really work because it lacks the --force knob. sigh...
In 12.1/Factory yes. But this bug is 11.4 where xm_cmd doesn't exist in xendomains script. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c32
--- Comment #32 from Frank Frewer
Does this issue happen also with the updated packages, or did you see it only once while dom0 ran the broken tools and thus created kind-of broken guests?
The result of my test: It happens again. I rebooted the dom0 and after that I had no access to the console again. Rebooting the guests "repairs" it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c33
--- Comment #33 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c34
Frank Frewer
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c35
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=708025
https://bugzilla.novell.com/show_bug.cgi?id=708025#c
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=708025
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com