Test report for xen-unstable and qemu-xen

Test report for xen-unstable and qemu-xen

[Vasiliy Tolstov]

Dom0:
linux 3.9.0

xen:
latest from git

domain config (plain):
name='"21-10887"'
kernel='"/usr/lib/xen/boot/pv-grub-x86_64.gz"'
vif='["mac=00:16:3e:00:20:3b,ip=62.76.191.124"]'
disk='["phy:/dev/disk/vbd/21-885,xvda,w"]'
memory=512
maxmem=4096
vcpus=7
maxvcpus=7
cpu_cap=700
cpu_weight=512
vfb='["type=vnc,vnclisten=0.0.0.0,vncpasswd=0a7cwrZEb9"]'
extra='"(hd0,0)/boot/grub/menu.lst root=/dev/xvda1 selinux=1
enforcing=0 iommu=soft earlyprintk=xen console=hvc0"'
on_restart='"destroy"'
cpuid='"host,x2apic=0,aes=0,xsave=0,avx=0"'

domain config from xl list -l:
[
    {
        "domid": 1,
        "config": {
            "c_info": {
                "type": "pv",
                "hap": "<default>",
                "oos": "<default>",
                "ssidref": 0,
                "name": "21-10887",
                "uuid": "0657b941-07b6-457f-8bcf-9488bd8e2827",
                "xsdata": {

                },
                "platformdata": {

                },
                "poolid": 0,
                "run_hotplug_scripts": "True"
            },
            "b_info": {
                "max_vcpus": 7,
                "avail_vcpus": [
                    0,
                    1,
                    2,
                    3,
                    4,
                    5,
                    6
                ],
                "cpumap": [

                ],
                "nodemap": [

                ],
                "numa_placement": "<default>",
                "tsc_mode": "default",
                "max_memkb": 4194304,
                "target_memkb": 524288,
                "video_memkb": -1,
                "shadow_memkb": 39936,
                "rtc_timeoffset": 0,
                "exec_ssidref": 0,
                "localtime": "<default>",
                "disable_migrate": "<default>",
                "cpuid": [
                    {
                        "leaf": 1,
                        "ecx": "xxx0x00xxx0xxxxxxxxxxxxxxxxxxxxx"
                    }
                ],
                "blkdev_start": null,
                "device_model_version": null,
                "device_model_stubdomain": "<default>",
                "device_model": null,
                "device_model_ssidref": 0,
                "extra": [

                ],
                "extra_pv": [

                ],
                "extra_hvm": [

                ],
                "sched_params": {
                    "sched": "unknown",
                    "weight": 512,
                    "cap": -1,
                    "period": -1,
                    "slice": -1,
                    "latency": -1,
                    "extratime": -1
                },
                "ioports": [

                ],
                "irqs": [

                ],
                "iomem": [

                ],
                "claim_mode": "False",
                "u": {
                    "kernel": "/usr/lib/xen/boot/pv-grub-x86_64.gz",
                    "slack_memkb": -1,
                    "bootloader": null,
                    "bootloader_args": [

                    ],
                    "cmdline": "(hd0,0)/boot/grub/menu.lst
root=/dev/xvda1 selinux=1 enforcing=0 iommu=soft earlyprintk=xen
console=hvc0",
                    "ramdisk": null,
                    "e820_host": "<default>"
                }
            },
            "disks": [
                {
                    "backend_domid": 0,
                    "backend_domname": null,
                    "pdev_path": "/dev/disk/vbd/21-885",
                    "vdev": "xvda",
                    "backend": "unknown",
                    "format": "raw",
                    "script": null,
                    "removable": 0,
                    "readwrite": 1,
                    "is_cdrom": 0
                }
            ],
            "nics": [
                {
                    "backend_domid": 0,
                    "backend_domname": null,
                    "devid": 0,
                    "mtu": 0,
                    "model": null,
                    "mac": "00:16:3e:00:20:3b",
                    "ip": "62.76.191.124",
                    "bridge": null,
                    "ifname": null,
                    "script": "/etc/xen/scripts/vif-route",
                    "nictype": null,
                    "rate_bytes_per_interval": 0,
                    "rate_interval_usecs": 0,
                    "gatewaydev": null
                }
            ],
            "pcidevs": [

            ],
            "vfbs": [
                {
                    "backend_domid": 0,
                    "backend_domname": null,
                    "devid": 0,
                    "vnc": {
                        "enable": "<default>",
                        "listen": "0.0.0.0",
                        "passwd": "0a7cwrZEb9",
                        "display": 0,
                        "findunused": "<default>"
                    },
                    "sdl": {
                        "enable": "<default>",
                        "opengl": "<default>",
                        "display": null,
                        "xauthority": null
                    },
                    "keymap": null
                }
            ],
            "vkbs": [
                {
                    "backend_domid": 0,
                    "backend_domname": null,
                    "devid": 0
                }
            ],
            "vtpms": [

            ],
            "on_poweroff": "destroy",
            "on_reboot": "restart",
            "on_watchdog": "destroy",
            "on_crash": "destroy"
        }
    }
]

Issues:
Very slow migration speed. Domain tries to migrate is about 30 minutes
and nothing happened
I'm migrate via infiniband 40 Gb/s

Progress is:
xl migrate --debug 21-10887 192.168.25.28
the global config option vifscript is deprecated, please switch to
vif.default.script
the global config option vifscript is deprecated, please switch to
vif.default.script
migration target: Ready to receive domain.
Saving to migration stream new xl format (info 0x0/0x0/587)
Loading new save file <incoming migration stream> (new xl fmt info 0x0/0x0/587)
 Savefile contains xl domain config
xc: progress: Reloading memory pages: 53248/1048576    5%
xc: progress: Reloading memory pages: 105472/1048576   10%
xc: progress: Reloading memory pages: 157621/1048576   15%

--
Vasiliy Tolstov,
e-mail: v.tolstov@selfip.ru
jabber: vase@selfip.ru

Re: Test report for xen-unstable and qemu-xen

[Vasiliy Tolstov]

And domain dies, migration not completed:
[ 1826.587110] PM: late freeze of devices complete after 0.048 msecs
[ 1826.591220] ------------[ cut here ]------------
[ 1826.591220] kernel BUG at
/build/buildd-linux_3.2.41-2-amd64-Wvc92F/linux-3.2.41/drivers/xen/events.c:1489!
[ 1826.591220] invalid opcode: 0000 [#1] SMP
[ 1826.591220] CPU 0
[ 1826.591220] Modules linked in: xenfs snd_pcm snd_page_alloc
snd_timer snd coretemp soundcore crc32c_intel evdev
ghash_clmulni_intel joydev pcspkr cryptd ext3 mbcache jbd xen_netfront
xen_blkfront
[ 1826.591220]
[ 1826.591220] Pid: 6, comm: migration/0 Not tainted 3.2.0-4-amd64 #1
Debian 3.2.41-2
[ 1826.591220] RIP: e030:[<ffffffff8121c4e2>]  [<ffffffff8121c4e2>]
xen_irq_resume+0xbd/0x28b
[ 1826.591220] RSP: e02b:ffff88001ae99d20  EFLAGS: 00010082
[ 1826.591220] RAX: ffffffffffffffef RBX: 0000000000000000 RCX: 0000000000000001
[ 1826.591220] RDX: 0000000000000000 RSI: 00000000deadbeef RDI: 00000000deadbeef
[ 1826.591220] RBP: 0000000000000000 R08: ffff88001f026e00 R09: ffff88001ae99d48
[ 1826.591220] R10: 0000000000013780 R11: 0000000000013780 R12: 0000000000000010
[ 1826.591220] R13: 0000000000010dd0 R14: 0000000000010d70 R15: 0000000000000000
[ 1826.591220] FS:  00007f8d6f4907a0(0000) GS:ffff88001fc00000(0000)
knlGS:0000000000000000
[ 1826.591220] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 1826.591220] CR2: 00007f51210a1e60 CR3: 00000000032af000 CR4: 0000000000002660
[ 1826.591220] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 1826.591220] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 1826.591220] Process migration/0 (pid: 6, threadinfo
ffff88001ae98000, task ffff88001ae8e0c0)
[ 1826.591220] Stack:
[ 1826.591220]  0000000000013780 0000000000000000 ffff880000000000
0000000000010d70
[ 1826.591220]  0000160000000000 0000000000000000 ffff88001affbddc
ffffffff810050a2
[ 1826.591220]  0000000000013780 ffffea000009f0b8 ffffffff810043e3
ffff88001affbe40
[ 1826.591220] Call Trace:
[ 1826.591220]  [<ffffffff810050a2>] ? xen_mc_issue+0x3e/0x50
[ 1826.591220]  [<ffffffff810043e3>] ? arch_local_irq_restore+0x7/0x8
[ 1826.591220]  [<ffffffff8121ca3b>] ? xen_suspend+0x73/0x8b
[ 1826.591220]  [<ffffffff81087d89>] ? stop_machine_cpu_stop+0x89/0xc3
[ 1826.591220]  [<ffffffff81087d00>] ? queue_stop_cpus_work+0xa5/0xa5
[ 1826.591220]  [<ffffffff81087b5a>] ? cpu_stopper_thread+0xea/0x177
[ 1826.591220]  [<ffffffff810359d7>] ? arch_local_irq_enable+0x7/0x8
[ 1826.591220]  [<ffffffff81039854>] ? finish_task_switch+0x88/0xb9
[ 1826.591220]  [<ffffffff8134c634>] ? __schedule+0x5ac/0x5c3
[ 1826.591220]  [<ffffffff81087a70>] ? cpu_stop_signal_done+0x2a/0x2a
[ 1826.591220]  [<ffffffff8105f321>] ? kthread+0x76/0x7e
[ 1826.591220]  [<ffffffff81354ab4>] ? kernel_thread_helper+0x4/0x10
[ 1826.591220]  [<ffffffff81352b73>] ? int_ret_from_sys_call+0x7/0x1b
[ 1826.591220]  [<ffffffff8134dcbc>] ? retint_restore_args+0x5/0x6
[ 1826.591220]  [<ffffffff81354ab0>] ? gs_change+0x13/0x13
[ 1826.591220] Code: 74 79 44 89 e7 e8 77 ee ff ff 39 e8 74 02 0f 0b
48 8d 74 24 28 bf 01 00 00 00 89 6c 24 28 89 5c 24 2c e8 19 ec ff ff
85 c0 74 02 <0f> 0b 8b 44 24 30 44 89 e7 89 44 24 14 e8 58 e9 ff ff 0f
b7 4c
[ 1826.591220] RIP  [<ffffffff8121c4e2>] xen_irq_resume+0xbd/0x28b
[ 1826.591220]  RSP <ffff88001ae99d20>
[ 1826.591220] ---[ end trace 60605833d257c851 ]---
[ 1826.591220] ------------[ cut here ]------------
[ 1826.591220] WARNING: at
/build/buildd-linux_3.2.41-2-amd64-Wvc92F/linux-3.2.41/kernel/time/timekeeping.c:265
ktime_get+0x1e/0x86()
[ 1826.591220] Modules linked in: xenfs snd_pcm snd_page_alloc
snd_timer snd coretemp soundcore crc32c_intel evdev
ghash_clmulni_intel joydev pcspkr cryptd ext3 mbcache jbd xen_netfront
xen_blkfront
[ 1826.591220] Pid: 0, comm: swapper/0 Tainted: G      D
3.2.0-4-amd64 #1 Debian 3.2.41-2
[ 1826.591220] Call Trace:
[ 1826.591220]  [<ffffffff81046a55>] ? warn_slowpath_common+0x78/0x8c
[ 1826.591220]  [<ffffffff81066447>] ? ktime_get+0x1e/0x86
[ 1826.591220]  [<ffffffff8106c21b>] ? tick_nohz_stop_sched_tick+0x61/0x327
[ 1826.591220]  [<ffffffff8100d210>] ? cpu_idle+0x72/0xf2
[ 1826.591220]  [<ffffffff816abb36>] ? start_kernel+0x3b8/0x3c3
[ 1826.591220]  [<ffffffff816ad4d9>] ? xen_start_kernel+0x412/0x418
[ 1826.591220] ---[ end trace 60605833d257c852 ]---

2013/5/14 Vasiliy Tolstov <v.tolstov@selfip.ru>:
> Dom0:
> linux 3.9.0
>
> xen:
> latest from git
>
> domain config (plain):
> name='"21-10887"'
> kernel='"/usr/lib/xen/boot/pv-grub-x86_64.gz"'
> vif='["mac=00:16:3e:00:20:3b,ip=62.76.191.124"]'
> disk='["phy:/dev/disk/vbd/21-885,xvda,w"]'
> memory=512
> maxmem=4096
> vcpus=7
> maxvcpus=7
> cpu_cap=700
> cpu_weight=512
> vfb='["type=vnc,vnclisten=0.0.0.0,vncpasswd=0a7cwrZEb9"]'
> extra='"(hd0,0)/boot/grub/menu.lst root=/dev/xvda1 selinux=1
> enforcing=0 iommu=soft earlyprintk=xen console=hvc0"'
> on_restart='"destroy"'
> cpuid='"host,x2apic=0,aes=0,xsave=0,avx=0"'
>
> domain config from xl list -l:
> [
>     {
>         "domid": 1,
>         "config": {
>             "c_info": {
>                 "type": "pv",
>                 "hap": "<default>",
>                 "oos": "<default>",
>                 "ssidref": 0,
>                 "name": "21-10887",
>                 "uuid": "0657b941-07b6-457f-8bcf-9488bd8e2827",
>                 "xsdata": {
>
>                 },
>                 "platformdata": {
>
>                 },
>                 "poolid": 0,
>                 "run_hotplug_scripts": "True"
>             },
>             "b_info": {
>                 "max_vcpus": 7,
>                 "avail_vcpus": [
>                     0,
>                     1,
>                     2,
>                     3,
>                     4,
>                     5,
>                     6
>                 ],
>                 "cpumap": [
>
>                 ],
>                 "nodemap": [
>
>                 ],
>                 "numa_placement": "<default>",
>                 "tsc_mode": "default",
>                 "max_memkb": 4194304,
>                 "target_memkb": 524288,
>                 "video_memkb": -1,
>                 "shadow_memkb": 39936,
>                 "rtc_timeoffset": 0,
>                 "exec_ssidref": 0,
>                 "localtime": "<default>",
>                 "disable_migrate": "<default>",
>                 "cpuid": [
>                     {
>                         "leaf": 1,
>                         "ecx": "xxx0x00xxx0xxxxxxxxxxxxxxxxxxxxx"
>                     }
>                 ],
>                 "blkdev_start": null,
>                 "device_model_version": null,
>                 "device_model_stubdomain": "<default>",
>                 "device_model": null,
>                 "device_model_ssidref": 0,
>                 "extra": [
>
>                 ],
>                 "extra_pv": [
>
>                 ],
>                 "extra_hvm": [
>
>                 ],
>                 "sched_params": {
>                     "sched": "unknown",
>                     "weight": 512,
>                     "cap": -1,
>                     "period": -1,
>                     "slice": -1,
>                     "latency": -1,
>                     "extratime": -1
>                 },
>                 "ioports": [
>
>                 ],
>                 "irqs": [
>
>                 ],
>                 "iomem": [
>
>                 ],
>                 "claim_mode": "False",
>                 "u": {
>                     "kernel": "/usr/lib/xen/boot/pv-grub-x86_64.gz",
>                     "slack_memkb": -1,
>                     "bootloader": null,
>                     "bootloader_args": [
>
>                     ],
>                     "cmdline": "(hd0,0)/boot/grub/menu.lst
> root=/dev/xvda1 selinux=1 enforcing=0 iommu=soft earlyprintk=xen
> console=hvc0",
>                     "ramdisk": null,
>                     "e820_host": "<default>"
>                 }
>             },
>             "disks": [
>                 {
>                     "backend_domid": 0,
>                     "backend_domname": null,
>                     "pdev_path": "/dev/disk/vbd/21-885",
>                     "vdev": "xvda",
>                     "backend": "unknown",
>                     "format": "raw",
>                     "script": null,
>                     "removable": 0,
>                     "readwrite": 1,
>                     "is_cdrom": 0
>                 }
>             ],
>             "nics": [
>                 {
>                     "backend_domid": 0,
>                     "backend_domname": null,
>                     "devid": 0,
>                     "mtu": 0,
>                     "model": null,
>                     "mac": "00:16:3e:00:20:3b",
>                     "ip": "62.76.191.124",
>                     "bridge": null,
>                     "ifname": null,
>                     "script": "/etc/xen/scripts/vif-route",
>                     "nictype": null,
>                     "rate_bytes_per_interval": 0,
>                     "rate_interval_usecs": 0,
>                     "gatewaydev": null
>                 }
>             ],
>             "pcidevs": [
>
>             ],
>             "vfbs": [
>                 {
>                     "backend_domid": 0,
>                     "backend_domname": null,
>                     "devid": 0,
>                     "vnc": {
>                         "enable": "<default>",
>                         "listen": "0.0.0.0",
>                         "passwd": "0a7cwrZEb9",
>                         "display": 0,
>                         "findunused": "<default>"
>                     },
>                     "sdl": {
>                         "enable": "<default>",
>                         "opengl": "<default>",
>                         "display": null,
>                         "xauthority": null
>                     },
>                     "keymap": null
>                 }
>             ],
>             "vkbs": [
>                 {
>                     "backend_domid": 0,
>                     "backend_domname": null,
>                     "devid": 0
>                 }
>             ],
>             "vtpms": [
>
>             ],
>             "on_poweroff": "destroy",
>             "on_reboot": "restart",
>             "on_watchdog": "destroy",
>             "on_crash": "destroy"
>         }
>     }
> ]
>
> Issues:
> Very slow migration speed. Domain tries to migrate is about 30 minutes
> and nothing happened
> I'm migrate via infiniband 40 Gb/s
>
> Progress is:
> xl migrate --debug 21-10887 192.168.25.28
> the global config option vifscript is deprecated, please switch to
> vif.default.script
> the global config option vifscript is deprecated, please switch to
> vif.default.script
> migration target: Ready to receive domain.
> Saving to migration stream new xl format (info 0x0/0x0/587)
> Loading new save file <incoming migration stream> (new xl fmt info 0x0/0x0/587)
>  Savefile contains xl domain config
> xc: progress: Reloading memory pages: 53248/1048576    5%
> xc: progress: Reloading memory pages: 105472/1048576   10%
> xc: progress: Reloading memory pages: 157621/1048576   15%
>
> --
> Vasiliy Tolstov,
> e-mail: v.tolstov@selfip.ru
> jabber: vase@selfip.ru



-- 
Vasiliy Tolstov,
e-mail: v.tolstov@selfip.ru
jabber: vase@selfip.ru

Re: Test report for xen-unstable and qemu-xen

[Konrad Rzeszutek Wilk]

> Issues:
> Very slow migration speed. Domain tries to migrate is about 30 minutes
> and nothing happened

Was the earlier version of Xen (Xen 4.2 or Xen 4.1) showing the same slowness?

> I'm migrate via infiniband 40 Gb/s
> 
> Progress is:
> xl migrate --debug 21-10887 192.168.25.28
> the global config option vifscript is deprecated, please switch to
> vif.default.script
> the global config option vifscript is deprecated, please switch to
> vif.default.script
> migration target: Ready to receive domain.
> Saving to migration stream new xl format (info 0x0/0x0/587)
> Loading new save file <incoming migration stream> (new xl fmt info 0x0/0x0/587)
>  Savefile contains xl domain config
> xc: progress: Reloading memory pages: 53248/1048576    5%
> xc: progress: Reloading memory pages: 105472/1048576   10%
> xc: progress: Reloading memory pages: 157621/1048576   15%
> 
> --
> Vasiliy Tolstov,
> e-mail: v.tolstov@selfip.ru
> jabber: vase@selfip.ru
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

Re: Test report for xen-unstable and qemu-xen

[Vasiliy Tolstov]

[-- Attachment #1.1: Type: text/plain, Size: 1424 bytes --]

14.05.2013 17:12 пользователь "Konrad Rzeszutek Wilk" <
konrad.wilk@oracle.com> написал:
>
> > Issues:
> > Very slow migration speed. Domain tries to migrate is about 30 minutes
> > and nothing happened
>
> Was the earlier version of Xen (Xen 4.2 or Xen 4.1) showing the same
slowness?
>

Xen 4.2.2 not so slow, but fail to migrate.
Xen 4.1.0 with suse patches works fine and migrate domain in 3 minutes.

> > I'm migrate via infiniband 40 Gb/s
> >
> > Progress is:
> > xl migrate --debug 21-10887 192.168.25.28
> > the global config option vifscript is deprecated, please switch to
> > vif.default.script
> > the global config option vifscript is deprecated, please switch to
> > vif.default.script
> > migration target: Ready to receive domain.
> > Saving to migration stream new xl format (info 0x0/0x0/587)
> > Loading new save file <incoming migration stream> (new xl fmt info
0x0/0x0/587)
> >  Savefile contains xl domain config
> > xc: progress: Reloading memory pages: 53248/1048576    5%
> > xc: progress: Reloading memory pages: 105472/1048576   10%
> > xc: progress: Reloading memory pages: 157621/1048576   15%
> >
> > --
> > Vasiliy Tolstov,
> > e-mail: v.tolstov@selfip.ru
> > jabber: vase@selfip.ru
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> >

[-- Attachment #1.2: Type: text/html, Size: 2037 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.51-1 and all dependency packages for xen, spice and usb redirection.
Seabios 1.7.3-1, spice 0.12.4-0nocelt1 and usbredir 0.6-2 compiled from 
debian unstable sources.
-------------------------
git clone https://github.com/Fantu/Xen.git
git checkout rebase/m2r-next
the xen upstream commit is 699be3096ce62e2d6ef953b2a223c34330598ac8, 
plus these patches not upstream:
libxl: new parameters for upstream qemu's vga interfaces
libxl: remove qemu default devices for upstream qemu
tools: various things just to build test
tools: Improve make debball
libxl: Add qxl vga interface support for upstream qemu
libxl: usb2 and usb3 controller support for upstream qemu
libxl: spice usbredirection support for upstream qemu
-------------------------
vi Config.mk # Change upstream qemu to 1.7 from git (commit 
1cdae4573d7613149348d834c605bfbe3c7d405b)
QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
QEMU_UPSTREAM_REVISION ?= master
----
./configure --prefix=/usr --enable-qemu-traditional=no 
--with-system-seabios=/usr/share/seabios/bios.bin
-------------------------
make debball


-------------------------
Regression:
-------------
- xl console not working, details here:
   http://lists.xen.org/archives/html/xen-devel/2013-10/msg00587.html
-------------------------

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
   Workaround: fixed mac address
-------------
- Unable to get QXL vga full working
   Status: Seems needed other changes/fixes on xen side before have it 
full working.
   After latest Jan Beulich patches doesn't show any other visible xen 
errors (at least I can't see them).
   Here some other data comparing with stdvga or with kvm:
   lists.xen.org/archives/html/xen-devel/2013-10/msg00016.html
-------------
- on W7 pro 64 bit domU error in the begin of qemu log, while domU seem 
to work:
   xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed 
(22 = Invalid argument): Internal error
   xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
-------------------------

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.46-1+deb7u1 and all dependency packages for xen, spice and usb 
redirection.
Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1 and 
usbredir 0.6-2 compiled from debian unstable sources.
-------------------------
git clone git://xenbits.xen.org/xen.git (in this build commit is 
de333b694591909787da54a40496fc82c8ba5b62)
-------------------------
Added some patches:
- tools-configure-qemu-for-spice-and-usbredir
- libxl-Add-spice-vdagent-support-for-upstream-qemu v5
- libxl: usb2 and usb3 controller support for upstream qemu v4
- libxl: Add qxl vga interface support for upstream qemu
- tools: Improve make deb v4
- pc: Initializing ram_memory under Xen. v2 (for fix qemu 1.6 critical 
regression)
-------------------------
vi Config.mk # Change upstream qemu to 1.6
QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
QEMU_UPSTREAM_REVISION ?= 1ee2daeb6448312d6d0e22175f5c1b9b01f8974c
----
./configure --prefix=/usr --disable-xend --enable-qemu-traditional=no 
--with-system-seabios=/usr/share/seabios/bios.bin
-------------------------
make debball

Note: mainly tested with qemu 1.6

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
   Workaround: fixed mac address
-------------
- Unable to get QXL vga full working
   Status: require SSE support on hvm domU to be implemented, for now 
works only as standard vga
-------------
- on W7 pro 64 bit domU error in the begin of qemu log, while domU seem 
to work:
   xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed 
(22 = Invalid argument): Internal error
   xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
-------------------------

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.46-1 and all dependency packages for xen, spice and usb redirection.
Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1 and 
usbredir 0.6-2 compiled from debian unstable sources.
-------------------------
git clone git://xenbits.xen.org/xen.git (in this build commit is 
30e9a840b822ea57319abc0d136945a150fb915b)
-------------------------
Added some patches:
- tools-configure-qemu-for-spice-and-usbredir
- libxl-Add-spice-vdagent-support-for-upstream-qemu v3
- libxl: Spice disable-copy-paste support for upstream qemu
- libxl: usb2 and usb3 controller support for upstream qemu v4
- tools-firmware-seabios-packaged
- tools: Improve make deb v3
- pc:Fix initialization of the ram_memory variable (to fix qemu 1.6 
critical regression)
-------------------------
vi Config.mk # Change upstream qemu to 1.6
QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
QEMU_UPSTREAM_REVISION ?= 1ee2daeb6448312d6d0e22175f5c1b9b01f8974c
----
./configure --prefix=/usr --disable-xend --enable-qemu-traditional=no
-------------------------
make debball

