Init segfault is reproducible even on kernels that works for me before on Precise. More specifically I have same init segfault with 3.2.0-31 on host and 3.2.0-31 in guest VM (backtrace attached). If I mount NFS shares using mount CL utility or script that exacute on boot there is no init segfault - that results of at least one day testing of this issue in different VM's on different kernels (host & guest).
** Description changed: - Init in VM segfault if NFS-client installed in guest KVM system (while nfs-common package installation or on next boot after package installation). Please look at attached calltraces taken from Precise and Quantal VM's. + Init in VM segfault on boot if NFS-client installed in guest KVM system and there is at least one NFS share in fstab. Please look at attached calltraces taken from Precise and Quantal VM's. Host system is Quantal (3.5.0-17-generic) upgraded from Precise (upgraded without any errors). This regression appear only after upgrade so I guess this issue related to Linux 3.5. Testing of upstream 3.6 kernel is impossible due to another regression. What additional information I need to provide? ** Attachment added: "Linux 3.2 segfault in KVM (host Linux 3.2).png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065831/+attachment/3408667/+files/Linux%203.2%20segfault%20in%20KVM%20%28host%20Linux%203.2%29.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065831 Title: Init in VM segfault if NFS-client installed in guest KVM system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065831/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
