Just starting and playing around with Xen on Centos 5. I created a new VM (para-virtualized) with the Virtual Machine Manager, installed Centos 5 minimal on it, rebooted after successful installation. The VM console vanishes on shutdown and that's it. The VM id vanishes from the VM Manager and there's no way to get it back. It looks like the new VM doesn't exist. xm list shows only Domain-0, virsh list --all tells me that it cannot list the inactive domains. A restore from the VM file fails as well. The VM image file exists (in /home/vm), a config file for it in /etc/xen exists. But I don't see where the path to the image file might have been saved. Maybe that's the problem? (I know the location can create a problem with SELinux, but I'm currently running permissive and only testing.)
Kai
On Mon, 27 Aug 2007, Kai Schaetzl wrote:
Just starting and playing around with Xen on Centos 5. I created a new VM (para-virtualized) with the Virtual Machine Manager, installed Centos 5 minimal on it, rebooted after successful installation.
I did a presentation in some depth at a local LUG (third in a series) just last Saturday, and the notes are at: http://www.colug.net/notes/0708mtg/
The VM console vanishes on shutdown and that's it. The VM id vanishes from the VM Manager and there's no way to get it back. It looks like the new VM doesn't exist. xm list shows only Domain-0, virsh list
do a:
cd /etc/xen
and rerun the command -- 'xm' does not have a reasonable default search path.
--all tells me that it cannot list the inactive domains. A restore from the VM file fails as well. The VM image file exists (in /home/vm), a config file for it in /etc/xen exists. But I don't see where the path to the image file might have been saved. Maybe that's the problem? (I know the location can create a problem with SELinux, but I'm currently running permissive and only testing.)
yes -- the SELinux issue also is present as noted in the outline.
-- Russ Herrold
R P Herrold wrote on Mon, 27 Aug 2007 11:29:47 -0400 (EDT):
I did a presentation in some depth at a local LUG (third in a series) just last Saturday, and the notes are at: http://www.colug.net/notes/0708mtg/
Thanks, browsed it and keep a link to it. I didn't know Citrix just bought XenSource.
cd /etc/xenand rerun the command -- 'xm' does not have a reasonable default search path.
Still no go. It doesn't exist according to xm. It also ignores the sample config files in this directory. How does it determine they are samples?
Kai
On Mon, 27 Aug 2007, Kai Schaetzl wrote:
R P Herrold wrote on Mon, 27 Aug 2007 11:29:47 -0400 (EDT):
cd /etc/xen
hmmm -- As I recall, you noted in your initial post having built the xen images at: /home/xen. Please, could you please place in a pastebin (http://www.pastebin.ca/) the following:
ls -l /etc/xen ls -l /home/xen
and advise us of the pastebin URL?
thanks
-- Russ Herrold
R P Herrold wrote on Mon, 27 Aug 2007 12:13:47 -0400 (EDT):
hmmm -- As I recall, you noted in your initial post having built the xen images at: /home/xen. Please, could you please place in a pastebin (http://www.pastebin.ca/) the following:
ls -l /etc/xen ls -l /home/xenand advise us of the pastebin URL?
That's so short I could post it here. But here you go:
test1 is the name of the VM. It's the first and only I created so far. I made one or two edits in xend-config.sxp *after* the problem occurred, nothing that could have any effect on this (mainly enabled the http access).
Kai
Hi all
1/ ls the Centos 5.0 equal to Redhat enterprise 5? 2/ what is meaning live CD? CentOS-5.0-i386-LiveCD.iso
ls it meaning rescure CD? 3/ what is meaning of torrent? it is just 278K
Thank you
____________________________________________________________________________________ Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/
ann kok wrote:
Hi all
1/ ls the Centos 5.0 equal to Redhat enterprise 5? 2/ what is meaning live CD? CentOS-5.0-i386-LiveCD.iso
ls it meaning rescure CD? 3/ what is meaning of torrent? it is just 278K
Thank you
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/ _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS5 is based on RHEL5.
A Live CD typically means an OS on a bootable CD.
A Rescue CD is typically used to help 'rescue' a corrupted system when the bootable partition on the system can't be reached for some reason.
A torrent file is a function of 'BitTorrent'. This is a distributed method of providing content, not unlike gnutella clients.
ann kok spake the following on 8/27/2007 10:16 AM:
Hi all
1/ ls the Centos 5.0 equal to Redhat enterprise 5? 2/ what is meaning live CD? CentOS-5.0-i386-LiveCD.iso
ls it meaning rescure CD? 3/ what is meaning of torrent? it is just 278K
And since you are new, you won't get the flogging for hijacking someone else's thread. If you are making a new message don't reply to someone else's message and change the subject.
Please: when you want to send a question use "new message" and not "reply", thanks.
Kai
On Mon, 27 Aug 2007, Kai Schaetzl wrote:
That's so short I could post it here. But here you go:
test1 is the name of the VM. It's the first and only I created so far. I made one or two edits in xend-config.sxp *after* the problem occurred, nothing that could have any effect on this (mainly enabled the http access).
I have never tried using the LO as the interface ---
27/08/2007 03:08:46 Client 127.0.0.1 gone
and do not know what may have happened in the edit of xend-config.sxp, but do not know of any need to edit that.
These are wild guesses, but to partition the problem further, either restore xend-config.sxp to stock, or try to install against an interface where bridging can occur -- I mage a PDF of: http://www.colug.net/notes/0708mtg/xen-COLUG-Aug2007.txt so that we have page numbers: see page 4 of http://www.colug.net/notes/0708mtg/xen-COLUG-Aug2007.pdf I am not at all sure that the LO device can do that.
-- Russ Herrold
R P Herrold wrote on Mon, 27 Aug 2007 14:14:12 -0400 (EDT):
I have never tried using the LO as the interface ---
27/08/2007 03:08:46 Client 127.0.0.1 gone
I think this is misleading you in the wrong direction. That doesn't say anything about which IP the guest is using. Actually it had a public IP address, so I could install via FTP from a CentOS mirror. That local IP above just means that the VM is running on localhost and not on another machine.
and do not know what may have happened in the edit of xend-config.sxp, but do not know of any need to edit that.
I edited it to get the http interface to it. You can then access it on port 8000 via http. (I see only two root slashes, though, when connecting. But I assume that's normal since it thinks there are no VMs available at the moment.) As I said I did that *after* hitting the problem, as you can also see from the save time. So, that file sure is okay. What I don't udnerstand is how xend or xm determines where the image file is located. I can't see that anywhere. And the same applies to how it determines that a file in /etc/xen configures an existing VM and others are only samples. There must be another information store that has this information. I browsed thru the RHEL Virtualization Guide and some other documents, but couldn't find any clues to this.
Kai
On Mon, 27 Aug 2007, Kai Schaetzl wrote:
What I don't udnerstand is how xend or xm determines where the image file is located. I can't see that anywhere. And the same applies to how it
man xm
holds this answer -- if the path variable is not set, it seems to look at the CWD, from some of the error cruft I can provoke (it does not sanity test with 'file' that it has an image, before starting to run a matching named file it may find in the CWD, such as the config file in /var/xen in my case ;)
-- Russ Herrold
R P Herrold wrote on Mon, 27 Aug 2007 15:25:41 -0400 (EDT):
holds this answer -- if the path variable is not set, it seems to look at the CWD, from some of the error cruft I can provoke
The problem is not the configuration file, the problem is the vm filesystem file. That is not mentioned anywhere. How do you shutdown or start your VMs? I made another test and created a second VM and then *saved* that VM. That saved it in the state it was in and I was able to restore it from that save file. However, when I then shutdown the same VM the save file has completely vanished and only the filesystem file is there as before. There's no way to "revive" it then. This can't be it, I must be missing something, although I've read almost all of the Virtualization Guide by now. Or is it really intended that the only way to keep a VM is to save it in the middle of operation and restore it?
Kai
On Mon, 2007-08-27 at 22:18 +0200, Kai Schaetzl wrote:
R P Herrold wrote on Mon, 27 Aug 2007 15:25:41 -0400 (EDT):
holds this answer -- if the path variable is not set, it seems to look at the CWD, from some of the error cruft I can provoke
The problem is not the configuration file, the problem is the vm filesystem file. That is not mentioned anywhere. How do you shutdown or start your VMs? I made another test and created a second VM and then *saved* that VM. That saved it in the state it was in and I was able to restore it from that save file. However, when I then shutdown the same VM the save file has completely vanished and only the filesystem file is there as before. There's no way to "revive" it then. This can't be it, I must be missing something, although I've read almost all of the Virtualization Guide by now. Or is it really intended that the only way to keep a VM is to save it in the middle of operation and restore it?
Kai
As another poster already said...`man xm`. Here's a hint: `/usr/sbin/xm create ${config_file}`. When you shutdown a guest it does leave the list of running domains (i.e. what `xm list` shows you). The default location for VM configurations is '/etc/xen/'. If you want them to start at boot, sym-link the conf to '/etc/xen/auto/'.
Timothy Selivanow wrote on Mon, 27 Aug 2007 14:55:15 -0700:
As another poster already said...`man xm`.
Doesn't help, doesn't tell me how to start a VM that wasn't saved. No, "xm create" does *not* do this.
Here's a hint: `/usr/sbin/xm
create ${config_file}`. When you shutdown a guest it does leave the list of running domains (i.e. what `xm list` shows you). The default location for VM configurations is '/etc/xen/'. If you want them to start at boot, sym-link the conf to '/etc/xen/auto/'.
And how do I start this VM in a running system? Or is booting it up when xend boots up the only option? If so, then I don't see this mentioned anywhere.
Kai
On Tue, 2007-08-28 at 00:15 +0200, Kai Schaetzl wrote:
Timothy Selivanow wrote on Mon, 27 Aug 2007 14:55:15 -0700:
As another poster already said...`man xm`.
Doesn't help, doesn't tell me how to start a VM that wasn't saved. No, "xm create" does *not* do this.
Here's a hint: `/usr/sbin/xm
create ${config_file}`. When you shutdown a guest it does leave the list of running domains (i.e. what `xm list` shows you). The default location for VM configurations is '/etc/xen/'. If you want them to start at boot, sym-link the conf to '/etc/xen/auto/'.
And how do I start this VM in a running system? Or is booting it up when xend boots up the only option? If so, then I don't see this mentioned anywhere.
Kai
I've used `xm create ${config_file}` many, many times. It'll work :)
$ sudo /usr/sbin/xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 485 8 r----- 2838940.8 Domain_Services 1 511 1 -b---- 1962.0 Mail_Services 2 511 1 -b---- 1989.9 Web_Services 3 511 2 -b---- 4927.6
$ sudo /usr/sbin/xm shutdown Web_Services
$ sudo /usr/sbin/xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 485 8 r----- 2839060.6 Domain_Services 1 511 1 -b---- 1962.1 Mail_Services 2 511 1 -b---- 1989.9
$ sudo /usr/sbin/xm create /etc/xen/Web_Services Using config file "/etc/xen/Web_Services". Going to boot CentOS (2.6.18-8.1.8.el5xen) kernel: /vmlinuz-2.6.18-8.1.8.el5xen initrd: /initrd-2.6.18-8.1.8.el5xen.img Started domain Web_Services
$ sudo /usr/sbin/xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 485 8 r----- 2839121.3 Domain_Services 1 511 1 -b---- 1962.1 Mail_Services 2 511 1 -b---- 1990.0 Web_Services 4 512 2 r----- 2.4
02c0c.004b4d96@news.conactive.com> X-Rcpt-To: centos@centos.org
Ok, I finally managed to get this going. There was a problem with my second test2 domain that prevented reading the filesystem, so it couldn't start up. I had done all my later testing with test2. Then I tried with test1 again and there the "xm create" works. I find that "create" is rather misleading, it doesn't "create" a VM it starts it up. Unfortunately, the documentation builds on this misleading information by saying it makes or creates a domain. And there's obviously no way to start a VM from the Virtual Machine Manager which is quite surprising. Thanks for bearing with me.
Kai
-
ann kok -
Kai Schaetzl -
R P Herrold -
Ray Leventhal -
Scott Silva -
Timothy Selivanow