Note: mainly tested with qemu 1.6

-------------------------
Issues solved from my previous test build report:
-------------
- domU not start with qemu 1.5.1 and more that 2 gb of ram:
   tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it 
works,
   while with qemu 1.5.1 doesn't (stops at the beginning, spice client 
show only the lines of seabios version and machine UUID;
   qemu log show nothing more that 2 gb test), while with 2 gb of ram 
works also with qemu 1.5.1
   (SOLVED WITH QEMU 1.6)
-------------
- Starting xendomain with "xl create" show some debug options:
   Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY ARRANGEMENT:
   Loader:        0000000000100000->000000000019eb68
   Modules:       0000000000000000->0000000000000000
   TOTAL:         0000000000000000->000000007f000000
   ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
   4KB PAGES: 0x0000000000000200
   2MB PAGES: 0x00000000000003f7
   1GB PAGES: 0x0000000000000000
[done].
-------------
- nested hvm was bugged: started test it on windows 7 pro 64 domU on 
qemu-xen,
   on xpmode now works also integration features 
(disks,printers,clipboard sharing) and usb passthrough
-------------------------

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
   Workaround: fixed mac address
-------------
- on W7 pro 64 bit domU error in the begin of qemu log, while domU seem 
to work:
   xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed 
(22 = Invalid argument): Internal error
   xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
-------------------------

Re: Test report for xen-unstable and qemu-xen

[Zhang, Yang Z]

Fabio Fantoni wrote on 2013-08-27:
> Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
> version 3.2.46-1 and all dependency packages for xen, spice and usb
> redirection. Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice
> 0.12.4-0nocelt1 and usbredir 0.6-2 compiled from debian unstable
> sources. ------------------------- git clone
> git://xenbits.xen.org/xen.git (in this build commit is
> 30e9a840b822ea57319abc0d136945a150fb915b) -------------------------
> Added some patches: - tools-configure-qemu-for-spice-and-usbredir -
> libxl-Add-spice-vdagent-support-for-upstream-qemu v3 - libxl: Spice
> disable-copy-paste support for upstream qemu - libxl: usb2 and usb3
> controller support for upstream qemu v4 -
> tools-firmware-seabios-packaged - tools: Improve make deb v3 - pc:Fix
> initialization of the ram_memory variable (to fix qemu 1.6 critical
> regression) ------------------------- vi Config.mk # Change upstream
> qemu to 1.6 QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
> QEMU_UPSTREAM_REVISION ?= 1ee2daeb6448312d6d0e22175f5c1b9b01f8974c ----
> ./configure --prefix=/usr --disable-xend --enable-qemu-traditional=no
> ------------------------- make debball
> 
> Note: mainly tested with qemu 1.6
> 
> -------------------------
> Issues solved from my previous test build report:
> -------------
> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>    tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>    works, while with qemu 1.5.1 doesn't (stops at the beginning, spice
>    client show only the lines of seabios version and machine UUID; qemu
>    log show nothing more that 2 gb test), while with 2 gb of ram works
>    also with qemu 1.5.1 (SOLVED WITH QEMU 1.6)
> -------------
> - Starting xendomain with "xl create" show some debug options:
>    Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY
>    ARRANGEMENT: Loader:        0000000000100000->000000000019eb68
>    Modules:       0000000000000000->0000000000000000 TOTAL:        
>    0000000000000000->000000007f000000 ENTRY ADDRESS: 0000000000100000
>    xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200
>    2MB PAGES: 0x00000000000003f7 1GB PAGES: 0x0000000000000000
> [done].
> -------------
> - nested hvm was bugged: started test it on windows 7 pro 64 domU on
> qemu-xen,
>    on xpmode now works also integration features
> (disks,printers,clipboard sharing) and usb passthrough
> -------------------------
I didn't quite catch your meaning. Can you give more detail of what kind of nested cases you test and how many passed and how many fail?

> 
> -------------------------
> Old issue:
> - Network is not working after restore on Windows domU with qemu-xen and
> gplpv
>    Workaround: fixed mac address
> -------------
> - on W7 pro 64 bit domU error in the begin of qemu log, while domU seem
> to work:
>    xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed
>    (22 = Invalid argument): Internal error xen be: qdisk-832:
>    xc_gnttab_set_max_grants failed: Invalid argument
> -------------------------


Best regards,
Yang

Re: Test report for xen-unstable and qemu-xen

[George Dunlap]

On Wed, Aug 28, 2013 at 1:53 AM, Zhang, Yang Z <yang.z.zhang@intel.com> wrote:
> Fabio Fantoni wrote on 2013-08-27:
>> Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
>> version 3.2.46-1 and all dependency packages for xen, spice and usb
>> redirection. Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice
>> 0.12.4-0nocelt1 and usbredir 0.6-2 compiled from debian unstable
>> sources. ------------------------- git clone
>> git://xenbits.xen.org/xen.git (in this build commit is
>> 30e9a840b822ea57319abc0d136945a150fb915b) -------------------------
>> Added some patches: - tools-configure-qemu-for-spice-and-usbredir -
>> libxl-Add-spice-vdagent-support-for-upstream-qemu v3 - libxl: Spice
>> disable-copy-paste support for upstream qemu - libxl: usb2 and usb3
>> controller support for upstream qemu v4 -
>> tools-firmware-seabios-packaged - tools: Improve make deb v3 - pc:Fix
>> initialization of the ram_memory variable (to fix qemu 1.6 critical
>> regression) ------------------------- vi Config.mk # Change upstream
>> qemu to 1.6 QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
>> QEMU_UPSTREAM_REVISION ?= 1ee2daeb6448312d6d0e22175f5c1b9b01f8974c ----
>> ./configure --prefix=/usr --disable-xend --enable-qemu-traditional=no
>> ------------------------- make debball
>>
>> Note: mainly tested with qemu 1.6
>>
>> -------------------------
>> Issues solved from my previous test build report:
>> -------------
>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>    tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>>    works, while with qemu 1.5.1 doesn't (stops at the beginning, spice
>>    client show only the lines of seabios version and machine UUID; qemu
>>    log show nothing more that 2 gb test), while with 2 gb of ram works
>>    also with qemu 1.5.1 (SOLVED WITH QEMU 1.6)
>> -------------
>> - Starting xendomain with "xl create" show some debug options:
>>    Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY
>>    ARRANGEMENT: Loader:        0000000000100000->000000000019eb68
>>    Modules:       0000000000000000->0000000000000000 TOTAL:
>>    0000000000000000->000000007f000000 ENTRY ADDRESS: 0000000000100000
>>    xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200
>>    2MB PAGES: 0x00000000000003f7 1GB PAGES: 0x0000000000000000
>> [done].
>> -------------
>> - nested hvm was bugged: started test it on windows 7 pro 64 domU on
>> qemu-xen,
>>    on xpmode now works also integration features
>> (disks,printers,clipboard sharing) and usb passthrough
>> -------------------------
> I didn't quite catch your meaning. Can you give more detail of what kind of nested cases you test and how many passed and how many fail?

This is under the "issues solved" section, and it says "was bugged"
(note the past tense) and "now works", so I took him to mean that it
didn't work time he tested it, but it works now.  Is that correct,
Fabio?

It is a bit confusing. :-)

 -George

Re: Test report for xen-unstable and qemu-xen

[George Dunlap]

On Wed, Aug 28, 2013 at 11:22 AM, George Dunlap <dunlapg@umich.edu> wrote:
> On Wed, Aug 28, 2013 at 1:53 AM, Zhang, Yang Z <yang.z.zhang@intel.com> wrote:
>> Fabio Fantoni wrote on 2013-08-27:
>>> Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
>>> version 3.2.46-1 and all dependency packages for xen, spice and usb
>>> redirection. Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice
>>> 0.12.4-0nocelt1 and usbredir 0.6-2 compiled from debian unstable
>>> sources. ------------------------- git clone
>>> git://xenbits.xen.org/xen.git (in this build commit is
>>> 30e9a840b822ea57319abc0d136945a150fb915b) -------------------------
>>> Added some patches: - tools-configure-qemu-for-spice-and-usbredir -
>>> libxl-Add-spice-vdagent-support-for-upstream-qemu v3 - libxl: Spice
>>> disable-copy-paste support for upstream qemu - libxl: usb2 and usb3
>>> controller support for upstream qemu v4 -
>>> tools-firmware-seabios-packaged - tools: Improve make deb v3 - pc:Fix
>>> initialization of the ram_memory variable (to fix qemu 1.6 critical
>>> regression) ------------------------- vi Config.mk # Change upstream
>>> qemu to 1.6 QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
>>> QEMU_UPSTREAM_REVISION ?= 1ee2daeb6448312d6d0e22175f5c1b9b01f8974c ----
>>> ./configure --prefix=/usr --disable-xend --enable-qemu-traditional=no
>>> ------------------------- make debball
>>>
>>> Note: mainly tested with qemu 1.6
>>>
>>> -------------------------
>>> Issues solved from my previous test build report:
>>> -------------
>>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>>    tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>>>    works, while with qemu 1.5.1 doesn't (stops at the beginning, spice
>>>    client show only the lines of seabios version and machine UUID; qemu
>>>    log show nothing more that 2 gb test), while with 2 gb of ram works
>>>    also with qemu 1.5.1 (SOLVED WITH QEMU 1.6)
>>> -------------
>>> - Starting xendomain with "xl create" show some debug options:
>>>    Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY
>>>    ARRANGEMENT: Loader:        0000000000100000->000000000019eb68
>>>    Modules:       0000000000000000->0000000000000000 TOTAL:
>>>    0000000000000000->000000007f000000 ENTRY ADDRESS: 0000000000100000
>>>    xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200
>>>    2MB PAGES: 0x00000000000003f7 1GB PAGES: 0x0000000000000000
>>> [done].
>>> -------------
>>> - nested hvm was bugged: started test it on windows 7 pro 64 domU on
>>> qemu-xen,
>>>    on xpmode now works also integration features
>>> (disks,printers,clipboard sharing) and usb passthrough
>>> -------------------------
>> I didn't quite catch your meaning. Can you give more detail of what kind of nested cases you test and how many passed and how many fail?
>
> This is under the "issues solved" section, and it says "was bugged"
> (note the past tense) and "now works", so I took him to mean that it
> didn't work time he tested it, but it works now.  Is that correct,

*didn't work *last* time he tested it... gah..

 -G

Re: Test report for xen-unstable and qemu-xen

[Zhang, Yang Z]

George Dunlap wrote on 2013-08-28:
> On Wed, Aug 28, 2013 at 11:22 AM, George Dunlap <dunlapg@umich.edu>
> wrote:
>> On Wed, Aug 28, 2013 at 1:53 AM, Zhang, Yang Z
>> <yang.z.zhang@intel.com>
> wrote:
>>> Fabio Fantoni wrote on 2013-08-27:
>>>> Dom0: Wheezy 64 bit with kernel from package
>>>> linux-image-3.2.0-4-amd64 version 3.2.46-1 and all dependency
>>>> packages for xen, spice and usb redirection. Seabios 1.7.3-1, qemu
>>>> 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1 and usbredir 0.6-2
>>>> compiled from debian unstable sources. ------------------------- git
>>>> clone git://xenbits.xen.org/xen.git (in this build commit is
>>>> 30e9a840b822ea57319abc0d136945a150fb915b) -------------------------
>>>> Added some patches: - tools-configure-qemu-for-spice-and-usbredir -
>>>> libxl-Add-spice-vdagent-support-for-upstream-qemu v3 - libxl: Spice
>>>> disable-copy-paste support for upstream qemu - libxl: usb2 and usb3
>>>> controller support for upstream qemu v4 -
>>>> tools-firmware-seabios-packaged - tools: Improve make deb v3 - pc:Fix
>>>> initialization of the ram_memory variable (to fix qemu 1.6 critical
>>>> regression) ------------------------- vi Config.mk # Change upstream
>>>> qemu to 1.6 QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
>>>> QEMU_UPSTREAM_REVISION ?= 1ee2daeb6448312d6d0e22175f5c1b9b01f8974c
>>>> ---- ./configure --prefix=/usr --disable-xend
>>>> --enable-qemu-traditional=no ------------------------- make debball
>>>> 
>>>> Note: mainly tested with qemu 1.6
>>>> 
>>>> -------------------------
>>>> Issues solved from my previous test build report:
>>>> -------------
>>>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>>>    tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>>>>    works, while with qemu 1.5.1 doesn't (stops at the beginning, spice
>>>>    client show only the lines of seabios version and machine UUID; qemu
>>>>    log show nothing more that 2 gb test), while with 2 gb of ram works
>>>>    also with qemu 1.5.1 (SOLVED WITH QEMU 1.6)
>>>> -------------
>>>> - Starting xendomain with "xl create" show some debug options:
>>>>    Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY
>>>>    ARRANGEMENT: Loader: 0000000000100000->000000000019eb68 Modules:  
>>>>        0000000000000000->0000000000000000 TOTAL:
>>>>    0000000000000000->000000007f000000 ENTRY ADDRESS: 0000000000100000
>>>>    xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES:
>>>>    0x0000000000000200 2MB PAGES: 0x00000000000003f7 1GB PAGES:
>>>>    0x0000000000000000
>>>> [done].
>>>> -------------
>>>> - nested hvm was bugged: started test it on windows 7 pro 64 domU
>>>> on qemu-xen,
>>>>    on xpmode now works also integration features
>>>> (disks,printers,clipboard sharing) and usb passthrough
>>>> -------------------------
>>> I didn't quite catch your meaning. Can you give more detail of what
>>> kind of
> nested cases you test and how many passed and how many fail?
>> 
>> This is under the "issues solved" section, and it says "was bugged"
>> (note the past tense) and "now works", so I took him to mean that it
>> didn't work time he tested it, but it works now.  Is that correct,
> 
> *didn't work *last* time he tested it... gah..
But the patch to fix xpmode wasn't applied. So I am a little confused that why it works now.

> 
>  -G


Best regards,
Yang

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Il 28/08/2013 14:14, Zhang, Yang Z ha scritto:
> George Dunlap wrote on 2013-08-28:
>> On Wed, Aug 28, 2013 at 11:22 AM, George Dunlap <dunlapg@umich.edu>
>> wrote:
>>> On Wed, Aug 28, 2013 at 1:53 AM, Zhang, Yang Z
>>> <yang.z.zhang@intel.com>
>> wrote:
>>>> Fabio Fantoni wrote on 2013-08-27:
>>>>> Dom0: Wheezy 64 bit with kernel from package
>>>>> linux-image-3.2.0-4-amd64 version 3.2.46-1 and all dependency
>>>>> packages for xen, spice and usb redirection. Seabios 1.7.3-1, qemu
>>>>> 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1 and usbredir 0.6-2
>>>>> compiled from debian unstable sources. ------------------------- git
>>>>> clone git://xenbits.xen.org/xen.git (in this build commit is
>>>>> 30e9a840b822ea57319abc0d136945a150fb915b) -------------------------
>>>>> Added some patches: - tools-configure-qemu-for-spice-and-usbredir -
>>>>> libxl-Add-spice-vdagent-support-for-upstream-qemu v3 - libxl: Spice
>>>>> disable-copy-paste support for upstream qemu - libxl: usb2 and usb3
>>>>> controller support for upstream qemu v4 -
>>>>> tools-firmware-seabios-packaged - tools: Improve make deb v3 - pc:Fix
>>>>> initialization of the ram_memory variable (to fix qemu 1.6 critical
>>>>> regression) ------------------------- vi Config.mk # Change upstream
>>>>> qemu to 1.6 QEMU_UPSTREAM_URL ?= git://git.qemu.org/qemu.git
>>>>> QEMU_UPSTREAM_REVISION ?= 1ee2daeb6448312d6d0e22175f5c1b9b01f8974c
>>>>> ---- ./configure --prefix=/usr --disable-xend
>>>>> --enable-qemu-traditional=no ------------------------- make debball
>>>>>
>>>>> Note: mainly tested with qemu 1.6
>>>>>
>>>>> -------------------------
>>>>> Issues solved from my previous test build report:
>>>>> -------------
>>>>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>>>>     tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>>>>>     works, while with qemu 1.5.1 doesn't (stops at the beginning, spice
>>>>>     client show only the lines of seabios version and machine UUID; qemu
>>>>>     log show nothing more that 2 gb test), while with 2 gb of ram works
>>>>>     also with qemu 1.5.1 (SOLVED WITH QEMU 1.6)
>>>>> -------------
>>>>> - Starting xendomain with "xl create" show some debug options:
>>>>>     Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY
>>>>>     ARRANGEMENT: Loader: 0000000000100000->000000000019eb68 Modules:
>>>>>         0000000000000000->0000000000000000 TOTAL:
>>>>>     0000000000000000->000000007f000000 ENTRY ADDRESS: 0000000000100000
>>>>>     xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES:
>>>>>     0x0000000000000200 2MB PAGES: 0x00000000000003f7 1GB PAGES:
>>>>>     0x0000000000000000
>>>>> [done].
>>>>> -------------
>>>>> - nested hvm was bugged: started test it on windows 7 pro 64 domU
>>>>> on qemu-xen,
>>>>>     on xpmode now works also integration features
>>>>> (disks,printers,clipboard sharing) and usb passthrough
>>>>> -------------------------
>>>> I didn't quite catch your meaning. Can you give more detail of what
>>>> kind of
>> nested cases you test and how many passed and how many fail?
>>> This is under the "issues solved" section, and it says "was bugged"
>>> (note the past tense) and "now works", so I took him to mean that it
>>> didn't work time he tested it, but it works now.  Is that correct,
>> *didn't work *last* time he tested it... gah..
> But the patch to fix xpmode wasn't applied. So I am a little confused that why it works now.
>
>>   -G
>
> Best regards,
> Yang
>

For now I tested only xpmode on windows 7 pro 64 bit domU and on latest 
my build is fully working; on my previous build integration features and 
usb passthrough (of xpmode) was not working, I suppose that your Nested 
VMX patches inserted on git 6 days ago fixed them (my dom0 cpu is Intel 
Xeon X3450).
For now I not have time for other tests on nested hvm, I have priority 
issues to which I can't find solution.
If you need specific tests/details just tell me that I'll do when I can.
For example my actual problem is the support of some resolutions (in 
particular 1366x768), where Frediano patch to qemu and vgabios of stdvga 
have problems, the only possible solution is probably the qxl vga but is 
blocked by missed SSE support on hvm domUs:
http://bugs.xenproject.org/xen/bug/11
For now there is nobody that can add full SSE support on hvm domUs and I 
do not have sufficient knowledge to do it.
Can you look about adding 32 byte operands on hvm domUs to full support 
sse/avx? Or if you cannot, get involved some other guys to help in this 
task please?

Thanks for any reply and sorry for my bad english

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.46-1 and all dependency packages for xen, spice and usb redirection.
Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1 and 
usbredir 0.6-2 compiled from debian unstable sources.
-------------------------
git clone git://xenbits.xen.org/xen.git (in this build commit is 
73f18583dd824f0e49f65149ef603600ce31b8ee)
-------------------------
Added some patches:
- tools-configure-qemu-for-spice-and-usbredir
- libxl-Add-spice-vdagent-support-for-upstream-qemu v3
- libxl: usb2 and usb3 controller support for upstream qemu v4
- tools-firmware-seabios-packaged
- tools: Improve make deb v3
- tools: remove or disable old/useless/unused/unmainted stuff (the whole 
series of 9 patches)
-------------------------
./configure --prefix=/usr --disable-xend
-------------------------
make debball

-------------------------
New issue:
- domU not start with qemu 1.5.1 and more that 2 gb of ram:
   tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it 
works,
   while with qemu 1.5.1 doesn't (stops at the beginning, spice client 
show only the lines of seabios version and machine UUID;
   qemu log show nothing more that 2 gb test), while with 2 gb of ram 
works also with qemu 1.5.1
-------------------------

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
   Workaround: fixed mac address
-------------
- Starting xendomain with "xl create" show some debug options:
   Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY ARRANGEMENT:
   Loader:        0000000000100000->000000000019eb68
   Modules:       0000000000000000->0000000000000000
   TOTAL:         0000000000000000->000000007f000000
   ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
   4KB PAGES: 0x0000000000000200
   2MB PAGES: 0x00000000000003f7
   1GB PAGES: 0x0000000000000000
[done].
I think it is would be better hiding them here
-------------
- on W7 pro 64 bit domU error in the begin of qemu log, while domU seem 
to work:
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 
= Invalid argument): Internal error
xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
-------------
- nested hvm was bugged: started test it on windows 7 pro 64 domU on 
qemu-xen,
   xpmode crashed on install without show error, no error on logs and 
