On Wed, Mar 25, 2009 at 10:38:33PM +0100, Samuel Thibault wrote:> Jody Belka, le Wed 25 Mar 2009 19:17:30 +0000, a écrit : > > Apologies; it seems that there''s some bug somewhere that means fs-backend > > doesn''t work with a pvops-dom0. > > It''d be good to report that on xen-unstable.So, as mentioned above, fs-backend isn''t working on a pvops-dom0. With non-pvops, running fs-backend looks like this: Connection to the xenbus deamon opened successfully. XS transaction is 3 xenbus_printf (backend/vfs/exports/0/name) <= default. Path changed backend/vfs/exports/requests Awaiting next connection. However, under pvops, this is all I get: Connection to the xenbus deamon opened successfully. XS transaction is 3 xenbus_printf (backend/vfs/exports/0/name) <= default. And stubdom''s can''t make a connection to it. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jody Belka wrote:> On Wed, Mar 25, 2009 at 10:38:33PM +0100, Samuel Thibault wrote: > >> Jody Belka, le Wed 25 Mar 2009 19:17:30 +0000, a écrit : >> >>> Apologies; it seems that there''s some bug somewhere that means fs-backend >>> doesn''t work with a pvops-dom0. >>> >> It''d be good to report that on xen-unstable. >> > > So, as mentioned above, fs-backend isn''t working on a pvops-dom0. With > non-pvops, running fs-backend looks like this: > > Connection to the xenbus deamon opened successfully. > XS transaction is 3 > xenbus_printf (backend/vfs/exports/0/name) <= default. > Path changed backend/vfs/exports/requests > Awaiting next connection. > > > However, under pvops, this is all I get: > > Connection to the xenbus deamon opened successfully. > XS transaction is 3 > xenbus_printf (backend/vfs/exports/0/name) <= default. > > > And stubdom''s can''t make a connection to it.Hm, I had it working not too long ago. But there are still some issues starting hvm domains, and maybe stubdoms are also affected. Does pv-grub work? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, Mar 25, 2009 at 03:49:46PM -0700, Jeremy Fitzhardinge wrote:> Jody Belka wrote: > >On Wed, Mar 25, 2009 at 10:38:33PM +0100, Samuel Thibault wrote: > > > >>Jody Belka, le Wed 25 Mar 2009 19:17:30 +0000, a écrit : > >> > >>>Apologies; it seems that there''s some bug somewhere that means fs-backend > >>>doesn''t work with a pvops-dom0. > >>> > >>It''d be good to report that on xen-unstable. > >> > > > >So, as mentioned above, fs-backend isn''t working on a pvops-dom0. With > >non-pvops, running fs-backend looks like this: > > > >Connection to the xenbus deamon opened successfully. > >XS transaction is 3 > >xenbus_printf (backend/vfs/exports/0/name) <= default. > >Path changed backend/vfs/exports/requests > >Awaiting next connection. > > > > > >However, under pvops, this is all I get: > > > >Connection to the xenbus deamon opened successfully. > >XS transaction is 3 > >xenbus_printf (backend/vfs/exports/0/name) <= default. > > > > > >And stubdom''s can''t make a connection to it. > > Hm, I had it working not too long ago. But there are still some issues > starting hvm domains, and maybe stubdoms are also affected. > > Does pv-grub work?Ok, had to sort out creating a linux domain, as had nothing I could actually try pv-grub with on the test-box in question :) Anyway, having done so, pv-grub is working fine under pvops0 J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jody Belka wrote:> Ok, had to sort out creating a linux domain, as had nothing I could actually > try pv-grub with on the test-box in question :) > > Anyway, having done so, pv-grub is working fine under pvops0Hm. If pv-grub starts then that''s most of the way to stubdom. Are there any other log messages? Are you trying to start an hvm domain? That''s known-problematic. Are you having any success at all? Does it work without a stub domain? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, Mar 25, 2009 at 05:05:13PM -0700, Jeremy Fitzhardinge wrote:> Jody Belka wrote: > >Ok, had to sort out creating a linux domain, as had nothing I could > >actually > >try pv-grub with on the test-box in question :) > > > >Anyway, having done so, pv-grub is working fine under pvops0 > > Hm. If pv-grub starts then that''s most of the way to stubdom. Are > there any other log messages? > > Are you trying to start an hvm domain? That''s known-problematic. Are > you having any success at all? Does it work without a stub domain?Not hvm, no. I try it every so often to see if it''s been sorted out, but here I''m just trying a stub domain. Now, the stub domain isn''t actually working for me anyway, even on non-pvops0, but it is able to talk to the fs-backend at least. To show what that looks like, I''ve attached a couple of emails I sent off-list. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>Hm. If pv-grub starts then that''s most of the way to stubdom. Are there any other log messages?PV-grub works fine with the most recent 2.6.29-rc8 and the most recent stubdom build. But, fs-backend is irresponsive. Stubdoms fail to start. Boris --- On Wed, 3/25/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: [Xen-devel] Re: fs-backend on -unstable To: "Jody Belka" <lists-xen@pimb.org> Cc: "Samuel Thibault" <samuel.thibault@ens-lyon.org>, "Xen-devel" <xen-devel@lists.xensource.com>, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com> Date: Wednesday, March 25, 2009, 8:05 PM Jody Belka wrote:> Ok, had to sort out creating a linux domain, as had nothing I couldactually> try pv-grub with on the test-box in question :) > > Anyway, having done so, pv-grub is working fine under pvops0Hm. If pv-grub starts then that''s most of the way to stubdom. Are there any other log messages? Are you trying to start an hvm domain? That''s known-problematic. Are you having any success at all? Does it work without a stub domain? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jody Belka wrote:> Now, the stub domain isn''t actually working for me anyway, even on > non-pvops0, but it is able to talk to the fs-backend at least. To show > what that looks like, I''ve attached a couple of emails I sent off-list.There are some known issues that affect stubdoms at the moment, since they involve some changes made on qemu upstream I am trying to find a solution there. However if you want to test the latest stubdoms you can try this patch, it works for me. --- diff --git a/hw/ide.c b/hw/ide.c index 7031ba1..a97c78b 100644 --- a/hw/ide.c +++ b/hw/ide.c @@ -1056,10 +1056,11 @@ static int dma_buf_prepare(BMDMAState *bm, int is_write) uint32_t addr; uint32_t size; } prd; - int l, len; + int l, len, n; void *mem; target_phys_addr_t l1; + n = s->nsector <= IDE_DMA_BUF_SECTORS ? s->nsector : IDE_DMA_BUF_SECTORS; qemu_iovec_init(&s->iovec, s->nsector / (TARGET_PAGE_SIZE/512) + 1); s->io_buffer_size = 0; for(;;) { @@ -1082,6 +1083,13 @@ static int dma_buf_prepare(BMDMAState *bm, int is_write) l = bm->cur_prd_len; if (l > 0) { l1 = l; + if (l1 > IDE_DMA_BUF_SECTORS * 512) + l1 = IDE_DMA_BUF_SECTORS * 512; + if (s->io_buffer_size + l1 > IDE_DMA_BUF_SECTORS * 512) { + l1 = IDE_DMA_BUF_SECTORS * 512 - s->io_buffer_size; + if (!l1) + return s->io_buffer_size != 0; + } mem = cpu_physical_memory_map(bm->cur_prd_addr, &l1, is_write); if (!mem) { break; @@ -1263,6 +1271,8 @@ static void ide_read_dma_cb(void *opaque, int ret) /* launch next transfer */ n = s->nsector; + if (n > IDE_DMA_BUF_SECTORS) + n = IDE_DMA_BUF_SECTORS; s->io_buffer_index = 0; s->io_buffer_size = n * 512; if (dma_buf_prepare(bm, 1) == 0) @@ -1412,6 +1422,8 @@ static void ide_write_dma_cb(void *opaque, int ret) } n = s->nsector; + if (n > IDE_DMA_BUF_SECTORS) + n = IDE_DMA_BUF_SECTORS; s->io_buffer_size = n * 512; /* launch next transfer */ if (dma_buf_prepare(bm, 0) == 0) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Patch applied to /usr/src/xen-unstable.hg/tools/ioemu-dir/hw/ide.c. # cd /usr/src/xen-unstable.hg # find . -name ide.c -print ./stubdom/ioemu/hw/ide.c ./tools/ioemu-remote/hw/ide.c # ls -l ./stubdom/ioemu/hw/ide.c lrwxrwxrwx 1 root src 50 2009-03-26 07:45 ./stubdom/ioemu/hw/ide.c -> /usr/src/xen-unstable.hg//tools/ioemu-dir/hw/ide.c # make tools # make install-tools # cd stubdom # there is symlink to ./tools/ioemu-remote/ide.c # make # make install System restarted (just in case). No luck (just same picture as before) under Xen Unstable & Suse''s 2.6.27-5 Boris. --- On Thu, 3/26/09, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote: From: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Subject: [Xen-devel] Re: fs-backend on -unstable To: "Jody Belka" <lists-xen@pimb.org> Cc: "Samuel Thibault" <samuel.thibault@ens-lyon.org>, "Jeremy Fitzhardinge" <jeremy@goop.org>, "Xen-devel" <xen-devel@lists.xensource.com> Date: Thursday, March 26, 2009, 6:21 AM Jody Belka wrote:> Now, the stub domain isn''t actually working for me anyway, even on > non-pvops0, but it is able to talk to the fs-backend at least. To show > what that looks like, I''ve attached a couple of emails I sentoff-list. There are some known issues that affect stubdoms at the moment, since they involve some changes made on qemu upstream I am trying to find a solution there. However if you want to test the latest stubdoms you can try this patch, it works for me. --- diff --git a/hw/ide.c b/hw/ide.c index 7031ba1..a97c78b 100644 --- a/hw/ide.c +++ b/hw/ide.c @@ -1056,10 +1056,11 @@ static int dma_buf_prepare(BMDMAState *bm, int is_write) uint32_t addr; uint32_t size; } prd; - int l, len; + int l, len, n; void *mem; target_phys_addr_t l1; + n = s->nsector <= IDE_DMA_BUF_SECTORS ? s->nsector : IDE_DMA_BUF_SECTORS; qemu_iovec_init(&s->iovec, s->nsector / (TARGET_PAGE_SIZE/512) + 1); s->io_buffer_size = 0; for(;;) { @@ -1082,6 +1083,13 @@ static int dma_buf_prepare(BMDMAState *bm, int is_write) l = bm->cur_prd_len; if (l > 0) { l1 = l; + if (l1 > IDE_DMA_BUF_SECTORS * 512) + l1 = IDE_DMA_BUF_SECTORS * 512; + if (s->io_buffer_size + l1 > IDE_DMA_BUF_SECTORS * 512) { + l1 = IDE_DMA_BUF_SECTORS * 512 - s->io_buffer_size; + if (!l1) + return s->io_buffer_size != 0; + } mem = cpu_physical_memory_map(bm->cur_prd_addr, &l1, is_write); if (!mem) { break; @@ -1263,6 +1271,8 @@ static void ide_read_dma_cb(void *opaque, int ret) /* launch next transfer */ n = s->nsector; + if (n > IDE_DMA_BUF_SECTORS) + n = IDE_DMA_BUF_SECTORS; s->io_buffer_index = 0; s->io_buffer_size = n * 512; if (dma_buf_prepare(bm, 1) == 0) @@ -1412,6 +1422,8 @@ static void ide_write_dma_cb(void *opaque, int ret) } n = s->nsector; + if (n > IDE_DMA_BUF_SECTORS) + n = IDE_DMA_BUF_SECTORS; s->io_buffer_size = n * 512; /* launch next transfer */ if (dma_buf_prepare(bm, 0) == 0) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Mar 26, 2009 at 10:21:01AM +0000, Stefano Stabellini wrote:> Jody Belka wrote: > > > Now, the stub domain isn''t actually working for me anyway, even on > > non-pvops0, but it is able to talk to the fs-backend at least. To show > > what that looks like, I''ve attached a couple of emails I sent off-list. > > > > There are some known issues that affect stubdoms at the moment, since > they involve some changes made on qemu upstream I am trying to find a > solution there.Ok, by changing from a pvfb vnc inside the stubdom config, to vnc in the master config, I now get output into my qemu-dm log file, and so can see the debug printf''s I added in. It also means a msg from qemu is appearing: Could not initialize device ''tap'' Which is coming from within vl.c: for(i = 0;i < nb_net_clients; i++) { if (net_client_parse(net_clients[i]) < 0) exit(1); } The qemu cmdline parameters are being reported as follows: "main" "-d" "23" "-domain-name" "wintest-sd" "-videoram" "4" "-vnc" "192.168.254.135:0" "-vncunused" "-vcpus" "1" "-boot" "c" "-acpi" "-net" "nic,vlan=1,macaddr=aa:00:00:12:23:34,model=e1000" "-net" "tap,vlan=1,ifname=tap23.0,bridge=eth0" Any debugging I could add that could track down the cause of the above error, or is this something you recognize? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-26 14:54 UTC
[Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
Occasionally during VNC session CentOS 5.2 PV DomU crashes
Attempt to restart it remind hotplug scripts issue . Stack trace upon the crash
during VNC session :-
Unable to handle kernel NULL pointer dereference at 000000000000013f RIP:
[<ffffffff88110a37>] :xennet:network_tx_buf_gc+0xea/0x1cf
PGD 742b8067 PUD 7429c067 PMD 0
Oops: 0002 [1] SMP
last sysfs file: /block/dm-1/range
CPU 0
Modules linked in: ipv6 xfrm_nalgo crypto_api autofs4 hidp rfcomm l2cap
bluetooth sunrpc xennet
dm_multipath parport_pc lp parport pcspkr dm_snapshot dm_zero dm_mirror dm_mod
xenblk ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Pid: 0, comm: swapper Not tainted 2.6.18-92.1.22.el5xen #1
RIP: e030:[<ffffffff88110a37>] [<ffffffff88110a37>]
:xennet:network_tx_buf_gc+0xea/0x1cf
RSP: e02b:ffffffff8062fe78 EFLAGS: 00010046
RAX: 0000000000000078 RBX: ffff88007d438500 RCX: 0000000000000000
RDX: 000000000000006f RSI: 0000000000000000 RDI: ffff88007d439670
RBP: 0000000000000073 R08: ffffc20000000000 R09: 00000000ffff61ae
R10: ffff880075e4fac0 R11: 0000000000000246 R12: 000000000000006f
R13: ffff88007d438000 R14: 0000000000000fd0 R15: 0000000000000fcf
FS: 00002b8fc16d62d0(0000) GS:ffffffff805b0000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff805f0000, task ffffffff804d8b00)
Stack: 0000006f00000001 ffff88007d438000 ffff88007d438500 0000000000000000
0000000000000109 ffffffff805f1ea8 ffffffff805f1ea8 ffffffff88111d46
ffff88007f1cfac0 0000000000000000
Call Trace:
<IRQ> [<ffffffff88111d46>] :xennet:netif_int+0x2c/0x72
[<ffffffff802112c1>] handle_IRQ_event+0x2d/0x60
[<ffffffff802b1af5>] __do_IRQ+0xa4/0x103
[<ffffffff8028fd9d>] _local_bh_enable+0x61/0xc5
[<ffffffff8026db48>] do_IRQ+0xe7/0xf5
[<ffffffff803a0c69>] evtchn_do_upcall+0x86/0xe0
[<ffffffff802608d6>] do_hypervisor_callback+0x1e/0x2c
<EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
[<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
[<ffffffff8026f139>] raw_safe_halt+0x84/0xa8
[<ffffffff8026c683>] xen_idle+0x38/0x4a
[<ffffffff8024aa8e>] cpu_idle+0x97/0xba
[<ffffffff805fab09>] start_kernel+0x21f/0x224
Attempt to restart CentOS 5.2 PV DomU
Scanning and configuring dmraid supported devices
Scanning logical volumes
Reading all physical volumes. This may take a while...
No volume groups found
Activating logical volumes
Volume group "VolGroup00" not found
Creating root device.
Mounting root filesystem.
mount: could not find filesystem ''/dev/root''
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
root@ServerIntrepid:/home/boris/vm# Error: Device 0 (vif) could not be
connected. Hotplug scripts not working.
F10 PV DomU also cannot be started after the accident due to Hotplug scripts not
working.
VNC at Linux DomUs worked fine with rc5 as far as i remember.
Boris.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-26 16:14 UTC
Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
I believe i have to describe the issue in more details:-
1. Xen Unstable Dom0 with 2.6.29-rc8 pvops kernel is installed on top
of Ubuntu 8.10 Server with ubuntu desktop up and running. GDM service is
running,
with gdm.conf configured to allow remote connections, xinetd is running Xvnc
configured for remote connection as well.
2. This configuration provides remote connection to Dom0 with pvops kernel via
Gnome Desktop. Crash happens when i run VNC session opened via gnome terminal at
remote Dom0''s desktop ( it worked fine with rc5 or rc6 for sure).
If i ussue :-
# vncviewer IP_DomU:1
from gnome terminal running on remote host (i.e. without any interaction with
Ubuntu
specific X-Server clients services) VNC session seems to be running stable.
Boris
--- On Thu, 3/26/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable
( 2.6.29-rc8 kernel)
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Thursday, March 26, 2009, 10:54 AM
Occasionally during VNC session CentOS 5.2 PV DomU crashes
Attempt to restart it remind hotplug scripts issue . Stack trace upon the crash
during VNC session :-
Unable to handle kernel NULL pointer dereference at 000000000000013f RIP:
[<ffffffff88110a37>] :xennet:network_tx_buf_gc+0xea/0x1cf
PGD 742b8067 PUD 7429c067 PMD 0
Oops: 0002 [1] SMP
last sysfs file: /block/dm-1/range
CPU 0
Modules linked in: ipv6 xfrm_nalgo crypto_api autofs4 hidp rfcomm l2cap
bluetooth sunrpc xennet
dm_multipath parport_pc lp parport pcspkr dm_snapshot dm_zero dm_mirror dm_mod
xenblk ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Pid: 0, comm: swapper Not tainted 2.6.18-92.1.22.el5xen #1
RIP: e030:[<ffffffff88110a37>] [<ffffffff88110a37>]
:xennet:network_tx_buf_gc+0xea/0x1cf
RSP: e02b:ffffffff8062fe78 EFLAGS:
00010046
RAX: 0000000000000078 RBX: ffff88007d438500 RCX: 0000000000000000
RDX: 000000000000006f RSI: 0000000000000000 RDI: ffff88007d439670
RBP: 0000000000000073 R08: ffffc20000000000 R09: 00000000ffff61ae
R10: ffff880075e4fac0 R11: 0000000000000246 R12: 000000000000006f
R13: ffff88007d438000 R14: 0000000000000fd0 R15: 0000000000000fcf
FS: 00002b8fc16d62d0(0000) GS:ffffffff805b0000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff805f0000, task ffffffff804d8b00)
Stack: 0000006f00000001 ffff88007d438000 ffff88007d438500 0000000000000000
0000000000000109 ffffffff805f1ea8 ffffffff805f1ea8 ffffffff88111d46
ffff88007f1cfac0 0000000000000000
Call Trace:
<IRQ> [<ffffffff88111d46>] :xennet:netif_int+0x2c/0x72
[<ffffffff802112c1>]
handle_IRQ_event+0x2d/0x60
[<ffffffff802b1af5>] __do_IRQ+0xa4/0x103
[<ffffffff8028fd9d>] _local_bh_enable+0x61/0xc5
[<ffffffff8026db48>] do_IRQ+0xe7/0xf5
[<ffffffff803a0c69>] evtchn_do_upcall+0x86/0xe0
[<ffffffff802608d6>] do_hypervisor_callback+0x1e/0x2c
<EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
[<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
[<ffffffff8026f139>] raw_safe_halt+0x84/0xa8
[<ffffffff8026c683>] xen_idle+0x38/0x4a
[<ffffffff8024aa8e>] cpu_idle+0x97/0xba
[<ffffffff805fab09>] start_kernel+0x21f/0x224
Attempt to restart CentOS 5.2 PV DomU
Scanning and configuring dmraid supported devices
Scanning logical volumes
Reading all physical volumes. This may take a while...
No volume groups found
Activating logical
volumes
Volume group "VolGroup00" not found
Creating root device.
Mounting root filesystem.
mount: could not find filesystem ''/dev/root''
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
root@ServerIntrepid:/home/boris/vm# Error: Device 0 (vif) could not be
connected. Hotplug scripts not working.
F10 PV DomU also cannot be started after the accident due to Hotplug scripts not
working.
VNC at Linux DomUs worked fine with rc5 as far as i
remember.
Boris.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Boris Derzhavets wrote:> >Hm. If pv-grub starts then that''s most of the way to stubdom. Are > there any other log messages? > > PV-grub works fine with the most recent 2.6.29-rc8 and the most recent > stubdom build. But, fs-backend is irresponsive. Stubdoms fail to start. >Make sure the backend modules are loaded, if you''ve made them modular. They don''t load automatically (not for me, at least). J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jody Belka wrote:> Ok, by changing from a pvfb vnc inside the stubdom config, to vnc in the > master config, I now get output into my qemu-dm log file, and so can see > the debug printf''s I added in. It also means a msg from qemu is appearing: > > Could not initialize device ''tap'' >pvops dom0 doesn''t support blktap yet, so you need to use normal blkback for disks for now. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Mar 26, 2009 at 11:57:05AM -0700, Jeremy Fitzhardinge wrote:> Jody Belka wrote: > >Ok, by changing from a pvfb vnc inside the stubdom config, to vnc in the > >master config, I now get output into my qemu-dm log file, and so can see > >the debug printf''s I added in. It also means a msg from qemu is appearing: > > > >Could not initialize device ''tap'' > > > > pvops dom0 doesn''t support blktap yet, so you need to use normal blkback > for disks for now.That line''s not referring to a block device, it''s referring to a qemu -net parameter. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jody Belka wrote:> On Thu, Mar 26, 2009 at 11:57:05AM -0700, Jeremy Fitzhardinge wrote: > >> Jody Belka wrote: >> >>> Ok, by changing from a pvfb vnc inside the stubdom config, to vnc in the >>> master config, I now get output into my qemu-dm log file, and so can see >>> the debug printf''s I added in. It also means a msg from qemu is appearing: >>> >>> Could not initialize device ''tap'' >>> >>> >> pvops dom0 doesn''t support blktap yet, so you need to use normal blkback >> for disks for now. >> > > That line''s not referring to a block device, it''s referring to a qemu -net > parameter.Oops, sorry. Too much pattern matching. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Mar 26, 2009 at 01:27:06PM +0000, Jody Belka wrote:> On Thu, Mar 26, 2009 at 10:21:01AM +0000, Stefano Stabellini wrote: > > Jody Belka wrote: > > > > > Now, the stub domain isn''t actually working for me anyway, even on > > > non-pvops0, but it is able to talk to the fs-backend at least. To show > > > what that looks like, I''ve attached a couple of emails I sent off-list. > > > > > > > > There are some known issues that affect stubdoms at the moment, since > > they involve some changes made on qemu upstream I am trying to find a > > solution there. > > Ok, by changing from a pvfb vnc inside the stubdom config, to vnc in the > master config, I now get output into my qemu-dm log file, and so can see > the debug printf''s I added in. It also means a msg from qemu is appearing: > > Could not initialize device ''tap'' > > Which is coming from within vl.c: > > for(i = 0;i < nb_net_clients; i++) { > if (net_client_parse(net_clients[i]) < 0) > exit(1); > } > > > The qemu cmdline parameters are being reported as follows: > > "main" "-d" "23" "-domain-name" "wintest-sd" "-videoram" "4" "-vnc" > "192.168.254.135:0" "-vncunused" "-vcpus" "1" "-boot" "c" "-acpi" "-net" > "nic,vlan=1,macaddr=aa:00:00:12:23:34,model=e1000" > "-net" "tap,vlan=1,ifname=tap23.0,bridge=eth0" > > > Any debugging I could add that could track down the cause of the above > error, or is this something you recognize?Ok, turns out that there''s a bit of code in there that deliberately causes -net tap to error out for a stubdom, which then causes the entire stubdom to die. Changing that to just ignore the tap lets the domain come up. Lots of error messages end up appearing in the log, and windows is currently crashing during boot, but it''s a long long long way along to really working :) J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>if you''ve made them modular. >They don''t load automatically (not for me, at least).I gues, i haven''t made them modular.CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XEN_BLKDEV_BACKEND=y CONFIG_XEN_NETDEV_BACKEND=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_XENBUS_FRONTEND=y CONFIG_XEN_S3=y CONFIG_XEN_GNTDEV=y CONFIG_XEN_SYS_HYPERVISOR=y Boris. --- On Thu, 3/26/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: [Xen-devel] Re: fs-backend on -unstable To: bderzhavets@yahoo.com Cc: "Samuel Thibault" <samuel.thibault@ens-lyon.org>, "Xen-devel" <xen-devel@lists.xensource.com>, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com> Date: Thursday, March 26, 2009, 2:39 PM Boris Derzhavets wrote:> >Hm. If pv-grub starts then that''s most of the way to stubdom. Arethere any other log messages?> > PV-grub works fine with the most recent 2.6.29-rc8 and the most recent > stubdom build. But, fs-backend is irresponsive. Stubdoms fail to start. >Make sure the backend modules are loaded, if you''ve made them modular. They don''t load automatically (not for me, at least). J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2009-Mar-27 23:21 UTC
Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
Boris Derzhavets wrote:> I believe i have to describe the issue in more details:- > 1. Xen Unstable Dom0 with 2.6.29-rc8 pvops kernel is installed on top > of Ubuntu 8.10 Server with ubuntu desktop up and running. GDM service > is running, > with gdm.conf configured to allow remote connections, xinetd is > running Xvnc configured for remote connection as well. > 2. This configuration provides remote connection to Dom0 with pvops > kernel via Gnome Desktop. Crash happens when i run VNC session opened > via gnome terminal at remote Dom0''s desktop ( it worked fine with rc5 > or rc6 for sure). > If i ussue :- > # vncviewer IP_DomU:1 > from gnome terminal running on remote host (i.e. without any > interaction with Ubuntu > specific X-Server clients services) VNC session seems to be running > stable. >That''s a bit worrying, because it would suggest that networking in general is broken. If you don''t start Xvnc (or whatever), but run some other network-intensive test, does that crash? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-28 08:41 UTC
Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
OpenSolaris 2008.11 PV DomU may run VNC session started via gnome terminal invoked on remote pvops Dom0 desktop pretty stable. So , OpenSolaris PV DomU is not affected. Actually , any remote VNC session with CentOS 5.2 PV DomU doing "yum upgrade" may be considered as network-intensive test and it works. I don''t think that network at DomU is broken in general. But , path for vncviewer to CentOS 5.2 DomU via vncserver at Dom0 and vncserver at DomU seems to be broken in meantime. This doesn''t work for CentOS 5.2 DomU:- WS - Work Station (Linux , Ubuntu Desktop) WS --------------------->Vncserver Dom0 ------- xm create -c DomU.pyrun---- | | | Vncviewer 1 Vncviewer 2 | | | |----------------------------> Gnome Desktop Dom0 ----------->Vncserver DomU This works:- WS -------------------->SSH conn to Dom0 ---- xm create -c DomU.pyrun----- | | | Vncviewer | | | |----------------------------> Gnome Desktop WS --------------->Vncserver DomU Boris --- On Fri, 3/27/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Friday, March 27, 2009, 7:21 PM Boris Derzhavets wrote:> I believe i have to describe the issue in more details:- > 1. Xen Unstable Dom0 with 2.6.29-rc8 pvops kernel is installed on top > of Ubuntu 8.10 Server with ubuntu desktop up and running. GDM service isrunning,> with gdm.conf configured to allow remote connections, xinetd is runningXvnc configured for remote connection as well.> 2. This configuration provides remote connection to Dom0 with pvopskernel via Gnome Desktop. Crash happens when i run VNC session opened via gnome terminal at remote Dom0''s desktop ( it worked fine with rc5 or rc6 for sure).> If i ussue :- > # vncviewer IP_DomU:1 > from gnome terminal running on remote host (i.e. without any interactionwith Ubuntu> specific X-Server clients services) VNC session seems to be runningstable.>That''s a bit worrying, because it would suggest that networking in general is broken. If you don''t start Xvnc (or whatever), but run some other network-intensive test, does that crash? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-28 10:18 UTC
Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
Solaris Nevada b106 is also affected in schema bellow. Looks like hotplug scripts gets locked after VNC Session failure WS -------------->Vncserver Dom0 ------ xm create -c SNV_DomU.pyrun------- | | | Vncviewer 1 Vncviewer 2 | | | |---------------------> Gnome Desktop Dom0 ----------->Vncserver SNV_DomU --- On Sat, 3/28/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Saturday, March 28, 2009, 4:41 AM OpenSolaris 2008.11 PV DomU may run VNC session started via gnome terminal invoked on remote pvops Dom0 desktop pretty stable. So , OpenSolaris PV DomU is not affected. Actually , any remote VNC session with CentOS 5.2 PV DomU doing "yum upgrade" may be considered as network-intensive test and it works. I don''t think that network at DomU is broken in general. But , path for vncviewer to CentOS 5.2 DomU via vncserver at Dom0 and vncserver at DomU seems to be broken in meantime. This doesn''t work for CentOS 5.2 DomU:- WS - Work Station (Linux , Ubuntu Desktop) WS --------------------->Vncserver Dom0 ------- xm create -c DomU.pyrun---- | | | Vncviewer 1 Vncviewer 2 | | | |----------------------------> Gnome Desktop Dom0 ----------->Vncserver DomU This works:- WS -------------------->SSH conn to Dom0 ---- xm create -c DomU.pyrun----- | | | Vncviewer | | | |----------------------------> Gnome Desktop WS --------------->Vncserver DomU Boris --- On Fri, 3/27/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Friday, March 27, 2009, 7:21 PM Boris Derzhavets wrote:> I believe i have to describe the issue in more details:- > 1. Xen Unstable Dom0 with 2.6.29-rc8 pvops kernel is installed on top > of Ubuntu 8.10 Server with ubuntu desktop up and running. GDM service isrunning,> with gdm.conf configured to allow remote connections, xinetd is runningXvnc configured for remote connection as well.> 2.This configuration provides remote connection to Dom0 with pvops kernel via Gnome Desktop. Crash happens when i run VNC session opened via gnome terminal at remote Dom0''s desktop ( it worked fine with rc5 or rc6 for sure).> If i ussue :- > # vncviewer IP_DomU:1 > from gnome terminal running on remote host (i.e. without any interactionwith Ubuntu> specific X-Server clients services) VNC session seems to be runningstable.>That''s a bit worrying, because it would suggest that networking in general is broken. If you don''t start Xvnc (or whatever), but run some other network-intensive test, does that crash? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-28 11:45 UTC
Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
OK. After 20-25 min of extensive testing OS 2008.11 DomU crashed and dropped into stack trace, running VNC session, started via gnome terminal at remote Dom0 desktop same way as Nevada 106 did. For now there is no any exception for this issue. But, VNC session crash should not in general crash DomU. Would be glad to troubleshoot, been instructed. Boris. --- On Sat, 3/28/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Saturday, March 28, 2009, 6:18 AM Solaris Nevada b106 is also affected in schema bellow. Looks like hotplug scripts gets locked after VNC Session failure WS -------------->Vncserver Dom0 ------ xm create -c SNV_DomU.pyrun------- | | | Vncviewer 1 Vncviewer 2 | | | |---------------------> Gnome Desktop Dom0 ----------->Vncserver SNV_DomU --- On Sat, 3/28/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Saturday, March 28, 2009, 4:41 AM OpenSolaris 2008.11 PV DomU may run VNC session started via gnome terminal invoked on remote pvops Dom0 desktop pretty stable. So , OpenSolaris PV DomU is not affected. Actually , any remote VNC session with CentOS 5.2 PV DomU doing "yum upgrade" may be considered as network-intensive test and it works. I don''t think that network at DomU is broken in general. But , path for vncviewer to CentOS 5.2 DomU via vncserver at Dom0 and vncserver at DomU seems to be broken in meantime. This doesn''t work for CentOS 5.2 DomU:- WS - Work Station (Linux , Ubuntu Desktop) WS --------------------->Vncserver Dom0 ------- xm create -c DomU.pyrun---- | | | Vncviewer 1 Vncviewer 2 | | | |----------------------------> Gnome Desktop Dom0 ----------->Vncserver DomU This works:- WS -------------------->SSH conn to Dom0 ---- xm create -c DomU.pyrun----- | | | Vncviewer | | | |----------------------------> Gnome Desktop WS --------------->Vncserver DomU Boris --- On Fri, 3/27/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Friday, March 27, 2009, 7:21 PM Boris Derzhavets wrote:> I believe i have to describe the issue in more details:- > 1. Xen Unstable Dom0 with 2.6.29-rc8 pvops kernel is installed on top > of Ubuntu 8.10 Server with ubuntu desktop up and running. GDM service isrunning,> with gdm.conf configured to allow remote connections, xinetd is runningXvnc configured for remote connection as well.>2. This configuration provides remote connection to Dom0 with pvops kernel via Gnome Desktop. Crash happens when i run VNC session opened via gnome terminal at remote Dom0''s desktop ( it worked fine with rc5 or rc6 for sure).> If i ussue :- > # vncviewer IP_DomU:1 > from gnome terminal running on remote host (i.e. without any interactionwith Ubuntu> specific X-Server clients services) VNC session seems to be runningstable.>That''s a bit worrying, because it would suggest that networking in general is broken. If you don''t start Xvnc (or whatever), but run some other network-intensive test, does that crash? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2009-Mar-28 18:25 UTC
Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel)
If under Xen Unstable Suse''s 2.6.27-5 xen-ified kernel gets loaded, instead of 2.6.29-rc8 (pvops), problem disappears. Finally seems like 2.6.29-rc8 issue. Boris. --- On Sat, 3/28/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Saturday, March 28, 2009, 7:45 AM OK. After 20-25 min of extensive testing OS 2008.11 DomU crashed and dropped into stack trace, running VNC session, started via gnome terminal at remote Dom0 desktop same way as Nevada 106 did. For now there is no any exception for this issue. But, VNC session crash should not in general crash DomU. Would be glad to troubleshoot, been instructed. Boris. --- On Sat, 3/28/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Saturday, March 28, 2009, 6:18 AM Solaris Nevada b106 is also affected in schema bellow. Looks like hotplug scripts gets locked after VNC Session failure WS -------------->Vncserver Dom0 ------ xm create -c SNV_DomU.pyrun------- | | | Vncviewer 1 Vncviewer 2 | | | |---------------------> Gnome Desktop Dom0 ----------->Vncserver SNV_DomU --- On Sat, 3/28/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris Derzhavets <bderzhavets@yahoo.com> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: "Jeremy Fitzhardinge" <jeremy@goop.org> Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Saturday, March 28, 2009, 4:41 AM OpenSolaris 2008.11 PV DomU may run VNC session started via gnome terminal invoked on remote pvops Dom0 desktop pretty stable. So , OpenSolaris PV DomU is not affected. Actually , any remote VNC session with CentOS 5.2 PV DomU doing "yum upgrade" may be considered as network-intensive test and it works. I don''t think that network at DomU is broken in general. But , path for vncviewer to CentOS 5.2 DomU via vncserver at Dom0 and vncserver at DomU seems to be broken in meantime. This doesn''t work for CentOS 5.2 DomU:- WS - Work Station (Linux , Ubuntu Desktop) WS --------------------->Vncserver Dom0 ------- xm create -c DomU.pyrun---- | | | Vncviewer 1 Vncviewer 2 | | | |----------------------------> Gnome Desktop Dom0 ----------->Vncserver DomU This works:- WS -------------------->SSH conn to Dom0 ---- xm create -c DomU.pyrun----- | | | Vncviewer | | | |----------------------------> Gnome Desktop WS --------------->Vncserver DomU Boris --- On Fri, 3/27/09, Jeremy Fitzhardinge <jeremy@goop.org> wrote: From: Jeremy Fitzhardinge <jeremy@goop.org> Subject: Re: [Xen-devel] Failure to setup VNC at CentOS 5.2 PV DomU at Xen Unstable ( 2.6.29-rc8 kernel) To: bderzhavets@yahoo.com Cc: "Xen-devel" <xen-devel@lists.xensource.com> Date: Friday, March 27, 2009, 7:21 PM Boris Derzhavets wrote:> I believe i have to describe the issue in more details:- > 1. Xen Unstable Dom0 with 2.6.29-rc8 pvops kernel is installed on top > of Ubuntu 8.10 Server with ubuntu desktop up and running. GDM service isrunning,> with gdm.conf configured to allow remote connections, xinetd is runningXvnc configured for remote connection as well.>2. This configuration provides remote connection to Dom0 with pvops kernel via Gnome Desktop. Crash happens when i run VNC session opened via gnome terminal at remote Dom0''s desktop ( it worked fine with rc5 or rc6 for sure).> If i ussue :- > # vncviewer IP_DomU:1 > from gnome terminal running on remote host (i.e. without any interactionwith Ubuntu> specific X-Server clients services) VNC session seems to be runningstable.>That''s a bit worrying, because it would suggest that networking in general is broken. If you don''t start Xvnc (or whatever), but run some other network-intensive test, does that crash? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel