[Bug 465379] New: xendomains does not start: Device 51952 (tap) could not be connected
https://bugzilla.novell.com/show_bug.cgi?id=465379 Summary: xendomains does not start: Device 51952 (tap) could not be connected Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: novell-web@zmi.at QAContact: qa@suse.de Found By: --- I've been searching a very long time investigating this problem. We're trying to use XEN in production, but currently documentation is very sparse, mostly outdated and wrong. Too bad! We've had the problem on one server where a single XEN domU was installed on openSUSE 11.0. After upgrading to openSUSE 11.1, xendomains didn't start the domain anymore. Symptom: autostart: # # rcxendomains start Starting auto Xen domains mailsrv2: Error: Device /dev/xvdp (tap) could not be disconnected. manual start: # xm create /etc/xen/auto/mailsrv Error: Device 51952 (tap) could not be connected. Hotplug scripts not working. You can google around, a lot of people have this problem with no real answer. I then found a first step: use "file:" instead "tap:aio" in the config works: 'tap:aio:/disks/daten/xen/mailsrv/root20080923.xvd,xvda,w', 'tap:aio:/disks/daten/xen/mailsrv/swap20080922.xvd,xvdb,w', 'tap:cdrom:/disks/daten/dvd/openSUSE-11.1-DVD-x86_64.iso,xvdz,r', ] changed to 'file:/disks/daten/xen/mailsrv/root20080923.xvd,xvda,w', 'file:/disks/daten/xen/mailsrv/swap20080922.xvd,xvdb,w', 'file:/disks/daten/dvd/openSUSE-11.1-DVD-x86_64.iso,xvdz,r', ] Then the domain can be created and runs without problems. But changing it back to tap:aio brings the error back also: # xm create /etc/xen/auto/mailsrv Using config file "/etc/xen/auto/mailsrv". Error: Device 51952 (tap) could not be connected. Hotplug scripts not working. And this leads into the totally wrong direction. The problem is elsewhere: When we started with XEN I read the Novell docs, especially http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7000062&sliceId=1&docTypeID=DT_TID_1_1&dialogID=74609719&stateId=0%200%2074607316 and how to use LVMs. But using LVMs within a simple file needs "xm block-attach", followed by a "vgchange -a y" in order to bring up the LVM. This seems to be done automatically by "xendomains", but there must be something that disturbs this, as after our upgrade 11.0 -> 11.1 it didn't work anymore. Also, as many people have problems with this, maybe you could post an article describing the problem and explaining the solution. I believe the solution is to either not use LVMs within files for XEN, and use files as disks directly. 1) The question remains, why the XEN scripts seem to remember to setup the LVM once, and then forgets it. The error messages should be cleaned up to explain the problem and point to the right direction. 2) # xm block-list 0 Vdev BE handle state evt-ch ring-ref BE-path 51952 0 0 4 30 8 /local/domain/0/backend/tap/0/51952 It would be good that "xm block-list" also tells which device it is connected to (/dev/xvdp in my case). 3) There are currently 2 different error messages on VM startup: xendomains or "xm create", and both do not help solve the problem really 4) Why can't xendomains *disconnect* the LVM? After all, we're just booting the machine, and it tells us it can't *disconnect*? Maybe this can be improved. Hope this helps, mfg zmi -- 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=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c1 Michael Monnerie <novell-web@zmi.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novell-web@zmi.at --- Comment #1 from Michael Monnerie <novell-web@zmi.at> 2009-01-12 07:53:43 MST --- One more thing: After trying a startup, I have this in dom0: *********************************** # xm block-list 0 Vdev BE handle state evt-ch ring-ref BE-path 51952 0 0 4 30 8 /local/domain/0/backend/tap/0/51952 *********************************** Trying to remove it does not work: *********************************** # xm block-detach 0 xvdp Error: Device 51952 not connected Usage: xm block-detach <Domain> <DevId> [-f|--force] Destroy a domain's virtual block device. *********************************** But I have no more reference to that file, and it's definitely xvdp: # l /dev/xv* crw-rw---- 1 root root 204, 191 12. Jan 14:33 /dev/xvc0 brw-rw---- 1 root root 202, 240 12. Jan 15:32 /dev/xvdp brw-rw---- 1 root root 202, 241 12. Jan 15:32 /dev/xvdp1 brw-rw---- 1 root root 202, 242 12. Jan 15:32 /dev/xvdp2 # pvscan PV /dev/dm-2 VG mailsrv-vg lvm2 [25,33 GB / 0 free] Total: 1 [25,33 GB] / in use: 1 [25,33 GB] / in no VG: 0 [0 ] # lvscan inactive '/dev/mailsrv-vg/mailsrv-data' [25,33 GB] inherit # lsof -n|grep xvd tapdisk-i 7073 root 2u REG 253,0 32212254720 13328 /disks/daten/xen/mailsrv/root20080923.xvd Why does tapdisk-ioemu still have a reference? And how to remove it? I did a "kill 7073" now, but XEN didn't react anymore, had to reboot the whole machine. -- 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=465379 Charles Arnold <carnold@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carnold@novell.com, | |lbendixs@novell.com AssignedTo|cgriffin@novell.com |kwolf@novell.com QAContact|qa@suse.de |jdouglas@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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c2 --- Comment #2 from Kevin Wolf <kwolf@novell.com> 2009-01-12 10:03:58 MST --- Let me see if I understand your scenario: You're using a VM config which is pretty much standard, i.e. the guest harddisk is file-based and that file is accessed through file: (works) or tap:aio: (doesn't work). The one special thing about your setup is that the guest uses LVM for everything (including /boot), so to extract the kernel domUloader needs to attach the file first and then we need to bring up the LVM volumes on top of that. Is that the right description? What guest OS are you using? Is the assumption right that you are using domUloader and not pygrub? The relevant log files are /var/log/messages, /var/log/xen/tapdisk-ioemu.log and possibly /var/log/xen/qemu-dm-$YOUR_VM_NAME.log. Could you please attach the corresponding log file snippets (if in doubt, attach the complete files) after a failed VM start? -- 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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c3 Kevin Wolf <kwolf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO Info Provider| |novell-web@zmi.at --- Comment #3 from Kevin Wolf <kwolf@novell.com> 2009-01-13 11:20:04 MST --- I couldn't reproduce the problem on my machine by doing a simple SLES installation with LVM in the guest. Reading the description again, I think I didn't try rcxendomains though, maybe the problem occurs only there. -- 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=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c4 --- Comment #4 from Michael Monnerie <novell-web@zmi.at> 2009-01-16 16:45:56 MST --- I will attach all the files you mentioned. LVM is just for the data partition, my xen virtual disks are all partitioned (xvdp1 in above case is /, xvdp2 is /disks/data). So booting is no problem. domUloader is used, as I found this in an example on the Novell site. Didn't know about pygrub, is that the preferred thing to use now? Do you have a link to more info at hand? Right now I had a problem again. A xen host didn't react when trying to "xm create mailsrv2", so I tried looking with "xm block-list 0", which also just blocked. CTRL-C and "rcxend restart" helped, then I got this output: # xm block-list 0 Vdev BE handle state evt-ch ring-ref BE-path 51952 0 0 1 -1 -1 /local/domain/0/backend/tap/0/51952 How to get rid of this? I simply restarted the whole machine, then the domU started (autostart via xendomains) normally. I would really like to find the problem, as we want to use XEN in production. Here's the xen config I use for the domU: # cat /etc/xen/auto/mailsrv2 name="mailsrv2" uuid="07b3b164-721e-70ec-0d5e-d79a4c65f0fb" memory=600 maxmem=4000 vcpus=1 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 keymap="de" builder="linux" # this lines active during install time: #kernel="/boot/xen-install-kernel" #ramdisk="/boot/xen-install-initrd" # this lines activate during normal boot time: bootloader="/usr/lib/xen/boot/domUloader.py" bootargs="--entry=xvda1:/boot/vmlinuz-xen,/boot/initrd-xen" #extra=" ssh=1 root=/dev/xvda1 install=hd:/dev/xvdz " extra=" root=/dev/xvda1 " boot="c" disk=[ 'tap:aio:/disks/daten/xen/mailsrv2/root20090113.xvd,xvda,w', 'tap:aio:/disks/daten/xen/mailsrv2/work20090116.xvd,xvdb,w', 'tap:aio:/disks/daten/xen/mailsrv2/data20090115.xvd,xvdc,w', 'tap:aio:/disks/daten/xen/mailsrv2/swap20090113.xvd,xvdd,w', 'tap:cdrom:/disks/daten/dvd/openSUSE-11.1-DVD-x86_64.iso,xvdz,r', ] vif=[ 'mac=00:16:3e:10:00:31,bridge=br0', 'mac=00:16:3e:00:00:01,bridge=br1', ] vfb=['type=vnc,vncunused=1'] -- 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=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c5 Michael Monnerie <novell-web@zmi.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|novell-web@zmi.at | --- Comment #5 from Michael Monnerie <novell-web@zmi.at> 2009-01-16 16:47:35 MST --- Created an attachment (id=265838) --> (https://bugzilla.novell.com/attachment.cgi?id=265838) tar of the 4 log files requested -- 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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c6 --- Comment #6 from Kevin Wolf <kwolf@novell.com> 2009-01-19 03:29:51 MST --- I think we have two separate problems here. The first one is that tapdisk-ioemu/qemu sometimes fails to open your images. Your tapdisk-ioemu.log contains several times "Could not open image file /disks/daten/xen/mailsrv2/root20090115.xvd". From reading the code I can't tell what's going wrong, this isn't doing anything special. If you can't think of a reason why the image really wouldn't be accessible, I would need to have this reproduced with more debugging code. The second problem seems to be that the failed open results in a block device which is in some strange state between attached and detached. I will try if I can reproduce at least this one. -- 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=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c7 --- Comment #7 from Michael Monnerie <novell-web@zmi.at> 2009-01-19 09:03:43 MST --- The first could be because I'm in the test phase, creating new images with different filesystems etc. The second - the block device - is really annoying, it's always /dev/xvdp and sometimes contains partitions. But I couldn't find out where it comes from, where it's defined. I thought it might come from when I started playing around with XEN, so I remove /etc/xen and reinstalled the packages, and I grep'd the whole /etc for xvdp, with no result. Would be good if we could solve that. -- 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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c8 --- Comment #8 from Kevin Wolf <kwolf@novell.com> 2009-01-19 09:50:17 MST --- It might not be obvious what xvdp is for, but that's easy to explain. If you use domUloader (or pygrub) instead of directly specifying kernel and initrd in the config, domUloader needs to extract the kernel from the guest's /boot. So it temporarily attaches your image to xvdp on the host and mounts the right partition. In your case the attach fails inside tapdisk-ioemu for an unknown reason but the error handling doesn't notice that (so the second problem is only revealed by the first one). The good news is that it's easy for me to provoke such failure and I'm currently trying to understand what's happening in all detail. So for the second problem I might find a solution soon, but for the first one I still don't have a clue. -- 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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c9 Kevin Wolf <kwolf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P2 - High Status|NEW |ASSIGNED Severity|Normal |Major --- Comment #9 from Kevin Wolf <kwolf@novell.com> 2009-01-28 01:51:30 MST --- Could your try the new xen-tools package I made available at http://download.opensuse.org/repositories/home:/kevinwolf/openSUSE_11.1/x86_... and report back if it helps? This fixes the hanging half-attached block devices for me. Also, it should give a more precise error message in tapdisk-ioemu.log if the image cannot be opened. -- 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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c10 Kevin Wolf <kwolf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |novell-web@zmi.at --- Comment #10 from Kevin Wolf <kwolf@novell.com> 2009-01-30 05:47:11 MST --- Forgot to set NEEDINFO. -- 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=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c11 --- Comment #11 from Michael Monnerie <novell-web@zmi.at> 2009-02-04 10:43:24 MST --- I tested this new script on another server, which cannot start it's 2 xen VMs anymore now, again "51952 could not be connected, I'll attach a screenshot). I took 2 reboots to be sure: it does not work at all with this new release from you. Do you need logs again? That other server is a 2x quad core AMD Opteron, and he has the problem that very often, upon booting the machine, it completely freezes when starting the first XEN vm (even SYSRQ keys are dead). Should I file another bug report for that? The problem is, I can't report anything apart from "server freezes". -- 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=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c12 Michael Monnerie <novell-web@zmi.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|novell-web@zmi.at | --- Comment #12 from Michael Monnerie <novell-web@zmi.at> 2009-02-04 10:45:02 MST --- Created an attachment (id=270095) --> (https://bugzilla.novell.com/attachment.cgi?id=270095) Logs needed to see problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c13 --- Comment #13 from Michael Monnerie <novell-web@zmi.at> 2009-02-04 10:56:39 MST --- Created an attachment (id=270105) --> (https://bugzilla.novell.com/attachment.cgi?id=270105) Screenshot: not starting xen vm's -- 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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c14 Kevin Wolf <kwolf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |novell-web@zmi.at --- Comment #14 from Kevin Wolf <kwolf@novell.com> 2009-02-04 11:34:24 MST --- I actually wouldn't have expected the new package to resolve the root of your problems (I still can't explain what's going on). However, in any case you should no longer see disks in a "half-attached" state as mentioned in comment #1 where the device doesn't really appear, but you also can't detach it any more. I also didn't see these failures in the logs again, so can you confirm this? Do you still have problems with attaching or detaching xvdp if you start the VMs manually? Do the problems also occur if you manually try to xm block-attach/block-detach an image to Dom0? For the freezes please open another bug report. Of course without additional information it's unlikely that we can do anything about it. Is there no chance to attach a serial console to catch the crash dumps? -- 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=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c15 Michael Monnerie <novell-web@zmi.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|novell-web@zmi.at | --- Comment #15 from Michael Monnerie <novell-web@zmi.at> 2009-02-04 16:39:56 MST --- Hm, I don't get the point. Now, my virtual machines do not start at all, as you can see from the picture screenshot. So there are no block devices started, but the error "Device 51952 (tap) could not be connected" now comes all the time when trying to start a machine. Yes, there's no half-attached block device, there is none at all now. xm block-attach 0 tap:aio:/disks/vmdata/xen/dns2/dns2-data20090108.xvd xvdb w Error: Device 51728 (tap) could not be connected. Hotplug scripts not working. xm block-attach 0 file:/disks/vmdata/xen/dns2/dns2-data20090108.xvd xvdb w (this is OK) detach also without problem. Can you explain me how to attach a serial console? A null modem cable from a notebook to the server? But what to set up? Never did that... -- 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=465379 User jdouglas@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c16 --- Comment #16 from Jason Douglas <jdouglas@novell.com> 2009-02-04 17:55:17 MST --- (In reply to comment #15)
Can you explain me how to attach a serial console? A null modem cable from a notebook to the server? But what to set up? Never did that...
http://en.opensuse.org/How_to_Capture_Xen_Hypervisor_and_Kernel_Messages_usi... -- 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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c17 --- Comment #17 from Kevin Wolf <kwolf@novell.com> 2009-02-05 03:27:04 MST --- Sorry, I think what I told you is wrong (or at least incomplete). Updating xen-tools is not enough. Please update all Xen packages you've installed with the new versions from the mentioned repository (http://download.opensuse.org/repositories/home:/kevinwolf/openSUSE_11.1/x86_...), in particular you'll need the change in xen-libs. I'll also update the packages there once more to fix bug #472075 which was revealed by this patch. -- 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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c18 Kevin Wolf <kwolf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |novell-web@zmi.at --- Comment #18 from Kevin Wolf <kwolf@novell.com> 2009-02-10 04:57:37 MST --- Any news here? -- 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=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c19 --- Comment #19 from Michael Monnerie <novell-web@zmi.at> 2009-02-11 01:24:57 MST --- Sorry, I'm busy this week on another project, and next week probably on holidays. Will test ASAP, as this is important for us! -- 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=465379 User novell-web@zmi.at added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c20 Michael Monnerie <novell-web@zmi.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|novell-web@zmi.at | --- Comment #20 from Michael Monnerie <novell-web@zmi.at> 2009-02-13 10:20:26 MST --- I just have the problem again. My daughter (3.5 years) switched of the power behind the UPS for the server running XEN. So I installed your tools now, and made /etc/init.d/xen restart. It didn't start then. So I rebooted the machine again - it works now! BTW: When I "xm list", there's an old version of my xen mailserver which I cannot get rid of: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2768 2 r----- 36.6 mailsrv 400 1 450.3 mailsrv2 1 1200 2 -b---- 12.4 orion:~ # xm destroy mailsrv orion:~ # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2768 2 r----- 37.1 mailsrv 400 1 450.3 mailsrv2 1 1200 2 -b---- 12.4 How can I remove that? Is that also a problem with the xen-tools I guess? -- 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=465379 User kwolf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465379#c21 Kevin Wolf <kwolf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Found By|--- |Community User Resolution| |FIXED --- Comment #21 from Kevin Wolf <kwolf@novell.com> 2009-02-16 04:54:53 MST --- This seems to be a managed domain which is already shut off (in other words: "destroyed"). Is "xm delete mailsrv" what you want? For this bug, I'm glad to hear that it works now. Marking the bug as fixed. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com