havdetection works
   Now xpmode install and start correctly except integration features
   (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
-------------------------

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Il 12/08/2013 17:04, Fabio Fantoni ha scritto:
> Dom0:
> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 
> version 3.2.46-1 and all dependency packages for xen, spice and usb 
> redirection.
> Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1 and 
> usbredir 0.6-2 compiled from debian unstable sources.
> -------------------------
> git clone git://xenbits.xen.org/xen.git (in this build commit is 
> 73f18583dd824f0e49f65149ef603600ce31b8ee)
> -------------------------
> Added some patches:
> - tools-configure-qemu-for-spice-and-usbredir
> - libxl-Add-spice-vdagent-support-for-upstream-qemu v3
> - libxl: usb2 and usb3 controller support for upstream qemu v4
> - tools-firmware-seabios-packaged
> - tools: Improve make deb v3
> - tools: remove or disable old/useless/unused/unmainted stuff (the 
> whole series of 9 patches)
> -------------------------
> ./configure --prefix=/usr --disable-xend
> -------------------------
> make debball
>
> -------------------------
> New issue:
> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>   tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it 
> works,
>   while with qemu 1.5.1 doesn't (stops at the beginning, spice client 
> show only the lines of seabios version and machine UUID;
>   qemu log show nothing more that 2 gb test), while with 2 gb of ram 
> works also with qemu 1.5.1
> -------------------------

Added qemu-devel and debian maintainers to cc for this regression about 
upstream qemu.
If you need more details and tests tell me and I'll do/post them.

>
> -------------------------
> Old issue:
> - Network is not working after restore on Windows domU with qemu-xen 
> and gplpv
>   Workaround: fixed mac address
> -------------
> - Starting xendomain with "xl create" show some debug options:
>   Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY ARRANGEMENT:
>   Loader:        0000000000100000->000000000019eb68
>   Modules:       0000000000000000->0000000000000000
>   TOTAL:         0000000000000000->000000007f000000
>   ENTRY ADDRESS: 0000000000100000
> xc: info: PHYSICAL MEMORY ALLOCATION:
>   4KB PAGES: 0x0000000000000200
>   2MB PAGES: 0x00000000000003f7
>   1GB PAGES: 0x0000000000000000
> [done].
> I think it is would be better hiding them here
> -------------
> - on W7 pro 64 bit domU error in the begin of qemu log, while domU 
> seem to work:
> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed 
> (22 = Invalid argument): Internal error
> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
> -------------
> - nested hvm was bugged: started test it on windows 7 pro 64 domU on 
> qemu-xen,
>   xpmode crashed on install without show error, no error on logs and 
> havdetection works
>   Now xpmode install and start correctly except integration features
>   (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
> -------------------------

Re: Test report for xen-unstable and qemu-xen

[Laszlo Ersek]

CC'ing Gerd and the seabios list:

On 08/13/13 11:16, Fabio Fantoni wrote:
> Il 12/08/2013 17:04, Fabio Fantoni ha scritto:
>> Dom0:
>> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
>> version 3.2.46-1 and all dependency packages for xen, spice and usb
>> redirection.
>> Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1 and
>> usbredir 0.6-2 compiled from debian unstable sources.
>> -------------------------
>> git clone git://xenbits.xen.org/xen.git (in this build commit is
>> 73f18583dd824f0e49f65149ef603600ce31b8ee)
>> -------------------------
>> Added some patches:
>> - tools-configure-qemu-for-spice-and-usbredir
>> - libxl-Add-spice-vdagent-support-for-upstream-qemu v3
>> - libxl: usb2 and usb3 controller support for upstream qemu v4
>> - tools-firmware-seabios-packaged
>> - tools: Improve make deb v3
>> - tools: remove or disable old/useless/unused/unmainted stuff (the
>> whole series of 9 patches)
>> -------------------------
>> ./configure --prefix=/usr --disable-xend
>> -------------------------
>> make debball
>>
>> -------------------------
>> New issue:
>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>   tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>> works,
>>   while with qemu 1.5.1 doesn't (stops at the beginning, spice client
>> show only the lines of seabios version and machine UUID;
>>   qemu log show nothing more that 2 gb test), while with 2 gb of ram
>> works also with qemu 1.5.1
>> -------------------------
> 
> Added qemu-devel and debian maintainers to cc for this regression about
> upstream qemu.
> If you need more details and tests tell me and I'll do/post them.

As a superficial guess, this could be fixed by the seabios-1.7.3.1 release:

http://thread.gmane.org/gmane.comp.emulators.qemu/227536

http://code.coreboot.org/p/seabios/source/commit/2a9aeabdfb34374ecac25e7a8d21c9e368618cd4/

Laszlo

> 
>>
>> -------------------------
>> Old issue:
>> - Network is not working after restore on Windows domU with qemu-xen
>> and gplpv
>>   Workaround: fixed mac address
>> -------------
>> - Starting xendomain with "xl create" show some debug options:
>>   Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY ARRANGEMENT:
>>   Loader:        0000000000100000->000000000019eb68
>>   Modules:       0000000000000000->0000000000000000
>>   TOTAL:         0000000000000000->000000007f000000
>>   ENTRY ADDRESS: 0000000000100000
>> xc: info: PHYSICAL MEMORY ALLOCATION:
>>   4KB PAGES: 0x0000000000000200
>>   2MB PAGES: 0x00000000000003f7
>>   1GB PAGES: 0x0000000000000000
>> [done].
>> I think it is would be better hiding them here
>> -------------
>> - on W7 pro 64 bit domU error in the begin of qemu log, while domU
>> seem to work:
>> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed
>> (22 = Invalid argument): Internal error
>> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
>> -------------
>> - nested hvm was bugged: started test it on windows 7 pro 64 domU on
>> qemu-xen,
>>   xpmode crashed on install without show error, no error on logs and
>> havdetection works
>>   Now xpmode install and start correctly except integration features
>>   (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
>> -------------------------

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Il 13/08/2013 12:04, Laszlo Ersek ha scritto:
> CC'ing Gerd and the seabios list:
>
> On 08/13/13 11:16, Fabio Fantoni wrote:
>> Il 12/08/2013 17:04, Fabio Fantoni ha scritto:
>>> Dom0:
>>> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
>>> version 3.2.46-1 and all dependency packages for xen, spice and usb
>>> redirection.
>>> Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1 and
>>> usbredir 0.6-2 compiled from debian unstable sources.
>>> -------------------------
>>> git clone git://xenbits.xen.org/xen.git (in this build commit is
>>> 73f18583dd824f0e49f65149ef603600ce31b8ee)
>>> -------------------------
>>> Added some patches:
>>> - tools-configure-qemu-for-spice-and-usbredir
>>> - libxl-Add-spice-vdagent-support-for-upstream-qemu v3
>>> - libxl: usb2 and usb3 controller support for upstream qemu v4
>>> - tools-firmware-seabios-packaged
>>> - tools: Improve make deb v3
>>> - tools: remove or disable old/useless/unused/unmainted stuff (the
>>> whole series of 9 patches)
>>> -------------------------
>>> ./configure --prefix=/usr --disable-xend
>>> -------------------------
>>> make debball
>>>
>>> -------------------------
>>> New issue:
>>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>>    tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>>> works,
>>>    while with qemu 1.5.1 doesn't (stops at the beginning, spice client
>>> show only the lines of seabios version and machine UUID;
>>>    qemu log show nothing more that 2 gb test), while with 2 gb of ram
>>> works also with qemu 1.5.1
>>> -------------------------
>> Added qemu-devel and debian maintainers to cc for this regression about
>> upstream qemu.
>> If you need more details and tests tell me and I'll do/post them.
> As a superficial guess, this could be fixed by the seabios-1.7.3.1 release:
>
> http://thread.gmane.org/gmane.comp.emulators.qemu/227536
>
> http://code.coreboot.org/p/seabios/source/commit/2a9aeabdfb34374ecac25e7a8d21c9e368618cd4/
>
> Laszlo

Thanks for reply, i did fast test adding this patch that you linked:
http://code.coreboot.org/p/seabios/source/commit/2a9aeabdfb34374ecac25e7a8d21c9e368618cd4/
Same result, the problem remains, should I test full seabios 1.7.3.1?

>
>>> -------------------------
>>> Old issue:
>>> - Network is not working after restore on Windows domU with qemu-xen
>>> and gplpv
>>>    Workaround: fixed mac address
>>> -------------
>>> - Starting xendomain with "xl create" show some debug options:
>>>    Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY ARRANGEMENT:
>>>    Loader:        0000000000100000->000000000019eb68
>>>    Modules:       0000000000000000->0000000000000000
>>>    TOTAL:         0000000000000000->000000007f000000
>>>    ENTRY ADDRESS: 0000000000100000
>>> xc: info: PHYSICAL MEMORY ALLOCATION:
>>>    4KB PAGES: 0x0000000000000200
>>>    2MB PAGES: 0x00000000000003f7
>>>    1GB PAGES: 0x0000000000000000
>>> [done].
>>> I think it is would be better hiding them here
>>> -------------
>>> - on W7 pro 64 bit domU error in the begin of qemu log, while domU
>>> seem to work:
>>> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed
>>> (22 = Invalid argument): Internal error
>>> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
>>> -------------
>>> - nested hvm was bugged: started test it on windows 7 pro 64 domU on
>>> qemu-xen,
>>>    xpmode crashed on install without show error, no error on logs and
>>> havdetection works
>>>    Now xpmode install and start correctly except integration features
>>>    (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
>>> -------------------------

Re: Test report for xen-unstable and qemu-xen

[Laszlo Ersek]

On 08/13/13 12:33, Fabio Fantoni wrote:
> Il 13/08/2013 12:04, Laszlo Ersek ha scritto:
>> CC'ing Gerd and the seabios list:
>>
>> On 08/13/13 11:16, Fabio Fantoni wrote:
>>> Il 12/08/2013 17:04, Fabio Fantoni ha scritto:

>>>> New issue:
>>>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>>>    tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>>>> works,
>>>>    while with qemu 1.5.1 doesn't (stops at the beginning, spice client
>>>> show only the lines of seabios version and machine UUID;
>>>>    qemu log show nothing more that 2 gb test), while with 2 gb of ram
>>>> works also with qemu 1.5.1
>>>> -------------------------
>>> Added qemu-devel and debian maintainers to cc for this regression about
>>> upstream qemu.
>>> If you need more details and tests tell me and I'll do/post them.
>> As a superficial guess, this could be fixed by the seabios-1.7.3.1
>> release:
>>
>> http://thread.gmane.org/gmane.comp.emulators.qemu/227536
>>
>> http://code.coreboot.org/p/seabios/source/commit/2a9aeabdfb34374ecac25e7a8d21c9e368618cd4/
>>
>>
>> Laszlo
> 
> Thanks for reply, i did fast test adding this patch that you linked:
> http://code.coreboot.org/p/seabios/source/commit/2a9aeabdfb34374ecac25e7a8d21c9e368618cd4/
> 
> Same result, the problem remains, should I test full seabios 1.7.3.1?

No idea, it was just a random shot, sorry... You're probably down to
bisecting qemu :(

Laszlo

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Il 13/08/2013 13:09, Laszlo Ersek ha scritto:
> On 08/13/13 12:33, Fabio Fantoni wrote:
>> Il 13/08/2013 12:04, Laszlo Ersek ha scritto:
>>> CC'ing Gerd and the seabios list:
>>>
>>> On 08/13/13 11:16, Fabio Fantoni wrote:
>>>> Il 12/08/2013 17:04, Fabio Fantoni ha scritto:
>>>>> New issue:
>>>>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>>>>     tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>>>>> works,
>>>>>     while with qemu 1.5.1 doesn't (stops at the beginning, spice client
>>>>> show only the lines of seabios version and machine UUID;
>>>>>     qemu log show nothing more that 2 gb test), while with 2 gb of ram
>>>>> works also with qemu 1.5.1
>>>>> -------------------------
>>>> Added qemu-devel and debian maintainers to cc for this regression about
>>>> upstream qemu.
>>>> If you need more details and tests tell me and I'll do/post them.
>>> As a superficial guess, this could be fixed by the seabios-1.7.3.1
>>> release:
>>>
>>> http://thread.gmane.org/gmane.comp.emulators.qemu/227536
>>>
>>> http://code.coreboot.org/p/seabios/source/commit/2a9aeabdfb34374ecac25e7a8d21c9e368618cd4/
>>>
>>>
>>> Laszlo
>> Thanks for reply, i did fast test adding this patch that you linked:
>> http://code.coreboot.org/p/seabios/source/commit/2a9aeabdfb34374ecac25e7a8d21c9e368618cd4/
>>
>> Same result, the problem remains, should I test full seabios 1.7.3.1?
> No idea, it was just a random shot, sorry... You're probably down to
> bisecting qemu :(
>
> Laszlo

I did another test disabling the usb controller: it didn't find any 
bootable disk and tried to boot with pxe. I also tried F12 and it 
reported an hard-disk size of 0 MB.
Configuration is correct because if I change the ram size to 2 GB 
instead of 4, it starts correctly.
No additional information from qemu log.
I tried also seabios 1.7.2.2 and master from git, both with same result.

Re: [Qemu-devel] Test report for xen-unstable and qemu-xen

[Kevin O'Connor]

On Tue, Aug 13, 2013 at 03:26:43PM +0200, Fabio Fantoni wrote:
> Il 13/08/2013 13:09, Laszlo Ersek ha scritto:
> >On 08/13/13 12:33, Fabio Fantoni wrote:
> >>Il 13/08/2013 12:04, Laszlo Ersek ha scritto:
> >>>On 08/13/13 11:16, Fabio Fantoni wrote:
> >>>>Il 12/08/2013 17:04, Fabio Fantoni ha scritto:
> >>>>>New issue:
> >>>>>- domU not start with qemu 1.5.1 and more that 2 gb of ram:
> >>>>>    tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
> >>>>>works,
> >>>>>    while with qemu 1.5.1 doesn't (stops at the beginning, spice client
> >>>>>show only the lines of seabios version and machine UUID;
> >>>>>    qemu log show nothing more that 2 gb test), while with 2 gb of ram
> >>>>>works also with qemu 1.5.1
> >>>>>-------------------------
[...]
> I did another test disabling the usb controller: it didn't find any
> bootable disk and tried to boot with pxe. I also tried F12 and it
> reported an hard-disk size of 0 MB.
> Configuration is correct because if I change the ram size to 2 GB
> instead of 4, it starts correctly.
> No additional information from qemu log.
> I tried also seabios 1.7.2.2 and master from git, both with same result.

It's not clear to me if this is a QEMU issue or SeaBIOS issue.  Can
you arrange to run qemu with the following added to the command line:

-chardev stdio,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios

and post the full log from a successful (2G) boot as well as the
unsuccessful (4G) boot?

-Kevin

Re: [Qemu-devel] Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Il 14/08/2013 01:58, Kevin O'Connor ha scritto:
> On Tue, Aug 13, 2013 at 03:26:43PM +0200, Fabio Fantoni wrote:
>> Il 13/08/2013 13:09, Laszlo Ersek ha scritto:
>>> On 08/13/13 12:33, Fabio Fantoni wrote:
>>>> Il 13/08/2013 12:04, Laszlo Ersek ha scritto:
>>>>> On 08/13/13 11:16, Fabio Fantoni wrote:
>>>>>> Il 12/08/2013 17:04, Fabio Fantoni ha scritto:
>>>>>>> New issue:
>>>>>>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>>>>>>     tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>>>>>>> works,
>>>>>>>     while with qemu 1.5.1 doesn't (stops at the beginning, spice client
>>>>>>> show only the lines of seabios version and machine UUID;
>>>>>>>     qemu log show nothing more that 2 gb test), while with 2 gb of ram
>>>>>>> works also with qemu 1.5.1
>>>>>>> -------------------------
> [...]
>> I did another test disabling the usb controller: it didn't find any
>> bootable disk and tried to boot with pxe. I also tried F12 and it
>> reported an hard-disk size of 0 MB.
>> Configuration is correct because if I change the ram size to 2 GB
>> instead of 4, it starts correctly.
>> No additional information from qemu log.
>> I tried also seabios 1.7.2.2 and master from git, both with same result.
> It's not clear to me if this is a QEMU issue or SeaBIOS issue.  Can
> you arrange to run qemu with the following added to the command line:
>
> -chardev stdio,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios
>
> and post the full log from a successful (2G) boot as well as the
> unsuccessful (4G) boot?
>
> -Kevin

Tried qemu 1.6.0-rc3, hvm domU does not start in any case because qemu 
crashes on start

------------------------------------
xl create /etc/xen/W7.cfg
------------------------------------
Parsing config from /etc/xen/W7.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
   Loader:        0000000000100000->000000000019ee88
   Modules:       0000000000000000->0000000000000000
   TOTAL:         0000000000000000->000000007f000000
   ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
   4KB PAGES: 0x0000000000000200
   2MB PAGES: 0x00000000000003f7
   1GB PAGES: 0x0000000000000000
libxl: error: libxl_dm.c:1313:device_model_spawn_outcome: domain 1 
device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1079:domcreate_devmodel_started: device 
model did not start: -3
libxl: error: libxl_dm.c:1344:libxl__destroy_device_model: Device Model 
already exited
------------------------------------

------------------------------------
/var/log/xen/qemu-dm-W7.log
------------------------------------
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 
= Invalid argument): Internal error
xen be: qdisk-768: xc_gnttab_set_max_grants failed: Invalid argument
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 
= Invalid argument): Internal error
xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
------------------------------------

Tried with qemu 1.4.2 and it works also with 4 gb of ram.
This ram regression seems to be introduced with qemu 1.5, and there is 
another regression more critical with qemu 1.6.

Tried to add seabios debug options to domU xl configuration file...

