Bug 512319 - On rhel4.8 DomU after installing run virsh save/restore,the domU will freeze
Summary: On rhel4.8 DomU after installing run virsh save/restore,the domU will freeze
Keywords:
Status: CLOSED DUPLICATE of bug 396631
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel-xen
Version: 4.8
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Andrew Jones
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-17 10:09 UTC by koka xiong
Modified: 2010-07-19 13:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-21 17:28:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description koka xiong 2009-07-17 10:09:33 UTC
Description of problem:
On rhel5.3 Dom0 install rhel4.6 DomU FV guest,then install kmod-xenpv.
then run virsh save domU file
The process virsh save can't pause unless using Ctrl+C

Version-Release number of selected component (if applicable):
kmod-xenpv-0.1-10.el4.rpm
module-init-tools-3.1-0.pre5.3.4.el4_6.1
modversions-1.0-4.el4_6.1

How reproducible:
always

Steps to Reproduce:
1.On rhel 5.3 Dom0 install rhel 4.6 domU FV guest,then install kmod-xenpv
according to the documentation
2.Open a terminal then run lsmod |grep xen, 
verify the 
xen_vbd,xen_vnif,xen_balloon,xen_platform_pci are loaded OK
3.In dom0 run virsh save domU filename to save the domU
  
Actual results:
The virsh save process works all the time,but you will see the file size doesn't change,it is 952.
In domU terminal,input something, it doesn't work though the cursor is blinking all the time
Kill the virsh save process, then run virsh save domU another file name
It will output
libvir:error:invalid argument in _virGetDomain
error:failed to get domain 'domU'

Expected results:
It can run virsh save domU filename well

Additional info:
Before I install xenpv then run virsh save domU filename,it can work well
i386,x86_64 all have the same problem

Comment 1 Chris Lalancette 2009-07-17 10:16:28 UTC
Can you try this same test with RHEL 4.8, which has the PV-on-HVM drivers included?  Unfortunately there was a bug prior to 4.8 which would cause hangs in the guest during save, and would cause something similar to this.  If you can't reproduce on 4.8, then we'll just close this as CURRENTRELEASE.

Chris Lalancette

Comment 2 koka xiong 2009-07-17 10:46:21 UTC
I have tried on rhel 4.8,on rhel 4.8,I can't install xenpv well.Please refer to bug 512326,

So I have to try it on rhel 4.6

Comment 3 Chris Lalancette 2009-07-17 10:58:55 UTC
(In reply to comment #2)
> I have tried on rhel 4.8,on rhel 4.8,I can't install xenpv well.Please refer to
> bug 512326,
> 
> So I have to try it on rhel 4.6  

As I said in Comment #1 and BZ 512326 which I just closed, that's expected.  The PV-on-HVM drivers are built in to the 4.8 kernel, so no xenpv-kmod package is required.  Just modprobe xen-vnif and modprobe xen-vbd should work find after a 4.8 guest installation.  Then try your test again.

Chris Lalancette

Comment 4 koka xiong 2009-07-17 11:53:12 UTC
I have retested again on 4.8 kernel according to your suggestion.
modprobe xen-vnif,
modprobe xen-vbd
then run virsh save domU filename
         virsh restore filename
After the domU is restored, the screen is freezing,it has no response.

Comment 5 Chris Lalancette 2009-07-17 12:32:05 UTC
OK, that's the information we're looking for, thanks.  Andrew, any chance you can take a look at this, try to recreate, and see what's going on?

Chris Lalancette

Comment 6 Andrew Jones 2009-07-17 22:38:18 UTC
I started looking at this today.  I don't get a frozen screen, but my domU resets.  I tried both modules separately and found that the save/restore works fine when only xen-vnif is loaded.  xm dmesg shows some mfn errors after the failure.  I'll continue looking at this Tuesday, since I have PTO Monday.

Andrew

Comment 7 Andrew Jones 2009-07-21 17:28:42 UTC
This is a dup of 396631 which is a clone of 396621.  The problem goes away using the 4.8 kernel, but modprobing in patched modules.

Closing as a dup.

*** This bug has been marked as a duplicate of bug 396631 ***

Comment 8 Chris Lalancette 2010-07-19 13:23:43 UTC
Clearing out flags for reporting purposes.

Chris Lalancette


Note You need to log in before you can comment on or make changes to this bug.