Actually, the command when we try to restore the vm domain returns this in the
xend.log:
[2007-05-16 14:50:13 xend 2903] ERROR (XendDomain:268) Restore failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 263,
in domain_restore_fd
return XendCheckpoint.restore(self, fd)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line
118, in restore
raise XendError("not a valid guest state file: found '%s'" %
XendError: not a valid guest state file: found 'ëH<90>^P<8e>[EMAIL
PROTECTED]@^@<8e>Ã<8e>Ã'
[2007-05-16 15:29:19 xend 2903] ERROR (XendDomain:268) Restore failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 263,
in domain_restore_fd
return XendCheckpoint.restore(self, fd)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line
118, in restore
raise XendError("not a valid guest state file: found '%s'" %
XendError: not a valid guest state file: found 'ëH<90>^P<8e>[EMAIL
PROTECTED]@^@<8e>Ã<8e>Ã'
That is while using the user interface, doing a "restore domain file", and
pointing to the storagefile.
Also, fyi:
[EMAIL PROTECTED] ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 3895 4 r----- 417.3
Thank you,
Michel
-----Message d'origine-----
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Andrei Pascal
Envoyé : 16 mai 2007 15:40
À : Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Objet : RE: [rhelv5-list] RHEL5 (para-)virtualizing RHEL5
On Wed, May 16, 2007 22:35, [EMAIL PROTECTED] wrote:
> Follow-up #1.
[snip]
> Once the installation got finalized (in /mnt/vm/1/storagefile), it rebooted
> but the server would not be in the list. It told us "error restoring
> '/mnt/vm/1/storagefile '. Is the domain already running?". We tried
> rebooting the principal server, we tried restoring it, we tried chmod 777
> it, nothing would make it work.
>
> We had the same problem while creating a full hw virtualization, but thought
> it was one of our config. Our next trial in 2 hours will be to reinstall the
> server and have 4 specific partitions for our 4 VMs.
>
> That is where we are at.
>
> Michel
Michel,
Don't start reinstalling the server. In a console (shell) just run
xm start vm (or whatever the machine name was).
Check again in virt-manager the state of the virtual machine.
HTH,
--
Andrei Pascal
RHCX
Romsym Data SRL
Life is like arriving late for a movie, having to figure out what was going on
without bothering everybody with a lot of questions, and then being
unexpectedly called away before you find out how it ends.
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
