FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 05-08-2008, 06:21 PM
Gerry Reno
 
Default F9 and KVM

Tom London wrote:

Try the following: "chcon -t virt_image_t ./f9-preview-i386-dvd.iso"
before running qemu-kvm.



Didn't help. Still can't initialize the virtual drive. Still seeing
avc denial message to the virtual drive image file.
I've tried restorecon -v on the file and fixfiles. Neither one gets rid
of the problem.


Regards,
Gerry


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-08-2008, 06:23 PM
"Tom London"
 
Default F9 and KVM

On Thu, May 8, 2008 at 11:18 AM, Suren Karapetyan
<surenkarapetyan@gmail.com> wrote:
> Tom London wrote:
>>
>> 2008/5/8 Gerry Reno <greno@verizon.net>:
>>>
>>> Gerry Reno wrote:
>>>
>>> Here's what I found so far:
>>> In BIOS there is a setting "AMD Cool n Quiet". I thought this was some
>>> type of fan thing. It is not. It controls the cpu speed. So I disable
>>> this and now dmesg and /proc/cpuinfo both show same at 2510 MHz. And I
>>> try
>>> creating a new F9 VM with 1 VCPU. The install now seems to run at a
>>> normal
>>> speed but still I cannot get F9 to install in VM. It says partition
>>> table
>>> on /dev/sda is unreadable and it needs to initialize. So I say yes and
>>> it
>>> sits there for about 10 mins until it give you an error (i/o error on
>>> device) retry,ignore,cancel. No choice helps. So I try with F7 as well
>>> and
>>> same thing, it cannot initialize the virtual drive (mine is file-based).
>>>
>>>
>>> I think SELinux is causing some problems with KVM:
>>>
>>> log:
>>> May 7 18:29:54 grp-01-10-01 yum: Installed: kvm-65-1.fc9.i386
>>> May 7 23:00:14 grp-01-10-01 setroubleshoot: SELinux is preventing
>>> qemu-kvm
>>> (qemu_t) "write" to ./MX_1-0.vmdk (var_t). For complete SELinux messages.
>>> run sealert -l c5d1da68-2969-4a93-843c-774a346e4705
>>> May 7 23:29:12 grp-01-10-01 setroubleshoot: SELinux is preventing
>>> qemu-kvm
>>> (qemu_t) "write" to ./MX_1-0.vmdk (var_t). For complete SELinux messages.
>>> run sealert -l c5d1da68-2969-4a93-843c-774a346e4705
>>> May 8 12:20:56 grp-01-10-01 setroubleshoot: SELinux is preventing
>>> qemu-kvm
>>> (qemu_t) "write" to ./MX_1-0.vmdk (var_t). For complete SELinux messages.
>>> run sealert -l e1adef63-a2c9-4e8e-a834-14cc9df77259
>>> May 8 12:20:56 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:20:56 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:20:56 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:20:56 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:20:56 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:20:56 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:20:56 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:20:56 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:21:06 grp-01-10-01 kernel: kvm: 3997: cpu0 kvm_set_msr_common:
>>> MSR_IA32_MC0_STATUS 0x0, nop
>>> May 8 12:21:06 grp-01-10-01 kernel: kvm: 3997: cpu1 kvm_set_msr_common:
>>> MSR_IA32_MC0_STATUS 0x0, nop
>>> May 8 12:21:06 grp-01-10-01 kernel: kvm: 3997: cpu2 kvm_set_msr_common:
>>> MSR_IA32_MC0_STATUS 0x0, nop
>>> May 8 12:21:07 grp-01-10-01 kernel: kvm: 3997: cpu3 kvm_set_msr_common:
>>> MSR_IA32_MC0_STATUS 0x0, nop
>>> May 8 12:21:08 grp-01-10-01 kernel: kvm: emulating exchange as write
>>> May 8 12:26:20 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:26:20 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 12:26:20 grp-01-10-01 setroubleshoot: SELinux is preventing
>>> qemu-kvm
>>> (qemu_t) "write" to ./TEST1.img (var_t). For complete SELinux messages.
>>> run
>>> sealert -l 15c2312c-dd5f-44fd-b2d1-b9fb90188284
>>> May 8 12:26:20 grp-01-10-01 setroubleshoot: SELinux is preventing
>>> qemu-kvm
>>> (qemu_t) "write" to ./f9-preview-i386-dvd.iso (var_t). For complete
>>> SELinux
>>> messages. run sealert -l af4954a1-8379-403d-bc1b-ff6b1e0041df
>>> May 8 12:26:26 grp-01-10-01 kernel: kvm: 4075: cpu0 kvm_set_msr_common:
>>> MSR_IA32_MC0_STATUS 0x0, nop
>>> May 8 13:28:25 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 13:28:25 grp-01-10-01 kernel: kvm: guest NX capability removed
>>> May 8 13:28:25 grp-01-10-01 setroubleshoot: SELinux is preventing
>>> qemu-kvm
>>> (qemu_t) "write" to ./TEST1.img (var_t). For complete SELinux messages.
>>> run
>>> sealert -l 15c2312c-dd5f-44fd-b2d1-b9fb90188284
>>> May 8 13:28:25 grp-01-10-01 setroubleshoot: SELinux is preventing
>>> qemu-kvm
>>> (qemu_t) "write" to ./f9-preview-i386-dvd.iso (var_t). For complete
>>> SELinux
>>> messages. run sealert -l af4954a1-8379-403d-bc1b-ff6b1e0041df
>>> May 8 13:29:35 grp-01-10-01 kernel: kvm: 4353: cpu0 kvm_set_msr_common:
>>> MSR_IA32_MC0_STATUS 0x0, nop
>>>
>>>
>>> I ran a fixfiles on all filesystems but still get the messages.
>>>
>>>
>>> Regards,
>>> Gerry
>>>
>>
>> Try the following: "chcon -t virt_image_t ./f9-preview-i386-dvd.iso"
>> before running qemu-kvm.
>>
>> tom
>
> And what about ./TEST1.img ?
> I think THIS is the problem.
>
> Is ./TEST1.img the file which holds hda?
>
Yeah.... sorry..... only saw the .iso one.

