Re: [Xen-devel] pvgrub2 is merged

[Fabio Fantoni <fabio.fantoni@xxxxxxx>]

Il 17/12/2013 14:32, Vladimir 'Ï-coder/phcoder' Serbinenko ha scritto:
> On 17.12.2013 14:11, Fabio Fantoni wrote:
> > Il 17/12/2013 12:03, Vladimir 'Ï-coder/phcoder' Serbinenko ha scritto:
> > > On 17.12.2013 11:44, Fabio Fantoni wrote:
> > > > Il 09/12/2013 11:06, Fabio Fantoni ha scritto:
> > > > > Il 07/12/2013 11:06, Vladimir 'Ï-coder/phcoder' Serbinenko ha scritto:
> > > > > > On 06.12.2013 16:22, Fabio Fantoni wrote:
> > > > > > > Il 06/12/2013 15:55, Vladimir 'Ï-coder/phcoder' Serbinenko ha
> > > > > > > scritto:
> > > > > > > > On 06.12.2013 15:44, Fabio Fantoni wrote:
> > > > > > > > > Il 06/12/2013 12:32, Vladimir 'Ï-coder/phcoder' Serbinenko ha
> > > > > > > > > scritto:
> > > > > > > > > > On 06.12.2013 12:11, Fabio Fantoni wrote:
> > > > > > > > > > > Il 03/12/2013 17:16, Fabio Fantoni ha scritto:
> > > > > > > > > > > > Il 03/12/2013 16:33, Vladimir 'Ï-coder/phcoder' Serbinenko ha
> > > > > > > > > > > > scritto:
> > > > > > > > > > > > > On 03.12.2013 15:00, Fabio Fantoni wrote:
> > > > > > > > > > > > > > Il 03/12/2013 12:29, Vladimir 'Ï-coder/phcoder' Serbinenko ha
> > > > > > > > > > > > > > scritto:
> > > > > > > > > > > > > > > On 03.12.2013 12:22, Fabio Fantoni wrote:
> > > > > > > > > > > > > > > > Il 03/12/2013 11:33, Vladimir 'Ï-coder/phcoder'
> > > > > > > > > > > > > > > > Serbinenko ha
> > > > > > > > > > > > > > > > scritto:
> > > > > > > > > > > > > > > > > On 03.12.2013 11:31, Fabio Fantoni wrote:
> > > > > > > > > > > > > > > > > > If you need more tests/informations tell me and I'll post
> > > > > > > > > > > > > > > > > > them.
> > > > > > > > > > > > > > > > > I've already asked you for exact kernel that I can
> > > > > > > > > > > > > > > > > download (and
> > > > > > > > > > > > > > > > > SHA512
> > > > > > > > > > > > > > > > > to check it's the same one) and got only vague response
> > > > > > > > > > > > > > > > Thanks for reply.
> > > > > > > > > > > > > > > > The actual kernel used is from this package:
> > > > > > > > > > > > > > > > http://packages.debian.org/sid/linux-image-3.11-2-amd64
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I already checked kernel's files integrity with md5
> > > > > > > > > > > > > > > > (using the
> > > > > > > > > > > > > > > > debian
> > > > > > > > > > > > > > > > package's md5sums file and is correct).
> > > > > > > > > > > > > > > > Same domU with pygrub with manual and minimal grub.cfg
> > > > > > > > > > > > > > > > configuration and
> > > > > > > > > > > > > > > > it boots correctly, but with pvgrub2 and grub.cfg created
> > > > > > > > > > > > > > > > automatically
> > > > > > > > > > > > > > > > (see attachment of previous mail) it doesn't boot.
> > > > > > > > > > > > > > > With HEAD:
> > > > > > > > > > > > > > > phcoder@debian:12:21:06:~/compile/bt/x86_64-xen$ ar x
> > > > > > > > > > > > > > > ~/downloads/linux-image-3.11-2-amd64_3.11.8-1_amd64.deb
> > > > > > > > > > > > > > > phcoder@debian:12:23:29:~/compile/bt/x86_64-xen$ tar --xz -xf
> > > > > > > > > > > > > > > data.tar.xz
> > > > > > > > > > > > > > > phcoder@debian:12:28:36:~/compile/bt/x86_64-xen$ sha512sum
> > > > > > > > > > > > > > > boot/vmlinuz-3.11-2-amd64
> > > > > > > > > > > > > > > 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >         boot/vmlinuz-3.11-2-amd64
> > > > > > > > > > > > > > > phcoder@debian:12:23:38:~/compile/bt/x86_64-xen$
> > > > > > > > > > > > > > > ./grub-mkstandalone
> > > > > > > > > > > > > > > --grub-mkimage=./grub-mkimage -o grub.xen -O x86_64-xen -d
> > > > > > > > > > > > > > > grub-core/
> > > > > > > > > > > > > > > boot/vmlinuz-3.11-2-amd64
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >                                     GNU GRUB version 2.00
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >           Minimal BASH-like line editing is supported. For the
> > > > > > > > > > > > > > > first
> > > > > > > > > > > > > > > word, TAB
> > > > > > > > > > > > > > >           lists possible command completions. Anywhere else
> > > > > > > > > > > > > > > TAB lists
> > > > > > > > > > > > > > > possible
> > > > > > > > > > > > > > >           device or file completions.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > grub> insmod xzio
> > > > > > > > > > > > > > > grub> linux /boot/vmlinuz-3.11-2-amd64
> > > > > > > > > > > > > > > grub> boot
> > > > > > > > > > > > > > > [    0.000000] Initializing cgroup subsys cpuset
> > > > > > > > > > > > > > > [    0.000000] Initializing cgroup subsys cpu
> > > > > > > > > > > > > > > [    0.000000] Initializing cgroup subsys cpuacct
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I've uploaded my grub.xen to
> > > > > > > > > > > > > > > http://download-mirror.savannah.gnu.org/releases/grub/phcoder/grub.xen.xz
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Thanks for any reply.
> > > > > > > > > > > > > > Thanks for your reply.
> > > > > > > > > > > > > > I tried with your build and gave me:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Caricamento Linux 3.11-2-amd64...
> > > > > > > > > > > > > > errore: not xen image.
> > > > > > > > > > > > > > Caricamento ramdisk iniziale...
> > > > > > > > > > > > > > errore: ? necessario caricare il kernel prima.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I also rebuilt pvgrub2 from clean directory, full logs of
> > > > > > > > > > > > > > configure,
> > > > > > > > > > > > > > make and xl create on attachment.
> > > > > > > > > > > > > > Also in this case domU destroys on kernel and initrd loading.
> > > > > > > > > > > > > > I not understand what are my errors and/or forgetfulness.
> > > > > > > > > > > > > $ sha512sum /boot/vmlinuz-3.11-2-amd64
> > > > > > > > > > > > sha512sum /mnt/tmp/boot/vmlinuz-3.11-2-amd64
> > > > > > > > > > > > 002bc39cfc0191614ec380a44993d20691e1dc8791a8c6f3a163777ef6fb733243d3da48760b2eedfc3ab9b8bd7b8fe2d473cdd3a91eb3d855eb4f3db9f7b6df
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > /mnt/tmp/boot/vmlinuz-3.11-2-amd64
> > > > > > > > > > > >
> > > > > > > > > > > > > Did you try with kernel embed in GRUB?
> > > > > > > > > > > > I tried with ./grub-mkstandalone
> > > > > > > > > > > > --grub-mkimage=./grub-mkimage -o
> > > > > > > > > > > > pvgrub2.xen -O x86_64-xen -d grub-core/
> > > > > > > > > > > > /mnt/tmp/boot/vmlinuz-3.11-2-amd64
> > > > > > > > > > > > Probably I did something wrong or missed about this test.
> > > > > > > > > > > > On xl create it arrives to grub console, so I tried to set root
> > > > > > > > > > > > and
> > > > > > > > > > > > include the grub.cfg of domU but gave nothing, only new console
> > > > > > > > > > > > line.
> > > > > > > > > > > > Can you give me more details to do a complete and correct test?
> > > > > > > > > > > >
> > > > > > > > > > > > > Did you try root/linux/initrd/boot sequence manually?
> > > > > > > > > > > > I presume you mean to do insmod, set root and all other command
> > > > > > > > > > > > manually without using grub.cfg, could you confirm that or give
> > > > > > > > > > > > me an
> > > > > > > > > > > > exact howto?
> > > > > > > > > > > I tried manually sequence instead of do it with grub.cfg (I
> > > > > > > > > > > hope to
> > > > > > > > > > > did
> > > > > > > > > > > it correctly):
> > > > > > > > > > >
> > > > > > > > > > > ...
> > > > > > > > > > > grub> insmod part_msdos
> > > > > > > > > > > grub> insmod xzio
> > > > > > > > > > > grub> insmod ext2
> > > > > > > > > > > grub> insmod gzio
> > > > > > > > > > > grub> set root=(xen/xvda,msdos1)
> > > > > > > > > > > grub> linux /boot/vmlinuz-3.11-2-amd64
> > > > > > > > > > > root=UUID=3ab55964-09d1-4853-be38-661b56a14 ro console=tty0 debug
> > > > > > > > > > > grub> initrd /boot/initrd.img-3.11-2-amd64
> > > > > > > > > > > grub> boot
> > > > > > > > > > > xc: debug: hypercall buffer: total allocations:237 total
> > > > > > > > > > > releases:237
> > > > > > > > > > > xc: debug: hypercall buffer: current allocations:0 maximum
> > > > > > > > > > > allocations:4
> > > > > > > > > > > xc: debug: hypercall buffer: cache current size:4
> > > > > > > > > > > xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7
> > > > > > > > > > >
> > > > > > > > > > > unfortunately the result is the same :(
> > > > > > > > > > Hm, that is different from previous. Previously you spoke about
> > > > > > > > > > "not a
> > > > > > > > > > xen image" message. I'd remove console=tty0 and also try without
> > > > > > > > > > initrd.
> > > > > > > > > Without console and initrd:
> > > > > > > > >
> > > > > > > > > ...
> > > > > > > > > grub> insmod part_msdos
> > > > > > > > > grub> insmod xzio
> > > > > > > > > grub> insmod ext2
> > > > > > > > > grub> insmod gzio
> > > > > > > > > grub> set root=(xen/xvda,msdos1)
> > > > > > > > > grub> linux /boot/vmlinuz-3.11-2-amd64
> > > > > > > > > root=UUID=3ab55964-09d1-4853-be38-661b5a476a14 ro debug
> > > > > > > > > grub> boot
> > > > > > > > > xc: debug: hypercall buffer: total allocations:247 total
> > > > > > > > > releases:247
> > > > > > > > > xc: debug: hypercall buffer: current allocations:0 maximum
> > > > > > > > > allocations:4
> > > > > > > > > xc: debug: hypercall buffer: cache current size:4
> > > > > > > > > xc: debug: hypercall buffer: cache hits:236 misses:4 toobig:7
> > > > > > > > Which xen version is it? I tried only with 4.3
> > > > > > > I always use xen-unstable (4.4) for pvgrub2 tests.
> > > > > > > My actual build is on upstream commit
> > > > > > > 4b07b3cbf29f66da6090d52e75b5fdae592c6441
> > > > > > > Could you check with xen-unstable? (now on freeze and near to first
> > > > > > > 4.4 rc)
> > > > > > Can't tell I get far on this one. I installed xen from git but when I
> > > > > > attempt to execute any command with xl it just hangs.
> > > > > Did you try also -vvv?
> > > > > If it show any debug messages please post them and add also xen-devel
> > > > > to cc in that case.
> > > > > Can you also post details about your dom0?
> > > > >
> > > > > > Is there anything in your xl dmesg
> > > > > > Meanwhile I implemented vfb/vkbd in phcoder/vfb branch.
> > > > > I tried vfb branch:
> > > > > git log
> > > > > commit acc3ea93f59727bdac47b1fef4eef24380161847
> > > > > Author: Vladimir Serbinenko <phcoder@xxxxxxxxx>
> > > > > Date:   Sat Dec 7 12:46:59 2013 +0100
> > > > >
> > > > >       Fix compilation error
> > > > >
> > > > > I installed missed unifont package and compiled grub.
> > > > >
> > > > > xl -vvv create -c does not show any grub line and crashes.
> > > > > I attached xl -vvv create -c output and xl dmesg with calltrace inside.
> > > > >
> > > > > If you need more informations and/or tests tell me and I'll post them.
> > > > >
> > > > > Thanks for any reply.
> > > > I've seen 2 new commits about xen on master, than I tried to update and
> > > > rebuild pvgrub2.
> > > With Xen 4.3 everything seems to work. However if I install Xen 4.4 from
> > > git. All I get:
> > > phcoder@debian:11:58:30:~/grub2$ sudo /usr/local/sbin/xl create -f
> > > grub.dom -vv
> > > Swipe your right index finger across the fingerprint reader
> > > xc: error: Could not obtain handle on privileged command interface (2 =
> > > No such file or directory): Internal error
> > > libxl: error: libxl.c:92:libxl_ctx_alloc: cannot open libxc handle: No
> > > such file or directory
> > > cannot init xl context
> > > phcoder@debian:11:58:36:~/grub2$ sudo mount -t xenfs xenfs /proc/xen/
> > > phcoder@debian:11:58:46:~/grub2$ sudo /usr/local/sbin/xl create -f
> > > grub.dom -vv
> > > option `v' not supported.
> > > option `v' not supported.
> > > Parsing config from grub.dom
> > > <just sits there>
> > -v must be before the subcommand, for example "xl -vvv create
> > /etc/xen/sid.cfg".
> > xenfs should be automatically mounted by xencommons init script, make
> > sure that it is running before executing xl commands, it is needed to
> > load necessary kernel modules (if they are not already loaded), xenfs,
> > xenstore and xenconsoled.
> Yes, gone through that already, see my other mail and recent commits.
> Your issue should be fixed.
Thanks.
Now there is another error, probably introduced by xenfb support:

xl -vvv create -c /etc/xen/sid.cfg
...
Welcome to GRUB!
error: file `/boot/grub/x86_64-xen/gfxterm.mod' not found.
error: file `/boot/grub/locale/it.gmo' not found.
[    0.000000] PAGETABLE BUG #02!
[    1.298688] i8042: No controller found
[    1.368244] /build/linux-4VBEpo/linux-3.11.8/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
xc: debug: hypercall buffer: total allocations:237 total releases:237
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:226 misses:4 toobig:7

xl dmesg
...
(d17) mapping kernel into physical memory
(d17) about to get started...
(XEN) mm.c:2352:d17 Bad type (saw 7400000000000001 != exp 
1000000000000000) for mfn 2171b8 (pfn 3fbe8)
(XEN) mm.c:2995:d17 Error while pinning mfn 2171b8
(XEN) mm.c:2352:d17 Bad type (saw 7400000000000001 != exp 
1000000000000000) for mfn 2171b8 (pfn 3fbe8)
(XEN) mm.c:906:d17 Attempt to create linear p.t. with write perms
(XEN) mm.c:2352:d17 Bad type (saw 7400000000000001 != exp 
1000000000000000) for mfn 2171ba (pfn 3fbe6)
(XEN) mm.c:2995:d17 Error while pinning mfn 2171ba
(XEN) mm.c:2352:d17 Bad type (saw 7400000000000001 != exp 
1000000000000000) for mfn 2171bb (pfn 3fbe5)
(XEN) mm.c:2995:d17 Error while pinning mfn 2171bb
(XEN) mm.c:2352:d17 Bad type (saw 7400000000000001 != exp 
2000000000000000) for mfn 2171b9 (pfn 3fbe7)
(XEN) mm.c:948:d17 Attempt to create linear p.t. with write perms
(XEN) mm.c:1379:d17 Failure in alloc_l3_table: entry 511
(XEN) mm.c:2099:d17 Error while validating mfn 23df00 (pfn 19a0) for 
type 3000000000000000: caf=8000000000000003 taf=3000000000000001
(XEN) mm.c:972:d17 Attempt to create linear p.t. with write perms
(XEN) mm.c:1438:d17 Failure in alloc_l4_table: entry 511
(XEN) mm.c:2099:d17 Error while validating mfn 2b5d85 (pfn 241b) for 
type 4000000000000000: caf=8000000000000003 taf=4000000000000001
(XEN) mm.c:2995:d17 Error while pinning mfn 2b5d85
(XEN) mm.c:2352:d17 Bad type (saw 7400000000000001 != exp 
2000000000000000) for mfn 2171b9 (pfn 3fbe7)
(XEN) mm.c:948:d17 Attempt to create linear p.t. with write perms
(XEN) mm.c:1379:d17 Failure in alloc_l3_table: entry 511
(XEN) mm.c:2099:d17 Error while validating mfn 23df00 (pfn 19a0) for 
type 3000000000000000: caf=8000000000000003 taf=3000000000000001
(XEN) mm.c:972:d17 Attempt to create linear p.t. with write perms
(XEN) mm.c:1438:d17 Failure in alloc_l4_table: entry 511
(XEN) mm.c:2099:d17 Error while validating mfn 2b5d85 (pfn 241b) for 
type 4000000000000000: caf=8000000000000003 taf=4000000000000001
(XEN) mm.c:3122:d17 Error while installing new mfn 2b5d85
(XEN) traps.c:291:d17 Guest switching to user mode with no user page tables
(XEN) traps.c:320:d17 Fatal error
(XEN) domain_crash called from traps.c:321
(XEN) Domain 17 (vcpu#1) crashed on cpu#3:
(XEN) ----[ Xen-4.4-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    3
(XEN) RIP:    e033:[<ffffffff810012ed>]
(XEN) RFLAGS: 0000000000000286   EM: 1   CONTEXT: pv guest
(XEN) rax: 0000000000000017   rbx: 0000000000000000   rcx: ffffffff810012ed
(XEN) rdx: 0000000000000000   rsi: 0000000000000000   rdi: 0000000000000000
(XEN) rbp: 0000000000000000   rsp: ffff88003e1f9fb8   r8: 0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000286
(XEN) cr0: 000000008005003b   cr4: 00000000000026f0
(XEN) cr3: 00000002b5d86000   cr2: 00007fffb46b9e19
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e02b   cs: e033
(XEN) Guest stack trace from rsp=ffff88003e1f9fb8:
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    00007f0b1f431500 0000000000000033 0000000000000200 00007fffb46b9ca0
(XEN)    000000000000002b ffff88003e004958 ffff88003e004958 0000000000000080
(XEN)    ffff88003e1fa080 ffffffff00000006 d5dc82dde2520000 0000000200000001
(XEN)    0000000400000003 ffffffff00000005 0501e668a45aed37 d3a51001f8186504
(XEN)    3d41962be0a726d3 fbee8906bde13da3 9e907ea339feb0c4 270b40af55a0f4b8
(XEN)    264b0560a7e2c9dc 0a3145802804d2e1 faf4b4eca4180ba6 01957dd1d4131d2e
(XEN)    a18b79fe805a7821 bf0afc62c71eddcb 630fca5df80eb04b 845a16e1648fdd51
(XEN)    c588c03d2edcf807 9cf4717d19322687 510724530fcbf04b d8f1199bd10015fe
(XEN)    5272422fa11fb05c f2447667cb9fa47a 37c90f94df9206f9 43eca9d987b7240b
(XEN)    def99e5d7d577367 9b0d95f77cdf3672 4ef9836df37ccdf6 5a79437e62989ecf
(XEN)    3772f347b726713a 27fc0fe3f633e7e4 b975e7e927ca3183 a3eb9b3cea9ebb28
(XEN)    76b3d73a083d2d34 3e7c801b21bd2ad3 4874b5adac7be5fe 327fb4145bc5967e
(XEN)    ce5fd2670ed6fe93 6671781eb982fcaf 865c0f25bbc6796d da793d360234fc4d
(XEN)    fe53c86f9465bf2c cf6fc89cfcb9d3e9 a05d1a75741d9703 0670c66fb870cfae
(XEN)    fc725a3f8a7f7448 759e29fdd16ebe29 3bea153e12f5193a 8a2727cf5451fa53
(XEN)    740afaa283c9cbea e8059556115ea89f 08b76c91fd5bd13f 21d63b340cca2982
(XEN)    9ae74e68a733e980 ace9f7ded7134e44 6c7e4a6a743f4959 fbe3ca9cd6501e75
(XEN)    93b91393e99784e0 dd54b7bd06b739b9 2aefee3afab953f4 5a9c30b6dd98fadc
(XEN)    390f275e52fa88ef 18115b1dfc41622e 29960fc50c03101e 04a4d7f6a9fd0795

> > In that case it is good to use also -c after create to open the xl
> > console strightaway and see what pvgrub2 is doing, for example "xl -vvv
> > create -c /etc/xen/sid.cfg".
> >
> > > > git log
> > > > commit a82010503e3098930a56110826c4ffe6e1609726
> > > > Author: Vladimir Serbinenko <phcoder@xxxxxxxxx>
> > > > Date:   Tue Dec 17 01:18:09 2013 +0100
> > > >
> > > >           Update exclude.pot and mark few strings for translation.
> > > >
> > > >
> > > > My problem on kernel boot with Sid and Wheezy domUs persist.
> > > >
> > > > Thanks for any reply.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel