xen 3.4.1 + myoung x86_64 kernel
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
xen 3.4.1 + myoung x86_64 kernel
by Mark Schloesser
::
Rate this Message:
Hi,
I was just trying to get this combination setup up and running. I am on Fedora 11 and mostly followed Boris Derzhavets' blog to get it done. Sadly the box complains that it can not connect to the hypervisor when starting libvirtd and also xend startup fails. libvirtd screen message: ERROR Internal error: Could not obtain handle on privileged command interface (13 = Permission denied) FATAL: Failed to open connection to hypervisor: Permission denied In the kernel log I saw this: ====================================================== [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ] 2.6.31-0.1.2.60.rc7.git4.xendom0.fc12.x86_64 #1 ------------------------------------------------------ See dmesg at http://p.carnivore.it/MrGxdQ for more info. Thanks for any hints or clarification! Cheers, Mark -- Fedora-xen mailing list Fedora-xen@... https://www.redhat.com/mailman/listinfo/fedora-xen |
|
|
|
|
signature.asc (268 bytes) 
| I didn't suggest to install Michael Young's kernel. You may build directly via J.F. Git Repo:- # yum install mercurial gitk # git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen # cd *-xen # git checkout origin/rebase/master -b rebase/master # copy ../config-work .config # make # make modules_install install Pvops kernel 2.6.31-rc6 should be built and installed on system. Working .config is attached (x86_64). No need run "make menuconfig" However, i got it working with both kernel. Stack trace in dmesg output of fedora's kernel seems to be harmless. Clean install with right sequence of steps seems to be important. I was unable reinstall system once been built. Try to follow blog's steps one by one. Point of kernel build doesn't matter. Boris. --- On Wed, 9/2/09, Mark Schloesser <mark.schloesser@...> wrote:
|
--
Fedora-xen mailing list
Fedora-xen@...
https://www.redhat.com/mailman/listinfo/fedora-xen
Re: xen 3.4.1 + myoung x86_64 kernel
by dbaxps
::
Rate this Message:
Re: xen 3.4.1 + myoung x86_64 kernel
by Mark Schloesser
::
Rate this Message:
Thanks Boris, I finally have xen running!
I started over with a fresh F11 install and used JF git kernel with
xen-3.1.4-3.src.rpm. The system starts up just fine with or without xen
enabled on this 2.6.31-rc6 kernel.
The GDM/Xorg does not work though. I have an nvidia NVS290 in this
machine and the nouveau driver complained about not being able to load
the kernel module - directly followed by a backtrace dump in the Xorg
log. I then disabled the nouveau driver trying to get it done with vesa
driver - seemed to give no errors but ended up in the same kind of
backtrace.
on vesa:
Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e89b6]
1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d63f]
2: /lib64/libc.so.6 [0x350fc33370]
3: /usr/lib64/xorg/modules//libint10.so(x_outl+0x25) [0x7f70cf4bde15]
4: /usr/lib64/xorg/modules//libint10.so [0x7f70cf4c43d0]
5: /usr/lib64/xorg/modules//libint10.so(X86EMU_exec+0x81) [0x7f70cf4d0e81]
6: /usr/lib64/xorg/modules//libint10.so(xf86ExecX86int10+0x55)
[0x7f70cf4bf585]
7: /usr/lib64/xorg/modules//libvbe.so(VBEExtendedInit+0x96) [0x7f70cf6dd066]
8: /usr/lib64/xorg/modules/drivers//vesa_drv.so [0x7f70cfcee458]
9: /usr/bin/Xorg(InitOutput+0x507) [0x467377]
10: /usr/bin/Xorg(main+0x1fe) [0x42cf1e]
11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x350fc1ea2d]
12: /usr/bin/Xorg [0x42c559]
any hints on how to get X back up again?
Thanks,
Mark
Boris Derzhavets wrote:
> Did you build and and start services as root ?
> After xen-3.1.4-3.src.rpm "rpmbuild" followed by install of generated packages run:-
>
> # chkconfig xend on
>
> # service xend start
> Same commands for xenstored,xenconsoled,xendomains
>
> Configure Libvirt Preview Repo and run :-
> # yum install libvirt libvirt-python python-virtinst virt-manager virt-viewer
>
> # chkconfig libvirtd on
>
> # service libvirtd start
>
> Next :-
> # rpm -qa|grep xen
> # rpm -qa|grep virt
>
> Make sure right packages installed on F11
>
> Boris.
>
> --- On Wed, 9/2/09, Mark Schloesser <mark.schloesser@...> wrote:
>
> From: Mark Schloesser <mark.schloesser@...>
> Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel
> To: fedora-xen@...
> Date: Wednesday, September 2, 2009, 5:55 PM
>
> Hi,
>
> I was just trying to get this combination setup up and running. I am on
> Fedora 11 and mostly followed Boris Derzhavets' blog to get it done.
>
> Sadly the box complains that it can not connect to the hypervisor when
> starting libvirtd and also xend startup fails.
>
> libvirtd screen message:
> ERROR Internal error: Could not obtain handle on privileged command
> interface (13 = Permission denied)
> FATAL: Failed to open connection to hypervisor: Permission denied
>
> In the kernel log I saw this:
> ======================================================
> [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]
> 2.6.31-0.1.2.60.rc7.git4.xendom0.fc12.x86_64 #1
> ------------------------------------------------------
>
> See dmesg at http://p.carnivore.it/MrGxdQ for more info.
>
> Thanks for any hints or clarification!
>
> Cheers,
> Mark
>
>
>
>
> -----Inline Attachment Follows-----
>
> --
> Fedora-xen mailing list
> Fedora-xen@...
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>
>
--
Fedora-xen mailing list
Fedora-xen@...
https://www.redhat.com/mailman/listinfo/fedora-xen
I started over with a fresh F11 install and used JF git kernel with
xen-3.1.4-3.src.rpm. The system starts up just fine with or without xen
enabled on this 2.6.31-rc6 kernel.
The GDM/Xorg does not work though. I have an nvidia NVS290 in this
machine and the nouveau driver complained about not being able to load
the kernel module - directly followed by a backtrace dump in the Xorg
log. I then disabled the nouveau driver trying to get it done with vesa
driver - seemed to give no errors but ended up in the same kind of
backtrace.
on vesa:
Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e89b6]
1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d63f]
2: /lib64/libc.so.6 [0x350fc33370]
3: /usr/lib64/xorg/modules//libint10.so(x_outl+0x25) [0x7f70cf4bde15]
4: /usr/lib64/xorg/modules//libint10.so [0x7f70cf4c43d0]
5: /usr/lib64/xorg/modules//libint10.so(X86EMU_exec+0x81) [0x7f70cf4d0e81]
6: /usr/lib64/xorg/modules//libint10.so(xf86ExecX86int10+0x55)
[0x7f70cf4bf585]
7: /usr/lib64/xorg/modules//libvbe.so(VBEExtendedInit+0x96) [0x7f70cf6dd066]
8: /usr/lib64/xorg/modules/drivers//vesa_drv.so [0x7f70cfcee458]
9: /usr/bin/Xorg(InitOutput+0x507) [0x467377]
10: /usr/bin/Xorg(main+0x1fe) [0x42cf1e]
11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x350fc1ea2d]
12: /usr/bin/Xorg [0x42c559]
any hints on how to get X back up again?
Thanks,
Mark
Boris Derzhavets wrote:
> Did you build and and start services as root ?
> After xen-3.1.4-3.src.rpm "rpmbuild" followed by install of generated packages run:-
>
> # chkconfig xend on
>
> # service xend start
> Same commands for xenstored,xenconsoled,xendomains
>
> Configure Libvirt Preview Repo and run :-
> # yum install libvirt libvirt-python python-virtinst virt-manager virt-viewer
>
> # chkconfig libvirtd on
>
> # service libvirtd start
>
> Next :-
> # rpm -qa|grep xen
> # rpm -qa|grep virt
>
> Make sure right packages installed on F11
>
> Boris.
>
> --- On Wed, 9/2/09, Mark Schloesser <mark.schloesser@...> wrote:
>
> From: Mark Schloesser <mark.schloesser@...>
> Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel
> To: fedora-xen@...
> Date: Wednesday, September 2, 2009, 5:55 PM
>
> Hi,
>
> I was just trying to get this combination setup up and running. I am on
> Fedora 11 and mostly followed Boris Derzhavets' blog to get it done.
>
> Sadly the box complains that it can not connect to the hypervisor when
> starting libvirtd and also xend startup fails.
>
> libvirtd screen message:
> ERROR Internal error: Could not obtain handle on privileged command
> interface (13 = Permission denied)
> FATAL: Failed to open connection to hypervisor: Permission denied
>
> In the kernel log I saw this:
> ======================================================
> [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]
> 2.6.31-0.1.2.60.rc7.git4.xendom0.fc12.x86_64 #1
> ------------------------------------------------------
>
> See dmesg at http://p.carnivore.it/MrGxdQ for more info.
>
> Thanks for any hints or clarification!
>
> Cheers,
> Mark
>
>
>
>
> -----Inline Attachment Follows-----
>
> --
> Fedora-xen mailing list
> Fedora-xen@...
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>
>
>
--
Fedora-xen mailing list
Fedora-xen@...
https://www.redhat.com/mailman/listinfo/fedora-xen
Re: xen 3.4.1 + myoung x86_64 kernel
by Mark Schloesser
::
Rate this Message:
I somehow did not search deeply enough - there was a related discussion
on xen-devel mailing list. It is a little hidden in the "Vt-d not
working with 3.4.1" thread. There does not seem to be a final "i got it"
post though - I'll try some different solutions proposed there.
Mark
Mark Schloesser wrote:
> Thanks Boris, I finally have xen running!
>
> I started over with a fresh F11 install and used JF git kernel with
> xen-3.1.4-3.src.rpm. The system starts up just fine with or without xen
> enabled on this 2.6.31-rc6 kernel.
>
> The GDM/Xorg does not work though. I have an nvidia NVS290 in this
> machine and the nouveau driver complained about not being able to load
> the kernel module - directly followed by a backtrace dump in the Xorg
> log. I then disabled the nouveau driver trying to get it done with vesa
> driver - seemed to give no errors but ended up in the same kind of
> backtrace.
>
> on vesa:
>
> Backtrace:
> 0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e89b6]
> 1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d63f]
> 2: /lib64/libc.so.6 [0x350fc33370]
> 3: /usr/lib64/xorg/modules//libint10.so(x_outl+0x25) [0x7f70cf4bde15]
> 4: /usr/lib64/xorg/modules//libint10.so [0x7f70cf4c43d0]
> 5: /usr/lib64/xorg/modules//libint10.so(X86EMU_exec+0x81) [0x7f70cf4d0e81]
> 6: /usr/lib64/xorg/modules//libint10.so(xf86ExecX86int10+0x55)
> [0x7f70cf4bf585]
> 7: /usr/lib64/xorg/modules//libvbe.so(VBEExtendedInit+0x96) [0x7f70cf6dd066]
> 8: /usr/lib64/xorg/modules/drivers//vesa_drv.so [0x7f70cfcee458]
> 9: /usr/bin/Xorg(InitOutput+0x507) [0x467377]
> 10: /usr/bin/Xorg(main+0x1fe) [0x42cf1e]
> 11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x350fc1ea2d]
> 12: /usr/bin/Xorg [0x42c559]
>
>
> any hints on how to get X back up again?
>
> Thanks,
> Mark
>
>
> Boris Derzhavets wrote:
>> Did you build and and start services as root ?
>> After xen-3.1.4-3.src.rpm "rpmbuild" followed by install of generated packages run:-
>>
>> # chkconfig xend on
>>
>> # service xend start
>> Same commands for xenstored,xenconsoled,xendomains
>>
>> Configure Libvirt Preview Repo and run :-
>> # yum install libvirt libvirt-python python-virtinst virt-manager virt-viewer
>>
>> # chkconfig libvirtd on
>>
>> # service libvirtd start
>>
>> Next :-
>> # rpm -qa|grep xen
>> # rpm -qa|grep virt
>>
>> Make sure right packages installed on F11
>>
>> Boris.
>>
>> --- On Wed, 9/2/09, Mark Schloesser <mark.schloesser@...> wrote:
>>
>> From: Mark Schloesser <mark.schloesser@...>
>> Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel
>> To: fedora-xen@...
>> Date: Wednesday, September 2, 2009, 5:55 PM
>>
>> Hi,
>>
>> I was just trying to get this combination setup up and running. I am on
>> Fedora 11 and mostly followed Boris Derzhavets' blog to get it done.
>>
>> Sadly the box complains that it can not connect to the hypervisor when
>> starting libvirtd and also xend startup fails.
>>
>> libvirtd screen message:
>> ERROR Internal error: Could not obtain handle on privileged command
>> interface (13 = Permission denied)
>> FATAL: Failed to open connection to hypervisor: Permission denied
>>
>> In the kernel log I saw this:
>> ======================================================
>> [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]
>> 2.6.31-0.1.2.60.rc7.git4.xendom0.fc12.x86_64 #1
>> ------------------------------------------------------
>>
>> See dmesg at http://p.carnivore.it/MrGxdQ for more info.
>>
>> Thanks for any hints or clarification!
>>
>> Cheers,
>> Mark
>>
>>
>>
>>
>> -----Inline Attachment Follows-----
>>
>> --
>> Fedora-xen mailing list
>> Fedora-xen@...
>> https://www.redhat.com/mailman/listinfo/fedora-xen
>>
>>
>>
>>
>
>
> ------------------------------------------------------------------------
>
> --
> Fedora-xen mailing list
> Fedora-xen@...
> https://www.redhat.com/mailman/listinfo/fedora-xen
--
Fedora-xen mailing list
Fedora-xen@...
https://www.redhat.com/mailman/listinfo/fedora-xen
on xen-devel mailing list. It is a little hidden in the "Vt-d not
working with 3.4.1" thread. There does not seem to be a final "i got it"
post though - I'll try some different solutions proposed there.
Mark
Mark Schloesser wrote:
> Thanks Boris, I finally have xen running!
>
> I started over with a fresh F11 install and used JF git kernel with
> xen-3.1.4-3.src.rpm. The system starts up just fine with or without xen
> enabled on this 2.6.31-rc6 kernel.
>
> The GDM/Xorg does not work though. I have an nvidia NVS290 in this
> machine and the nouveau driver complained about not being able to load
> the kernel module - directly followed by a backtrace dump in the Xorg
> log. I then disabled the nouveau driver trying to get it done with vesa
> driver - seemed to give no errors but ended up in the same kind of
> backtrace.
>
> on vesa:
>
> Backtrace:
> 0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e89b6]
> 1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d63f]
> 2: /lib64/libc.so.6 [0x350fc33370]
> 3: /usr/lib64/xorg/modules//libint10.so(x_outl+0x25) [0x7f70cf4bde15]
> 4: /usr/lib64/xorg/modules//libint10.so [0x7f70cf4c43d0]
> 5: /usr/lib64/xorg/modules//libint10.so(X86EMU_exec+0x81) [0x7f70cf4d0e81]
> 6: /usr/lib64/xorg/modules//libint10.so(xf86ExecX86int10+0x55)
> [0x7f70cf4bf585]
> 7: /usr/lib64/xorg/modules//libvbe.so(VBEExtendedInit+0x96) [0x7f70cf6dd066]
> 8: /usr/lib64/xorg/modules/drivers//vesa_drv.so [0x7f70cfcee458]
> 9: /usr/bin/Xorg(InitOutput+0x507) [0x467377]
> 10: /usr/bin/Xorg(main+0x1fe) [0x42cf1e]
> 11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x350fc1ea2d]
> 12: /usr/bin/Xorg [0x42c559]
>
>
> any hints on how to get X back up again?
>
> Thanks,
> Mark
>
>
> Boris Derzhavets wrote:
>> Did you build and and start services as root ?
>> After xen-3.1.4-3.src.rpm "rpmbuild" followed by install of generated packages run:-
>>
>> # chkconfig xend on
>>
>> # service xend start
>> Same commands for xenstored,xenconsoled,xendomains
>>
>> Configure Libvirt Preview Repo and run :-
>> # yum install libvirt libvirt-python python-virtinst virt-manager virt-viewer
>>
>> # chkconfig libvirtd on
>>
>> # service libvirtd start
>>
>> Next :-
>> # rpm -qa|grep xen
>> # rpm -qa|grep virt
>>
>> Make sure right packages installed on F11
>>
>> Boris.
>>
>> --- On Wed, 9/2/09, Mark Schloesser <mark.schloesser@...> wrote:
>>
>> From: Mark Schloesser <mark.schloesser@...>
>> Subject: [Fedora-xen] xen 3.4.1 + myoung x86_64 kernel
>> To: fedora-xen@...
>> Date: Wednesday, September 2, 2009, 5:55 PM
>>
>> Hi,
>>
>> I was just trying to get this combination setup up and running. I am on
>> Fedora 11 and mostly followed Boris Derzhavets' blog to get it done.
>>
>> Sadly the box complains that it can not connect to the hypervisor when
>> starting libvirtd and also xend startup fails.
>>
>> libvirtd screen message:
>> ERROR Internal error: Could not obtain handle on privileged command
>> interface (13 = Permission denied)
>> FATAL: Failed to open connection to hypervisor: Permission denied
>>
>> In the kernel log I saw this:
>> ======================================================
>> [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]
>> 2.6.31-0.1.2.60.rc7.git4.xendom0.fc12.x86_64 #1
>> ------------------------------------------------------
>>
>> See dmesg at http://p.carnivore.it/MrGxdQ for more info.
>>
>> Thanks for any hints or clarification!
>>
>> Cheers,
>> Mark
>>
>>
>>
>>
>> -----Inline Attachment Follows-----
>>
>> --
>> Fedora-xen mailing list
>> Fedora-xen@...
>> https://www.redhat.com/mailman/listinfo/fedora-xen
>>
>>
>>
>>
>
>
> ------------------------------------------------------------------------
>
> --
> Fedora-xen mailing list
> Fedora-xen@...
> https://www.redhat.com/mailman/listinfo/fedora-xen
--
Fedora-xen mailing list
Fedora-xen@...
https://www.redhat.com/mailman/listinfo/fedora-xen
Re: xen 3.4.1 + myoung x86_64 kernel
by dbaxps
::
Rate this Message:
Re: xen 3.4.1 + myoung x86_64 kernel
by dbaxps
::
Rate this Message:
| Free embeddable forum powered by Nabble | Forum Help |
