https://bugzilla.novell.com/show_bug.cgi?id=848754 https://bugzilla.novell.com/show_bug.cgi?id=848754#c0 Summary: Xen domU can't find VG after dom0 is rebooted Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas@suse.com ReportedBy: eruby@knowledgematters.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 I build a Xen server using OpenSUSE 12.3 with all of the latest patches. I can reboot the server and it reboots just fine, no problems. Then I create several OpenSUSE 12.3 VMs. I can reboot the VMs and they reboot just fine, no problems. However, once I reboot the dom0 Xen server the domU VMs will no longer boot. The console shows 'Volume group "whatever" not found' errors. dom0 has a single physical LUN from a SAN with an LVM installed. The LVM has the VG name "switch". We are using multipathd and there are four fiberchannel paths to each LUN. The domU's are also single physical LUN from the same SAN with an LVM installed. The LVMs have a VG name matching the host name, e.g. host www4 has VG "www4". Everything works fine as long as I do not reboot dom0. Once dom0 reboots, none of the domUs can find their volume groups. I can see the volume groups when I type "vgdisplay" or "vgs" in dom0, but they cannot be accessed in their domU VMs. I did verify that the blkbk module is loaded. I have rebuilt the OpenSUSE 12.3 Xen server 4 times now. I get the same results each time. I suspect any problem this serious in 12.3 Xen would already have an open ticket, so there's probably something in my setup that isn't correct, or it could be something about the combination of multipathd + LVM + Xen I'm using. If anyone has any suggestions of what I should look at or what else I should try I'm open to suggestions. Separate data point: I also tried shutting down a OpenSUSE 11.4 domU running on a OpenSUSE 11.4 Xen server, I changed it's LUN mapping on the SAN so the LUN was visible on the OpenSUSE 12.3 Xen server, then tried to boot it up on the OpenSUSE 12.3 Xen server. I got the same error on the console that it could not find its volume group. I shut it down, remapped the LUN back to the 11.4 Xen server and bought it back up on the 11.4 Xen server without a problem. Reproducible: Always Steps to Reproduce: 1. Build OpenSUSE 12.3 Xen server 2. Build OpenSUSE 12.3 VMs 3. Reboot OpenSUSE 12.3 Xen Server 4. OpenSUSE 12.3 VMs no longer boot Actual Results: Non-working VMs Expected Results: Working VMs The Xen console for www4 shows: Will boot selected entry in 2 seconds [ 0.172967] PCI: Fatal: No config space access function found [ 0.176373] Unable to read sysrq code in control/sysrq [ 1.365196] i8042: No controller found [ 1.366095] /home/abuild/rpmbuild/BUILD/kernel-xen-3.7.10/linux-3.7/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) doing fast boot Creating device nodes with udev Volume group "www4" not found Volume group "www4" not found Volume group "www4" not found Volume group "www4" not found Volume group "www4" not found Trying manual resume from /dev/www4/swap0 Trying manual resume from /dev/www4/swap0 Waiting for device /dev/www4/root to appear: Reading all physical volumes. This may take a while... No volume groups found PARTIAL MODE. Incomplete logical volumes will be processed. Volume group "www4" not found PARTIAL MODE. Incomplete logical volumes will be processed. Volume group "www4" not found PARTIAL MODE. Incomplete logical volumes will be processed. Volume group "www4" not found PARTIAL MODE. Incomplete logical volumes will be processed. Volume group "www4" not found PARTIAL MODE. Incomplete logical volumes will be processed. Volume group "www4" not found PARTIAL MODE. Incomplete logical volumes will be processed. Volume group "www4" not found [this goes on for a long time.............] -- 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.