[Xen-users] problem on loading VM

[janskey <janskey_boy@xxxxxxxxx>]

Hi All,

Has anyone encounter this problem:

Issue1: VM1 can't boot automatically in /etc/xen/auto
-------------------------------------------------------
[root@vm1]# tail -f /var/log/xen/xend
[2008-12-19 17:20:50 xend 3358] INFO (XendCheckpoint:351) ERROR Internal error: Error when reading page (type was 0)
[2008-12-19 17:20:53 xend 3358] INFO (XendCheckpoint:351) Restore exit with rc=1
[2008-12-19 17:20:53 xend.XendDomainInfo 3358] DEBUG (XendDomainInfo:1560) XendDomainInfo.destroy: domid=2
[2008-12-19 17:20:53 xend.XendDomainInfo 3358] DEBUG (XendDomainInfo:1568) XendDomainInfo.destroyDomain(2)
[2008-12-19 17:20:53 xend.XendDomainInfo 3358] ERROR (XendDomainInfo:1575) XendDomainInfo.destroy: xc.domain_destroy failed.
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1573, in destroyDomain
    xc.domain_destroy(self.domid)
Error: (3, 'No such process')
[2008-12-19 17:20:53 xend 3358] ERROR (XendDomain:278) Restore failed
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 273, in domain_restore_fd
    return XendCheckpoint.restore(self, fd)
  File "/usr/lib/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 219, in restore
    forkHelper(cmd, fd, handler.handler, True)
  File "/usr/lib/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 339, in forkHelper
    raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib/xen/bin/xc_restore 21 2 1 2 0 0 0 failed

Here are the details:

Issue1: I add my Guest OS (vm1) to /etc/xen/auto so that it will run automatically when the Host is restarted. But VM1 can't boot because of the error above. If I start manually using "xm create vm1", it can run normally. The only problem is it can't run automatically. What does the error means?


Issue2: VM2 can't load second interface if run manually using "xm create" but putting it on /etc/xen/auto 2nd interface is ok
---------------------------------------------------------------------------------------------------------------------------
SenarioA:
If put VM2 in /etc/xen/auto, it runs normally and has no problem but I found something when I get in to the VM using console:

[root@vm2]# xm console 1
BUG: soft lockup detected on CPU#1!
 [<c043ea67>] softlockup_tick+0x98/0xa6
 [<c0408b7d>] timer_interrupt+0x504/0x557
 [<c043ec9b>] handle_IRQ_event+0x27/0x51
 [<c043ed58>] __do_IRQ+0x93/0xe8
 [<c040672b>] do_IRQ+0x93/0xae
 [<c053a045>] evtchn_do_upcall+0x64/0x9b
 [<c0404ec5>] hypervisor_callback+0x3d/0x48
 [<c0407fd1>] raw_safe_halt+0x8c/0xaf
 [<c0402bca>] xen_idle+0x22/0x2e
 [<c0402ce9>] cpu_idle+0x91/0xab
 =======================
 
Red Hat Enterprise Linux Server release 5 (Tikanga)
Kernel 2.6.18-8.el5xen on an i686
 
vm2 login:
 
A) Is this a bug?
B) what is the output means?

SenarioB:
If I remove vm2 on /etc/xen/auto, reboot the Hosts and then run the vm2 manually using "xm create vm2", my 2nd interface can't be loaded. Only 1st interface. Any idea?

 

cheers,

janskey

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users