tom

--
Tom London

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-08-2008, 06:24 PM
"Tom London"
 
Default F9 and KVM

On Thu, May 8, 2008 at 11:21 AM, Gerry Reno <greno@verizon.net> wrote:
> Tom London wrote:
>>
>> Try the following: "chcon -t virt_image_t ./f9-preview-i386-dvd.iso"
>> before running qemu-kvm.
>>
>>
>>
>
> Didn't help. Still can't initialize the virtual drive. Still seeing avc
> denial message to the virtual drive image file.
> I've tried restorecon -v on the file and fixfiles. Neither one gets rid of
> the problem.
>
> Regards,
> Gerry
>
Neither restorecon nor fixfiles will fix this.

Must run "chcon" on all the "image type files", e.g., hda, cdrom, etc.

tom
--
Tom London

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-08-2008, 06:31 PM
Gerry Reno
 
Default F9 and KVM

I ran the chcon on both the image and the iso and no change. Still gets
error trying to initialize the virtual drive.


Regards,
Gerry

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-08-2008, 06:35 PM
Gerry Reno
 
Default F9 and KVM

Gerry Reno wrote:
I ran the chcon on both the image and the iso and no change. Still
gets error trying to initialize the virtual drive.


I think the problem is that virt-manager is creating a new TEST1.img
file everytime. Because I'm destroying the old instance and deleting
the old image.


Regards,
Gerry

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-08-2008, 06:42 PM
Jesse Keating
 
Default F9 and KVM

On Thu, 2008-05-08 at 14:35 -0400, Gerry Reno wrote:
> I think the problem is that virt-manager is creating a new TEST1.img
> file everytime. Because I'm destroying the old instance and deleting
> the old image.

Try creating it in /var/lib/libvirt/images/ which has the correct
selinux context for these images.

--
Jesse Keating
Fedora -- Freedom˛ is a feature!
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-08-2008, 07:11 PM
Suren Karapetyan
 
Default F9 and KVM

Jesse Keating wrote:

On Thu, 2008-05-08 at 14:35 -0400, Gerry Reno wrote:
I think the problem is that virt-manager is creating a new TEST1.img
file everytime. Because I'm destroying the old instance and deleting
the old image.


Try creating it in /var/lib/libvirt/images/ which has the correct
selinux context for these images.




And if this fails too, try to *temporary* switch selinux to permissive
just to be sure if it has anything to do with it


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-08-2008, 07:27 PM
Gerry Reno
 
Default F9 and KVM

Jesse Keating wrote:

On Thu, 2008-05-08 at 14:35 -0400, Gerry Reno wrote:


I think the problem is that virt-manager is creating a new TEST1.img
file everytime. Because I'm destroying the old instance and deleting
the old image.



Try creating it in /var/lib/libvirt/images/ which has the correct
selinux context for these images.



Jesse, that got it.* I just installed F9 in an image there.



Now, how can I set the correct context for where I need to store my
images?* I have several vm image directories on different filesystems
so that the vm's are not competing for the same drive all the time.* Is
just doing a 'chcon -t virt_image_t ./imagedir' enough to set the
context of the images directories?



Also, one last problem is that neither network service nor
NetworkManager seem to be able to get a dhcp connection to the lan in
the guest.* I selected shared network using br0(eth0) during image
creation but all I get in the guest is network unreachable.* Is there
some trick you need to do in the guest?



Regards,

Gerry






--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-08-2008, 09:23 PM
Gerry Reno
 
Default F9 and KVM

Gerry Reno wrote:


Now, how can I set the correct context for where I need to store
my
images?* I have several vm image directories on different filesystems
so that the vm's are not competing for the same drive all the time.* Is
just doing a 'chcon -t virt_image_t ./imagedir' enough to set the
context of the images directories?


Yes, this works.* I just did this to my old vmdk file and directory and
now it runs.





Also, one last problem is that neither network service nor
NetworkManager seem to be able to get a dhcp connection to the lan in
the guest.* I selected shared network using br0(eth0) during image
creation but all I get in the guest is network unreachable.* Is there
some trick you need to do in the guest?


I'm still stuck with this guest networking problem.* I have br0 defined
on the host with a static IP on the lan.* I have eth0 on the host that
points to the bridge br0.* When I created the vm I selected shared
network br0(eth0).* In the guest I have ifcfg-eth0 that has:

BOOTPROTO=dhcp.*

But when you do ifup eth0 it just sits there trying to determine IP and
eventually it pings 192.168.122.1 which to me looks like it thinks its
in a NAT environment rather than bridged networking.



Regards,

Gerry







--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 05-09-2008, 12:03 AM
"Mark Bidewell"
 
Default F9 and KVM

> I'm still stuck with this guest networking problem. I have br0 defined
> on the host with a static IP on the lan. I have eth0 on the host that
> points to the bridge br0. When I created the vm I selected shared
> network br0(eth0). In the guest I have ifcfg-eth0 that has:
> BOOTPROTO=dhcp.
> But when you do ifup eth0 it just sits there trying to determine IP and
> eventually it pings 192.168.122.1 which to me looks like it thinks its
> in a NAT environment rather than bridged networking.
>
> Regards,
> Gerry
>
>
>


have you looked here?

http://kvm.qumranet.com/kvmwiki/Networking

Mark Bidewell

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 12:16 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org