[opensuse-virtual] "EVTCHNOP failure" @ OS 12.3 + Xen 4.3 boot for some Guests; launch manually OK
I've recently upgraded pkgs an Opensuse 12.3 + XEN 4.3 (xen-4.3.0_08-264.1.x86_64) server. It's got two guests set for auto-launch @ boot. It's been working fine for awhile. The guest cfg's have not changed in ages. Just the upgrade has occured recently. Now, reproducibly after boot, one Guest is missing, xl list Name ID Mem VCPUs State Time(s) (null) 0 985 4 r----- 44.2 <====== Why "(null)" here? systemd? test2 2 1024 4 -b---- 13.3 but launches manually xl create /etc/xen/auto/test1.cfg xl list Name ID Mem VCPUs State Time(s) (null) 0 985 4 r----- 48.2 test2 2 1024 4 -b---- 13.8 test1 3 768 2 -b---- 2.3 and functions normally. checking xen boot logs, I find these, new failures xl dmesg ... [ OK ] Started Haveged Entropy Gathering Daemon. [ OK ] Started Restore Sound Card State. [ OK ] Started LSB: irqbalance daemon providing irq balancing on MP-machines. [ OK ] Started LSB: Framebuffer setup. [ 35.614880] Event-channel device installed. [ 35.677851] usbcore: registered new interface driver usbback [ 35.711552] pciback: backend is vpci [ 35.748410] blktap_device_init: blktap device major 252 Welcome to openSUSE 12.3 "Dartmouth" - Kernel 3.7.10-1.16-xen (xvc0). testsvr login: (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 [ OK ] Started LSB: Configure network interfaces and set up routing. [ OK ] Reached target Network. Starting Command Scheduler... ... Those "event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22" errors are new to me. Looks like a XEN issue. I've seen recent work on event channel deadlock on the dev list, but my xen's logs don't mention anything evtchn-related since ~ Nov 2011. Before deciding to file a bug, I need to do some local troubleshooting. Any suggestions as to what this might be about, or specific additional info that might be enlightening? AR -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 15.08.13 at 04:17, ar16 <ar16@imapmail.org> wrote: (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22
These being failures of Dom0 trying to bind inter-domain event channels between itself and Dom2, these would quite likely be accompanied by some log entries from the xen tools or the Dom0 kernel. In any case - the failure message here indicates that the event channel either wasn't in "unbound" state, or wasn't intended to be bound to by Dom0. For what it's worth, both seem pretty unlikely... Furthermore, you certainly realize that with the update to Xen 4.3, which isn't part of 12.3, you also got switched from xend/xm to the libxl based tools, which may be part of your problem. Thus it would also be important to know what's so specific about this one failing VM (there ought to be something, or else it wouldn't be always the same VM that fails to come up). Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
These being failures of Dom0 trying to bind inter-domain event channels between itself and Dom2, these would quite likely be accompanied by some log entries from the xen tools or the Dom0 kernel. In any case - the failure message here indicates that the event channel either wasn't in "unbound" state, or wasn't intended to be bound to by Dom0. For what it's worth, both seem pretty unlikely...
Furthermore, you certainly realize that with the update to Xen 4.3, which isn't part of 12.3, you also got switched from xend/xm to the libxl based tools, which may be part of your problem. Thus it would also be important to know what's so specific about this one failing VM (there ought to be something, or else it wouldn't be always the same VM that fails to come up).
That's enough explanation for me to read further on, thanks. The most verbose log anomalies that I've noticed so far I've included above. Nothing else I've noticed in dmesg, xl dmesg, journalctl, serial console output, /var/log/*, etc. I _do_ also find in /var/log/xen/*, cat qemu-dm-test1.log qemu: terminating on signal 1 from pid 1176 and, cat xl-test2.log Waiting for domain pvr (domid 2) to die [pid 2976] Not much detail there. Either I'm not looking in the right places, my logging level isn't sufficient, or there isn't anything else. I'll keep digging on logs. Something's clearly changed recently. Although I've made pkg-upgrades @ Dom0, I haven't made any knowing changes to the failing Guest. The two Guest domains are supposed to be roughly similar; different RAM allocations, basically. They _used_ to both launch @boot without error; they still do, manually. But, a test of 10 reboots resulted in 10 identical @boot failures -- all & only this same Guest. Supports your suggestion that there's something specific to this Guest. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
I've been unable as yet to find anything suspicious/unique about the 'test1' Guest that fails to launch, as above. As an experiment, I moved the 'good' Guest out of the way, ls -1 /etc/xen/auto/ test1.cfg test2.cfg mv /etc/xen/auto/test1.cfg ~/ now, after reboot, xl list Name ID Mem VCPUs State Time(s) (null) 0 985 4 r----- 37.2 test2 1 1024 2 -b---- 7.9 i.e., the previously-failing Guest, 'test2', launches without error. It seems it's not just an issue of this Guest, but the presence of both. Now, back to: why? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Ooops, sry, cp'd the wrong result. Same result for BOTH Guests, alone. My point is that in BOTH cases, the single-guest -- whether it's "test1" or "test2" -- launches without error. If BOTH guests are included to auto-launch, then only the one launches successfully. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Sounds like your generated Guests aren't "unique" enough. Recommend doing a compare between the config files, specifically any/all the following should be unique All ID strings Guest name network settings If any are found to be the same, a manual edit changing just one character or value should probably fix the problem... Tony On Thu, Aug 15, 2013 at 10:13 AM, ar16 <ar16@imapmail.org> wrote:
Ooops, sry, cp'd the wrong result. Same result for BOTH Guests, alone.
My point is that in BOTH cases, the single-guest -- whether it's "test1" or "test2" -- launches without error.
If BOTH guests are included to auto-launch, then only the one launches successfully.
-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Sounds like your generated Guests aren't "unique" enough.
Seems like it. Though I'm a bit suspicious of the fact that the 'failing' guest only fails in the multiple-guest case.
Recommend doing a compare between the config files, specifically any/all the following should be unique
here's a diff of the current configs: http://www.diffchecker.com/olp2438w As you can see, similar, but -- I think -- different enough. Still looking ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
ar16 wrote:
Ooops, sry, cp'd the wrong result. Same result for BOTH Guests, alone.
My point is that in BOTH cases, the single-guest -- whether it's "test1" or "test2" -- launches without error.
If BOTH guests are included to auto-launch, then only the one launches successfully.
Were you using the xl toolstack before the packages were updated? Do both guests start if you run the xendomains script after boot? I.e. disable the script from running at boot, then do '/etc/init.d/xendomains start' after boot. Your suspicion of systemd might warrent some investigation # rpm -q xen --changelog | grep -A 7 systemd - Added support for systemd with the following service files xenstored.service blktapctrl.service xend.service xenconsoled.service xen-watchdog.service xendomains.service xencommons.service Perhaps a bit of tweaking on the xendomains script might give some hints too, e.g. --- /etc/init.d/xendomains.orig 2013-08-15 11:53:39.487569293 -0600 +++ /etc/init.d/xendomains 2013-08-15 11:54:33.440841893 -0600 @@ -34,7 +34,7 @@ $CMD list &> /dev/null if test $? -ne 0 then - CMD=${SBINDIR}/xl + CMD=${SBINDIR}/xl -v HEADCOMP="Xen saved domain" fi @@ -297,7 +297,7 @@ if [ $? -eq 0 ] || is_running $dom; then echo -n "(skip)" else - XMC=`$CMD create --quiet --defconfig $dom` + XMC=`$CMD create --defconfig $dom` if [ $? -ne 0 ]; then echo -e "\nAn error occurred while creating domain ${dom##*/}: $XMC\n" rc_failed $? Regards, Jim -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Thu, Aug 15, 2013, at 11:02 AM, Jim Fehlig wrote:
Were you using the xl toolstack before the packages were updated?
Yes. I've been using Xen 4.3 for quite a long time.
Do both guests start if you run the xendomains script after boot? I.e. disable the script from running at boot, then do '/etc/init.d/xendomains start' after boot.
Yes, without fail or error.
Your suspicion of systemd might warrent some investigation # rpm -q xen --changelog | grep -A 7 systemd - Added support for systemd with the following service files
Noted
Perhaps a bit of tweaking on the xendomains script might give some hints too, e.g. ...
Aha!. Just found that, if I edit BOTH .cfg's, - vcpus = 2 - cpu_cap = 100 - cpu_weight = 256 + #vcpus = 2 + #cpu_cap = 100 + #cpu_weight = 256 then reboot, now BOTH Guests launch, xl list Name ID Mem VCPUs State Time(s) (null) 0 1241 4 r----- 38.9 test1 1 1024 1 -b---- 6.6 test2 2 1024 1 r----- 14.0 Those configs most certainly used to be OK and functional. I can still tweak the xendomains script here in a bit ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
with cat /etc/xen/auto/test1.cfg ---------------------------------------------------------------- name = 'test1' builder = 'linux' bootloader = 'pygrub' bootargs = '' disk = [ 'phy:/dev/VG0/test1_boot,xvda,w', 'phy:/dev/VG0/test1_swap,xvdb,w', 'phy:/dev/VG0/test1_root,xvdc,w', ] root = '/dev/xvdc1' netif = 'yes' vif = [ 'mac=00:16:3E:02:01:00, bridge=br0, vifname=vifT1.int', ] vfb = [ 'type=vnc, vncdisplay=201, vnclisten=127.0.0.1' ] extra = 'textmode=1 xencons=xvc0 noirqdebug elevator=noop' maxmem = 1024 memory = 1024 vcpus = 2 cpu_cap = 100 cpu_weight = 256 localtime = 0 on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' ---------------------------------------------------------------- cat /etc/xen/auto/test2.cfg ---------------------------------------------------------------- name = 'test2' builder = 'linux' bootloader = 'pygrub' bootargs = '' disk = [ 'phy:/dev/VG0/test2_boot,xvda,w', 'phy:/dev/VG0/test2_swap,xvdb,w', 'phy:/dev/VG0/test2_root,xvdc,w', ] root = '/dev/xvdc1' netif = 'yes' vif = [ 'mac=00:16:3E:02:02:00, bridge=br0, vifname=vifT2.int', ] vfb = [ 'type=vnc, vncdisplay=202, vnclisten=127.0.0.1' ] extra = 'textmode=1 xencons=xvc0 noirqdebug elevator=noop' maxmem = 1024 memory = 1024 vcpus = 2 cpu_cap = 100 cpu_weight = 256 localtime = 0 on_shutdown = 'destroy' on_reboot = 'restart' on_crash = 'destroy' ---------------------------------------------------------------- and 'verbose' mods made to xendomains, after boot, xl list Name ID Mem VCPUs State Time(s) (null) 0 1241 4 r----- 39.1 test2 2 1024 2 -b---- 26.7 and, journalctl -b | grep -i xen Aug 15 11:48:48 testsvr.loc kernel: Linux version 3.7.10-1.16-xen (geeko@buildhost) (gcc version 4.7.2 20130108 [gcc-4_7-branch revision 195012] (SUSE Linux) ) #1 SMP Fri May 31 20:21:23 UTC 2013 (97c14ba) Aug 15 11:48:48 testsvr.loc kernel: Command line: xencons=xvc console=tty0 console=xvc0 root=/dev/VG0/ROOT rootfstype=ext4 noresume vga=0x31a log_buf_len=10M earlyprintk=xen nomodeset=0 rootflags=journal_checksum showopts selinux=0 SELINUX_INIT=NO apparmor=0 elevator=cfq clocksource=xen mce=off noquiet Aug 15 11:48:48 testsvr.loc kernel: Xen-provided machine memory map: Aug 15 11:48:48 testsvr.loc kernel: e820: Xen-provided physical RAM map: Aug 15 11:48:48 testsvr.loc kernel: Xen: [mem 0x0000000000000000-0x00000000507fffff] usable Aug 15 11:48:48 testsvr.loc kernel: Kernel command line: xencons=xvc console=tty0 console=xvc0 root=/dev/VG0/ROOT rootfstype=ext4 noresume vga=0x31a log_buf_len=10M earlyprintk=xen nomodeset=0 rootflags=journal_checksum showopts selinux=0 SELINUX_INIT=NO apparmor=0 elevator=cfq clocksource=xen mce=off noquiet Aug 15 11:48:48 testsvr.loc kernel: Xen reported: 2806.472 MHz processor. Aug 15 11:48:48 testsvr.loc kernel: xen_mem: Initialising balloon driver. Aug 15 11:48:48 testsvr.loc kernel: xen/balloon: Xen selfballooning driver disabled for domain0. Aug 15 11:48:48 testsvr.loc kernel: Switching to clocksource xen Aug 15 11:48:48 testsvr.loc kernel: Xen virtual console successfully installed as xvc0 Aug 15 11:48:48 testsvr.loc kernel: usb usb1: Manufacturer: Linux 3.7.10-1.16-xen ehci_hcd Aug 15 11:48:48 testsvr.loc kernel: usb usb2: Manufacturer: Linux 3.7.10-1.16-xen ehci_hcd Aug 15 11:48:48 testsvr.loc kernel: usb usb3: Manufacturer: Linux 3.7.10-1.16-xen ohci_hcd Aug 15 11:48:48 testsvr.loc kernel: usb usb4: Manufacturer: Linux 3.7.10-1.16-xen ohci_hcd Aug 15 11:48:48 testsvr.loc kernel: usb usb5: Manufacturer: Linux 3.7.10-1.16-xen ohci_hcd Aug 15 11:48:48 testsvr.loc kernel: usb usb6: Manufacturer: Linux 3.7.10-1.16-xen ohci_hcd Aug 15 11:48:48 testsvr.loc kernel: usb usb7: Manufacturer: Linux 3.7.10-1.16-xen ohci_hcd Aug 15 11:48:48 testsvr.loc systemd[1]: Expecting device dev-VG0-STORAGE.device... Aug 15 11:48:50 testsvr.loc systemd[1]: Found device /dev/VG0/STORAGE. Aug 15 11:49:03 testsvr.loc systemd[1]: Starting File System Check on /dev/VG0/STORAGE... Aug 15 11:49:04 testsvr.loc systemd-fsck[905]: STORAGE: clean, 73/1966080 files, 2410116/7864320 blocks Aug 15 11:49:04 testsvr.loc systemd[1]: Started File System Check on /dev/VG0/STORAGE. Aug 15 11:49:04 testsvr.loc systemd[1]: Mounting /home/xen_store... Aug 15 11:49:05 testsvr.loc systemd[1]: Mounted /home/xen_store. Aug 15 11:49:06 testsvr.loc xenstored[1121]: Checking store ... Aug 15 11:49:06 testsvr.loc xenstored[1121]: Checking store complete. Aug 15 11:49:06 testsvr.loc xenstored[1121]: Checking store ... Aug 15 11:49:06 testsvr.loc xenstored[1121]: Checking store complete. Aug 15 11:49:10 testsvr.loc dkms_autoinstaller[1034]: dkms: running auto installation service for kernel 3.7.10-1.16-xen Aug 15 11:49:10 testsvr.loc xencommons[1094]: Starting xenconsoled... Aug 15 11:49:10 testsvr.loc xencommons[1094]: Starting QEMU as disk backend for dom0 Aug 15 11:49:10 testsvr.loc xendomains[1157]: Starting auto Xen domains: test1.cfglibxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement candidate with 1 nodes, 4 cpus and 6599 KB free selected Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebug elevator=noop", features="(null)" Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_kernel_mem: called Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_ramdisk_mem: called Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_boot_xen_init: ver 4.3, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_parse_image: called Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: loader probe failed Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_malloc : 11718 kB Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x42596c -> 0xb71a08 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: loader probe OK Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: phdr: paddr=0x2000 memsz=0x87b000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: phdr: paddr=0x87d000 memsz=0x800f0 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: phdr: paddr=0x8fe000 memsz=0xb700 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: phdr: paddr=0x90a000 memsz=0x15b000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: memory: 0x2000 -> 0xa65000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: GUEST_OS = "linux" Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6" Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0" Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: ENTRY = 0xffffffff80002000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80003000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: unknown xen elf note (0xd) Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: MOD_START_PFN = 0x1 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: INIT_P2M = 0xffffea0000000000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: FEATURES = "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel" Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: SUPPORTED_FEATURES = 0x80f Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: LOADER = "generic" Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: SUSPEND_CANCEL = 0x1 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_xen_addr_calc_check: addresses: Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: virt_base = 0xffffffff80000000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_paddr_offset = 0x0 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: virt_offset = 0xffffffff80000000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: virt_kstart = 0xffffffff80002000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: virt_kend = 0xffffffff80a65000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: virt_entry = 0xffffffff80002000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: p2m_base = 0xffffea0000000000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0xffffffff80002000 -> 0xffffffff80a65000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_mem_init: mem 1024 MB, pages 0x40000 pages, 4k each Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_mem_init: 0x40000 pages Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_boot_mem_init: called Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_malloc : 2048 kB Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_build_image: called Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_segment: kernel : 0xffffffff80002000 -> 0xffffffff80a65000 (pfn 0x2 + 0xa63 pages) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x2+0xa63 at 0x7f72ad71f000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_load_binary: phdr 0 at 0x7f72ad71f000 -> 0x7f72adf9a000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_load_binary: phdr 1 at 0x7f72adf9a000 -> 0x7f72ae01a0f0 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_load_binary: phdr 2 at 0x7f72ae01b000 -> 0x7f72ae026700 Aug 15 11:49:10 testsvr.loc xendomains[1157]: xc: detail: elf_load_binary: phdr 3 at 0x7f72ae027000 -> 0x7f72ae08e000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_segment: ramdisk : 0xffffffff80a65000 -> 0xffffffff8171a000 (pfn 0xa65 + 0xcb5 pages) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0xa65+0xcb5 at 0x7f72aca6a000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x56082f -> 0xcb4010 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0xffffffff8171a000 -> 0xffffffff8191a000 (pfn 0x171a + 0x200 pages) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x171a+0x200 at 0x7f72ac86a000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_page : start info : 0xffffffff8191a000 (pfn 0x191a) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_page : xenstore : 0xffffffff8191b000 (pfn 0x191b) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_page : console : 0xffffffff8191c000 (pfn 0x191c) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 0xffff000000000000 -> 0xffffffffffffffff, 1 table(s) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 0xffffff8000000000 -> 0xffffffffffffffff, 1 table(s) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0xffffffff80000000 -> 0xffffffffbfffffff, 1 table(s) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0xffffffff80000000 -> 0xffffffff81bfffff, 14 table(s) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_segment: page tables : 0xffffffff8191d000 -> 0xffffffff8192e000 (pfn 0x191d + 0x11 pages) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x191d+0x11 at 0x7f72b1b84000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_page : boot stack : 0xffffffff8192e000 (pfn 0x192e) Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0xffffffff8192f000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0xffffffff81c00000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_boot_image: called Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: arch_setup_bootearly: doing nothing Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x40000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: clear_page: pfn 0x191c, mfn 0x15116f Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: clear_page: pfn 0x191b, mfn 0x151170 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x191a+0x1 at 0x7f72b1b81000 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: start_info_x86_64: called Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: setup_hypercall_page: vaddr=0xffffffff80003000 pfn=0x3 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: domain builder memory footprint Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: allocated Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: malloc : 13920 kB Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: anon mmap : 0 bytes Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: mapped Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: file mmap : 0 bytes Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: domU mmap : 25768 kB Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xcff74 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: shared_info_x86_64: called Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: vcpu_x86_64: called Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x191d mfn 0x15116e Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: launch_vm: called, ctxt=0x7fff513303b0 Aug 15 11:49:10 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_release: called Aug 15 11:49:10 testsvr.loc logger[1967]: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/51712 Aug 15 11:49:10 testsvr.loc logger[1965]: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/51744 Aug 15 11:49:10 testsvr.loc logger[1970]: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/51728 Aug 15 11:49:10 testsvr.loc logger[2085]: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/1/0 Aug 15 11:49:11 testsvr.loc logger[2129]: /etc/xen/scripts/vif-bridge: Writing backend/vif/1/0/hotplug-error Could not find bridge device br0 backend/vif/1/0/hotplug-status error to xenstore. Aug 15 11:49:11 testsvr.loc logger[2136]: /etc/xen/scripts/vif-bridge: Could not find bridge device br0 Aug 15 11:49:11 testsvr.loc xendomains[1157]: libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge online [2056] exited with error status 1 Aug 15 11:49:11 testsvr.loc xendomains[1157]: libxl: error: libxl_device.c:1021:device_hotplug_child_death_cb: script: Could not find bridge device br0 Aug 15 11:49:11 testsvr.loc xendomains[1157]: libxl: error: libxl_create.c:1115:domcreate_attach_vtpms: unable to add nic devices Aug 15 11:49:11 testsvr.loc logger[2203]: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/51728 Aug 15 11:49:11 testsvr.loc logger[2213]: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/51744 Aug 15 11:49:11 testsvr.loc logger[2224]: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/51712 Aug 15 11:49:11 testsvr.loc logger[2244]: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/1/0 Aug 15 11:49:11 testsvr.loc logger[2270]: /etc/xen/scripts/vif-bridge: Writing backend/vif/1/0/hotplug-error Could not find bridge device br0 backend/vif/1/0/hotplug-status error to xenstore. Aug 15 11:49:11 testsvr.loc logger[2276]: /etc/xen/scripts/vif-bridge: Could not find bridge device br0 Aug 15 11:49:11 testsvr.loc xendomains[1157]: libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge offline [2195] exited with error status 1 Aug 15 11:49:11 testsvr.loc xendomains[1157]: libxl: error: libxl_device.c:1021:device_hotplug_child_death_cb: script: Could not find bridge device br0 Aug 15 11:49:13 testsvr.loc xendomains[1157]: An error occurred while creating domain test1.cfg: Parsing config from /etc/xen/auto/test1.cfg Aug 15 11:49:13 testsvr.loc xendomains[1157]: ! Aug 15 11:49:14 testsvr.loc xendomains[1157]: test2.cfglibxl: detail: libxl_dom.c:195:numa_place_domain: NUMA placement candidate with 1 nodes, 4 cpus and 6600 KB free selected Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_allocate: cmdline="root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebug elevator=noop", features="(null)" Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_kernel_mem: called Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_ramdisk_mem: called Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_boot_xen_init: ver 4.3, caps xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_parse_image: called Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: loader probe failed Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_malloc : 11718 kB Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x42596c -> 0xb71a08 Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: loader probe OK Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: phdr: paddr=0x2000 memsz=0x87b000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: phdr: paddr=0x87d000 memsz=0x800f0 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: phdr: paddr=0x8fe000 memsz=0xb700 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: phdr: paddr=0x90a000 memsz=0x15b000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_parse_binary: memory: 0x2000 -> 0xa65000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: GUEST_OS = "linux" Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: GUEST_VERSION = "2.6" Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: XEN_VERSION = "xen-3.0" Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: PADDR_OFFSET = 0x0 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: ENTRY = 0xffffffff80002000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80003000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: unknown xen elf note (0xd) Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: MOD_START_PFN = 0x1 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: INIT_P2M = 0xffffea0000000000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: FEATURES = "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel" Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: SUPPORTED_FEATURES = 0x80f Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: LOADER = "generic" Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_parse_note: SUSPEND_CANCEL = 0x1 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_xen_addr_calc_check: addresses: Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: virt_base = 0xffffffff80000000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_paddr_offset = 0x0 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: virt_offset = 0xffffffff80000000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: virt_kstart = 0xffffffff80002000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: virt_kend = 0xffffffff80a65000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: virt_entry = 0xffffffff80002000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: p2m_base = 0xffffea0000000000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0xffffffff80002000 -> 0xffffffff80a65000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_mem_init: mem 1024 MB, pages 0x40000 pages, 4k each Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_mem_init: 0x40000 pages Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_boot_mem_init: called Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_malloc : 2048 kB Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_build_image: called Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_segment: kernel : 0xffffffff80002000 -> 0xffffffff80a65000 (pfn 0x2 + 0xa63 pages) Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x2+0xa63 at 0x7fe06f59d000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_load_binary: phdr 0 at 0x7fe06f59d000 -> 0x7fe06fe18000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_load_binary: phdr 1 at 0x7fe06fe18000 -> 0x7fe06fe980f0 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_load_binary: phdr 2 at 0x7fe06fe99000 -> 0x7fe06fea4700 Aug 15 11:49:14 testsvr.loc xendomains[1157]: xc: detail: elf_load_binary: phdr 3 at 0x7fe06fea5000 -> 0x7fe06ff0c000 Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_segment: ramdisk : 0xffffffff80a65000 -> 0xffffffff8180c000 (pfn 0xa65 + 0xda7 pages) Aug 15 11:49:14 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0xa65+0xda7 at 0x7fe06e7f6000 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x5ab9ab -> 0xda6c10 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0xffffffff8180c000 -> 0xffffffff81a0c000 (pfn 0x180c + 0x200 pages) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x180c+0x200 at 0x7fe06e5f6000 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_page : start info : 0xffffffff81a0c000 (pfn 0x1a0c) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_page : xenstore : 0xffffffff81a0d000 (pfn 0x1a0d) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_page : console : 0xffffffff81a0e000 (pfn 0x1a0e) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 0xffff000000000000 -> 0xffffffffffffffff, 1 table(s) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 0xffffff8000000000 -> 0xffffffffffffffff, 1 table(s) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0xffffffff80000000 -> 0xffffffffbfffffff, 1 table(s) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0xffffffff80000000 -> 0xffffffff81bfffff, 14 table(s) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_segment: page tables : 0xffffffff81a0f000 -> 0xffffffff81a20000 (pfn 0x1a0f + 0x11 pages) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x1a0f+0x11 at 0x7fe077bd7000 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_alloc_page : boot stack : 0xffffffff81a20000 (pfn 0x1a20) Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0xffffffff81a21000 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0xffffffff81c00000 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_boot_image: called Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: arch_setup_bootearly: doing nothing Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_compat_check: supported guest type: hvm-3.0-x86_64 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x40000 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: clear_page: pfn 0x1a0e, mfn 0x1527ff Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: clear_page: pfn 0x1a0d, mfn 0x151300 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x1a0c+0x1 at 0x7fe077bd4000 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: start_info_x86_64: called Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: setup_hypercall_page: vaddr=0xffffffff80003000 pfn=0x3 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: domain builder memory footprint Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: allocated Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: malloc : 13926 kB Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: anon mmap : 0 bytes Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: mapped Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: file mmap : 0 bytes Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: domU mmap : 26736 kB Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0xcff74 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: shared_info_x86_64: called Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: vcpu_x86_64: called Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x1a0f mfn 0x1527fe Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: launch_vm: called, ctxt=0x7fff74374c30 Aug 15 11:49:15 testsvr.loc xendomains[1157]: domainbuilder: detail: xc_dom_release: called Aug 15 11:49:15 testsvr.loc logger[2932]: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/2/51712 Aug 15 11:49:15 testsvr.loc logger[2931]: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/2/51728 Aug 15 11:49:15 testsvr.loc logger[2933]: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/2/51744 Aug 15 11:49:15 testsvr.loc logger[3018]: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/2/0 Aug 15 11:49:15 testsvr.loc logger[3128]: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vifT2.int, bridge br0. Aug 15 11:49:15 testsvr.loc logger[3131]: /etc/xen/scripts/vif-bridge: Writing backend/vif/2/0/hotplug-status connected to xenstore. Aug 15 11:49:20 testsvr.loc xendomains[1157]: ..done Aug 15 11:49:20 testsvr.loc systemd[1]: Started Xendomains - start and stop Xen VMs on boot and shutdown. re: issues with br0 above, checking brctl show bridge name bridge id STP enabled interfaces br0 8000.005235d94336 no eth0 vifT2.int br0 is clearly 'up' and found/used by 'test2' guest. missing systemd dependency? not waiting long enough @ xendomain start? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
ar16 wrote:
re: issues with br0 above, checking
brctl show bridge name bridge id STP enabled interfaces br0 8000.005235d94336 no eth0 vifT2.int
br0 is clearly 'up' and found/used by 'test2' guest. missing systemd dependency? not waiting long enough @ xendomain start?
Perhaps the former. Does adding 'network.target' to 'After' in xendomains.service help? E.g. After=xenstored.service xenconsoled.service network.target Regards, Jim -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Perhaps the former. Does adding 'network.target' to 'After' in xendomains.service help? E.g.
After=xenstored.service xenconsoled.service network.target
For ls -al /etc/systemd/system/multi-user.target.wants/xendomains.service /usr/lib/systemd/system/xendomains.service lrwxrwxrwx 1 root root 42 Aug 13 19:34 /etc/systemd/system/multi-user.target.wants/xendomains.service -> /usr/lib/systemd/system/xendomains.service -rw-r--r-- 1 root root 416 Aug 5 03:39 /usr/lib/systemd/system/xendomains.service Adding the systemd dependency on network, edit /usr/lib/systemd/system/xendomains.service - After=xenstored.service xenconsoled.service + After=xenstored.service xenconsoled.service network.service After reboot shutdown -r now ... both Guests, with their complete/original/uncommented .cfg's, launch again as expected, xl list Name ID Mem VCPUs State Time(s) (null) 0 1241 4 r----- 43.3 test1 1 1024 2 -b---- 8.4 test2 2 1024 2 -b---- 26.8 and, checking, seem to be fully functional. Looks like adding the 'network.service' dep does the trick. Just one question ... I'm not sure that Xen *should* depend on external network being up, but rather just local network and bridges -- even without attached eth0 interfaces. I think ... Iiuc, though, network.service brings up the bridges, no? Catch-22? Doesn't matter? I'm just not clear yet on the startup deps of local, external interfaces, and bridge (and other virtual?) interfaces. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
ar16 wrote:
Perhaps the former. Does adding 'network.target' to 'After' in xendomains.service help? E.g.
After=xenstored.service xenconsoled.service network.target
For
ls -al /etc/systemd/system/multi-user.target.wants/xendomains.service /usr/lib/systemd/system/xendomains.service lrwxrwxrwx 1 root root 42 Aug 13 19:34 /etc/systemd/system/multi-user.target.wants/xendomains.service -> /usr/lib/systemd/system/xendomains.service -rw-r--r-- 1 root root 416 Aug 5 03:39 /usr/lib/systemd/system/xendomains.service
Adding the systemd dependency on network,
edit /usr/lib/systemd/system/xendomains.service - After=xenstored.service xenconsoled.service + After=xenstored.service xenconsoled.service network.service
After reboot
shutdown -r now ...
both Guests, with their complete/original/uncommented .cfg's, launch again as expected,
xl list Name ID Mem VCPUs State Time(s) (null) 0 1241 4 r----- 43.3 test1 1 1024 2 -b---- 8.4 test2 2 1024 2 -b---- 26.8
and, checking, seem to be fully functional.
Looks like adding the 'network.service' dep does the trick.
Just one question ...
I'm not sure that Xen *should* depend on external network being up, but rather just local network and bridges -- even without attached eth0 interfaces. I think ...
Agreed, Xen should not depend on the external network being up. But we are talking about xendomains, which IMO should depend on external network. The domains it starts may need that... Regards, Jim -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Jim Fehlig wrote:
ar16 wrote:
I'm not sure that Xen *should* depend on external network being up, but rather just local network and bridges -- even without attached eth0 interfaces. I think ...
Agreed, Xen should not depend on the external network being up. But we are talking about xendomains,
which, btw, is not enabled by default and thus no external network dependency when simply booting Xen. Regards, Jim -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Thu, Aug 15, 2013, at 01:47 PM, Jim Fehlig wrote:
Agreed, Xen should not depend on the external network being up. But we are talking about xendomains, which IMO should depend on external network. The domains it starts may need that...
Fair enough. At this point, is the add'n of the "network.services" dependency in the queue to be added to pkgs? Or does a bug need to get filed? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
ar16 wrote:
On Thu, Aug 15, 2013, at 01:47 PM, Jim Fehlig wrote:
Agreed, Xen should not depend on the external network being up. But we are talking about xendomains, which IMO should depend on external network. The domains it starts may need that...
Fair enough.
At this point, is the add'n of the "network.services" dependency in the queue to be added to pkgs? Or does a bug need to get filed?
carnold will take care of it, no bug necessary IMO. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
carnold will take care of it, no bug necessary IMO.
Updating @Dom0 rpm -qa | grep -i xen ipset-kmp-xen-6.19_k3.7.10_1.1-32.1.x86_64 kernel-xen-3.7.10-1.16.1.x86_64 kernel-xen-devel-3.7.10-1.16.1.x86_64 xen-4.3.0_09-265.1.x86_64 xen-devel-4.3.0_09-265.1.x86_64 xen-libs-4.3.0_09-265.1.x86_64 xen-tools-4.3.0_09-265.1.x86_64 rpm -q --changelog xen | head -n5 * Thu Aug 15 2013 carnold@suse.com - Change the default bridge in xl.conf from xenbr0 to just br0 xl-conf-default-bridge.patch - Add network.target to xendomains.service 'After' tag xendomains.service after reboot, not so good, xl list Name ID Mem VCPUs State Time(s) (null) 0 1280 4 r----- 114.0 (null) 1 0 0 --p--- 0.0 (null) 2 0 0 --p--- 0.0 and, journatctl -b | grep xen ... Aug 15 15:56:14 testsvr.loc xenstored[1124]: Checking store ... Aug 15 15:56:14 testsvr.loc xenstored[1124]: Checking store complete. Aug 15 15:56:14 testsvr.loc xenstored[1124]: Checking store ... Aug 15 15:56:14 testsvr.loc xenstored[1124]: Checking store complete. Aug 15 15:56:16 testsvr.loc xenconsoled[1516]: xenstore watch on @introduceDomain fails. Aug 15 15:56:20 testsvr.loc kernel: xenstored[1124]: segfault at 4 ip 00007f5f74f82eac sp 00007fff1f5ab310 error 4 Aug 15 15:56:20 testsvr.loc kernel: in libxenctrl.so.4.3.0[7f5f74f67000+25000] Aug 15 15:56:20 testsvr.loc dkms_autoinstaller[1044]: dkms: running auto installation service for kernel 3.7.10-1.16-xen Aug 15 15:56:20 testsvr.loc xenstored[1076]: FATAL: Failed to open evtchn device: No such file or directory Aug 15 15:56:20 testsvr.loc xenconsoled[1516]: xenstore watch on @introduceDomain fails. Aug 15 15:56:27 testsvr.loc systemd[1]: Starting Xendomains - start and stop Xen VMs on boot and shutdown... Aug 15 15:56:29 testsvr.loc xendomains[2895]: Starting auto Xen domains: test1.cfglibxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get dompath for 1: Bad file descriptor Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl_create.c:644:initiate_domain_create: cannot make domain: -3 Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get dompath for 1: Bad file descriptor Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get dompath for 1: Bad file descriptor Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl.c:1342:domain_destroy_callback: unable to destroy guest with domid 1 Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl_create.c:1209:domcreate_destruction_cb: unable to destroy domain 1 following failed creation Aug 15 15:56:29 testsvr.loc xendomains[2895]: An error occurred while creating domain test1.cfg: Aug 15 15:56:29 testsvr.loc xendomains[2895]: ! Aug 15 15:56:29 testsvr.loc xendomains[2895]: test2.cfgDomain name must be specified. Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get dompath for 2: Bad file descriptor Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl_create.c:644:initiate_domain_create: cannot make domain: -3 Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get dompath for 2: Bad file descriptor Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl_xshelp.c:134:libxl__xs_get_dompath: failed to get dompath for 2: Bad file descriptor Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl.c:1342:domain_destroy_callback: unable to destroy guest with domid 2 Aug 15 15:56:29 testsvr.loc xendomains[2895]: libxl: error: libxl_create.c:1209:domcreate_destruction_cb: unable to destroy domain 2 following failed creation Aug 15 15:56:29 testsvr.loc xendomains[2895]: An error occurred while creating domain test2.cfg: Aug 15 15:56:29 testsvr.loc xendomains[2895]: ! Aug 15 15:56:29 testsvr.loc xendomains[2895]: ..done Aug 15 15:56:29 testsvr.loc systemd[1]: Started Xendomains - start and stop Xen VMs on boot and shutdown. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
changing edit /etc/sysconfig/kernel - DOMU_INITRD_MODULES="xennet xenblk" + DOMU_INITRD_MODULES="xennet xenblk evtchn" then mkinitrd reboot now, lsmod | grep evt evtchn 13162 1 bug NO guests xl list Name ID Mem VCPUs State Time(s) (null) 0 1280 4 r----- 38.2 checking journalctl -b | egrep -i "xen|evt" ... Aug 15 16:28:09 testsvr.loc xendomains[2924]: Starting auto Xen domains: test1.cfglibxl: error: libxl_bootloader.c:364:libxl__bootloader_run: failed to create bootloader dir /var/run/xen/bootloader.1.d: No such file or directory Aug 15 16:28:09 testsvr.loc xendomains[2924]: libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot (re-)build domain: -3 Aug 15 16:28:09 testsvr.loc xendomains[2924]: An error occurred while creating domain test1.cfg: Aug 15 16:28:09 testsvr.loc xendomains[2924]: ! Aug 15 16:28:09 testsvr.loc xendomains[2924]: test2.cfglibxl: error: libxl_bootloader.c:364:libxl__bootloader_run: failed to create bootloader dir /var/run/xen/bootloader.2.d: No such file or directory Aug 15 16:28:09 testsvr.loc xendomains[2924]: libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot (re-)build domain: -3 Aug 15 16:28:09 testsvr.loc xendomains[2924]: An error occurred while creating domain test2.cfg: Aug 15 16:28:09 testsvr.loc xendomains[2924]: ! Aug 15 16:28:09 testsvr.loc xendomains[2924]: ..done Aug 15 16:28:09 testsvr.loc systemd[1]: Started Xendomains - start and stop Xen VMs on boot and shutdown. and ls -al /var/run/xen/ ls: cannot access /var/run/xen/: No such file or directory i suspsect you'll need, at least, some form of cat /etc/tmpfiles.d/xendomains.conf D /var/run/xen 0755 root root - ('root' user correct here?) and systemd-tmpfiles --create /etc/tmpfiles.d/xendomains.conf on install -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
doing edit /etc/tmpfiles.d/xendomains.conf D /var/run/xen 0755 root root - systemd-tmpfiles --create /etc/tmpfiles.d/xendomains.conf here, does the trick. after reboot, xl list Name ID Mem VCPUs State Time(s) (null) 0 1269 4 r----- 43.7 test1 1 1024 2 -b---- 7.7 test2 2 1024 4 -b---- 28.6 and back to full function. still have that "(null") rather than Dom0 in its Name, but doesn't appear (yet) to have any detrimental effect on function -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 8/15/2013 at 05:46 PM, in message <1376610383.9775.10349293.0D21BF6A@webmail.messagingengine.com>, ar16 <ar16@imapmail.org> wrote: doing
edit /etc/tmpfiles.d/xendomains.conf D /var/run/xen 0755 root root -
systemd-tmpfiles --create /etc/tmpfiles.d/xendomains.conf
here, does the trick. after reboot,
xl list Name ID Mem VCPUs State Time(s) (null) 0 1269 4 r----- 43.7 test1 1 1024 2 -b---- 7.7 test2 2 1024 4 -b---- 28.6
and back to full function.
still have that "(null") rather than Dom0 in its Name, but doesn't appear (yet) to have any detrimental effect on function
This missing /var/run/xen and evtchn not being loaded seems to indicate that xencommons is not executed at boot. It modprobes in evtchn and creates /var/run/xen. - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Charles Arnold wrote:
On 8/15/2013 at 05:46 PM, in message
<1376610383.9775.10349293.0D21BF6A@webmail.messagingengine.com>, ar16 <ar16@imapmail.org> wrote:
doing
edit /etc/tmpfiles.d/xendomains.conf D /var/run/xen 0755 root root -
systemd-tmpfiles --create /etc/tmpfiles.d/xendomains.conf
here, does the trick. after reboot,
xl list Name ID Mem VCPUs State Time(s) (null) 0 1269 4 r----- 43.7 test1 1 1024 2 -b---- 7.7 test2 2 1024 4 -b---- 28.6
and back to full function.
still have that "(null") rather than Dom0 in its Name, but doesn't appear (yet) to have any detrimental effect on function
This missing /var/run/xen and evtchn not being loaded seems to indicate that xencommons is not executed at boot. It modprobes in evtchn and creates /var/run/xen.
Hmm, we might want to ensure xendomains.service is run After xencommons.service. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 8/16/2013 at 08:11 AM, in message <520E330C.60607@suse.com>, Jim Fehlig <jfehlig@suse.com> wrote: Charles Arnold wrote:
On 8/15/2013 at 05:46 PM, in message
<1376610383.9775.10349293.0D21BF6A@webmail.messagingengine.com>, ar16 <ar16@imapmail.org> wrote:
doing
edit /etc/tmpfiles.d/xendomains.conf D /var/run/xen 0755 root root -
systemd-tmpfiles --create /etc/tmpfiles.d/xendomains.conf
here, does the trick. after reboot,
xl list Name ID Mem VCPUs State Time(s) (null) 0 1269 4 r----- 43.7 test1 1 1024 2 -b---- 7.7 test2 2 1024 4 -b---- 28.6
and back to full function.
still have that "(null") rather than Dom0 in its Name, but doesn't appear (yet) to have any detrimental effect on function
This missing /var/run/xen and evtchn not being loaded seems to indicate that xencommons is not executed at boot. It modprobes in evtchn and creates /var/run/xen.
Hmm, we might want to ensure xendomains.service is run After xencommons.service.
Yes. We probably need to add both Requires and After. -Requires=xenstored.service xenconsoled.service -After=xenstored.service xenconsoled.service network.target +Requires=xencommons.service xenstored.service xenconsoled.service +After=xencommons.service xenstored.service xenconsoled.service network.target - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
fyi, back in business. thanks. grep -i xen /etc/sysconfig/kernel DOMU_INITRD_MODULES="xennet xenblk" ls /etc/tmpfiles.d/xen* ls: cannot access /etc/tmpfiles.d/xen*: No such file or directory egrep "Requires=|After=" xendomains.service Requires=xencommons.service xenstored.service xenconsoled.service After=xencommons.service xenstored.service xenconsoled.service network.target ls -al xen* lrwxrwxrwx 1 root root 42 Aug 16 10:01 xencommons.service -> /usr/lib/systemd/system/xencommons.service lrwxrwxrwx 1 root root 43 Aug 16 10:01 xenconsoled.service -> /usr/lib/systemd/system/xenconsoled.service lrwxrwxrwx 1 root root 42 Aug 16 10:01 xendomains.service -> /usr/lib/systemd/system/xendomains.service lrwxrwxrwx 1 root root 41 Aug 16 10:01 xenstored.service -> /usr/lib/systemd/system/xenstored.service mkinitrd reboot ... xl list Name ID Mem VCPUs State Time(s) (null) 0 1241 4 r----- 45.3 test1 1 1024 2 -b---- 8.8 test2 2 1024 4 -b---- 30.2 Still have that "(null)" Name for Dom0 ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 8/16/2013 at 11:16 AM, in message <1376673404.5670.10627501.46679636@webmail.messagingengine.com>, ar16 <ar16@imapmail.org> wrote: fyi, back in business. thanks.
grep -i xen /etc/sysconfig/kernel DOMU_INITRD_MODULES="xennet xenblk"
ls /etc/tmpfiles.d/xen* ls: cannot access /etc/tmpfiles.d/xen*: No such file or directory
egrep "Requires=|After=" xendomains.service Requires=xencommons.service xenstored.service xenconsoled.service After=xencommons.service xenstored.service xenconsoled.service network.target
ls -al xen* lrwxrwxrwx 1 root root 42 Aug 16 10:01 xencommons.service -> /usr/lib/systemd/system/xencommons.service lrwxrwxrwx 1 root root 43 Aug 16 10:01 xenconsoled.service -> /usr/lib/systemd/system/xenconsoled.service lrwxrwxrwx 1 root root 42 Aug 16 10:01 xendomains.service -> /usr/lib/systemd/system/xendomains.service lrwxrwxrwx 1 root root 41 Aug 16 10:01 xenstored.service -> /usr/lib/systemd/system/xenstored.service
mkinitrd reboot ...
xl list Name ID Mem VCPUs State Time(s) (null) 0 1241 4 r----- 45.3 test1 1 1024 2 -b---- 8.8 test2 2 1024 4 -b---- 30.2
Still have that "(null)" Name for Dom0 ...
How is Dom0 displayed when you do a xenstore-ls? Any chance you have a /etc/init.d/xend script hanging around and getting started? - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Any chance you have a /etc/init.d/xend script hanging around and getting started?
Doesn't look like it: ls -al /etc/init.d/xen* -rwxr-xr-x 1 root root 4.9K Aug 15 14:20 /etc/init.d/xencommons* -rwxr-xr-x 1 root root 14K Aug 15 15:52 /etc/init.d/xendomains* -rwxr-xr-x 1 root root 1.5K Jul 9 11:57 /etc/init.d/xen-watchdog* systemctl status xen-watchdog.service xen-watchdog.service - Xen-watchdog - run xen watchdog daemon Loaded: loaded (/usr/lib/systemd/system/xen-watchdog.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/xen-watchdog.service
How is Dom0 displayed when you do a xenstore-ls?
Not sure what you're looking for specifically. Here's the whole output xenstore-ls tool = "" xenstored = "" vm = "" www... = "" uuid = "www..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.2DQGzh" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.4TDO9l" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376592317.47" xxx... = "" uuid = "xxx..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.rrFFtJ" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.Sj2nYp" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376592554.77" yyy... = "" uuid = "yyy..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.8ACINd" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.QKWG2S" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376598384.76" zzz... = "" uuid = "zzz..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.cc08JL" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.mLPoB3" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376598661.27" aaa... = "" uuid = "aaa..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.GU6fZ7" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.NyNqNT" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376610136.76" bbb... = "" uuid = "bbb..." name = "test1" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.1.d/boot_kernel.sYNpOD" ramdisk = "/var/run/xen/bootloader.1.d/boot_ramdisk.KjtNA7" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376672796.72" ddd... = "" uuid = "ddd..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.7xanX5" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.rr6wPE" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376672804.77" libxl = "" 1 = "" dm-version = "qemu_xen" 2 = "" dm-version = "qemu_xen" local = "" domain = "" 0 = "" device-model = "" 0 = "" state = "running" 1 = "" state = "running" 2 = "" state = "running" libxl = "" disable_udev = "1" backend = "" vbd = "" 1 = "" 51712 = "" frontend = "/local/domain/1/device/vbd/51712" params = "/dev/VG0/test1_boot" script = "/etc/xen/scripts/block" physical-device = "fd:8" frontend-id = "1" online = "1" removable = "0" bootable = "1" state = "4" dev = "xvda" type = "phy" mode = "w" device-type = "disk" max-ring-page-order = "0" feature-flush-cache = "1" feature-barrier = "1" feature-discard = "0" sectors = "327680" info = "0" sector-size = "512" 51728 = "" frontend = "/local/domain/1/device/vbd/51728" params = "/dev/VG0/test1_swap" script = "/etc/xen/scripts/block" physical-device = "fd:a" frontend-id = "1" online = "1" removable = "0" bootable = "1" state = "4" dev = "xvdb" type = "phy" mode = "w" device-type = "disk" max-ring-page-order = "0" feature-flush-cache = "1" feature-barrier = "1" feature-discard = "0" sectors = "1048576" info = "0" sector-size = "512" 51744 = "" frontend = "/local/domain/1/device/vbd/51744" params = "/dev/VG0/test1_root" script = "/etc/xen/scripts/block" physical-device = "fd:9" frontend-id = "1" online = "1" removable = "0" bootable = "1" state = "4" dev = "xvdc" type = "phy" mode = "w" device-type = "disk" max-ring-page-order = "0" feature-flush-cache = "1" feature-barrier = "1" feature-discard = "0" sectors = "8388608" info = "0" sector-size = "512" 2 = "" 51712 = "" frontend = "/local/domain/2/device/vbd/51712" params = "/dev/VG0/test2_boot" script = "/etc/xen/scripts/block" physical-device = "fd:d" frontend-id = "2" online = "1" removable = "0" bootable = "1" state = "4" dev = "xvda" type = "phy" mode = "w" device-type = "disk" max-ring-page-order = "0" feature-flush-cache = "1" feature-barrier = "1" feature-discard = "0" sectors = "327680" info = "0" sector-size = "512" 51728 = "" frontend = "/local/domain/2/device/vbd/51728" params = "/dev/VG0/test2_swap" script = "/etc/xen/scripts/block" physical-device = "fd:f" frontend-id = "2" online = "1" removable = "0" bootable = "1" state = "4" dev = "xvdb" type = "phy" mode = "w" device-type = "disk" max-ring-page-order = "0" feature-flush-cache = "1" feature-barrier = "1" feature-discard = "0" sectors = "1048576" info = "0" sector-size = "512" 51744 = "" frontend = "/local/domain/2/device/vbd/51744" params = "/dev/VG0/test2_root" script = "/etc/xen/scripts/block" physical-device = "fd:e" frontend-id = "2" online = "1" removable = "0" bootable = "1" state = "4" dev = "xvdc" type = "phy" mode = "w" device-type = "disk" max-ring-page-order = "0" feature-flush-cache = "1" feature-barrier = "1" feature-discard = "0" sectors = "25165824" info = "0" sector-size = "512" vfb = "" 1 = "" 0 = "" frontend = "/local/domain/1/device/vfb/0" frontend-id = "1" online = "1" state = "4" domain = "test1" vnc = "1" vnclisten = "127.0.0.1" vncdisplay = "99" vncunused = "1" sdl = "0" opengl = "0" feature-resize = "1" hotplug-status = "connected" request-update = "1" 2 = "" 0 = "" frontend = "/local/domain/2/device/vfb/0" frontend-id = "2" online = "1" state = "4" domain = "test2" vnc = "1" vnclisten = "127.0.0.1" vncdisplay = "202" vncunused = "1" sdl = "0" opengl = "0" feature-resize = "1" hotplug-status = "connected" request-update = "1" vkbd = "" 1 = "" 0 = "" frontend = "/local/domain/1/device/vkbd/0" frontend-id = "1" online = "1" state = "4" domain = "test1" feature-abs-pointer = "1" hotplug-status = "connected" 2 = "" 0 = "" frontend = "/local/domain/2/device/vkbd/0" frontend-id = "2" online = "1" state = "4" domain = "test2" feature-abs-pointer = "1" hotplug-status = "connected" console = "" 1 = "" 0 = "" frontend = "/local/domain/1/console" frontend-id = "1" online = "1" state = "1" domain = "test1" protocol = "vt100" 2 = "" 0 = "" frontend = "/local/domain/2/console" frontend-id = "2" online = "1" state = "1" domain = "test2" protocol = "vt100" vif = "" 1 = "" 0 = "" frontend = "/local/domain/1/device/vif/0" frontend-id = "1" online = "1" state = "4" script = "/etc/xen/scripts/vif-bridge" vifname = "vifT1.int" mac = "00:16:3e:02:01:00" bridge = "brINT" handle = "0" type = "vif" feature-sg = "1" feature-gso-tcpv4 = "1" feature-rx-copy = "1" feature-rx-flip = "0" hotplug-status = "connected" 2 = "" 0 = "" frontend = "/local/domain/2/device/vif/0" frontend-id = "2" online = "1" state = "4" script = "/etc/xen/scripts/vif-bridge" vifname = "vifT2.int" mac = "00:16:3e:02:02:00" bridge = "brINT" handle = "0" type = "vif" feature-sg = "1" feature-gso-tcpv4 = "1" feature-rx-copy = "1" feature-rx-flip = "0" hotplug-status = "connected" 1 = "" frontend = "/local/domain/2/device/vif/1" frontend-id = "2" online = "1" state = "4" script = "/etc/xen/scripts/vif-bridge" vifname = "vifT2.ext" mac = "00:16:3e:02:02:01" bridge = "br0" handle = "1" type = "vif" feature-sg = "1" feature-gso-tcpv4 = "1" feature-rx-copy = "1" feature-rx-flip = "0" hotplug-status = "connected" 1 = "" vm = "/vm/bbb..." name = "test1" cpu = "" 0 = "" availability = "online" 1 = "" availability = "online" memory = "" static-max = "1048576" target = "1048577" videoram = "-1" device = "" suspend = "" event-channel = "9" vbd = "" 51712 = "" backend = "/local/domain/0/backend/vbd/1/51712" backend-id = "0" state = "4" virtual-device = "51712" device-type = "disk" protocol = "x86_64-abi" ring-ref = "8" event-channel = "12" 51728 = "" backend = "/local/domain/0/backend/vbd/1/51728" backend-id = "0" state = "4" virtual-device = "51728" device-type = "disk" protocol = "x86_64-abi" ring-ref = "9" event-channel = "13" 51744 = "" backend = "/local/domain/0/backend/vbd/1/51744" backend-id = "0" state = "4" virtual-device = "51744" device-type = "disk" protocol = "x86_64-abi" ring-ref = "10" event-channel = "14" vfb = "" 0 = "" backend = "/local/domain/0/backend/vfb/1/0" backend-id = "0" state = "4" page-ref = "1654010" event-channel = "10" protocol = "x86_64-abi" feature-update = "1" vkbd = "" 0 = "" backend = "/local/domain/0/backend/vkbd/1/0" backend-id = "0" state = "4" request-abs-pointer = "1" page-ref = "1652518" event-channel = "11" vif = "" 0 = "" backend = "/local/domain/0/backend/vif/1/0" backend-id = "0" state = "4" handle = "0" mac = "00:16:3e:02:01:00" tx-ring-ref = "768" rx-ring-ref = "769" event-channel = "15" request-rx-copy = "1" feature-rx-notify = "1" feature-no-csum-offload = "0" feature-sg = "1" feature-gso-tcpv4 = "1" control = "" shutdown = "" platform-feature-multiprocessor-suspend = "1" platform-feature-xs_reset_watches = "1" data = "" domid = "1" store = "" port = "1" ring-ref = "1437554" console = "" backend = "/local/domain/0/backend/console/1/0" backend-id = "0" limit = "1048576" type = "xenconsoled" output = "pty" tty = "/dev/pts/0" port = "2" ring-ref = "1437553" vnc-listen = "127.0.0.1" vnc-port = "5999" image = "" device-model-pid = "3878" 2 = "" vm = "/vm/ddd..." name = "test2" cpu = "" 0 = "" availability = "online" 1 = "" availability = "online" 2 = "" availability = "online" 3 = "" availability = "online" memory = "" static-max = "1048576" target = "1048577" videoram = "-1" device = "" suspend = "" event-channel = "15" vbd = "" 51712 = "" backend = "/local/domain/0/backend/vbd/2/51712" backend-id = "0" state = "4" virtual-device = "51712" device-type = "disk" protocol = "x86_64-abi" ring-ref = "8" event-channel = "18" 51728 = "" backend = "/local/domain/0/backend/vbd/2/51728" backend-id = "0" state = "4" virtual-device = "51728" device-type = "disk" protocol = "x86_64-abi" ring-ref = "9" event-channel = "19" 51744 = "" backend = "/local/domain/0/backend/vbd/2/51744" backend-id = "0" state = "4" virtual-device = "51744" device-type = "disk" protocol = "x86_64-abi" ring-ref = "10" event-channel = "20" vfb = "" 0 = "" backend = "/local/domain/0/backend/vfb/2/0" backend-id = "0" state = "4" page-ref = "1915948" event-channel = "16" protocol = "x86_64-abi" feature-update = "1" vkbd = "" 0 = "" backend = "/local/domain/0/backend/vkbd/2/0" backend-id = "0" state = "4" request-abs-pointer = "1" page-ref = "1915942" event-channel = "17" vif = "" 0 = "" backend = "/local/domain/0/backend/vif/2/0" backend-id = "0" state = "4" handle = "0" mac = "00:16:3e:02:02:00" tx-ring-ref = "1280" rx-ring-ref = "1281" event-channel = "21" request-rx-copy = "1" feature-rx-notify = "1" feature-no-csum-offload = "0" feature-sg = "1" feature-gso-tcpv4 = "1" 1 = "" backend = "/local/domain/0/backend/vif/2/1" backend-id = "0" state = "4" handle = "1" mac = "00:16:3e:02:02:01" tx-ring-ref = "1282" rx-ring-ref = "1283" event-channel = "22" request-rx-copy = "1" feature-rx-notify = "1" feature-no-csum-offload = "0" feature-sg = "1" feature-gso-tcpv4 = "1" control = "" shutdown = "" platform-feature-multiprocessor-suspend = "1" platform-feature-xs_reset_watches = "1" data = "" domid = "2" store = "" port = "1" ring-ref = "1634638" console = "" backend = "/local/domain/0/backend/console/2/0" backend-id = "0" limit = "1048576" type = "xenconsoled" output = "pty" tty = "/dev/pts/1" port = "2" ring-ref = "1634637" image = "" device-model-pid = "4073" -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Should a package update DISable enabled services? ls -al /etc/systemd/system/multi-user.target.wants/xen* lrwxrwxrwx 1 root root 42 Aug 16 10:01 xencommons.service -> /usr/lib/systemd/system/xencommons.service lrwxrwxrwx 1 root root 43 Aug 16 10:01 xenconsoled.service -> /usr/lib/systemd/system/xenconsoled.service lrwxrwxrwx 1 root root 42 Aug 16 10:01 xendomains.service -> /usr/lib/systemd/system/xendomains.service lrwxrwxrwx 1 root root 41 Aug 16 10:01 xenstored.service -> /usr/lib/systemd/system/xenstored.service zypper dup --from XEN4 ... ls -al /etc/systemd/system/multi-user.target.wants/xen* lrwxrwxrwx 1 root root 43 Aug 16 10:01 xenconsoled.service -> /usr/lib/systemd/system/xenconsoled.service lrwxrwxrwx 1 root root 41 Aug 16 10:01 xenstored.service -> /usr/lib/systemd/system/xenstored.service Shouldn't it leave the state alone? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
ar16 wrote:
xenstore-ls tool = "" xenstored = "" vm = "" www... = "" uuid = "www..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.2DQGzh" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.4TDO9l" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376592317.47" xxx... = "" uuid = "xxx..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.rrFFtJ" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.Sj2nYp" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376592554.77" yyy... = "" uuid = "yyy..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.8ACINd" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.QKWG2S" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376598384.76" zzz... = "" uuid = "zzz..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.cc08JL" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.mLPoB3" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376598661.27" aaa... = "" uuid = "aaa..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.GU6fZ7" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.NyNqNT" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376610136.76" bbb... = "" uuid = "bbb..." name = "test1" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.1.d/boot_kernel.sYNpOD" ramdisk = "/var/run/xen/bootloader.1.d/boot_ramdisk.KjtNA7" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376672796.72" ddd... = "" uuid = "ddd..." name = "test2" image = "" ostype = "linux" kernel = "/var/run/xen/bootloader.2.d/boot_kernel.7xanX5" ramdisk = "/var/run/xen/bootloader.2.d/boot_ramdisk.rr6wPE" cmdline = "root=/dev/xvdc1 resume=/dev/xvdb1 kbdtype=us headless text quiet nofb selinux=0 apparmor-0 edd=off splash=silent noshell showopts ide0=noprobe ide1=noprobe hda=noprobe root=/dev/xvdc1 textmode=1 xencons=xvc0 noirqdebu\..." start_time = "1376672804.77" libxl = "" 1 = "" dm-version = "qemu_xen" 2 = "" dm-version = "qemu_xen" local = "" domain = "" 0 = ""
Odd. There should be a name = "Domain-0" node under /local/domain/0, e.g. # xenstore-ls /local/domain/0 name = "Domain-0" device-model = "" ... And that looks to be written by the do_start() function in xencommons. Maybe you can poke around there and see why ${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0" is not being executed. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
And that looks to be written by the do_start() function in xencommons. Maybe you can poke around there and see why
${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0"
is not being executed.
1st check, the write works @shell, but is not sticky at boot xenstore-ls /local/domain/0 | grep "Domain-0" (empty) /usr/bin/xenstore-write "/local/domain/0/name" "Domain-0" xenstore-ls /local/domain/0 | grep "Domain-0" -B3 -A3 feature-rx-copy = "1" feature-rx-flip = "0" hotplug-status = "connected" name = "Domain-0" xl list Name ID Mem VCPUs State Time(s) Domain-0 0 1241 4 r----- 57.2 test1 1 1024 2 -b---- 12.6 test2 2 1024 4 -b---- 32.7 shutdown -r now ... xl list Name ID Mem VCPUs State Time(s) (null) 0 1241 4 r----- 43.5 test1 1 1024 2 -b---- 8.0 test2 2 1024 4 -b---- 29.1 checking in /etc/init.d/xencommons, the if clause that wraps it if ! `${BINDIR}/xenstore-read -s / >/dev/null 2>&1` then ... echo Setting domain 0 name... ${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0" fi I don't see the "Setting domain 0 name" @ boot journalctl -b | grep -i xenstore Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store ... Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store complete. Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store ... Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store complete. Aug 16 12:00:44 testsvr.loc logger[4201]: /etc/xen/scripts/vif-bridge: Writing backend/vif/1/0/hotplug-status connected to xenstore. Aug 16 12:00:52 testsvr.loc logger[4420]: /etc/xen/scripts/vif-bridge: Writing backend/vif/2/0/hotplug-status connected to xenstore. Aug 16 12:00:52 testsvr.loc logger[4426]: /etc/xen/scripts/vif-bridge: Writing backend/vif/2/1/hotplug-status connected to xenstore. testing, here, @ shell, xenstore-read -s / (empty) i'm staring at if ! `${BINDIR}/xenstore-read -s / >/dev/null 2>&1` what exactly is the intent here? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 8/16/2013 at 01:16 PM, in message <1376680595.31373.10662789.2FC45E8F@webmail.messagingengine.com>, ar16 <ar16@imapmail.org> wrote: And that looks to be written by the do_start() function in xencommons. Maybe you can poke around there and see why
${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0"
is not being executed.
1st check, the write works @shell, but is not sticky at boot
xenstore-ls /local/domain/0 | grep "Domain-0" (empty) /usr/bin/xenstore-write "/local/domain/0/name" "Domain-0"
xenstore-ls /local/domain/0 | grep "Domain-0" -B3 -A3 feature-rx-copy = "1" feature-rx-flip = "0" hotplug-status = "connected" name = "Domain-0" xl list Name ID Mem VCPUs State Time(s) Domain-0 0 1241 4 r----- 57.2 test1 1 1024 2 -b---- 12.6 test2 2 1024 4 -b---- 32.7 shutdown -r now ... xl list Name ID Mem VCPUs State Time(s) (null) 0 1241 4 r----- 43.5 test1 1 1024 2 -b---- 8.0 test2 2 1024 4 -b---- 29.1
checking in /etc/init.d/xencommons, the if clause that wraps it
if ! `${BINDIR}/xenstore-read -s / >/dev/null 2>&1` then ...
echo Setting domain 0 name... ${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0" fi
I don't see the "Setting domain 0 name" @ boot
journalctl -b | grep -i xenstore Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store ... Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store complete. Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store ... Aug 16 12:00:28 testsvr.loc xenstored[1122]: Checking store complete. Aug 16 12:00:44 testsvr.loc logger[4201]: /etc/xen/scripts/vif-bridge: Writing backend/vif/1/0/hotplug-status connected to xenstore. Aug 16 12:00:52 testsvr.loc logger[4420]: /etc/xen/scripts/vif-bridge: Writing backend/vif/2/0/hotplug-status connected to xenstore. Aug 16 12:00:52 testsvr.loc logger[4426]: /etc/xen/scripts/vif-bridge: Writing backend/vif/2/1/hotplug-status connected to xenstore.
testing, here, @ shell,
xenstore-read -s / (empty)
i'm staring at
if ! `${BINDIR}/xenstore-read -s / >/dev/null 2>&1`
what exactly is the intent here?
It checks the status of xenstore to see if it is running by reading from the socket (-s). On failure, it executes the code to start xenstored. After loading xenstored it then hits a while loop checking for up to 30 seconds to see if things were properly setup. The only failure points are if xenstored is already running, xenstored could not be found, or it times out. - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
i'm staring at
if ! `${BINDIR}/xenstore-read -s / >/dev/null 2>&1`
what exactly is the intent here?
It checks the status of xenstore to see if it is running by reading from the socket (-s). On failure, it executes the code to start xenstored. After loading xenstored it then hits a while loop checking for up to 30 seconds to see if things were properly setup. The only failure points are if xenstored is already running, xenstored could not be found, or it times out.
Is there any reason, then, NOT to simply move edit /etc/init.d/xenstored fi echo Setting domain 0 name... - ${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0" + # ${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0" fi + ${BINDIR}/xenstore-write "/local/domain/0/name" "Domain-0" echo Starting xenconsoled... which appears to 'cure' the "(null)" name issue. reboot ... xl list Name ID Mem VCPUs State Time(s) Domain-0 0 1241 4 r----- 42.2 test1 1 1024 2 -b---- 7.9 test2 2 1024 4 -b---- 28.3 xenstore-ls | grep "Domain-0" name = "Domain-0" -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Charles Arnold wrote:
i'm staring at
if ! `${BINDIR}/xenstore-read -s / >/dev/null 2>&1`
what exactly is the intent here?
It checks the status of xenstore to see if it is running by reading from the socket (-s). On failure, it executes the code to start xenstored. After loading xenstored it then hits a while loop checking for up to 30 seconds to see if things were properly setup. The only failure points are if xenstored is already running,
This is probably the case. xenstored.service must be running before xencommons.service. Since xencommons will start xenstored, we may not need xenstored.service right? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
This is probably the case. xenstored.service must be running before xencommons.service. Since xencommons will start xenstored, we may not need xenstored.service right?
It's useful to be able to disable xen guest launching on boot. disabling xendomains.service seems a logical way/place to do that. if not, &/or you remove it, what't the 'right' way to do it? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
ar16 wrote:
This is probably the case. xenstored.service must be running before xencommons.service. Since xencommons will start xenstored, we may not need xenstored.service right?
It's useful to be able to disable xen guest launching on boot.
Right, that is the default config.
disabling xendomains.service seems a logical way/place to do that.
Right, not enabled out of the box.
if not, &/or you remove it, what't the 'right' way to do it?
I'm not talking about xendomains.service, but xenstored.service. xencommons starts xenstored, so no need to have systemd do that and hence no need for the service file. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 8/16/2013 at 02:30 PM, in message <520E8BE3.9010302@suse.com>, Jim Fehlig <jfehlig@suse.com> wrote: ar16 wrote: This is probably the case. xenstored.service must be running before xencommons.service. Since xencommons will start xenstored, we may not need xenstored.service right?
It's useful to be able to disable xen guest launching on boot.
Right, that is the default config.
disabling xendomains.service seems a logical way/place to do that.
Right, not enabled out of the box.
if not, &/or you remove it, what't the 'right' way to do it?
I'm not talking about xendomains.service, but xenstored.service. xencommons starts xenstored, so no need to have systemd do that and hence no need for the service file.
We get to pick the 'right' way as upstream has no service files :) Historically, for as long as xencommons existed, it has always started xendomains. I'll experiment without the xendomains.service file and if it seems reasonable, I'll remove it. - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
I'll experiment without the xendomains.service file and if it seems reasonable, I'll remove it.
ok, so we _are_ talking about the xendomains.service now. back to my point -- imo, fine as long as there's still a clear/straightforward way to disable 'just' Guest-startup at boot ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 8/16/2013 at 02:43 PM, in message <1376685807.15628.10690689.56FD15EC@webmail.messagingengine.com>, ar16 <ar16@imapmail.org> wrote: I'll experiment without the xendomains.service file and if it seems reasonable, I'll remove it.
ok, so we _are_ talking about the xendomains.service now.
back to my point -- imo, fine as long as there's still a clear/straightforward way to disable 'just' Guest-startup at boot ...
Now it's my bad. xenstored.service (and xenconsoled.service as well) to be dropped. - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Charles Arnold wrote:
On 8/16/2013 at 02:43 PM, in message
<1376685807.15628.10690689.56FD15EC@webmail.messagingengine.com>, ar16 <ar16@imapmail.org> wrote:
I'll experiment without the xendomains.service file and if it seems
reasonable, I'll remove it.
ok, so we _are_ talking about the xendomains.service now.
back to my point -- imo, fine as long as there's still a clear/straightforward way to disable 'just' Guest-startup at boot ...
Now it's my bad. xenstored.service (and xenconsoled.service as well) to be dropped.
:) Too many xen*.service files, which is more impetus to remove a few of them. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Too many xen*.service files, which is more impetus to remove a few of them.
Well, now that you mention it ... AND the /etc/init.d/xen* files? Time to bite the bullet and move to ONLY/native systemd service, etc files? Especially if 'upstream' is not (yet) doing so ... -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Fri, Aug 16, 2013, at 02:13 PM, ar16 wrote:
Too many xen*.service files, which is more impetus to remove a few of them.
Well, now that you mention it ... AND the /etc/init.d/xen* files? Time to bite the bullet and move to ONLY/native systemd service, etc files?
Especially if 'upstream' is not (yet) doing so ...
fyi, these are where I started reading up https://wiki.archlinux.org/index.php/Xen#Installation_of_Xen_systemd_service... https://gist.github.com/paleo9/a2b71e4a17fdf7bbcfc0/raw/e32ad3f742f540eb29d3... http://code.ohloh.net/project?pid=To_geo_UShk&prevcid=1&browser=Default&did=xen%2Ftrunk&cid=Ei8D1IuxHe4 -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 8/16/2013 at 03:04 PM, in message <520E3F71020000910008B5A3@novprvoes0310.provo.novell.com>, "Charles Arnold" <carnold@suse.com> wrote:
On 8/16/2013 at 02:43 PM, in message <1376685807.15628.10690689.56FD15EC@webmail.messagingengine.com>, ar16 <ar16@imapmail.org> wrote: I'll experiment without the xendomains.service file and if it seems reasonable, I'll remove it.
ok, so we _are_ talking about the xendomains.service now.
back to my point -- imo, fine as long as there's still a clear/straightforward way to disable 'just' Guest-startup at boot ...
Now it's my bad. xenstored.service (and xenconsoled.service as well) to be dropped.
If you want to try this manually, you can remove the files from /usr/lib/systemd/system. You will also need to edit xendomains.service to something like this, -Requires=xenstored.service xenconsoled.service -After=xencommons.service xenstored.service xenconsoled.service network.target +After=xencommons.service network.target - Charles -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
participants (5)
-
ar16 -
Charles Arnold -
Jan Beulich -
Jim Fehlig -
Tony Su