public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerry Reno <greno@verizon.net>
To: kvm@vger.kernel.org
Subject: After upgrading from  F7 kvm-65-15  to  F10 kvm-74-10
Date: Sun, 29 Mar 2009 12:15:55 -0400	[thread overview]
Message-ID: <49CF9EBB.3070404@verizon.net> (raw)

Hi,
  We had setup a number of VM's using KVM-65 running on F7 some time 
ago.  We just ocmpleted upgrading a number of hosts to F10 and with that 
came KVM-74-10.  We had some problems after that upgrade.  First, none 
of the VM's would start.  After digging around awhile we finally figured 
out that we had to once again 'chcon -t virt_image_t  path_to_image' as 
we had done back when we first setup the VM's.  But what is the proper 
procedure so that we don't lose the selinux attributes on these image 
files?  Shouldn't this be set by fedora's selinux-policy package?  Or by 
the kvm upgrade?  Next issue is that with KVM-74 we are having a lot of 
problems with the dreaded "TCP/IP VNC connection to hypervisor host has 
been refused or disconnected".  This has now happened to one of the VM's 
after it was shutdown and then we tried to Run it again and we haven't 
found a way to reconnect to it.  Also, another VM has this weird problem 
that when you run it, it looks like its running because the screen keeps 
changing size but all we see is a blank palette on the console page, no 
screen at all, but the thing is running.  How do we fix these things?

Regards,
Gerry


             reply	other threads:[~2009-03-29 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29 16:15 Gerry Reno [this message]
2009-03-29 21:47 ` After upgrading from F7 kvm-65-15 to F10 kvm-74-10 Gerry Reno
2009-03-30  1:18   ` Gerry Reno
2009-03-30  3:08     ` Gerry Reno
2009-03-29 22:00 ` Ross McKay
2009-03-29 23:56   ` Gerry Reno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49CF9EBB.3070404@verizon.net \
    --to=greno@verizon.net \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox