https://bugzilla.novell.com/show_bug.cgi?id=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c A R changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c2 --- Comment #2 from A R 2013-06-18 09:08:53 UTC ---

for 2), it looks like a xen kernel bug, you should fill a separate bug report.

done. "Bug 825510 - "shutdown -r now" fails @ Xen 4.3.0 Dom0 -- systems halts, but does not restart" https://bugzilla.novell.com/show_bug.cgi?id=825510

for 1): ... Are you sure your xen packages are ok ?

I'm not sure what this tells me rpm -V xen-tools S.5....T. c /etc/xen/xl.conf cat /etc/xen/xl.conf autoballoon=0 where, http://wiki.xen.org/wiki/Xen_Best_Practices If you are using the XL toolstack this can be done by editing /etc/xen/xl.conf and setting autoballoon=0. This will prevent XL from ever automatically adjusting the amount of memory assigned to dom0. -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c4 --- Comment #4 from A R 2013-06-18 09:20:02 UTC --- this is odd ... systemctl status xendomains.service xendomains.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) Jun 05 22:44:48 testsvr.loc xendomains[14925]: template: saving... ..done Jun 05 22:44:48 testsvr.loc systemd[1]: Stopped LSB: Starts and stops Xen VMs. Jun 05 22:10:59 testsvr.loc systemd[1]: Starting LSB: Starts and stops Xen VMs... Jun 05 22:10:59 testsvr.loc xendomains[1853]: Restoring saved Xen domains Jun 05 23:11:24 testsvr.loc logger[4060]: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/51744 Jun 05 23:11:24 testsvr.loc xendomains[1853]: template: ..done Jun 05 23:11:24 testsvr.loc xendomains[1853]: Starting auto Xen domains Jun 05 23:11:25 testsvr.loc xendomains[1853]: test.cfg: ..skipped Jun 05 23:11:25 testsvr.loc systemd[1]: Started LSB: Starts and stops Xen VMs. Jun 13 13:40:29 testsvr.loc systemd[1]: Stopping LSB: Starts and stops Xen VMs... nothing since Jun 13? perhaps a forced Xen* reinstall is called for? -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c6 --- Comment #6 from A R 2013-06-18 10:28:49 UTC --- zypper in --force xen-tools Forcing installation of 'xen-tools-4.3.0_03-251.5.x86_64' from repository 'XEN4'. Resolving package dependencies... The following package is going to be reinstalled: xen-tools 1 package to reinstall. Overall download size: 8.1 MiB. No additional space will be used or freed after the operation. Continue? [y/n/?] (y): Retrieving package xen-tools-4.3.0_03-251.5.x86_64 (1/1), 8.1 MiB ( 18.4 MiB unpacked) Retrieving: xen-tools-4.3.0_03-251.5.x86_64.rpm ....................[done] (1/1) Installing: xen-tools-4.3.0_03-251.5 .........................[done] Additional rpm output: Updating /etc/sysconfig/xencommons... /var/tmp/rpm-tmp.g7yKAJ: line 137: /etc/init.d/xendomains: No such file or directory Updating /etc/sysconfig/pciback... grep baseurl /etc/zypp/repos.d/XEN4.repo baseurl=http://ftp.halifax.rwth-aachen.de/opensuse/repositories/Virtualization/openS... ls -al /etc/init.d/xen* ls: cannot access /etc/init.d/xen*: No such file or directory shutdown -r now ... cold restart ... xendomains.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) ... same as above, Jun 13 last entry ??? -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c8 --- Comment #8 from A R 2013-06-19 09:07:40 UTC --- I'd moved long ago to Xen 4.3.0, based on discussions/support @Xen team. Xen < v4.3 is no longer an option here. Thanks for x-fer; I'll work with the Xen team on this. -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c9 A R changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |carnold@suse.com --- Comment #9 from A R 2013-07-03 04:47:01 UTC --- Using Xen 4.3, there's no `xendomains.service` installed. *NO* guests are auto-launched on boot. Is this by design, requiring other config? Or is this a bug, requiring a fix? -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c10 --- Comment #10 from Charles Arnold 2013-07-08 20:30:03 UTC --- I'm looking into this now. It looks like we are missing the file from xen-tools package. -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c12 --- Comment #12 from A R 2013-07-09 03:18:34 UTC ---

use virt-manager

I've no GUI on my servers. In any case, I'd had problems with virt-manager some time in the past; removed it, and never went back. Imo, it adds more complexity than needed --another package/daemon (aka, possible point of failure) to the Dom0, etc. For production, I simply create/edit /etc/xen/auto/foo.cfg's by hand. Nice and clean that way. -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c14 A R changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ar16@imapmail.org | --- Comment #14 from A R 2013-07-09 23:43:56 UTC --- Upgrading to rpm -qa | grep -i ^xen xen-4.3.0_07-258.1.x86_64 xen-devel-4.3.0_07-258.1.x86_64 xen-tools-4.3.0_07-258.1.x86_64 xen-libs-4.3.0_07-258.1.x86_64 'enabling' the service (should xen* inits be made *native* systemd services now that sysvinit's deprecated ?) systemctl enable xendomains.service with ls -al /etc/xen/auto/testguest.cfg lrwxrwxrwx 1 root root 64 Mar 13 22:37 /etc/xen/auto/testguest.cfg -> /home/xen/VMs/testguest.cfg after shutdown -r now guest is correctly auto-launched xl list Name ID Mem VCPUs State Time(s) Domain-0 0 986 4 r----- 37.4 template 1 1024 0 --p--- 0.0 and I can ssh into the guest as always, either as 'root' or 'myuser', ssh -l root testguest.lan Last login: Tue Jul 9 16:30:03 2013 from 10.10.120.17 or ssh -l myuser testguest.lan Last login: Tue Jul 9 16:32:02 2013 from 10.10.120.17 but I ca no longer login to the guest console @ DomU shell as 'root' anymore, only as 'myuser' xl console 1 ctrl-] Welcome to openSUSE 12.3 "Dartmouth" - Kernel 3.7.10-1.11-xen (xvc0). testguest: root Login incorrect testguest: root Login incorrect testguest: myuser Password: XXXXXXX Last login: Tue Apr 30 09:38:10 on xvc0 Have a lot of fun... somthing's change; this is new (mis)behavior. digging as to cause now ... -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c16 --- Comment #16 from A R 2013-07-09 23:53:15 UTC --- adding vi /etc/securetty ... + xvc0 fixes the no-root-login-at-console issue. i've not had that added on any of my guests to date. they're all responding properly. i guess a change to Xen that I've missed? -- 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=825501 https://bugzilla.novell.com/show_bug.cgi?id=825501#c18 darx suse changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |darx+opensuse@sent.com --- Comment #18 from darx suse 2013-07-10 15:40:12 UTC ---

This is normally set by the 'yast2 xen' program at install time. I installed an os12.3 PV guest (used defaults) and the xvc0 was there.

None of my guests (started as minimal installs, then added to as needed) have ever had yast2-vm installed. Again, odd. I'd always been able to -- previously -- get to my Guest consoles. The requirements for the /etc/securetty seems to be new, or is recently being enforced. I'd suggest console functionality is a basic requirement of a Xen install. Perhaps -- to make sure this works -- moving the /etc/securetty install/modify script into Guests' "xen-tools-domU" packages, or adding a dep from xen-libs to yast2-vm pkg? In any case -- resolved here. Thanks. -- 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.