device_model_args=["-chardev 
stdio,id=seabios","-device","isa-debugcon,iobase=0x402,chardev=seabios"]

But it doesn't boot

/var/log/xen/qemu-dm-W7.log
qemu-system-x86_64: -chardev stdio,id=seabios: invalid option

Re: [Qemu-devel] Test report for xen-unstable and qemu-xen

[Laszlo Ersek]

On 08/14/13 11:19, Fabio Fantoni wrote:

> Tried with qemu 1.4.2 and it works also with 4 gb of ram.
> This ram regression seems to be introduced with qemu 1.5, and there is
> another regression more critical with qemu 1.6.

Can you save qemu's stderr for the 1.5->1.6 regression?

> Tried to add seabios debug options to domU xl configuration file...
> 
> device_model_args=["-chardev
> stdio,id=seabios","-device","isa-debugcon,iobase=0x402,chardev=seabios"]
> 
> But it doesn't boot
> 
> /var/log/xen/qemu-dm-W7.log
> qemu-system-x86_64: -chardev stdio,id=seabios: invalid option

That's probably because you forgot to break up this option into
separate python list entries:

device_model_args=["-chardev", "stdio,id=seabios", "-device", "isa-debugcon,iobase=0x402,chardev=seabios"]

Laszlo

Re: [Qemu-devel] Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Il 14/08/2013 11:56, Laszlo Ersek ha scritto:
> On 08/14/13 11:19, Fabio Fantoni wrote:
>
>> Tried with qemu 1.4.2 and it works also with 4 gb of ram.
>> This ram regression seems to be introduced with qemu 1.5, and there is
>> another regression more critical with qemu 1.6.
> Can you save qemu's stderr for the 1.5->1.6 regression?
>
>> Tried to add seabios debug options to domU xl configuration file...
>>
>> device_model_args=["-chardev
>> stdio,id=seabios","-device","isa-debugcon,iobase=0x402,chardev=seabios"]
>>
>> But it doesn't boot
>>
>> /var/log/xen/qemu-dm-W7.log
>> qemu-system-x86_64: -chardev stdio,id=seabios: invalid option
> That's probably because you forgot to break up this option into
> separate python list entries:
>
> device_model_args=["-chardev", "stdio,id=seabios", "-device", "isa-debugcon,iobase=0x402,chardev=seabios"]
>
> Laszlo
>

Thanks for your reply and sorry for my very stupid error.
I retried with the correct parameters and on both cases (2 gb of ram 
working and 4gb of ram not working) I get only this one more line on 
qemu log:
Start bios (version debian/1.7.3-1-1-ga76c6f1-dirty-20130813_122010-test)

The probable cause is that on xen, seabios doesn't generate some tables 
but it takes the static ones from hvmloader.

Re: [Qemu-devel] Test report for xen-unstable and qemu-xen

[Kevin O'Connor]

On Wed, Aug 14, 2013 at 12:54:06PM +0200, Fabio Fantoni wrote:
> I retried with the correct parameters and on both cases (2 gb of ram
> working and 4gb of ram not working) I get only this one more line on
> qemu log:
> Start bios (version debian/1.7.3-1-1-ga76c6f1-dirty-20130813_122010-test)

Xen moves the debug port to 0xe9 - can you try again with
iobase=0xe9.  (There should be some way to tell xen to log 0xe9 on its
own, but I'm not familiar with xen.)

-Kevin

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Il 14/08/2013 14:29, Kevin O'Connor ha scritto:
> On Wed, Aug 14, 2013 at 12:54:06PM +0200, Fabio Fantoni wrote:
>> I retried with the correct parameters and on both cases (2 gb of ram
>> working and 4gb of ram not working) I get only this one more line on
>> qemu log:
>> Start bios (version debian/1.7.3-1-1-ga76c6f1-dirty-20130813_122010-test)
> Xen moves the debug port to 0xe9 - can you try again with
> iobase=0xe9.  (There should be some way to tell xen to log 0xe9 on its
> own, but I'm not familiar with xen.)
>
> -Kevin

Thanks for reply.
I tried with this:
device_model_args=["-chardev","stdio,id=seabios","-device","isa-debugcon,iobase=0xe9,chardev=seabios"]

No more lines in qemu log are written and also "Start bios" line does 
not appair any more.

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.46-1 and all dependency packages for xen, spice and usb redirection.
Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1 and 
usbredir 0.6-2 compiled from debian unstable sources.
-------------------------
/etc/modules
------------
loop max_loop=64
-------------------------
git clone git://xenbits.xen.org/xen.git (in this build commit is 
6072b7c808043b6886c33f896e06fc32ee28346e)
-------------------------
Added some patches:
- tools-configure-qemu-for-spice-and-usbredir
- libxl-Add-spice-vdagent-support-for-upstream-qemu v3
- libxl: usb2 and usb3 controller support for upstream qemu v4
- tools-firmware-seabios-packaged
- tools: Improve make deb v3
-------------------------
./configure --prefix=/usr
-------------------------
make debball

Note:
I tested both upstream qemu of xen git and debian unstable packages.
On this test I removed blktap2 (after see disabled for next version of 
xen debian package), no regression found with qdisk and performance 
significantly improved. One benchmark result on windows 7 64 bit domU on 
attachment.

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
   Workaround: fixed mac address
-------------
- Starting xendomain with "xl create" show some debug options:
   Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY ARRANGEMENT:
   Loader:        0000000000100000->000000000019eb68
   Modules:       0000000000000000->0000000000000000
   TOTAL:         0000000000000000->000000007f000000
   ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
   4KB PAGES: 0x0000000000000200
   2MB PAGES: 0x00000000000003f7
   1GB PAGES: 0x0000000000000000
[done].
I think it is would be better hiding them here
-------------
- on W7 pro 64 bit domU error in the begin of qemu log, while domU seem 
to work:
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 
= Invalid argument): Internal error
xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
-------------
- nested hvm was bugged: started test it on windows 7 pro 64 domU on 
qemu-xen,
   xpmode crashed on install without show error, no error on logs and 
havdetection works
   Now xpmode install and start correctly except integration features
   (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
-------------------------

[-- Attachment #2: blktap2_vs_qdisk.JPG --]
[-- Type: image/jpeg, Size: 149719 bytes --]

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

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

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

[-- Attachment #1.1: Type: text/plain, Size: 4518 bytes --]

Il 31/07/2013 19:54, jacek burghardt ha scritto:
> I wonder if you could share pachest that you listed in your test.

I posted all patches applied in my test.

 >     - tools-configure-qemu-for-spice-and-usbredir

Posted one year or more ago as first of 3 methods to add spice on 
upsteam qemu compile but rejected because the latest stable version of 
major distribution all haven't spice prerequisites, I recently ask if is 
possible to reconsider it, but no reply for now:
http://lists.xen.org/archives/html/xen-devel/2013-07/msg02521.html

 >     - libxl-Add-spice-vdagent-support-for-upstream-qemu v3

Awaiting reply...
http://lists.xen.org/archives/html/xen-devel/2013-07/msg02153.html

 >     - libxl: usb2 and usb3 controller support for upstream qemu v4

Awaiting reply...
http://lists.xen.org/archives/html/xen-devel/2013-07/msg01101.html

 >     - tools-firmware-seabios-packaged

Taken from debian package but must be done with better configure patch.
Awaiting Ian news about that, probably he has already done a draft for 
xen configure and also also upstream qemu.

 >     - tools: Improve make deb v3

Posted last year but rejected.


There is also another patch about qxl support and I waiting about adding 
of SSE support on hvm domU for have it full working.

> Did you test with large memory assigment ?
1 and 2 gb of ram on my test domUs.
FWIK the large memory assignment is problem only with pci passthrough 
(I'm not using that by now).
For now I use ram > 2gb only with rare pv domUs in production, if 
necessary I'll test large memory also on spare system and also with hvm 
domUs.
>
>
> On Wed, Jul 31, 2013 at 9:15 AM, Fabio Fantoni <fabio.fantoni@m2r.biz 
> <mailto:fabio.fantoni@m2r.biz>> wrote:
>
>     Dom0:
>     Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
>     version 3.2.46-1 and all dependency packages for xen, spice and
>     usb redirection.
>     Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1
>     and usbredir 0.6-2 compiled from debian unstable sources.
>     -------------------------
>     /etc/modules
>     ------------
>     loop max_loop=64
>     -------------------------
>     git clone git://xenbits.xen.org/xen.git
>     <http://xenbits.xen.org/xen.git> (in this build commit is
>     6072b7c808043b6886c33f896e06fc32ee28346e)
>     -------------------------
>     Added some patches:
>

>     -------------------------
>     ./configure --prefix=/usr
>     -------------------------
>     make debball
>
>     Note:
>     I tested both upstream qemu of xen git and debian unstable packages.
>     On this test I removed blktap2 (after see disabled for next
>     version of xen debian package), no regression found with qdisk and
>     performance significantly improved. One benchmark result on
>     windows 7 64 bit domU on attachment.
>
>     -------------------------
>     Old issue:
>     - Network is not working after restore on Windows domU with
>     qemu-xen and gplpv
>       Workaround: fixed mac address
>     -------------
>     - Starting xendomain with "xl create" show some debug options:
>       Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY
>     ARRANGEMENT:
>       Loader:        0000000000100000->000000000019eb68
>       Modules:       0000000000000000->0000000000000000
>       TOTAL:         0000000000000000->000000007f000000
>       ENTRY ADDRESS: 0000000000100000
>     xc: info: PHYSICAL MEMORY ALLOCATION:
>       4KB PAGES: 0x0000000000000200
>       2MB PAGES: 0x00000000000003f7
>       1GB PAGES: 0x0000000000000000
>     [done].
>     I think it is would be better hiding them here
>     -------------
>     - on W7 pro 64 bit domU error in the begin of qemu log, while domU
>     seem to work:
>     xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS
>     failed (22 = Invalid argument): Internal error
>     xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
>     -------------
>     - nested hvm was bugged: started test it on windows 7 pro 64 domU
>     on qemu-xen,
>       xpmode crashed on install without show error, no error on logs
>     and havdetection works
>       Now xpmode install and start correctly except integration features
>       (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
>     -------------------------
>
>     _______________________________________________
>     Xen-devel mailing list
>     Xen-devel@lists.xen.org <mailto:Xen-devel@lists.xen.org>
>     http://lists.xen.org/xen-devel
>
>


[-- Attachment #1.2: Type: text/html, Size: 7755 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

[-- Attachment #1.1: Type: text/plain, Size: 4902 bytes --]

Il 01/08/2013 11:01, Fabio Fantoni ha scritto:
> Il 31/07/2013 19:54, jacek burghardt ha scritto:
>> I wonder if you could share pachest that you listed in your test.
>
> I posted all patches applied in my test.
>
> >     - tools-configure-qemu-for-spice-and-usbredir
>
> Posted one year or more ago as first of 3 methods to add spice on 
> upsteam qemu compile but rejected because the latest stable version of 
> major distribution all haven't spice prerequisites, I recently ask if 
> is possible to reconsider it, but no reply for now:
> http://lists.xen.org/archives/html/xen-devel/2013-07/msg02521.html
>
> >     - libxl-Add-spice-vdagent-support-for-upstream-qemu v3
>
> Awaiting reply...
> http://lists.xen.org/archives/html/xen-devel/2013-07/msg02153.html
>
> >     - libxl: usb2 and usb3 controller support for upstream qemu v4
>
> Awaiting reply...
> http://lists.xen.org/archives/html/xen-devel/2013-07/msg01101.html
>
> >     - tools-firmware-seabios-packaged
>
> Taken from debian package but must be done with better configure patch.
> Awaiting Ian news about that, probably he has already done a draft for 
> xen configure and also also upstream qemu.
>
> >     - tools: Improve make deb v3
>
> Posted last year but rejected.
>
>
> There is also another patch about qxl support and I waiting about 
> adding of SSE support on hvm domU for have it full working.
>
>> Did you test with large memory assigment ?
> 1 and 2 gb of ram on my test domUs.
> FWIK the large memory assignment is problem only with pci passthrough 
> (I'm not using that by now).
> For now I use ram > 2gb only with rare pv domUs in production, if 
> necessary I'll test large memory also on spare system and also with 
> hvm domUs.

Tried fast test on w7 64 bit domU with 4 gb of ram, with built-in qemu 
1.3 it works, while with qemu 1.5.1 doesn't (on start it does not see 
the virtual disk, while with 2 gb of ram works)

>>
>>
>> On Wed, Jul 31, 2013 at 9:15 AM, Fabio Fantoni <fabio.fantoni@m2r.biz 
>> <mailto:fabio.fantoni@m2r.biz>> wrote:
>>
>>     Dom0:
>>     Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
>>     version 3.2.46-1 and all dependency packages for xen, spice and
>>     usb redirection.
>>     Seabios 1.7.3-1, qemu 1.5.0+dfsg-5 (1.5.1), spice 0.12.4-0nocelt1
>>     and usbredir 0.6-2 compiled from debian unstable sources.
>>     -------------------------
>>     /etc/modules
>>     ------------
>>     loop max_loop=64
>>     -------------------------
>>     git clone git://xenbits.xen.org/xen.git
>>     <http://xenbits.xen.org/xen.git> (in this build commit is
>>     6072b7c808043b6886c33f896e06fc32ee28346e)
>>     -------------------------
>>     Added some patches:
>>
>
>>     -------------------------
>>     ./configure --prefix=/usr
>>     -------------------------
>>     make debball
>>
>>     Note:
>>     I tested both upstream qemu of xen git and debian unstable packages.
>>     On this test I removed blktap2 (after see disabled for next
>>     version of xen debian package), no regression found with qdisk
>>     and performance significantly improved. One benchmark result on
>>     windows 7 64 bit domU on attachment.
>>
>>     -------------------------
>>     Old issue:
>>     - Network is not working after restore on Windows domU with
>>     qemu-xen and gplpv
>>       Workaround: fixed mac address
>>     -------------
>>     - Starting xendomain with "xl create" show some debug options:
>>       Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY
>>     ARRANGEMENT:
>>       Loader:        0000000000100000->000000000019eb68
>>       Modules:       0000000000000000->0000000000000000
>>       TOTAL:         0000000000000000->000000007f000000
>>       ENTRY ADDRESS: 0000000000100000
>>     xc: info: PHYSICAL MEMORY ALLOCATION:
>>       4KB PAGES: 0x0000000000000200
>>       2MB PAGES: 0x00000000000003f7
>>       1GB PAGES: 0x0000000000000000
>>     [done].
>>     I think it is would be better hiding them here
>>     -------------
>>     - on W7 pro 64 bit domU error in the begin of qemu log, while
>>     domU seem to work:
>>     xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS
>>     failed (22 = Invalid argument): Internal error
>>     xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
>>     -------------
>>     - nested hvm was bugged: started test it on windows 7 pro 64 domU
>>     on qemu-xen,
>>       xpmode crashed on install without show error, no error on logs
>>     and havdetection works
>>       Now xpmode install and start correctly except integration features
>>       (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
>>     -------------------------
>>
>>     _______________________________________________
>>     Xen-devel mailing list
>>     Xen-devel@lists.xen.org <mailto:Xen-devel@lists.xen.org>
>>     http://lists.xen.org/xen-devel
>>
>>
>


[-- Attachment #1.2: Type: text/html, Size: 8762 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for 
xen, spice and usb redirection.
Seabios 1.7.2-3 and latest spice and usbredir compiled from debian 
unstable sources.
-------------------------
/etc/modules
------------
loop max_loop=64
xenfs
xen-evtchn
blktap
-------------------------
git clone git://xenbits.xen.org/xen.git (in this build commit is 
bcb49301c21ed69b4e8c164fa215efe9db30621a)
-------------------------
Added some patches:
- tools-configure-qemu-for-spice-and-usbredir
- libxl-Add-spice-vdagent-support-for-upstream-qemu
- tools-firmware-seabios-packaged
- tools: Improve make deb
- vgabios-stdvga.bin custom build from Frediano
- qemu-xen change for support other resolutions:
hw/vga.c: # from Frediano patch
     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
-------------------------
./configure --prefix=/usr
-------------------------
make debball

-------------------------
Issues solved from my previous test build report:
-------------
- nested hvm was bugged:

   Before: started test it on windows 7 pro 64 domU on qemu-xen,
   xpmode crashed on install without show error, no error on logs and 
havdetection works.

   Now xpmode installs and starts correctly except integration features
   (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
-------------------------

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
   Workaround: fixed mac address
-------------
- Starting xendomain with "xl create" show some debug options:
   Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY ARRANGEMENT:
   Loader:        0000000000100000->000000000019eb68
   Modules:       0000000000000000->0000000000000000
   TOTAL:         0000000000000000->000000007f000000
   ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
   4KB PAGES: 0x0000000000000200
   2MB PAGES: 0x00000000000003f7
   1GB PAGES: 0x0000000000000000
[done].
I think it is would be better hiding them here
-------------
- on W7 pro 64 bit domU error in the begin of qemu log, while domU seem 
to work:
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 
= Invalid argument): Internal error
xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
-------------------------

Re: Test report for xen-unstable and qemu-xen

[Stefano Stabellini]

On Mon, 1 Jul 2013, Fabio Fantoni wrote:
> - on W7 pro 64 bit domU error in the begin of qemu log, while domU seem to
> work:
> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 =
> Invalid argument): Internal error
> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
> -------------------------

This is an harmless message if you are running a pvops kernel, it only
indicates a problem if you are running on a SUSE kernel.

Jan, could we figure out from the return code whether it was a real
problem and only print an error in that case?
I think that users might get confused otherwise.

Re: Test report for xen-unstable and qemu-xen

[Jan Beulich]

>>> On 01.07.13 at 15:50, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> On Mon, 1 Jul 2013, Fabio Fantoni wrote:
>> - on W7 pro 64 bit domU error in the begin of qemu log, while domU seem to
>> work:
>> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 =
>> Invalid argument): Internal error
>> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
>> -------------------------
> 
> This is an harmless message if you are running a pvops kernel, it only
> indicates a problem if you are running on a SUSE kernel.
> 
> Jan, could we figure out from the return code whether it was a real
> problem and only print an error in that case?
> I think that users might get confused otherwise.

This is supposed to happen already, by special casing the ENOTTY
errno value. Question is why EINVAL is being seen here instead.

Jan

Re: Test report for xen-unstable and qemu-xen

[Matthew Daley]

On Tue, Jul 2, 2013 at 2:07 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 01.07.13 at 15:50, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
>> On Mon, 1 Jul 2013, Fabio Fantoni wrote:
>>> - on W7 pro 64 bit domU error in the begin of qemu log, while domU seem to
>>> work:
>>> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 =
>>> Invalid argument): Internal error
>>> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
>>> -------------------------
>>
>> This is an harmless message if you are running a pvops kernel, it only
>> indicates a problem if you are running on a SUSE kernel.
>>
>> Jan, could we figure out from the return code whether it was a real
>> problem and only print an error in that case?
>> I think that users might get confused otherwise.
>
> This is supposed to happen already, by special casing the ENOTTY
> errno value. Question is why EINVAL is being seen here instead.

Probably because
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/ioctl.c?id=07d106d0a33d6063d2061305903deb02489eba20
only went in time for Linux 3.3 (it's not in my Debian unstable, for example).

I personally use the patch below to keep a clean log (I see this
message too), but I'm sure it would be NAK'd for continuing the
ENOTTY/EINVAL confusion and making legitmate EINVALs disappear.
Perhaps instead the message could be softened from an error to a
warning?

- Matthew


>From 8a47313339e4778e0cb282ad5b60da1449c8da34 Mon Sep 17 00:00:00 2001
From: Matthew Daley <mattjd@gmail.com>
Date: Thu, 23 May 2013 18:26:36 +1200
Subject: [PATCH] libxc: actually ignore missing ioctl in
 linux_gnttab_set_max_grants on Linux <= 3.2

Linux 3.2 and earlier (incorrectly) convert the ENOIOCTLCMD returned by
gntdev's ioctl handler to EINVAL instead of ENOTTY.

Handle this in linux_gnttab_set_max_grants, otherwise false negatives
can lead to misleading error messages, like one logged by qemu when a
qemu-backed xen virtual disk is created.

Signed-off-by: Matthew Daley <mattjd@gmail.com>
---
 tools/libxc/xc_linux_osdep.c |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tools/libxc/xc_linux_osdep.c b/tools/libxc/xc_linux_osdep.c
index 73860a2..3f85054 100644
--- a/tools/libxc/xc_linux_osdep.c
+++ b/tools/libxc/xc_linux_osdep.c
@@ -573,8 +573,10 @@ static int linux_gnttab_set_max_grants(xc_gnttab
*xch, xc_osdep_handle h,
         /*
          * Newer (e.g. pv-ops) kernels don't implement this IOCTL,
          * so ignore the resulting specific failure.
+         * gntdev in <= 3.2 kernels returns EINVAL instead of ENOTTY on
+         * unknown IOCTLs.
          */
-        if (errno == ENOTTY)
+        if (errno == ENOTTY || errno == EINVAL)
             rc = 0;
         else
             PERROR("linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed");
--
1.7.10.4

Re: Test report for xen-unstable and qemu-xen

[Jan Beulich]

>>> On 03.07.13 at 10:25, Matthew Daley <mattjd@gmail.com> wrote:
> On Tue, Jul 2, 2013 at 2:07 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>>> On 01.07.13 at 15:50, Stefano Stabellini <stefano.stabellini@eu.citrix.com> 
> wrote:
>>> On Mon, 1 Jul 2013, Fabio Fantoni wrote:
>>>> - on W7 pro 64 bit domU error in the begin of qemu log, while domU seem to
>>>> work:
>>>> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 =
>>>> Invalid argument): Internal error
>>>> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
>>>> -------------------------
>>>
>>> This is an harmless message if you are running a pvops kernel, it only
>>> indicates a problem if you are running on a SUSE kernel.
>>>
>>> Jan, could we figure out from the return code whether it was a real
>>> problem and only print an error in that case?
>>> I think that users might get confused otherwise.
>>
>> This is supposed to happen already, by special casing the ENOTTY
>> errno value. Question is why EINVAL is being seen here instead.
> 
> Probably because
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/io 
> ctl.c?id=07d106d0a33d6063d2061305903deb02489eba20
> only went in time for Linux 3.3 (it's not in my Debian unstable, for 
> example).

Very much so, and kernels should be backporting this if upstream
didn't.

> I personally use the patch below to keep a clean log (I see this
> message too), but I'm sure it would be NAK'd for continuing the
> ENOTTY/EINVAL confusion and making legitmate EINVALs disappear.
> Perhaps instead the message could be softened from an error to a
> warning?

Making this a warning may be acceptable, but I'm not eager to work
around kernel bugs like this (and in effect risk hiding _real_ errors,
which ought to not be logged as just a warning).

Jan

Re: Test report for xen-unstable and qemu-xen

[Stefano Stabellini]

On Wed, 3 Jul 2013, Jan Beulich wrote:
> >>> On 03.07.13 at 10:25, Matthew Daley <mattjd@gmail.com> wrote:
> > On Tue, Jul 2, 2013 at 2:07 AM, Jan Beulich <JBeulich@suse.com> wrote:
> >>>>> On 01.07.13 at 15:50, Stefano Stabellini <stefano.stabellini@eu.citrix.com> 
> > wrote:
> >>> On Mon, 1 Jul 2013, Fabio Fantoni wrote:
> >>>> - on W7 pro 64 bit domU error in the begin of qemu log, while domU seem to
> >>>> work:
> >>>> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 =
> >>>> Invalid argument): Internal error
> >>>> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
> >>>> -------------------------
> >>>
> >>> This is an harmless message if you are running a pvops kernel, it only
> >>> indicates a problem if you are running on a SUSE kernel.
> >>>
> >>> Jan, could we figure out from the return code whether it was a real
> >>> problem and only print an error in that case?
> >>> I think that users might get confused otherwise.
> >>
> >> This is supposed to happen already, by special casing the ENOTTY
> >> errno value. Question is why EINVAL is being seen here instead.
> > 
> > Probably because
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/io 
> > ctl.c?id=07d106d0a33d6063d2061305903deb02489eba20
> > only went in time for Linux 3.3 (it's not in my Debian unstable, for 
> > example).
> 
> Very much so, and kernels should be backporting this if upstream
> didn't.

Did anybody ask for a backport? It doesn't look like the patch was sent
to stable.

Re: Test report for xen-unstable and qemu-xen

[Ren, Yongjie]

[-- Attachment #1: Type: text/plain, Size: 3066 bytes --]

> -----Original Message-----
> From: xen-devel-bounces@lists.xen.org
> [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Fabio Fantoni
> Sent: Monday, July 01, 2013 9:20 PM
> To: xen-devel; Stefano Stabellini; Ian Campbell; Ian Jackson; Xu, Dongxiao;
> Jan Beulich
> Subject: [Xen-devel] Test report for xen-unstable and qemu-xen
> 
> Dom0:
> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
> version
> 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for
> xen, spice and usb redirection.
> Seabios 1.7.2-3 and latest spice and usbredir compiled from debian
> unstable sources.
> -------------------------
> /etc/modules
> ------------
> loop max_loop=64
> xenfs
> xen-evtchn
> blktap
> -------------------------
> git clone git://xenbits.xen.org/xen.git (in this build commit is
> bcb49301c21ed69b4e8c164fa215efe9db30621a)
> -------------------------
> Added some patches:
> - tools-configure-qemu-for-spice-and-usbredir
> - libxl-Add-spice-vdagent-support-for-upstream-qemu
> - tools-firmware-seabios-packaged
> - tools: Improve make deb
> - vgabios-stdvga.bin custom build from Frediano
> - qemu-xen change for support other resolutions:
> hw/vga.c: # from Frediano patch
>      - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
>      + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
> -------------------------
> ./configure --prefix=/usr
> -------------------------
> make debball
> 
> -------------------------
> Issues solved from my previous test build report:
> -------------
> - nested hvm was bugged:
> 
>    Before: started test it on windows 7 pro 64 domU on qemu-xen,
>    xpmode crashed on install without show error, no error on logs and
> havdetection works.
> 
>    Now xpmode installs and starts correctly except integration features
>    (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
> -------------------------
> 
Hi Fabio,
I'm also testing Win7 XP mode in nested VMX environment, but I met some
problems. In the Windows 7 HVM guest, a tool from Microsoft showed
hardware-assisted virtualization is supported, but XP mode showed "hardware-
assisted virtualization is disabled" and it refused to boot XP.
(see the attached 2 pictures to get the two conflicting messages..)

I followed the MS' below doc to set up XP mode.
http://windows.microsoft.com/en-us/windows7/install-and-use-windows-xp-mode-in-windows-7
And, used the tool http://go.microsoft.com/fwlink/p/?LinkId=163321 to check
whether hardware-assisted virtualization is enabled or not.

Test environment:
hardware: Sandy Bridge - EP server
L0: latest Xen 4.3, Dom0 3.10.0, qemu-xen (not traditional)
L1: Windows 7 Enterprise
L2: XP mode

my Win7 guest config file is below; can you give me any hints?
----------------------
builder = "hvm"
name = "jay-hvm-1"
memory = 2048
vcpus = 2
vif = [ '' ]
disk = [ '/home/jay/win7-1.qcow2,qcow2,xvda,w' ]
vnc = 1
stdvga = 1
usb=1
usbdevice='tablet'
nestedhvm=1
----------------------

[-- Attachment #2: check-VT-tools-shows-it-enabled.JPG --]
[-- Type: image/jpeg, Size: 45681 bytes --]

[-- Attachment #3: xp-mode-shows-VT-disabled.JPG --]
[-- Type: image/jpeg, Size: 33158 bytes --]

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

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

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Il 03/07/2013 17:12, Ren, Yongjie ha scritto:
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xen.org
>> [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Fabio Fantoni
>> Sent: Monday, July 01, 2013 9:20 PM
>> To: xen-devel; Stefano Stabellini; Ian Campbell; Ian Jackson; Xu, Dongxiao;
>> Jan Beulich
>> Subject: [Xen-devel] Test report for xen-unstable and qemu-xen
>>
>> Dom0:
>> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
>> version
>> 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for
>> xen, spice and usb redirection.
>> Seabios 1.7.2-3 and latest spice and usbredir compiled from debian
>> unstable sources.
>> -------------------------
>> /etc/modules
>> ------------
>> loop max_loop=64
>> xenfs
>> xen-evtchn
>> blktap
>> -------------------------
>> git clone git://xenbits.xen.org/xen.git (in this build commit is
>> bcb49301c21ed69b4e8c164fa215efe9db30621a)
>> -------------------------
>> Added some patches:
>> - tools-configure-qemu-for-spice-and-usbredir
>> - libxl-Add-spice-vdagent-support-for-upstream-qemu
>> - tools-firmware-seabios-packaged
>> - tools: Improve make deb
>> - vgabios-stdvga.bin custom build from Frediano
>> - qemu-xen change for support other resolutions:
>> hw/vga.c: # from Frediano patch
>>       - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
>>       + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
>> -------------------------
>> ./configure --prefix=/usr
>> -------------------------
>> make debball
>>
>> -------------------------
>> Issues solved from my previous test build report:
>> -------------
>> - nested hvm was bugged:
>>
>>     Before: started test it on windows 7 pro 64 domU on qemu-xen,
>>     xpmode crashed on install without show error, no error on logs and
>> havdetection works.
>>
>>     Now xpmode installs and starts correctly except integration features
>>     (disks,printers,clipboard sharing) and usb passthrough (of xpmode)
>> -------------------------
>>
> Hi Fabio,
> I'm also testing Win7 XP mode in nested VMX environment, but I met some
> problems. In the Windows 7 HVM guest, a tool from Microsoft showed
> hardware-assisted virtualization is supported, but XP mode showed "hardware-
> assisted virtualization is disabled" and it refused to boot XP.
> (see the attached 2 pictures to get the two conflicting messages..)
>
> I followed the MS' below doc to set up XP mode.
> http://windows.microsoft.com/en-us/windows7/install-and-use-windows-xp-mode-in-windows-7
> And, used the tool http://go.microsoft.com/fwlink/p/?LinkId=163321 to check
> whether hardware-assisted virtualization is enabled or not.
>
> Test environment:
> hardware: Sandy Bridge - EP server
> L0: latest Xen 4.3, Dom0 3.10.0, qemu-xen (not traditional)
> L1: Windows 7 Enterprise
> L2: XP mode
>
> my Win7 guest config file is below; can you give me any hints?
> ----------------------
> builder = "hvm"
> name = "jay-hvm-1"
> memory = 2048
> vcpus = 2
> vif = [ '' ]
> disk = [ '/home/jay/win7-1.qcow2,qcow2,xvda,w' ]
> vnc = 1
> stdvga = 1
> usb=1
> usbdevice='tablet'
> nestedhvm=1
> ----------------------
Have you tried with same xen commit? 
(bcb49301c21ed69b4e8c164fa215efe9db30621a) or atleast to this that 
probably have solved my problem: nested vmx: Fix the booting of L2 PAE 
guest - 49b55619e4923aa1a43b7c027dd3e352575e4e52

Re: Test report for xen-unstable and qemu-xen

[Ren, Yongjie]

> -----Original Message-----
> From: Fabio Fantoni [mailto:fabio.fantoni@m2r.biz]
> Sent: Thursday, July 04, 2013 3:55 PM
> To: Ren, Yongjie
> Cc: xen-devel; Stefano Stabellini; Ian Campbell; Ian Jackson; Xu, Dongxiao;
> Jan Beulich
> Subject: Re: [Xen-devel] Test report for xen-unstable and qemu-xen
> 
> Il 03/07/2013 17:12, Ren, Yongjie ha scritto:
> >> -----Original Message-----
> >> From: xen-devel-bounces@lists.xen.org
> >> [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Fabio Fantoni
> >> Sent: Monday, July 01, 2013 9:20 PM
> >> To: xen-devel; Stefano Stabellini; Ian Campbell; Ian Jackson; Xu,
> Dongxiao;
> >> Jan Beulich
> >> Subject: [Xen-devel] Test report for xen-unstable and qemu-xen
> >>
> >> Dom0:
> >> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64
> >> version
> >> 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages
> for
> >> xen, spice and usb redirection.
> >> Seabios 1.7.2-3 and latest spice and usbredir compiled from debian
> >> unstable sources.
> >> -------------------------
> >> /etc/modules
> >> ------------
> >> loop max_loop=64
> >> xenfs
> >> xen-evtchn
> >> blktap
> >> -------------------------
> >> git clone git://xenbits.xen.org/xen.git (in this build commit is
> >> bcb49301c21ed69b4e8c164fa215efe9db30621a)
> >> -------------------------
> >> Added some patches:
> >> - tools-configure-qemu-for-spice-and-usbredir
> >> - libxl-Add-spice-vdagent-support-for-upstream-qemu
> >> - tools-firmware-seabios-packaged
> >> - tools: Improve make deb
> >> - vgabios-stdvga.bin custom build from Frediano
> >> - qemu-xen change for support other resolutions:
> >> hw/vga.c: # from Frediano patch
> >>       - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
> >>       + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
> >> -------------------------
> >> ./configure --prefix=/usr
> >> -------------------------
> >> make debball
> >>
> >> -------------------------
> >> Issues solved from my previous test build report:
> >> -------------
> >> - nested hvm was bugged:
> >>
> >>     Before: started test it on windows 7 pro 64 domU on qemu-xen,
> >>     xpmode crashed on install without show error, no error on logs
> and
> >> havdetection works.
> >>
> >>     Now xpmode installs and starts correctly except integration
> features
> >>     (disks,printers,clipboard sharing) and usb passthrough (of
> xpmode)
> >> -------------------------
> >>
> > Hi Fabio,
> > I'm also testing Win7 XP mode in nested VMX environment, but I met
> some
> > problems. In the Windows 7 HVM guest, a tool from Microsoft showed
> > hardware-assisted virtualization is supported, but XP mode showed
> "hardware-
> > assisted virtualization is disabled" and it refused to boot XP.
> > (see the attached 2 pictures to get the two conflicting messages..)
> >
> > I followed the MS' below doc to set up XP mode.
> >
> http://windows.microsoft.com/en-us/windows7/install-and-use-windows-x
> p-mode-in-windows-7
> > And, used the tool http://go.microsoft.com/fwlink/p/?LinkId=163321 to
> check
> > whether hardware-assisted virtualization is enabled or not.
> >
> > Test environment:
> > hardware: Sandy Bridge - EP server
> > L0: latest Xen 4.3, Dom0 3.10.0, qemu-xen (not traditional)
> > L1: Windows 7 Enterprise
> > L2: XP mode
> >
> > my Win7 guest config file is below; can you give me any hints?
> > ----------------------
> > builder = "hvm"
> > name = "jay-hvm-1"
> > memory = 2048
> > vcpus = 2
> > vif = [ '' ]
> > disk = [ '/home/jay/win7-1.qcow2,qcow2,xvda,w' ]
> > vnc = 1
> > stdvga = 1
> > usb=1
> > usbdevice='tablet'
> > nestedhvm=1
> > ----------------------
> Have you tried with same xen commit?
> (bcb49301c21ed69b4e8c164fa215efe9db30621a) or atleast to this that
> probably have solved my problem: nested vmx: Fix the booting of L2 PAE
> guest - 49b55619e4923aa1a43b7c027dd3e352575e4e52
Yes, I tried that commit you mentioned. I also think Dongxiao's fix 
"nested vmx: Fix the booting of L2 PAE" can fix some issue as you tested.

But in my testing, with or without that fix, I met the same issue. I can't
even use 'XP mode' in Win7 guest. 'XP Moe' showed hardware VT is disabled;
while MS's another tool to check VT showed hardware VT is supported. 
I was confused and can't even start XP mode in Win7 HVM guest. 
(Before that fix, you can see your XP mode crash; but I can't start XP mode at all.)

thanks!  - Jay

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for 
xen, spice and usb redirection.
Seabios 1.7.2-3 and latest spice and usbredir compiled from debian 
unstable sources.
-------------------------
/etc/modules
------------
loop max_loop=64
xenfs
xen-evtchn
blktap
-------------------------
git clone git://xenbits.xen.org/xen.git (in this build commit is 
6859874b61d5ddaf5289e72ed2b2157739b72ca5)
-------------------------
Added some patches:
- tools-configure-qemu-for-spice-and-usbredir
- libxl-Add-spice-vdagent-support-for-upstream-qemu
- tools-firmware-seabios-packaged
- tools: Improve make deb
- vgabios-stdvga.bin custom build from Frediano
- qemu-xen change for support other resolutions:
hw/vga.c: # from Frediano patch
     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
- updated qemu upstream
Config-mk:
QEMU_UPSTREAM_REVISION ?= master
-------------------------
./configure --prefix=/usr
-------------------------
make debball

-------------------------
Issues solved from my previous test build report:
-------------
- restore with xl on xendomain not work (now solved upstream)
-------------------------

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
   Workaround: fixed mac address
-------------
- nested hvm probably bugged: started test it on windows 7 pro 64 domU 
on qemu-xen,
   xpmode crash on install without show error, no error on logs and 
havdetection works
-------------
- Starting xendomain with "xl create" show some debug options:
   Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY ARRANGEMENT:
   Loader:        0000000000100000->000000000019eb68
   Modules:       0000000000000000->0000000000000000
   TOTAL:         0000000000000000->000000007f000000
   ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
   4KB PAGES: 0x0000000000000200
   2MB PAGES: 0x00000000000003f7
   1GB PAGES: 0x0000000000000000
[done].
I think it is would be better hiding them here
-------------
- on W7 pro 64 bit domU error in the begin of qemu log, while domU seem 
to work:
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 
= Invalid argument): Internal error
xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
-------------------------

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for 
xen, spice and usb redirection.
Seabios 1.7.2-2 and latest spice and usbredir compiled from debian 
unstable sources.
-------------------------
/etc/modules
------------
loop max_loop=64
xenfs
xen-evtchn
blktap
-------------------------
git clone git://xenbits.xen.org/xen.git (in this build commit is 
3a4a1d297766c0617129fb9eeef164293926ae89)
-------------------------
Added some patches:
- tools-configure-qemu-for-spice-and-usbredir
- libxl-Add-spice-vdagent-support-for-upstream-qemu
- tools-firmware-seabios-packaged
- tools: Improve make deb
- vgabios-stdvga.bin custom build from Frediano
- tools-fix-xendomain-restore-xl
- qemu-xen change for support other resolutions:
hw/vga.c: # from Frediano patch
     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
- fix for one qxl bug: # from anthony perard
--- a/hw/qxl.c
+++ b/hw/qxl.c
@@ -390,6 +390,7 @@ static void init_qxl_ram(PCIQXLDevice *d)
      d->ram->int_pending = cpu_to_le32(0);
      d->ram->int_mask    = cpu_to_le32(0);
      d->ram->update_surface = 0;
+    d->ram->monitors_config = 0;
      SPICE_RING_INIT(&d->ram->cmd_ring);
      SPICE_RING_INIT(&d->ram->cursor_ring);
      SPICE_RING_INIT(&d->ram->release_ring);
-------------------------
./configure --prefix=/usr
-------------------------
make debball

-------------------------
Issues solved from my previous test build report:
-------------
- restore with xl on xendomain not work
   solved with patch "xl problems with xendomains":
   http://lists.xen.org/archives/html/xen-devel/2013-05/msg02107.html
-------------------------

-------------------------
Recent regression:
-------------
- on W7 pro 64 bit domU error in the begin of qemu log, while domU seem 
to work:
xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed (22 
= Invalid argument): Internal error
xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
-------------------------

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
   Workaround: fixed mac address
-------------
- Unable to get QXL vga working correctly
   Status: one fix available and work in progress about the remaining 
problem (for now I made quick tests without success)
-------------
- nested hvm probably bugged: started test it on windows 7 pro 64 domU 
on qemu-xen,
   xpmode crash on install without show error, no error on logs and 
havdetection works
-------------
- Starting xendomain with "xl create" show some debug options:
   Starting auto Xen domains: W7.cfgxc: info: VIRTUAL MEMORY ARRANGEMENT:
   Loader:        0000000000100000->000000000019eb68
   Modules:       0000000000000000->0000000000000000
   TOTAL:         0000000000000000->000000007f000000
   ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
   4KB PAGES: 0x0000000000000200
   2MB PAGES: 0x00000000000003f7
   1GB PAGES: 0x0000000000000000
[done].
I think it is would be better hiding them here
-------------------------

Re: Test report for xen-unstable and qemu-xen

[George Dunlap]

On 22/05/13 15:48, Fabio Fantoni wrote:
> Dom0:
> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 
> version 3.2.41-2+deb7u2, package blktap-dkms and all dependency 
> packages for xen, spice and usb redirection.
> Seabios 1.7.2-2 and latest spice and usbredir compiled from debian 
> unstable sources.
> -------------------------
> /etc/modules
> ------------
> loop max_loop=64
> xenfs
> xen-evtchn
> blktap
> -------------------------
> git clone git://xenbits.xen.org/xen.git (in this build commit is 
> 3a4a1d297766c0617129fb9eeef164293926ae89)
> -------------------------
> Added some patches:
> - tools-configure-qemu-for-spice-and-usbredir
> - libxl-Add-spice-vdagent-support-for-upstream-qemu
> - tools-firmware-seabios-packaged
> - tools: Improve make deb
> - vgabios-stdvga.bin custom build from Frediano
> - tools-fix-xendomain-restore-xl
> - qemu-xen change for support other resolutions:
> hw/vga.c: # from Frediano patch
>     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
>     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
> - fix for one qxl bug: # from anthony perard
> --- a/hw/qxl.c
> +++ b/hw/qxl.c
> @@ -390,6 +390,7 @@ static void init_qxl_ram(PCIQXLDevice *d)
>      d->ram->int_pending = cpu_to_le32(0);
>      d->ram->int_mask    = cpu_to_le32(0);
>      d->ram->update_surface = 0;
> +    d->ram->monitors_config = 0;
>      SPICE_RING_INIT(&d->ram->cmd_ring);
>      SPICE_RING_INIT(&d->ram->cursor_ring);
>      SPICE_RING_INIT(&d->ram->release_ring);
> -------------------------
> ./configure --prefix=/usr
> -------------------------
> make debball
>
> -------------------------
> Issues solved from my previous test build report:
> -------------
> - restore with xl on xendomain not work
>   solved with patch "xl problems with xendomains":
> http://lists.xen.org/archives/html/xen-devel/2013-05/msg02107.html

Thank you for testing this.  In general it would be better to respond to 
the threads pertaining to individual issues to update things, and make a 
new thread for new issues.  In this case, it would be helpful if you 
would instead respond to this thread saying, "Tested-by: Fabio Fantoni 
<...>"

> -------------------------
>
> -------------------------
> Recent regression:
> -------------
> - on W7 pro 64 bit domU error in the begin of qemu log, while domU 
> seem to work:
> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed 
> (22 = Invalid argument): Internal error
> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument

I don't quite understand: Are you saying that you see this error 
message, but the guest still works as far as you can tell?

> -------------------------
>
> -------------------------
> Old issue:
> - Network is not working after restore on Windows domU with qemu-xen 
> and gplpv
>   Workaround: fixed mac address
> -------------
> - Unable to get QXL vga working correctly
>   Status: one fix available and work in progress about the remaining 
> problem (for now I made quick tests without success)

These issues are actively being worked on; there's no need to comment on 
them in particular.  If you think the issue may have been forgotten 
about, the best thing to do is to respond to one of the old threads and 
ask if there has been any progress.

  -George

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

Il 22/05/2013 18:32, George Dunlap ha scritto:
> On 22/05/13 15:48, Fabio Fantoni wrote:
>> Dom0:
>> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 
>> version 3.2.41-2+deb7u2, package blktap-dkms and all dependency 
>> packages for xen, spice and usb redirection.
>> Seabios 1.7.2-2 and latest spice and usbredir compiled from debian 
>> unstable sources.
>> -------------------------
>> /etc/modules
>> ------------
>> loop max_loop=64
>> xenfs
>> xen-evtchn
>> blktap
>> -------------------------
>> git clone git://xenbits.xen.org/xen.git (in this build commit is 
>> 3a4a1d297766c0617129fb9eeef164293926ae89)
>> -------------------------
>> Added some patches:
>> - tools-configure-qemu-for-spice-and-usbredir
>> - libxl-Add-spice-vdagent-support-for-upstream-qemu
>> - tools-firmware-seabios-packaged
>> - tools: Improve make deb
>> - vgabios-stdvga.bin custom build from Frediano
>> - tools-fix-xendomain-restore-xl
>> - qemu-xen change for support other resolutions:
>> hw/vga.c: # from Frediano patch
>>     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
>>     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
>> - fix for one qxl bug: # from anthony perard
>> --- a/hw/qxl.c
>> +++ b/hw/qxl.c
>> @@ -390,6 +390,7 @@ static void init_qxl_ram(PCIQXLDevice *d)
>>      d->ram->int_pending = cpu_to_le32(0);
>>      d->ram->int_mask    = cpu_to_le32(0);
>>      d->ram->update_surface = 0;
>> +    d->ram->monitors_config = 0;
>>      SPICE_RING_INIT(&d->ram->cmd_ring);
>>      SPICE_RING_INIT(&d->ram->cursor_ring);
>>      SPICE_RING_INIT(&d->ram->release_ring);
>> -------------------------
>> ./configure --prefix=/usr
>> -------------------------
>> make debball
>>
>> -------------------------
>> Issues solved from my previous test build report:
>> -------------
>> - restore with xl on xendomain not work
>>   solved with patch "xl problems with xendomains":
>> http://lists.xen.org/archives/html/xen-devel/2013-05/msg02107.html
>
> Thank you for testing this.  In general it would be better to respond 
> to the threads pertaining to individual issues to update things, and 
> make a new thread for new issues.  In this case, it would be helpful 
> if you would instead respond to this thread saying, "Tested-by: Fabio 
> Fantoni <...>"
>
Done
>> -------------------------
>>
>> -------------------------
>> Recent regression:
>> -------------
>> - on W7 pro 64 bit domU error in the begin of qemu log, while domU 
>> seem to work:
>> xc: error: linux_gnttab_set_max_grants: ioctl SET_MAX_GRANTS failed 
>> (22 = Invalid argument): Internal error
>> xen be: qdisk-832: xc_gnttab_set_max_grants failed: Invalid argument
>
> I don't quite understand: Are you saying that you see this error 
> message, but the guest still works as far as you can tell?
Yes, it still works
>
>> -------------------------
>>
>> -------------------------
>> Old issue:
>> - Network is not working after restore on Windows domU with qemu-xen 
>> and gplpv
>>   Workaround: fixed mac address
>> -------------
>> - Unable to get QXL vga working correctly
>>   Status: one fix available and work in progress about the remaining 
>> problem (for now I made quick tests without success)
>
> These issues are actively being worked on; there's no need to comment 
> on them in particular.  If you think the issue may have been forgotten 
> about, the best thing to do is to respond to one of the old threads 
> and ask if there has been any progress.
>
>  -George

Re: Test report for xen-unstable and qemu-xen

[Pasi Kärkkäinen]

On Wed, May 22, 2013 at 04:48:04PM +0200, Fabio Fantoni wrote:
> -------------
> - nested hvm probably bugged: started test it on windows 7 pro 64
> domU on qemu-xen,
>   xpmode crash on install without show error, no error on logs and
> havdetection works
> -------------

I think earlier you were asked to open a new thread about this nested hvm issue.
Also you've not provided enough information:

	- What hardware are you using? Intel or AMD? Which CPU model?
	- Any errors in the hypervisor dmesg (xl dmesg) ? 
	- Any errors in qemu log files? 
	- Is it the xpmode guest that crashes, or is it the whole win7 that crashes?
	- etc


-- Pasi

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

Il 22/05/2013 18:37, Pasi Kärkkäinen ha scritto:
> On Wed, May 22, 2013 at 04:48:04PM +0200, Fabio Fantoni wrote:
>> -------------
>> - nested hvm probably bugged: started test it on windows 7 pro 64
>> domU on qemu-xen,
>>    xpmode crash on install without show error, no error on logs and
>> havdetection works
>> -------------
> I think earlier you were asked to open a new thread about this nested hvm issue.
> Also you've not provided enough information:
>
> 	- What hardware are you using? Intel or AMD? Which CPU model?
Intel Xeon X3450
> 	- Any errors in the hypervisor dmesg (xl dmesg) ?
See attachment
> 	- Any errors in qemu log files?
No error on qemu logs about this problem
> 	- Is it the xpmode guest that crashes, or is it the whole win7 that crashes?
The xpmode guest crashes during installation without show errors.

> 	- etc
>
>
> -- Pasi
>

[-- Attachment #2: xldmesg.log --]
[-- Type: text/plain, Size: 50955 bytes --]

 __  __            _  _    _____                    _        _     _      
 \ \/ /___ _ __   | || |  |___ /    _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \  | || |_   |_ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | | |__   _| ___) |__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_|    |_|(_)____/    \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                          
(XEN) Xen version 4.3-unstable (root@) (gcc (Debian 4.7.2-5) 4.7.2) debug=y Wed May 22 11:02:22 CEST 2013
(XEN) Latest ChangeSet: Tue May 21 15:00:01 2013 +0100 git:3a4a1d2-dirty
(XEN) Bootloader: GRUB 1.99-22.1
(XEN) Command line: placeholder dom0_mem=4G,max:4G
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e000 (usable)
(XEN)  0000000000100000 - 00000000bf699000 (usable)
(XEN)  00000000bf699000 - 00000000bf6af000 (reserved)
(XEN)  00000000bf6af000 - 00000000bf6ce000 (ACPI data)
(XEN)  00000000bf6ce000 - 00000000c0000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fe000000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000340000000 (usable)
(XEN) ACPI: RSDP 000F12C0, 0024 (r2 DELL  )
(XEN) ACPI: XSDT 000F13C0, 008C (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: FACP BF6C3BB4, 00F4 (r3 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: DSDT BF6AF000, 3EA6 (r1 DELL   PE_SC3          1 INTL 20050624)
(XEN) ACPI: FACS BF6C6000, 0040
(XEN) ACPI: APIC BF6C3478, 0152 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: SPCR BF6C35CC, 0050 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: HPET BF6C3620, 0038 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: DMAR BF6C365C, 00A8 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: MCFG BF6C3850, 003C (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: WDAT BF6C3890, 0134 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: SLIC BF6C39C8, 0024 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: ERST BF6B3028, 0270 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: HEST BF6B3298, 03A8 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: BERT BF6B2EA8, 0030 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: EINJ BF6B2ED8, 0150 (r1 DELL   PE_SC3          1 DELL        1)
(XEN) ACPI: TCPA BF6C3B4C, 0064 (r2 DELL   PE_SC3          1 DELL        1)
(XEN) System RAM: 12278MB (12572892kB)
(XEN) No NUMA configuration found
(XEN) Faking a node at 0000000000000000-0000000340000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.6 present.
(XEN) Using APIC driver bigsmp
(XEN) ACPI: PM-Timer IO Port: 0x808
(XEN) ACPI: SLEEP INFO: pm1x_cnt[804,0], pm1x_evt[800,0]
(XEN) ACPI:             wakeup_vec[bf6c600c], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
(XEN) Processor #4 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
(XEN) Processor #6 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
(XEN) Processor #1 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
(XEN) Processor #3 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
(XEN) Processor #5 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
(XEN) Processor #7 7:14 APIC version 21
(XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x28] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x29] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x2a] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x2b] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x2c] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x2d] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x2e] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x10] lapic_id[0x2f] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x11] lapic_id[0x30] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x12] lapic_id[0x31] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x13] lapic_id[0x32] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x14] lapic_id[0x33] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x15] lapic_id[0x34] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x16] lapic_id[0x35] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x17] lapic_id[0x36] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x18] lapic_id[0x37] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x19] lapic_id[0x38] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x39] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x3a] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1c] lapic_id[0x3b] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1d] lapic_id[0x3c] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1e] lapic_id[0x3d] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x1f] lapic_id[0x3e] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x20] lapic_id[0x3f] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Phys.  Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) Xen ERST support is initialized.
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) SMP: Allowing 32 CPUs (24 hotplug CPUs)
(XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2661.158 MHz processor.
(XEN) Initing memory sharing.
(XEN) mce_intel.c:717: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extended MCE MSR 0
(XEN) Intel machine check reporting enabled
(XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - ff
(XEN) PCI: MCFG area at e0000000 reserved in E820
(XEN) PCI: Using MCFG for segment 0000 bus 00-ff
(XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
(XEN) Intel VT-d Snoop Control enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping not enabled.
(XEN) Intel VT-d Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Interrupt remapping disabled
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) Using standard rendezvous
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 64 KiB.
(XEN) mwait-idle: MWAIT substates: 0x1120
(XEN) mwait-idle: v0.4 model 0x1e
(XEN) mwait-idle: lapic_timer_reliable_states 0x2
(XEN) HPET: 8 timers (8 will be used for broadcast)
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB
(XEN) Brought up 8 CPUs
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x557000
(XEN) elf_parse_binary: phdr: paddr=0x1600000 memsz=0x950e0
(XEN) elf_parse_binary: phdr: paddr=0x1696000 memsz=0x14400
(XEN) elf_parse_binary: phdr: paddr=0x16ab000 memsz=0x292000
(XEN) elf_parse_binary: memory: 0x1000000 -> 0x193d000
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000
(XEN) elf_xen_parse_note: ENTRY = 0xffffffff816ab200
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000
(XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb"
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xffffffff80000000
(XEN)     elf_paddr_offset = 0x0
(XEN)     virt_offset      = 0xffffffff80000000
(XEN)     virt_kstart      = 0xffffffff81000000
(XEN)     virt_kend        = 0xffffffff8193d000
(XEN)     virt_entry       = 0xffffffff816ab200
(XEN)     p2m_base         = 0xffffffffffffffff
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x193d000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000330000000->0000000334000000 (1024043 pages to be allocated)
(XEN)  Init. ramdisk: 000000033e02b000->000000033ffffe00
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff8193d000
(XEN)  Init. ramdisk: ffffffff8193d000->ffffffff83911e00
(XEN)  Phys-Mach map: ffffffff83912000->ffffffff84112000
(XEN)  Start info:    ffffffff84112000->ffffffff841124b4
(XEN)  Page tables:   ffffffff84113000->ffffffff84138000
(XEN)  Boot stack:    ffffffff84138000->ffffffff84139000
(XEN)  TOTAL:         ffffffff80000000->ffffffff84400000
(XEN)  ENTRY ADDRESS: ffffffff816ab200
(XEN) Dom0 has maximum 8 VCPUs
(XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81557000
(XEN) elf_load_binary: phdr 1 at 0xffffffff81600000 -> 0xffffffff816950e0
(XEN) elf_load_binary: phdr 2 at 0xffffffff81696000 -> 0xffffffff816aa400
(XEN) elf_load_binary: phdr 3 at 0xffffffff816ab000 -> 0xffffffff81729000
(XEN) Scrubbing Free RAM: ................................................................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 272kB init memory.
(XEN) PCI add device 0000:00:00.0
(XEN) PCI add device 0000:00:03.0
(XEN) PCI add device 0000:00:05.0
(XEN) PCI add device 0000:00:08.0
(XEN) PCI add device 0000:00:08.1
(XEN) PCI add device 0000:00:08.2
(XEN) PCI add device 0000:00:08.3
(XEN) PCI add device 0000:00:10.0
(XEN) PCI add device 0000:00:10.1
(XEN) PCI add device 0000:00:1a.0
(XEN) PCI add device 0000:00:1c.0
(XEN) PCI add device 0000:00:1c.2
(XEN) PCI add device 0000:00:1c.3
(XEN) PCI add device 0000:00:1c.4
(XEN) PCI add device 0000:00:1d.0
(XEN) PCI add device 0000:00:1e.0
(XEN) PCI add device 0000:00:1f.0
(XEN) PCI add device 0000:00:1f.2
(XEN) PCI add device 0000:00:1f.5
(XEN) PCI add device 0000:03:00.0
(XEN) PCI add device 0000:02:00.0
(XEN) PCI add device 0000:02:00.1
(XEN) PCI add device 0000:01:03.0
(XEN) PCI add device 0000:ff:00.0
(XEN) PCI add device 0000:ff:00.1
(XEN) PCI add device 0000:ff:02.0
(XEN) PCI add device 0000:ff:02.1
(XEN) PCI add device 0000:ff:03.0
(XEN) PCI add device 0000:ff:03.1
(XEN) PCI add device 0000:ff:03.2
(XEN) PCI add device 0000:ff:03.4
(XEN) PCI add device 0000:ff:04.0
(XEN) PCI add device 0000:ff:04.1
(XEN) PCI add device 0000:ff:04.2
(XEN) PCI add device 0000:ff:04.3
(XEN) PCI add device 0000:ff:05.0
(XEN) PCI add device 0000:ff:05.1
(XEN) PCI add device 0000:ff:05.2
(XEN) PCI add device 0000:ff:05.3
(XEN) HVM1: HVM Loader
(XEN) HVM1: Detected Xen v4.3-unstable
(XEN) HVM1: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM1: System requested SeaBIOS
(XEN) HVM1: CPU speed is 2661 MHz
(XEN) irq.c:270: Dom1 PCI link 0 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom1 PCI link 1 changed 0 -> 10
(XEN) HVM1: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom1 PCI link 2 changed 0 -> 11
(XEN) HVM1: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom1 PCI link 3 changed 0 -> 5
(XEN) HVM1: PCI-ISA link 3 routed to IRQ5
(XEN) HVM1: pci dev 01:3 INTA->IRQ10
(XEN) HVM1: pci dev 03:0 INTA->IRQ5
(XEN) HVM1: pci dev 04:0 INTA->IRQ5
(XEN) HVM1: pci dev 05:0 INTA->IRQ10
(XEN) HVM1: pci dev 06:0 INTA->IRQ11
(XEN) HVM1: pci dev 1d:0 INTA->IRQ10
(XEN) HVM1: pci dev 1d:1 INTB->IRQ11
(XEN) HVM1: pci dev 1d:2 INTC->IRQ5
(XEN) HVM1: pci dev 1d:7 INTD->IRQ5
(XEN) HVM1: pci dev 02:0 bar 10 size lx: 01000000
(XEN) HVM1: pci dev 03:0 bar 14 size lx: 01000000
(XEN) HVM1: pci dev 02:0 bar 30 size lx: 00010000
(XEN) HVM1: pci dev 06:0 bar 30 size lx: 00010000
(XEN) HVM1: pci dev 04:0 bar 10 size lx: 00004000
(XEN) HVM1: pci dev 02:0 bar 18 size lx: 00001000
(XEN) HVM1: pci dev 05:0 bar 14 size lx: 00001000
(XEN) HVM1: pci dev 1d:7 bar 10 size lx: 00001000
(XEN) HVM1: pci dev 03:0 bar 10 size lx: 00000100
(XEN) HVM1: pci dev 06:0 bar 10 size lx: 00000100
(XEN) HVM1: pci dev 06:0 bar 14 size lx: 00000100
(XEN) HVM1: pci dev 05:0 bar 10 size lx: 00000020
(XEN) HVM1: pci dev 1d:0 bar 20 size lx: 00000020
(XEN) HVM1: pci dev 1d:1 bar 20 size lx: 00000020
(XEN) HVM1: pci dev 1d:2 bar 20 size lx: 00000020
(XEN) HVM1: pci dev 01:1 bar 20 size lx: 00000010
(XEN) HVM1: Multiprocessor initialisation:
(XEN) HVM1:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM1:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM1: Testing HVM environment:
(XEN) HVM1:  - REP INSB across page boundaries ... passed
(XEN) HVM1:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM1: Passed 2 of 2 tests
(XEN) HVM1: Writing SMBIOS tables ...
(XEN) HVM1: Loading SeaBIOS ...
(XEN) HVM1: Creating MP tables ...
(XEN) HVM1: Loading ACPI ...
(XEN) HVM1: vm86 TSS at fc00a080
(XEN) HVM1: BIOS map:
(XEN) HVM1:  10000-100d3: Scratch space
(XEN) HVM1:  e0000-fffff: Main BIOS
(XEN) HVM1: E820 table:
(XEN) HVM1:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM1:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM1:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM1:  [02]: 00000000:00100000 - 00000000:7f000000: RAM
(XEN) HVM1:  HOLE: 00000000:7f000000 - 00000000:fc000000
(XEN) HVM1:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM1: Invoking SeaBIOS ...
(XEN) HVM1: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM1: 
(XEN) HVM1: Found Xen hypervisor signature at 40000000
(XEN) HVM1: xen: copy e820...
(XEN) HVM1: Ram Size=0x7f000000 (0x0000000000000000 high)
(XEN) HVM1: Relocating low data from 0x000e1890 to 0x000ef780 (size 2161)
(XEN) HVM1: Relocating init from 0x000e2101 to 0x7efe0aa0 (size 62523)
(XEN) HVM1: CPU Mhz=2662
(XEN) HVM1: Found 13 PCI devices (max PCI bus is 00)
(XEN) HVM1: Allocated Xen hypercall page at 7efff000
(XEN) HVM1: Detected Xen v4.3-unstable
(XEN) HVM1: Found 2 cpu(s) max supported 2 cpu(s)
(XEN) HVM1: xen: copy BIOS tables...
(XEN) HVM1: Copying SMBIOS entry point from 0x00010010 to 0x000fdbd0
(XEN) HVM1: Copying MPTABLE from 0xfc001170/fc001180 to 0x000fdad0
(XEN) HVM1: Copying PIR from 0x00010030 to 0x000fda50
(XEN) HVM1: Copying ACPI RSDP from 0x000100b0 to 0x000fda20
(XEN) HVM1: Scan for VGA option rom
(XEN) HVM1: Running option rom at c000:0003
(XEN) stdvga.c:147:d1 entering stdvga and caching modes
(XEN) HVM1: Turning on vga text mode console
(XEN) HVM1: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM1: Machine UUID e3f0e8cf-0a6c-409b-8c67-2560ae69f0bf
(XEN) HVM1: EHCI init on dev 00:1d.7 (regs=0xf2026020)
(XEN) HVM1: Found 1 lpt ports
(XEN) HVM1: Found 1 serial ports
(XEN) HVM1: ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
(XEN) HVM1: ATA controller 2 at 170/374/0 (irq 15 dev 9)
(XEN) HVM1: ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (50000 MiBytes)
(XEN) HVM1: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(XEN) HVM1: DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM1: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
(XEN) HVM1: DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM1: Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@0
(XEN) HVM1: PS2 keyboard initialized
(XEN) HVM1: All threads complete.
(XEN) HVM1: Scan for option roms
(XEN) HVM1: Running option rom at ca80:0003
(XEN) HVM1: pmm call arg1=1
(XEN) HVM1: pmm call arg1=0
(XEN) HVM1: pmm call arg1=1
(XEN) HVM1: pmm call arg1=0
(XEN) HVM1: Searching bootorder for: /pci@i0cf8/*@6
(XEN) HVM1: 
(XEN) HVM1: Press F12 for boot menu.
(XEN) HVM1: 
(XEN) HVM1: Searching bootorder for: HALT
(XEN) HVM1: drive 0x000fd9d0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=10240000
(XEN) HVM1: 0
(XEN) HVM1: Space available for UMB: 000cb800-000ee800
(XEN) HVM1: Returned 61440 bytes of ZoneHigh
(XEN) HVM1: e820 map has 6 items:
(XEN) HVM1:   0: 0000000000000000 - 000000000009fc00 = 1 RAM
(XEN) HVM1:   1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(XEN) HVM1:   2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(XEN) HVM1:   3: 0000000000100000 - 000000007efff000 = 1 RAM
(XEN) HVM1:   4: 000000007efff000 - 000000007f000000 = 2 RESERVED
(XEN) HVM1:   5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(XEN) HVM1: enter handle_19:
(XEN) HVM1:   NULL
(XEN) HVM1: Booting from DVD/CD...
(XEN) HVM1: Device reports MEDIUM NOT PRESENT
(XEN) HVM1: scsi_is_ready returned -1
(XEN) HVM1: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM1: enter handle_18:
(XEN) HVM1:   NULL
(XEN) HVM1: Booting from DVD/CD...
(XEN) HVM1: Device reports MEDIUM NOT PRESENT
(XEN) HVM1: scsi_is_ready returned -1
(XEN) HVM1: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM1: enter handle_18:
(XEN) HVM1:   NULL
(XEN) HVM1: Booting from Hard Disk...
(XEN) HVM1: Booting from 0000:7c00
(XEN) irq.c:270: Dom1 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom1 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom1 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom1 PCI link 3 changed 5 -> 0
(XEN) grant_table.c:1250:d1 Expanding dom (1) grant table from (4) to (32) frames.
(XEN) irq.c:375: Dom1 callback via changed to GSI 28
(XEN) HVM2: HVM Loader
(XEN) HVM2: Detected Xen v4.3-unstable
(XEN) HVM2: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM2: System requested SeaBIOS
(XEN) HVM2: CPU speed is 2661 MHz
(XEN) irq.c:270: Dom2 PCI link 0 changed 0 -> 5
(XEN) HVM2: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom2 PCI link 1 changed 0 -> 10
(XEN) HVM2: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom2 PCI link 2 changed 0 -> 11
(XEN) HVM2: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom2 PCI link 3 changed 0 -> 5
(XEN) HVM2: PCI-ISA link 3 routed to IRQ5
(XEN) HVM2: pci dev 01:3 INTA->IRQ10
(XEN) HVM2: pci dev 02:0 INTA->IRQ11
(XEN) HVM2: pci dev 03:0 INTA->IRQ5
(XEN) HVM2: pci dev 04:0 INTA->IRQ5
(XEN) HVM2: pci dev 05:0 INTA->IRQ10
(XEN) HVM2: pci dev 06:0 INTA->IRQ11
(XEN) HVM2: pci dev 1d:0 INTA->IRQ10
(XEN) HVM2: pci dev 1d:1 INTB->IRQ11
(XEN) HVM2: pci dev 1d:2 INTC->IRQ5
(XEN) HVM2: pci dev 1d:7 INTD->IRQ5
(XEN) HVM2: pci dev 02:0 bar 10 size lx: 04000000
(XEN) HVM2: pci dev 02:0 bar 14 size lx: 04000000
(XEN) HVM2: pci dev 03:0 bar 14 size lx: 01000000
(XEN) HVM2: pci dev 02:0 bar 30 size lx: 00010000
(XEN) HVM2: pci dev 06:0 bar 30 size lx: 00010000
(XEN) HVM2: pci dev 02:0 bar 18 size lx: 00004000
(XEN) HVM2: pci dev 04:0 bar 10 size lx: 00004000
(XEN) HVM2: pci dev 05:0 bar 14 size lx: 00001000
(XEN) HVM2: pci dev 1d:7 bar 10 size lx: 00001000
(XEN) HVM2: pci dev 03:0 bar 10 size lx: 00000100
(XEN) HVM2: pci dev 06:0 bar 10 size lx: 00000100
(XEN) HVM2: pci dev 06:0 bar 14 size lx: 00000100
(XEN) HVM2: pci dev 02:0 bar 1c size lx: 00000020
(XEN) HVM2: pci dev 05:0 bar 10 size lx: 00000020
(XEN) HVM2: pci dev 1d:0 bar 20 size lx: 00000020
(XEN) HVM2: pci dev 1d:1 bar 20 size lx: 00000020
(XEN) HVM2: pci dev 1d:2 bar 20 size lx: 00000020
(XEN) HVM2: pci dev 01:1 bar 20 size lx: 00000010
(XEN) HVM2: Multiprocessor initialisation:
(XEN) HVM2:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM2:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM2: Testing HVM environment:
(XEN) HVM2:  - REP INSB across page boundaries ... passed
(XEN) HVM2:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM2: Passed 2 of 2 tests
(XEN) HVM2: Writing SMBIOS tables ...
(XEN) HVM2: Loading SeaBIOS ...
(XEN) HVM2: Creating MP tables ...
(XEN) HVM2: Loading ACPI ...
(XEN) HVM2: vm86 TSS at fc00a080
(XEN) HVM2: BIOS map:
(XEN) HVM2:  10000-100d3: Scratch space
(XEN) HVM2:  e0000-fffff: Main BIOS
(XEN) HVM2: E820 table:
(XEN) HVM2:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM2:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM2:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM2:  [02]: 00000000:00100000 - 00000000:78000000: RAM
(XEN) HVM2:  HOLE: 00000000:78000000 - 00000000:fc000000
(XEN) HVM2:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM2: Invoking SeaBIOS ...
(XEN) HVM2: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM2: 
(XEN) HVM2: Found Xen hypervisor signature at 40000000
(XEN) HVM2: xen: copy e820...
(XEN) HVM2: Ram Size=0x78000000 (0x0000000000000000 high)
(XEN) HVM2: Relocating low data from 0x000e1890 to 0x000ef780 (size 2161)
(XEN) HVM2: Relocating init from 0x000e2101 to 0x77fe0aa0 (size 62523)
(XEN) HVM2: CPU Mhz=2662
(XEN) HVM2: Found 13 PCI devices (max PCI bus is 00)
(XEN) HVM2: Allocated Xen hypercall page at 77fff000
(XEN) HVM2: Detected Xen v4.3-unstable
(XEN) HVM2: Found 2 cpu(s) max supported 2 cpu(s)
(XEN) HVM2: xen: copy BIOS tables...
(XEN) HVM2: Copying SMBIOS entry point from 0x00010010 to 0x000fdbd0
(XEN) HVM2: Copying MPTABLE from 0xfc001170/fc001180 to 0x000fdad0
(XEN) HVM2: Copying PIR from 0x00010030 to 0x000fda50
(XEN) HVM2: Copying ACPI RSDP from 0x000100b0 to 0x000fda20
(XEN) HVM2: Scan for VGA option rom
(XEN) HVM2: Running option rom at c000:0003
(XEN) stdvga.c:147:d2 entering stdvga and caching modes
(XEN) HVM2: Turning on vga text mode console
(XEN) HVM2: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM2: Machine UUID 7b6695c1-c4ce-4941-bf1d-0c887476ef09
(XEN) HVM2: EHCI init on dev 00:1d.7 (regs=0xf9029020)
(XEN) HVM2: Found 1 lpt ports
(XEN) HVM2: Found 1 serial ports
(XEN) HVM2: ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
(XEN) HVM2: ATA controller 2 at 170/374/0 (irq 15 dev 9)
(XEN) HVM2: ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (50000 MiBytes)
(XEN) HVM2: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(XEN) HVM2: DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM2: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
(XEN) HVM2: DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM2: Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@0
(XEN) HVM2: PS2 keyboard initialized
(XEN) HVM2: All threads complete.
(XEN) HVM2: Scan for option roms
(XEN) HVM2: Running option rom at ca00:0003
(XEN) HVM2: pmm call arg1=1
(XEN) HVM2: pmm call arg1=0
(XEN) HVM2: pmm call arg1=1
(XEN) HVM2: pmm call arg1=0
(XEN) HVM2: Searching bootorder for: /pci@i0cf8/*@6
(XEN) HVM2: 
(XEN) HVM2: Press F12 for boot menu.
(XEN) HVM2: 
(XEN) HVM2: Searching bootorder for: HALT
(XEN) HVM2: drive 0x000fd9d0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=10240000
(XEN) HVM2: 0
(XEN) HVM2: Space available for UMB: 000cb000-000ee800
(XEN) HVM2: Returned 61440 bytes of ZoneHigh
(XEN) HVM2: e820 map has 6 items:
(XEN) HVM2:   0: 0000000000000000 - 000000000009fc00 = 1 RAM
(XEN) HVM2:   1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(XEN) HVM2:   2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(XEN) HVM2:   3: 0000000000100000 - 0000000077fff000 = 1 RAM
(XEN) HVM2:   4: 0000000077fff000 - 0000000078000000 = 2 RESERVED
(XEN) HVM2:   5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(XEN) HVM2: enter handle_19:
(XEN) HVM2:   NULL
(XEN) HVM2: Booting from DVD/CD...
(XEN) HVM2: Device reports MEDIUM NOT PRESENT
(XEN) HVM2: scsi_is_ready returned -1
(XEN) HVM2: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM2: enter handle_18:
(XEN) HVM2:   NULL
(XEN) HVM2: Booting from DVD/CD...
(XEN) HVM2: Device reports MEDIUM NOT PRESENT
(XEN) HVM2: scsi_is_ready returned -1
(XEN) HVM2: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM2: enter handle_18:
(XEN) HVM2:   NULL
(XEN) HVM2: Booting from Hard Disk...
(XEN) HVM2: Booting from 0000:7c00
(XEN) irq.c:270: Dom2 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom2 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom2 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom2 PCI link 3 changed 5 -> 0
(XEN) grant_table.c:1250:d2 Expanding dom (2) grant table from (4) to (32) frames.
(XEN) irq.c:375: Dom2 callback via changed to GSI 28
(XEN) HVM3: HVM Loader
(XEN) HVM3: Detected Xen v4.3-unstable
(XEN) HVM3: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM3: System requested SeaBIOS
(XEN) HVM3: CPU speed is 2661 MHz
(XEN) irq.c:270: Dom3 PCI link 0 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom3 PCI link 1 changed 0 -> 10
(XEN) HVM3: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom3 PCI link 2 changed 0 -> 11
(XEN) HVM3: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom3 PCI link 3 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 3 routed to IRQ5
(XEN) HVM3: pci dev 01:3 INTA->IRQ10
(XEN) HVM3: pci dev 03:0 INTA->IRQ5
(XEN) HVM3: pci dev 04:0 INTA->IRQ5
(XEN) HVM3: pci dev 05:0 INTA->IRQ10
(XEN) HVM3: pci dev 06:0 INTA->IRQ11
(XEN) HVM3: pci dev 1d:0 INTA->IRQ10
(XEN) HVM3: pci dev 1d:1 INTB->IRQ11
(XEN) HVM3: pci dev 1d:2 INTC->IRQ5
(XEN) HVM3: pci dev 1d:7 INTD->IRQ5
(XEN) HVM3: pci dev 02:0 bar 10 size lx: 01000000
(XEN) HVM3: pci dev 03:0 bar 14 size lx: 01000000
(XEN) HVM3: pci dev 02:0 bar 30 size lx: 00010000
(XEN) HVM3: pci dev 06:0 bar 30 size lx: 00010000
(XEN) HVM3: pci dev 04:0 bar 10 size lx: 00004000
(XEN) HVM3: pci dev 02:0 bar 18 size lx: 00001000
(XEN) HVM3: pci dev 05:0 bar 14 size lx: 00001000
(XEN) HVM3: pci dev 1d:7 bar 10 size lx: 00001000
(XEN) HVM3: pci dev 03:0 bar 10 size lx: 00000100
(XEN) HVM3: pci dev 06:0 bar 10 size lx: 00000100
(XEN) HVM3: pci dev 06:0 bar 14 size lx: 00000100
(XEN) HVM3: pci dev 05:0 bar 10 size lx: 00000020
(XEN) HVM3: pci dev 1d:0 bar 20 size lx: 00000020
(XEN) HVM3: pci dev 1d:1 bar 20 size lx: 00000020
(XEN) HVM3: pci dev 1d:2 bar 20 size lx: 00000020
(XEN) HVM3: pci dev 01:1 bar 20 size lx: 00000010
(XEN) HVM3: Multiprocessor initialisation:
(XEN) HVM3:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM3:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM3: Testing HVM environment:
(XEN) HVM3:  - REP INSB across page boundaries ... passed
(XEN) HVM3:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM3: Passed 2 of 2 tests
(XEN) HVM3: Writing SMBIOS tables ...
(XEN) HVM3: Loading SeaBIOS ...
(XEN) HVM3: Creating MP tables ...
(XEN) HVM3: Loading ACPI ...
(XEN) HVM3: vm86 TSS at fc00a080
(XEN) HVM3: BIOS map:
(XEN) HVM3:  10000-100d3: Scratch space
(XEN) HVM3:  e0000-fffff: Main BIOS
(XEN) HVM3: E820 table:
(XEN) HVM3:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM3:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM3:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM3:  [02]: 00000000:00100000 - 00000000:7f000000: RAM
(XEN) HVM3:  HOLE: 00000000:7f000000 - 00000000:fc000000
(XEN) HVM3:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM3: Invoking SeaBIOS ...
(XEN) HVM3: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM3: 
(XEN) HVM3: Found Xen hypervisor signature at 40000000
(XEN) HVM3: xen: copy e820...
(XEN) HVM3: Ram Size=0x7f000000 (0x0000000000000000 high)
(XEN) HVM3: Relocating low data from 0x000e1890 to 0x000ef780 (size 2161)
(XEN) HVM3: Relocating init from 0x000e2101 to 0x7efe0aa0 (size 62523)
(XEN) HVM3: CPU Mhz=2661
(XEN) HVM3: Found 13 PCI devices (max PCI bus is 00)
(XEN) HVM3: Allocated Xen hypercall page at 7efff000
(XEN) HVM3: Detected Xen v4.3-unstable
(XEN) HVM3: Found 2 cpu(s) max supported 2 cpu(s)
(XEN) HVM3: xen: copy BIOS tables...
(XEN) HVM3: Copying SMBIOS entry point from 0x00010010 to 0x000fdbd0
(XEN) HVM3: Copying MPTABLE from 0xfc001170/fc001180 to 0x000fdad0
(XEN) HVM3: Copying PIR from 0x00010030 to 0x000fda50
(XEN) HVM3: Copying ACPI RSDP from 0x000100b0 to 0x000fda20
(XEN) HVM3: Scan for VGA option rom
(XEN) HVM3: Running option rom at c000:0003
(XEN) stdvga.c:147:d3 entering stdvga and caching modes
(XEN) HVM3: Turning on vga text mode console
(XEN) HVM3: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM3: Machine UUID a0d1a6ac-4703-41ee-82c5-7073a7451c32
(XEN) HVM3: EHCI init on dev 00:1d.7 (regs=0xf2026020)
(XEN) HVM3: Found 1 lpt ports
(XEN) HVM3: Found 1 serial ports
(XEN) HVM3: ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
(XEN) HVM3: ATA controller 2 at 170/374/0 (irq 15 dev 9)
(XEN) HVM3: ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (50000 MiBytes)
(XEN) HVM3: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(XEN) HVM3: DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM3: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
(XEN) HVM3: DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM3: Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@0
(XEN) HVM3: PS2 keyboard initialized
(XEN) HVM3: All threads complete.
(XEN) HVM3: Scan for option roms
(XEN) HVM3: Running option rom at ca80:0003
(XEN) HVM3: pmm call arg1=1
(XEN) HVM3: pmm call arg1=0
(XEN) HVM3: pmm call arg1=1
(XEN) HVM3: pmm call arg1=0
(XEN) HVM3: Searching bootorder for: /pci@i0cf8/*@6
(XEN) HVM3: 
(XEN) HVM3: Press F12 for boot menu.
(XEN) HVM3: 
(XEN) HVM3: Searching bootorder for: HALT
(XEN) HVM3: drive 0x000fd9d0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=10240000
(XEN) HVM3: 0
(XEN) HVM3: Space available for UMB: 000cb800-000ee800
(XEN) HVM3: Returned 61440 bytes of ZoneHigh
(XEN) HVM3: e820 map has 6 items:
(XEN) HVM3:   0: 0000000000000000 - 000000000009fc00 = 1 RAM
(XEN) HVM3:   1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(XEN) HVM3:   2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(XEN) HVM3:   3: 0000000000100000 - 000000007efff000 = 1 RAM
(XEN) HVM3:   4: 000000007efff000 - 000000007f000000 = 2 RESERVED
(XEN) HVM3:   5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(XEN) HVM3: enter handle_19:
(XEN) HVM3:   NULL
(XEN) HVM3: Booting from DVD/CD...
(XEN) HVM3: Device reports MEDIUM NOT PRESENT
(XEN) HVM3: scsi_is_ready returned -1
(XEN) HVM3: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM3: enter handle_18:
(XEN) HVM3:   NULL
(XEN) HVM3: Booting from DVD/CD...
(XEN) HVM3: Device reports MEDIUM NOT PRESENT
(XEN) HVM3: scsi_is_ready returned -1
(XEN) HVM3: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM3: enter handle_18:
(XEN) HVM3:   NULL
(XEN) HVM3: Booting from Hard Disk...
(XEN) HVM3: Booting from 0000:7c00
(XEN) irq.c:270: Dom3 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom3 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom3 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom3 PCI link 3 changed 5 -> 0
(XEN) grant_table.c:1250:d3 Expanding dom (3) grant table from (4) to (32) frames.
(XEN) irq.c:375: Dom3 callback via changed to GSI 28
(XEN) irq.c:375: Dom3 callback via changed to None
(XEN) HVM3 save: CPU
(XEN) HVM3 save: PIC
(XEN) HVM3 save: IOAPIC
(XEN) HVM3 save: LAPIC
(XEN) HVM3 save: LAPIC_REGS
(XEN) HVM3 save: PCI_IRQ
(XEN) HVM3 save: ISA_IRQ
(XEN) HVM3 save: PCI_LINK
(XEN) HVM3 save: PIT
(XEN) HVM3 save: RTC
(XEN) HVM3 save: HPET
(XEN) HVM3 save: PMTIMER
(XEN) HVM3 save: MTRR
(XEN) HVM3 save: VIRIDIAN_DOMAIN
(XEN) HVM3 save: CPU_XSAVE
(XEN) HVM3 save: VIRIDIAN_VCPU
(XEN) HVM3 save: VMCE_VCPU
(XEN) HVM3 save: TSC_ADJUST
(XEN) HVM4 restore: CPU 0
(XEN) HVM4 restore: CPU 1
(XEN) HVM4 restore: PIC 0
(XEN) HVM4 restore: PIC 1
(XEN) HVM4 restore: IOAPIC 0
(XEN) HVM4 restore: LAPIC 0
(XEN) HVM4 restore: LAPIC 1
(XEN) HVM4 restore: LAPIC_REGS 0
(XEN) HVM4 restore: LAPIC_REGS 1
(XEN) HVM4 restore: PCI_IRQ 0
(XEN) HVM4 restore: ISA_IRQ 0
(XEN) HVM4 restore: PCI_LINK 0
(XEN) HVM4 restore: PIT 0
(XEN) HVM4 restore: RTC 0
(XEN) HVM4 restore: HPET 0
(XEN) HVM4 restore: PMTIMER 0
(XEN) HVM4 restore: MTRR 0
(XEN) HVM4 restore: MTRR 1
(XEN) HVM4 restore: VMCE_VCPU 0
(XEN) HVM4 restore: VMCE_VCPU 1
(XEN) HVM4 restore: TSC_ADJUST 0
(XEN) HVM4 restore: TSC_ADJUST 1
(XEN) memory.c:188:d4 Domain 4 page number 7e0c8 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0c9 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0ca invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0cb invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0cc invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0cd invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0ce invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0cf invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d0 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d1 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d2 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d3 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d4 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d5 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d6 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d7 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d8 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0d9 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0da invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0db invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0dc invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0dd invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0de invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0df invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0e0 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0e1 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0e2 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0e3 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0e4 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0e5 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0e6 invalid
(XEN) memory.c:188:d4 Domain 4 page number 7e0e7 invalid
(XEN) grant_table.c:1250:d4 Expanding dom (4) grant table from (4) to (32) frames.
(XEN) irq.c:375: Dom4 callback via changed to GSI 28
(XEN) irq.c:375: Dom4 callback via changed to None
(XEN) HVM4 save: CPU
(XEN) HVM4 save: PIC
(XEN) HVM4 save: IOAPIC
(XEN) HVM4 save: LAPIC
(XEN) HVM4 save: LAPIC_REGS
(XEN) HVM4 save: PCI_IRQ
(XEN) HVM4 save: ISA_IRQ
(XEN) HVM4 save: PCI_LINK
(XEN) HVM4 save: PIT
(XEN) HVM4 save: RTC
(XEN) HVM4 save: HPET
(XEN) HVM4 save: PMTIMER
(XEN) HVM4 save: MTRR
(XEN) HVM4 save: VIRIDIAN_DOMAIN
(XEN) HVM4 save: CPU_XSAVE
(XEN) HVM4 save: VIRIDIAN_VCPU
(XEN) HVM4 save: VMCE_VCPU
(XEN) HVM4 save: TSC_ADJUST
(XEN) HVM5 restore: CPU 0
(XEN) HVM5 restore: CPU 1
(XEN) HVM5 restore: PIC 0
(XEN) HVM5 restore: PIC 1
(XEN) HVM5 restore: IOAPIC 0
(XEN) HVM5 restore: LAPIC 0
(XEN) HVM5 restore: LAPIC 1
(XEN) HVM5 restore: LAPIC_REGS 0
(XEN) HVM5 restore: LAPIC_REGS 1
(XEN) HVM5 restore: PCI_IRQ 0
(XEN) HVM5 restore: ISA_IRQ 0
(XEN) HVM5 restore: PCI_LINK 0
(XEN) HVM5 restore: PIT 0
(XEN) HVM5 restore: RTC 0
(XEN) HVM5 restore: HPET 0
(XEN) HVM5 restore: PMTIMER 0
(XEN) HVM5 restore: MTRR 0
(XEN) HVM5 restore: MTRR 1
(XEN) HVM5 restore: VMCE_VCPU 0
(XEN) HVM5 restore: VMCE_VCPU 1
(XEN) HVM5 restore: TSC_ADJUST 0
(XEN) HVM5 restore: TSC_ADJUST 1
(XEN) memory.c:188:d5 Domain 5 page number 7e0c8 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0c9 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0ca invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0cb invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0cc invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0cd invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0ce invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0cf invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d0 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d1 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d2 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d3 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d4 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d5 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d6 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d7 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d8 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0d9 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0da invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0db invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0dc invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0dd invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0de invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0df invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0e0 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0e1 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0e2 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0e3 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0e4 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0e5 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0e6 invalid
(XEN) memory.c:188:d5 Domain 5 page number 7e0e7 invalid
(XEN) grant_table.c:1250:d5 Expanding dom (5) grant table from (4) to (32) frames.
(XEN) irq.c:375: Dom5 callback via changed to GSI 28
(XEN) HVM6: HVM Loader
(XEN) HVM6: Detected Xen v4.3-unstable
(XEN) HVM6: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM6: System requested SeaBIOS
(XEN) HVM6: CPU speed is 2661 MHz
(XEN) irq.c:270: Dom6 PCI link 0 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom6 PCI link 1 changed 0 -> 10
(XEN) HVM6: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom6 PCI link 2 changed 0 -> 11
(XEN) HVM6: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom6 PCI link 3 changed 0 -> 5
(XEN) HVM6: PCI-ISA link 3 routed to IRQ5
(XEN) HVM6: pci dev 01:3 INTA->IRQ10
(XEN) HVM6: pci dev 03:0 INTA->IRQ5
(XEN) HVM6: pci dev 04:0 INTA->IRQ5
(XEN) HVM6: pci dev 05:0 INTA->IRQ10
(XEN) HVM6: pci dev 06:0 INTA->IRQ11
(XEN) HVM6: pci dev 1d:0 INTA->IRQ10
(XEN) HVM6: pci dev 1d:1 INTB->IRQ11
(XEN) HVM6: pci dev 1d:2 INTC->IRQ5
(XEN) HVM6: pci dev 1d:7 INTD->IRQ5
(XEN) HVM6: pci dev 02:0 bar 10 size lx: 01000000
(XEN) HVM6: pci dev 03:0 bar 14 size lx: 01000000
(XEN) HVM6: pci dev 02:0 bar 30 size lx: 00010000
(XEN) HVM6: pci dev 06:0 bar 30 size lx: 00010000
(XEN) HVM6: pci dev 04:0 bar 10 size lx: 00004000
(XEN) HVM6: pci dev 02:0 bar 18 size lx: 00001000
(XEN) HVM6: pci dev 05:0 bar 14 size lx: 00001000
(XEN) HVM6: pci dev 1d:7 bar 10 size lx: 00001000
(XEN) HVM6: pci dev 03:0 bar 10 size lx: 00000100
(XEN) HVM6: pci dev 06:0 bar 10 size lx: 00000100
(XEN) HVM6: pci dev 06:0 bar 14 size lx: 00000100
(XEN) HVM6: pci dev 05:0 bar 10 size lx: 00000020
(XEN) HVM6: pci dev 1d:0 bar 20 size lx: 00000020
(XEN) HVM6: pci dev 1d:1 bar 20 size lx: 00000020
(XEN) HVM6: pci dev 1d:2 bar 20 size lx: 00000020
(XEN) HVM6: pci dev 01:1 bar 20 size lx: 00000010
(XEN) HVM6: Multiprocessor initialisation:
(XEN) HVM6:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM6: Testing HVM environment:
(XEN) HVM6:  - REP INSB across page boundaries ... passed
(XEN) HVM6:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM6: Passed 2 of 2 tests
(XEN) HVM6: Writing SMBIOS tables ...
(XEN) HVM6: Loading SeaBIOS ...
(XEN) HVM6: Creating MP tables ...
(XEN) HVM6: Loading ACPI ...
(XEN) HVM6: vm86 TSS at fc00a080
(XEN) HVM6: BIOS map:
(XEN) HVM6:  10000-100d3: Scratch space
(XEN) HVM6:  e0000-fffff: Main BIOS
(XEN) HVM6: E820 table:
(XEN) HVM6:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM6:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM6:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM6:  [02]: 00000000:00100000 - 00000000:7f000000: RAM
(XEN) HVM6:  HOLE: 00000000:7f000000 - 00000000:fc000000
(XEN) HVM6:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM6: Invoking SeaBIOS ...
(XEN) HVM6: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM6: 
(XEN) HVM6: Found Xen hypervisor signature at 40000000
(XEN) HVM6: xen: copy e820...
(XEN) HVM6: Ram Size=0x7f000000 (0x0000000000000000 high)
(XEN) HVM6: Relocating low data from 0x000e1890 to 0x000ef780 (size 2161)
(XEN) HVM6: Relocating init from 0x000e2101 to 0x7efe0aa0 (size 62523)
(XEN) HVM6: CPU Mhz=2662
(XEN) HVM6: Found 13 PCI devices (max PCI bus is 00)
(XEN) HVM6: Allocated Xen hypercall page at 7efff000
(XEN) HVM6: Detected Xen v4.3-unstable
(XEN) HVM6: Found 2 cpu(s) max supported 2 cpu(s)
(XEN) HVM6: xen: copy BIOS tables...
(XEN) HVM6: Copying SMBIOS entry point from 0x00010010 to 0x000fdbd0
(XEN) HVM6: Copying MPTABLE from 0xfc001170/fc001180 to 0x000fdad0
(XEN) HVM6: Copying PIR from 0x00010030 to 0x000fda50
(XEN) HVM6: Copying ACPI RSDP from 0x000100b0 to 0x000fda20
(XEN) HVM6: Scan for VGA option rom
(XEN) HVM6: Running option rom at c000:0003
(XEN) stdvga.c:147:d6 entering stdvga and caching modes
(XEN) HVM6: Turning on vga text mode console
(XEN) HVM6: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM6: Machine UUID e723180e-a50d-4f97-8606-8be46708a71f
(XEN) HVM6: EHCI init on dev 00:1d.7 (regs=0xf2026020)
(XEN) HVM6: Found 1 lpt ports
(XEN) HVM6: Found 1 serial ports
(XEN) HVM6: ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
(XEN) HVM6: ATA controller 2 at 170/374/0 (irq 15 dev 9)
(XEN) HVM6: ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (50000 MiBytes)
(XEN) HVM6: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(XEN) HVM6: DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM6: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
(XEN) HVM6: DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM6: Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@0
(XEN) HVM6: PS2 keyboard initialized
(XEN) HVM6: All threads complete.
(XEN) HVM6: Scan for option roms
(XEN) HVM6: Running option rom at ca80:0003
(XEN) HVM6: pmm call arg1=1
(XEN) HVM6: pmm call arg1=0
(XEN) HVM6: pmm call arg1=1
(XEN) HVM6: pmm call arg1=0
(XEN) HVM6: Searching bootorder for: /pci@i0cf8/*@6
(XEN) HVM6: 
(XEN) HVM6: Press F12 for boot menu.
(XEN) HVM6: 
(XEN) HVM6: Searching bootorder for: HALT
(XEN) HVM6: drive 0x000fd9d0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=10240000
(XEN) HVM6: 0
(XEN) HVM6: Space available for UMB: 000cb800-000ee800
(XEN) HVM6: Returned 61440 bytes of ZoneHigh
(XEN) HVM6: e820 map has 6 items:
(XEN) HVM6:   0: 0000000000000000 - 000000000009fc00 = 1 RAM
(XEN) HVM6:   1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(XEN) HVM6:   2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(XEN) HVM6:   3: 0000000000100000 - 000000007efff000 = 1 RAM
(XEN) HVM6:   4: 000000007efff000 - 000000007f000000 = 2 RESERVED
(XEN) HVM6:   5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(XEN) HVM6: enter handle_19:
(XEN) HVM6:   NULL
(XEN) HVM6: Booting from DVD/CD...
(XEN) HVM6: Device reports MEDIUM NOT PRESENT
(XEN) HVM6: scsi_is_ready returned -1
(XEN) HVM6: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM6: enter handle_18:
(XEN) HVM6:   NULL
(XEN) HVM6: Booting from DVD/CD...
(XEN) HVM6: Device reports MEDIUM NOT PRESENT
(XEN) HVM6: scsi_is_ready returned -1
(XEN) HVM6: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM6: enter handle_18:
(XEN) HVM6:   NULL
(XEN) HVM6: Booting from Hard Disk...
(XEN) HVM6: Booting from 0000:7c00
(XEN) irq.c:270: Dom6 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom6 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom6 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom6 PCI link 3 changed 5 -> 0
(XEN) grant_table.c:1250:d6 Expanding dom (6) grant table from (4) to (32) frames.
(XEN) irq.c:375: Dom6 callback via changed to GSI 28
(XEN) HVM7: HVM Loader
(XEN) HVM7: Detected Xen v4.3-unstable
(XEN) HVM7: Xenbus rings @0xfeffc000, event channel 4
(XEN) HVM7: System requested SeaBIOS
(XEN) HVM7: CPU speed is 2661 MHz
(XEN) irq.c:270: Dom7 PCI link 0 changed 0 -> 5
(XEN) HVM7: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom7 PCI link 1 changed 0 -> 10
(XEN) HVM7: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:270: Dom7 PCI link 2 changed 0 -> 11
(XEN) HVM7: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:270: Dom7 PCI link 3 changed 0 -> 5
(XEN) HVM7: PCI-ISA link 3 routed to IRQ5
(XEN) HVM7: pci dev 01:3 INTA->IRQ10
(XEN) HVM7: pci dev 03:0 INTA->IRQ5
(XEN) HVM7: pci dev 04:0 INTA->IRQ5
(XEN) HVM7: pci dev 05:0 INTA->IRQ10
(XEN) HVM7: pci dev 06:0 INTA->IRQ11
(XEN) HVM7: pci dev 1d:0 INTA->IRQ10
(XEN) HVM7: pci dev 1d:1 INTB->IRQ11
(XEN) HVM7: pci dev 1d:2 INTC->IRQ5
(XEN) HVM7: pci dev 1d:7 INTD->IRQ5
(XEN) HVM7: pci dev 02:0 bar 10 size lx: 01000000
(XEN) HVM7: pci dev 03:0 bar 14 size lx: 01000000
(XEN) HVM7: pci dev 02:0 bar 30 size lx: 00010000
(XEN) HVM7: pci dev 06:0 bar 30 size lx: 00010000
(XEN) HVM7: pci dev 04:0 bar 10 size lx: 00004000
(XEN) HVM7: pci dev 02:0 bar 18 size lx: 00001000
(XEN) HVM7: pci dev 05:0 bar 14 size lx: 00001000
(XEN) HVM7: pci dev 1d:7 bar 10 size lx: 00001000
(XEN) HVM7: pci dev 03:0 bar 10 size lx: 00000100
(XEN) HVM7: pci dev 06:0 bar 10 size lx: 00000100
(XEN) HVM7: pci dev 06:0 bar 14 size lx: 00000100
(XEN) HVM7: pci dev 05:0 bar 10 size lx: 00000020
(XEN) HVM7: pci dev 1d:0 bar 20 size lx: 00000020
(XEN) HVM7: pci dev 1d:1 bar 20 size lx: 00000020
(XEN) HVM7: pci dev 1d:2 bar 20 size lx: 00000020
(XEN) HVM7: pci dev 01:1 bar 20 size lx: 00000010
(XEN) HVM7: Multiprocessor initialisation:
(XEN) HVM7:  - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM7:  - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done.
(XEN) HVM7: Testing HVM environment:
(XEN) HVM7:  - REP INSB across page boundaries ... passed
(XEN) HVM7:  - GS base MSRs and SWAPGS ... passed
(XEN) HVM7: Passed 2 of 2 tests
(XEN) HVM7: Writing SMBIOS tables ...
(XEN) HVM7: Loading SeaBIOS ...
(XEN) HVM7: Creating MP tables ...
(XEN) HVM7: Loading ACPI ...
(XEN) HVM7: vm86 TSS at fc00a080
(XEN) HVM7: BIOS map:
(XEN) HVM7:  10000-100d3: Scratch space
(XEN) HVM7:  e0000-fffff: Main BIOS
(XEN) HVM7: E820 table:
(XEN) HVM7:  [00]: 00000000:00000000 - 00000000:000a0000: RAM
(XEN) HVM7:  HOLE: 00000000:000a0000 - 00000000:000e0000
(XEN) HVM7:  [01]: 00000000:000e0000 - 00000000:00100000: RESERVED
(XEN) HVM7:  [02]: 00000000:00100000 - 00000000:7f000000: RAM
(XEN) HVM7:  HOLE: 00000000:7f000000 - 00000000:fc000000
(XEN) HVM7:  [03]: 00000000:fc000000 - 00000001:00000000: RESERVED
(XEN) HVM7: Invoking SeaBIOS ...
(XEN) HVM7: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM7: 
(XEN) HVM7: Found Xen hypervisor signature at 40000000
(XEN) HVM7: xen: copy e820...
(XEN) HVM7: Ram Size=0x7f000000 (0x0000000000000000 high)
(XEN) HVM7: Relocating low data from 0x000e1890 to 0x000ef780 (size 2161)
(XEN) HVM7: Relocating init from 0x000e2101 to 0x7efe0aa0 (size 62523)
(XEN) HVM7: CPU Mhz=2661
(XEN) HVM7: Found 13 PCI devices (max PCI bus is 00)
(XEN) HVM7: Allocated Xen hypercall page at 7efff000
(XEN) HVM7: Detected Xen v4.3-unstable
(XEN) HVM7: Found 2 cpu(s) max supported 2 cpu(s)
(XEN) HVM7: xen: copy BIOS tables...
(XEN) HVM7: Copying SMBIOS entry point from 0x00010010 to 0x000fdbd0
(XEN) HVM7: Copying MPTABLE from 0xfc001170/fc001180 to 0x000fdad0
(XEN) HVM7: Copying PIR from 0x00010030 to 0x000fda50
(XEN) HVM7: Copying ACPI RSDP from 0x000100b0 to 0x000fda20
(XEN) HVM7: Scan for VGA option rom
(XEN) HVM7: Running option rom at c000:0003
(XEN) stdvga.c:147:d7 entering stdvga and caching modes
(XEN) HVM7: Turning on vga text mode console
(XEN) HVM7: SeaBIOS (version debian/1.7.2-2-0-g314321f-dirty-20130522_100712-vfarm)
(XEN) HVM7: Machine UUID 02ad3881-427e-43b9-909d-9df6638da1e0
(XEN) HVM7: EHCI init on dev 00:1d.7 (regs=0xf2026020)
(XEN) HVM7: Found 1 lpt ports
(XEN) HVM7: Found 1 serial ports
(XEN) HVM7: ATA controller 1 at 1f0/3f4/0 (irq 14 dev 9)
(XEN) HVM7: ATA controller 2 at 170/374/0 (irq 15 dev 9)
(XEN) HVM7: ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (50000 MiBytes)
(XEN) HVM7: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@0
(XEN) HVM7: DVD/CD [ata0-1: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM7: Searching bootorder for: /pci@i0cf8/*@1,1/drive@0/disk@1
(XEN) HVM7: DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD]
(XEN) HVM7: Searching bootorder for: /pci@i0cf8/*@1,1/drive@1/disk@0
(XEN) HVM7: PS2 keyboard initialized
(XEN) HVM7: All threads complete.
(XEN) HVM7: Scan for option roms
(XEN) HVM7: Running option rom at ca80:0003
(XEN) HVM7: pmm call arg1=1
(XEN) HVM7: pmm call arg1=0
(XEN) HVM7: pmm call arg1=1
(XEN) HVM7: pmm call arg1=0
(XEN) HVM7: Searching bootorder for: /pci@i0cf8/*@6
(XEN) HVM7: 
(XEN) HVM7: Press F12 for boot menu.
(XEN) HVM7: 
(XEN) HVM7: Searching bootorder for: HALT
(XEN) HVM7: drive 0x000fd9d0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=10240000
(XEN) HVM7: 0
(XEN) HVM7: Space available for UMB: 000cb800-000ee800
(XEN) HVM7: Returned 61440 bytes of ZoneHigh
(XEN) HVM7: e820 map has 6 items:
(XEN) HVM7:   0: 0000000000000000 - 000000000009fc00 = 1 RAM
(XEN) HVM7:   1: 000000000009fc00 - 00000000000a0000 = 2 RESERVED
(XEN) HVM7:   2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
(XEN) HVM7:   3: 0000000000100000 - 000000007efff000 = 1 RAM
(XEN) HVM7:   4: 000000007efff000 - 000000007f000000 = 2 RESERVED
(XEN) HVM7:   5: 00000000fc000000 - 0000000100000000 = 2 RESERVED
(XEN) HVM7: enter handle_19:
(XEN) HVM7:   NULL
(XEN) HVM7: Booting from DVD/CD...
(XEN) HVM7: Device reports MEDIUM NOT PRESENT
(XEN) HVM7: scsi_is_ready returned -1
(XEN) HVM7: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM7: enter handle_18:
(XEN) HVM7:   NULL
(XEN) HVM7: Booting from DVD/CD...
(XEN) HVM7: Device reports MEDIUM NOT PRESENT
(XEN) HVM7: scsi_is_ready returned -1
(XEN) HVM7: Boot failed: Could not read from CDROM (code 0003)
(XEN) HVM7: enter handle_18:
(XEN) HVM7:   NULL
(XEN) HVM7: Booting from Hard Disk...
(XEN) HVM7: Booting from 0000:7c00
(XEN) irq.c:270: Dom7 PCI link 0 changed 5 -> 0
(XEN) irq.c:270: Dom7 PCI link 1 changed 10 -> 0
(XEN) irq.c:270: Dom7 PCI link 2 changed 11 -> 0
(XEN) irq.c:270: Dom7 PCI link 3 changed 5 -> 0
(XEN) grant_table.c:1250:d7 Expanding dom (7) grant table from (4) to (32) frames.
(XEN) irq.c:375: Dom7 callback via changed to GSI 28

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

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

Re: Test report for xen-unstable and qemu-xen

[George Dunlap]

On 23/05/13 11:08, Fabio Fantoni wrote:
> Il 22/05/2013 18:37, Pasi Kärkkäinen ha scritto:
>> On Wed, May 22, 2013 at 04:48:04PM +0200, Fabio Fantoni wrote:
>>> -------------
>>> - nested hvm probably bugged: started test it on windows 7 pro 64
>>> domU on qemu-xen,
>>>    xpmode crash on install without show error, no error on logs and
>>> havdetection works
>>> -------------
>> I think earlier you were asked to open a new thread about this nested 
>> hvm issue.
>> Also you've not provided enough information:
>>
>>     - What hardware are you using? Intel or AMD? Which CPU model?
> Intel Xeon X3450
>>     - Any errors in the hypervisor dmesg (xl dmesg) ?
> See attachment
>>     - Any errors in qemu log files?
> No error on qemu logs about this problem
>>     - Is it the xpmode guest that crashes, or is it the whole win7 
>> that crashes?
> The xpmode guest crashes during installation without show errors.

Fabio,

Please make a new e-mail with all this information, and a descriptive 
subject line (e.g., "Bug: Nested virtualization: Win7 pro 64-bit XP mode 
fails on xen-4.3-rc2") and cc the Intel maintainers listed below.

M:    Jun Nakajima <jun.nakajima@intel.com>
M:    Eddie Dong <eddie.dong@intel.com>

Thanks,
  -George

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

[-- Attachment #1.1: Type: text/plain, Size: 1735 bytes --]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.41-2, package blktap-dkms and all dependency packages for xen, spice 
and usb redirection.
-------------------------
/etc/modules
------------
loop max_loop=64
xenfs
xen-evtchn
blktap
-------------------------
git clone git://xenbits.xen.org/xen.git (in this build commit is 
6f3059e0e05b72c3cc7246f3e6e81f80761b98cb)
-------------------------
Added some patches:
- tools-configure-qemu-for-spice-and-usbredir
- libxl-Add-spice-vdagent-support-for-upstream-qemu
- tools-firmware-seabios-packaged
- tools: Improve make deb
- vgabios-stdvga.bin custom build from Frediano
- qemu-xen change for support other resolutions:
hw/vga.c:
     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
-------------------------
./configure --prefix=/usr
-------------------------
make debball

-------------------------
Issues solved from my previous test build report:
-------------
- xl cd-eject/cd-insert now are working
-------------------------

-------------------------
New issue:
- nested hvm probably bugged: started test it on windows 7 pro 64 domU 
on qemu-xen,
   xpmode crash on install without show any error, nor error on logs 
even if havdetection
   completes  with success
-------------

-------------------------

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
   Workaround: fixed mac address since it changes after each restore
-------------
- Unable to get QXL vga working correctly (probably need hvmloader 
changes/fixes)
-------------------------


[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Test report for xen-unstable and qemu-xen

[Pasi Kärkkäinen]

On Wed, May 08, 2013 at 04:46:15PM +0200, Fabio Fantoni wrote:
> Added some patches:
> - tools-configure-qemu-for-spice-and-usbredir
>

So extra patches are still needed for Xen 4.3.0-rc1 qemu makefiles 
to build with spice-support enabled? 


> - tools-firmware-seabios-packaged
>

What's this patch, what does it change? 


> - tools: Improve make deb
>

Is this needed in upstream Xen? 


> - vgabios-stdvga.bin custom build from Frediano
>

What are the vgabios changes here? Why do you need them? 


> - qemu-xen change for support other resolutions:
> hw/vga.c:
>     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
>     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
>

Hmm.. has this been submitted for inclusion in qemu-xen ? 


> 
> -------------------------
> New issue:
> - nested hvm probably bugged: started test it on windows 7 pro 64
> domU on qemu-xen,
>   xpmode crash on install without show any error, nor error on logs
> even if havdetection
>   completes  with success
> -------------
> 

George: Should we track this nested hvm issue on the Xen 4.3 status emails? 


> -------------------------
> Old issue:
> - Network is not working after restore on Windows domU with qemu-xen
> and gplpv
>   Workaround: fixed mac address since it changes after each restore
>

And also this one? 

> -------------
> - Unable to get QXL vga working correctly (probably need hvmloader
> changes/fixes)
> -------------------------
> 

And probably this one too.. is anyone currently looking at fixing hvmloader 
to work with QXL ? (or whatever is causing the problem here..) 


-- Pasi

Re: Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

[-- Attachment #1.1: Type: text/plain, Size: 3092 bytes --]

Il 09/05/2013 14:15, Pasi Kärkkäinen ha scritto:
> On Wed, May 08, 2013 at 04:46:15PM +0200, Fabio Fantoni wrote:
>> Added some patches:
>> - tools-configure-qemu-for-spice-and-usbredir
>>
> So extra patches are still needed for Xen 4.3.0-rc1 qemu makefiles
> to build with spice-support enabled?
I did and posted the patch about one year ago but all versions was rejected
>
>
>> - tools-firmware-seabios-packaged
>>
> What's this patch, what does it change?
Is to use debian package.
About upstream is needed to adding options on configure in order to use 
seabios and qemu upstream from distribution packages instead of building 
them.
I did fast check time ago without success. I don't know how to do it 
with configure parameters and qemu build (on libxl I not found exactly 
how to point an external binary package).
>
>
>> - tools: Improve make deb
>>
> Is this needed in upstream Xen?
I thing is very useful, it helps me to save a lot of time onhundreds of 
tests build that I've done.
I think that now without this make debball is unusable, I think that 
atleast these parts must be applied:
- Remove version from installed package name for correct update
- Add conffiles to manage main config files on package update

I already posted it but rejected :(
http://lists.xen.org/archives/html/xen-devel/2013-02/msg02483.html

>
>
>> - vgabios-stdvga.bin custom build from Frediano
>>
> What are the vgabios changes here? Why do you need them?
For support some rosolution (for example the 1366x768, for now are 
supported only by qxl but qxl is not working for now)
>
>
>> - qemu-xen change for support other resolutions:
>> hw/vga.c:
>>      - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
>>      + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
>>
> Hmm.. has this been submitted for inclusion in qemu-xen ?
Frediano posted it on qemu-devel time ago but it was not added for now.
>
>> -------------------------
>> New issue:
>> - nested hvm probably bugged: started test it on windows 7 pro 64
>> domU on qemu-xen,
>>    xpmode crash on install without show any error, nor error on logs
>> even if havdetection
>>    completes  with success
>> -------------
>>
> George: Should we track this nested hvm issue on the Xen 4.3 status emails?
>
>
>> -------------------------
>> Old issue:
>> - Network is not working after restore on Windows domU with qemu-xen
>> and gplpv
>>    Workaround: fixed mac address since it changes after each restore
>>
> And also this one?
>
>> -------------
>> - Unable to get QXL vga working correctly (probably need hvmloader
>> changes/fixes)
>> -------------------------
>>
> And probably this one too.. is anyone currently looking at fixing hvmloader
> to work with QXL ? (or whatever is causing the problem here..)
>
I tried to solve it for more than one year without result, someone more 
than one year ago did patch to xl and qemu to solve 2 videoram bugs but 
recently nothing even if I continued to posted many times about.

> -- Pasi
>
>



[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Test report for xen-unstable and qemu-xen

[George Dunlap]

On 09/05/13 14:28, Fabio Fantoni wrote:
>>
>>
>>> - tools: Improve make deb
>>>
>> Is this needed in upstream Xen?
> I thing is very useful, it helps me to save a lot of time onhundreds 
> of tests build that I've done.
> I think that now without this make debball is unusable, I think that 
> atleast these parts must be applied:
> - Remove version from installed package name for correct update
> - Add conffiles to manage main config files on package update
>
> I already posted it but rejected :(
> http://lists.xen.org/archives/html/xen-devel/2013-02/msg02483.html

Yes, as we said in the discussions, we don't want the output of "make 
debball" useable as a full-fledged Debian package.  The general 
consensus (IIRC) was that we'd be happy if someone were to step up and 
maintain such a set of packages, however.

>>
>>> -------------------------
>>> New issue:
>>> - nested hvm probably bugged: started test it on windows 7 pro 64
>>> domU on qemu-xen,
>>>    xpmode crash on install without show any error, nor error on logs
>>> even if havdetection
>>>    completes  with success
>>> -------------
>>>
>> George: Should we track this nested hvm issue on the Xen 4.3 status 
>> emails?

This needs a proper report -- it doesn't say what cpu is being used.

>>
>>
>>> -------------------------
>>> Old issue:
>>> - Network is not working after restore on Windows domU with qemu-xen
>>> and gplpv
>>>    Workaround: fixed mac address since it changes after each restore
>>>
>> And also this one?

I'll put this on my list.  Not sure if this will be a release blocker, 
we'll see.

  -George

Re: Test report for xen-unstable and qemu-xen

[Ian Campbell]

On Thu, 2013-05-09 at 14:28 +0100, Fabio Fantoni wrote:

> >> -------------
> >> - Unable to get QXL vga working correctly (probably need hvmloader
> >> changes/fixes)
> >> -------------------------
> >>
> > And probably this one too.. is anyone currently looking at fixing hvmloader
> > to work with QXL ? (or whatever is causing the problem here..)
> >
> I tried to solve it for more than one year without result, someone more 
> than one year ago did patch to xl and qemu to solve 2 videoram bugs but 
> recently nothing even if I continued to posted many times about.

I don't understand, IIRC you are the one who contributed QXL VGA support
to libxl/xl (aab4d1b266ce). Are you now saying that it has never worked
for you?

I'm afraid that simply posting about it is unlikely to get the issue
fixed, someone who is interested in QXL (which effectively means you as
far as I can tell) will have to send patches to fix it. Perhaps this
means rebasing and reposting those patches from a year ago or perhaps it
means actually fixing the issues.

Ian.

Re: Test report for xen-unstable and qemu-xen

[George Dunlap]

On Wed, May 8, 2013 at 3:46 PM, Fabio Fantoni <fantonifabio@tiscali.it> wrote:
> Dom0:
> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version
> 3.2.41-2, package blktap-dkms and all dependency packages for xen, spice and
> usb redirection.
> -------------------------
> /etc/modules
> ------------
> loop max_loop=64
> xenfs
> xen-evtchn
> blktap
> -------------------------
> git clone git://xenbits.xen.org/xen.git (in this build commit is
> 6f3059e0e05b72c3cc7246f3e6e81f80761b98cb)
> -------------------------
> Added some patches:
> - tools-configure-qemu-for-spice-and-usbredir
> - libxl-Add-spice-vdagent-support-for-upstream-qemu
> - tools-firmware-seabios-packaged
> - tools: Improve make deb
> - vgabios-stdvga.bin custom build from Frediano
> - qemu-xen change for support other resolutions:
> hw/vga.c:
>     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
>     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
> -------------------------
> ./configure --prefix=/usr
> -------------------------
> make debball
>
> -------------------------
> Issues solved from my previous test build report:
> -------------
> - xl cd-eject/cd-insert now are working
> -------------------------
>
> -------------------------
> New issue:
> - nested hvm probably bugged: started test it on windows 7 pro 64 domU on
> qemu-xen,
>   xpmode crash on install without show any error, nor error on logs even if
> havdetection
>   completes  with success
> -------------

1. I don't see what architecture you're using -- AMD nested virt and
Intel nested virt are completely different codepaths with completely
different maintiners.

2. These kinds of e-mails will work better if you report one bug per
e-mail, and put the key info in the subject line (e.g., Nested HVM: XP
Mode fails on Intel Sandybridge)

It would be even better if you could cc the relevant maintainer, but
that's not something we expect users to be able to do. :-)

 -George

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

[-- Attachment #1.1: Type: text/plain, Size: 1788 bytes --]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.41-2, package blktap-dkms and all dependency packages for xen, spice 
and usb redirection.
-------------------------
/etc/modules
------------
loop max_loop=64
xenfs
xen-evtchn
blktap
-------------------------
git clone git://xenbits.xen.org/xen.git (in this build commit is 
96ef6e88359910738905ac2e1969dc05d7d7e7dc)
-------------------------
Added some patches:
- tools-configure-qemu-for-spice-and-usbredir
- libxl-Add-spice-vdagent-support-for-upstream-qemu
- tools-firmware-seabios-packaged
- tools: Improve make deb
- hotplug: add openvswitch script V3
- vgabios-stdvga.bin custom build from Frediano Ziglio
- qemu-xen change for support other resolutions:
hw/vga.c:
     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
-------------------------
./configure --prefix=/usr
-------------------------
make debball

-------------------------
Issues solved from my previous test build report:
-------------
- ovmf now build also with gcc!=44
-------------
- qemu-xen domU now has no more useless floppy
-------------
- openvswitch now works also with hvm domU
-------------
- stdvga now works also with latest qemu upstream version
-------------------------

-------------------------
Old issue:
- Network is not working after restore on Windows domU with qemu-xen and 
gplpv
-------------
- Unable to get QXL vga working correctly (probably need hvmloader changes)
-------------
- xl cd-eject/cd-insert not working with qemu-xen:
xl cd-eject W7 hdb
libxl: error: libxl_device.c:269:libxl__device_disk_set_backend: no 
suitable backend for disk hdb
-------------------------


[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

Re: Test report for xen-unstable and qemu-xen

[George Dunlap]

On Tue, Apr 23, 2013 at 2:13 PM, Fabio Fantoni <fantonifabio@tiscali.it> wrote:
> Dom0:
> Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version
> 3.2.41-2, package blktap-dkms and all dependency packages for xen, spice and
> usb redirection.
> -------------------------
> /etc/modules
> ------------
> loop max_loop=64
> xenfs
> xen-evtchn
> blktap
> -------------------------
> git clone git://xenbits.xen.org/xen.git (in this build commit is
> 96ef6e88359910738905ac2e1969dc05d7d7e7dc)
> -------------------------
> Added some patches:
> - tools-configure-qemu-for-spice-and-usbredir
> - libxl-Add-spice-vdagent-support-for-upstream-qemu
> - tools-firmware-seabios-packaged
> - tools: Improve make deb
> - hotplug: add openvswitch script V3
> - vgabios-stdvga.bin custom build from Frediano Ziglio
> - qemu-xen change for support other resolutions:
> hw/vga.c:
>     - if ((val <= VBE_DISPI_MAX_XRES) && ((val & 7) == 0)) {
>     + if ((val <= VBE_DISPI_MAX_XRES) && ((val & 1) == 0)) {
> -------------------------
> ./configure --prefix=/usr
> -------------------------
> make debball
>
> -------------------------
> Issues solved from my previous test build report:
> -------------
> - ovmf now build also with gcc!=44
> -------------
> - qemu-xen domU now has no more useless floppy
> -------------
> - openvswitch now works also with hvm domU
> -------------
> - stdvga now works also with latest qemu upstream version
> -------------------------
>
> -------------------------
> Old issue:
> - Network is not working after restore on Windows domU with qemu-xen and
> gplpv
> -------------
> - Unable to get QXL vga working correctly (probably need hvmloader changes)
> -------------
> - xl cd-eject/cd-insert not working with qemu-xen:
> xl cd-eject W7 hdb
> libxl: error: libxl_device.c:269:libxl__device_disk_set_backend: no suitable
> backend for disk hdb
> -------------------------

Can you please do a separate bug report e-mail, at least with the
first and last bugs here, including all of the pertinent information
(Xen version, kernel version, config file, OS version, PV drivers, &c
&c).

Thanks,
 -George

Test report for xen-unstable and qemu-xen

[Fabio Fantoni]

[-- Attachment #1.1: Type: text/plain, Size: 1945 bytes --]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 
3.2.32-1, package blktap-dkms and all dependency packages for xen
hg clone http://xenbits.xen.org/hg/xen-unstable.hg (in this build 
changeset is 26286:d5c0389bf26c)
-------------------------
vi Config.mk
------------
PYTHON_PREFIX_ARG =
-------------------------
Added some patches:
- Add qxl vga interface support v5 (posted by other people in mailing list)
- improve_make_deb (posted in mailing list)
- tools_config_spice_test (not posted now, enable spice build on qemu-xen)
-------------------------
./configure
-------------------------
make deb

-------------------------
Issues solved from my previous test build:
-------------
- xl cd-insert segmentation fault
-------------------------

-------------------------
Old issues not solved my previous test build:
-------------
- IMPORTANT - On restore the network is up but is not working, I tried 
it with W7 pro 64 bit with gplpv last build (357) on qemu-xen
- On qemu-xen there are empty floppy and cdrom device that are not set 
in configuration file (linux and windows)
- HVM Quantal domU with spice and qxl don't work, qemu crashes but it 
works without qxl
On log:
(/usr/sbin/xl:5250): Spice-CRITICAL **: red_memslots.c:123:get_virt: 
slot_id 194 too big, addr=c2c2c2c2c2c2c2c2
-------------------------

-------------------------
New issues from my previous test build:
-------------
- xl cd-eject and cd-insert are not working, tried with W7 pro 64 bit 
with gplpv last build (357) on qemu-xen and also ubuntu 12.10
xl cd-eject QUANTALHVM hdb # On my previuos test was working - changeset 
26094:c69bcb248128
libxl: error: libxl_device.c:269:libxl__device_disk_set_backend: no 
suitable backend for disk hdb
-------------------------

If you need other informations, logs and tests tell me and I'll do them 
and post them.
Thanks for any reply.


[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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