All of lore.kernel.org
 help / color / mirror / Atom feed
From: jim burns <jim_burn@bellsouth.net>
To: xen-devel@lists.xensource.com
Cc: xen-users@lists.xensource.com
Subject: Re: Problems with 'xl create winxp' (hvm) on xen 4.1.2 (also affects GPLPV)
Date: Sat, 29 Oct 2011 02:17:49 -0400	[thread overview]
Message-ID: <9873598.H8yuxEpZYE@dell4550> (raw)
In-Reply-To: <1758215.SCbitK4oVy@dell4550>

On Sat October 29 2011, 1:57:12 AM, jim burns wrote:
> For the remaining problems, note that 'xl create winxp' creates a qemu-dm 
> process with the following parameters:
> 
> qemu-dm -d 8 -domain-name winxp -vnc 0.0.0.0:3 -k en-us -serial pty
> -videoram  4 -boot cda -usb -usbdevice tablet -soundhw es1370 -acpi -vcpus
> 2 -vcpu_avail 0x3 -net nic,vlan=0,macaddr=00:16:3e:23:1d:36,model=rtl8139
> -net tap,vlan=0,ifname=tap8.0,bridge=xenbr0,script=no -M xenfv

Note, starting the domain with 'xm create' with the same config results in:

/usr/lib/xen/bin/qemu-dm -d 11 -domain-name winxp -videoram 4 -k en-us -vnc 
0.0.0.0:3 -monitor vc -vcpus 2 -vcpu_avail 0x3 -boot cda -soundhw es1370 -
localtime -serial pty -acpi -usbdevice tablet -net 
nic,vlan=1,macaddr=00:16:3e:23:1d:36,model=rtl8139 -net 
tap,vlan=1,ifname=tap11.0,bridge=xenbr0 -M xenfv

Note, 'xl create' does not pass the '-localtime' option, and its '-net tap' 
specifies 'script=no', unlike 'xm create'. Also, for some reason, the vlan 
numbers are different between xl and xm.

  reply	other threads:[~2011-10-29  6:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29  5:57 Problems with 'xl create winxp' (hvm) on xen 4.1.2 (also affects GPLPV) jim burns
2011-10-29  6:17 ` jim burns [this message]
2011-10-31 10:56   ` Ian Campbell
2011-10-31 10:50 ` Ian Campbell
2011-10-31 11:26   ` Ian Campbell
2011-10-31 23:00     ` jim burns
2011-11-01 12:49       ` Ian Campbell
2011-11-01 19:52         ` jim burns
2011-11-03  6:46   ` Stefano Stabellini
2011-11-03  8:39     ` Re: [Xen-devel] " Flavio
2011-11-03 23:33       ` [Xen-users] " Ian Campbell
2011-11-04  1:24         ` Stefano Stabellini

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=9873598.H8yuxEpZYE@dell4550 \
    --to=jim_burn@bellsouth.net \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.