All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
To: haicheng.li@intel.com
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: Regressions introduced by ioemu-remote -- Xen #18039.
Date: Mon, 14 Jul 2008 17:38:10 +0900	[thread overview]
Message-ID: <487B1072.3030600@ab.jp.nec.com> (raw)
In-Reply-To: <0E6B8CEB89DCFE40A52F80EB8F97D99D02B89483@pdsmsx413.ccr.corp.intel.com>

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

Perhaps the attached patch will fix the Issue2?
cs 18025 changed the size of vga ram, so we should reduce VGA_RAM_SIZE
to 4MB for ioemu-remote tree likewise.

Thanks,
-- Yosuke

Li, Haicheng wrote:
> With ioemu-remote, still failed to create hvm guest with vncviewer
> disabled by 'sdl=1' or 'vnc=1 & vncconsole=0'. Two issues were found
> with Xen #18039 as log pasted below.
> 
> BTW, will xen-3.3 release use ioemu-remote as default qemu? Looks there
> would be some compatibility issues between xm/xend and ioemu-remote.
> 
> Issue1: if no vif option set. qemu exits with following log:
> domid: 14
> qemu: the number of cpus is 1
> Unknown network device: user
> 
> Issue2: with vif option set, qemu exits with following log:
> domid: 18
> qemu: the number of cpus is 1
> config qemu network with xen bridge for  tap18.0 eth4
> Strip off blktap sub-type prefix to
> /share/imgs/hli22/xen-test/manual-test/ia32e_xp_smp.qcow (drv 'qcow')
> qemu: could not open vbd '/local/domain/18/device/vbd/768/phantom_vbd'
> or hard disk image
> '/share/imgs/hli22/xen-test/manual-test/ia32e_xp_smp.qcow' (drv 'qcow'
> format '0')
> Watching /local/domain/0/device-model/18/logdirty/next-active
> Watching /local/domain/0/device-model/18/command
> char device redirected to /dev/pts/3
> qemu_map_cache_init nr_buckets = 10000 size 3145728
> shared page at pfn 7ffe
> buffered io page at pfn 7ffc
> Time offset set 0
> Register xen platform.
> Done register platform.
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> (qemu) Failed allocation for dom 18: 2048 extents of order 0
> Failed to populate physmap
> Failed set_mm_mapping
> NULL vram_pointer
> 
> 
> -- haicheng
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


[-- Attachment #2: vga_ram_size.patch --]
[-- Type: all/allfiles, Size: 462 bytes --]

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

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

  reply	other threads:[~2008-07-14  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14  7:54 Regressions introduced by ioemu-remote -- Xen #18039 Li, Haicheng
2008-07-14  8:38 ` Yosuke Iwamatsu [this message]
2008-07-14  8:56   ` Keir Fraser
2008-07-14 12:51     ` Ian Jackson
2008-07-14  8:58 ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=487B1072.3030600@ab.jp.nec.com \
    --to=y-iwamatsu@ab.jp.nec.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=haicheng.li@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.