Displaying 20 results from an estimated 1000 matches similar to: "[PATCH] [xm] Fix vncdisplay for hvm guests"
2008 Apr 11
2
vncdisplay #
How does this setting work? I was hoping to use it to make connections predictable. I have vncunused = 1 as well, but xen never starts the server on the expected port (dom-u id).
Thanks!
jlc
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2007 Oct 24
16
PATCH 0/10: Merge PV framebuffer & console into QEMU
The following series of 10 patches is a merge of the xenfb and xenconsoled
functionality into the qemu-dm code. The general approach taken is to have
qemu-dm provide two machine types - one for xen paravirt, the other for
fullyvirt. For compatability the later is the default. The goals overall
are to kill LibVNCServer, remove alot of code duplication and/or parallel
impls of the same concepts, and
2008 Mar 06
3
static vnc port
Hi,
I''m trying so give all my guests a static vnc display my Configfile
looks like this.
1 ostype = "opensuse"
2 name = "suse-10.3-testcups"
3 builder = "linux"
4 memory = 512
5 vcpus = 1
6 uuid = "c6d9aa20-06c4-46f5-81e8-7906f7cfb642"
7 on_crash = "destroy"
8 on_poweroff =
2011 Aug 24
2
how to list vnc port in xen 4.1
Hi all,
I try xen 4.1, but in my domU''s HVM don''t appear vnc port. I used in my
domU.cfg the parameter ''vncunused=1''.
How to get vnc port specified domU?
In another Xen (4.0.2), I get vnc port with ''xm list --long domU''.
(vfb
(vncunused 1)
(vnc 1)
(uuid cb20995f-55ae-55ce-143d-dd6a2ecc5969)
2012 Aug 22
4
config file conflict??
I think it has to be something trivial, but I cannot start 2 windows servers
at the same time on the same dom0.
If I start server 2008 first I can''t start 2012, if I start 2012, I can''t
start 2008.
The failure is:
libxl: error: libxl_device.c:470:libxl__wait_for_device_model Device Model
not ready
xl: fatal error: libxl_create.c:535, rc=-1:
libxl__confirm_device_model_startup
2007 Apr 11
2
Error: Device 0 (vkbd) is already connected.
Hi,
Is vfb working well lately? I thought I''d test it out on ia64 and it
works great, but only once per boot. If I stop the domain and restart
it, I get the following:
Error: Device 0 (vkbd) is already connected.
To make sure this isn''t an ia64 anomaly, I tried it on an x86_64 system.
Same thing, works the first time, reboot the domain and it''s broken. I
see
2009 Nov 19
3
xm create: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi All,
I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs
for lennovo T400. I have installed all prerequisite component for running
xen and booted it.
while I am trying to create DomU I am getting following error. I tried doing
googling but none of suggested solution is working for me. Please guide me
through my first experience with xen.for more details please see
2009 Nov 20
3
Re: xm create: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. One more question.
Next question:-
eth0 8000.001c2596e32b no peth0
pan0 8000.000000000000 no
virbr0 8000.000000000000 yes
Presence virbr0 in report seems strange. Direct port Xen 3.4.2 to F11 doesn''t install daemon
libvirtd ( bridge virbr0 ) , unless you wrote xen-3.4.2-(x).fc12.src.rpm yourself.
So , from where bridge virbr0 comes
2010 Mar 10
9
Error starting stubdom HVM on Xen-3.4.3-rc4-pre
Hi there,
Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2.
My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,
2010 Mar 10
9
Error starting stubdom HVM on Xen-3.4.3-rc4-pre
Hi there,
Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2.
My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,
2011 Aug 28
1
Hanging boot of solaris 11 install image as HVM
Hello,
It looks like xen 4.1.2* has some problems with solaris 11 iso images
too (s. further below log messages)
hvm-solaris11.born2b3.net.cfg
# ---
kernel = ''/usr/lib64/xen-default/boot/hvmloader''
builder = ''hvm''
device_model= ''/usr/lib64/xen-4.1/bin/qemu-dm''
name = ''solaris11hvm.born2b3.net''
acpi =
2012 Feb 08
7
[PATCH] libxl: Set VNC password through QMP
This patch provide the code to set the VNC password to QEMU upstream through
VNC. The password is still stored in xenstore but will not be used by QEMU
upstream.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
---
tools/libxl/libxl_create.c | 3 +++
tools/libxl/libxl_dm.c | 21 ++++++++++++---------
tools/libxl/libxl_internal.h | 1 +
tools/libxl/libxl_qmp.c
2006 Sep 26
15
RE: Individual passwords for guest VNC servers ?
> Thanks all point about security, I''ll do as follows.
> I thought that the point was the following two.
>
>
> 1. Storage place of encrypted password
> Should I store it in /etc/xen/passwd ?
> Or, should I wait for DB of Xen that will be released in
> the future?
The xend life cycle management patches were posted by Alistair a couple
of months back.
2010 Jan 21
2
Windows Xen VM's have high guest CPU usage and poor performance
Hello all,
I have a PowerEdge 2950 that I am using to host Windows XP VM's under
CentOS. I am experiencing poor performance in the Xen VM's. Any time I
try to do something, the CPU usage (as reported by the Windows task
manager) hits 100% for a few and then drops back down. This is causing
the VM's to run sluggish and be quite annoying to use. Example.. I
click IE.. cpu hits
2013 Jun 27
20
SPICE with Upstream QEMU and qxl VGA cause Windows BSOD
Hi all,
These days I installed xen 4.3 unstable from source and recompiled qemu upstream with spice support.
After xl create , the windows domU started successfully and spice client can visit the VDI. However, it display blue screen
before entering the windows welcome screen.
Is it a bug in current upstream qemu support?
My domU configuration file is:
builder =
2008 May 27
1
Add new drive to Windows domu
Hi everyone,
I'm wondering how one adds a new drive to a Windows domu...
I'm running Centos 5.1 x86_64 on a Xeon server and have a Windows 2003
R2 64 bit domu. The Windows system was installed from a CD onto this
server so it is a brand new VM. All working fine.
So then I wish to add another drive to the Windows domu for a data drive.
I added the drive to the Xen configuration, but it
2020 Feb 27
2
xen hvm domU and > 3 nic's... bug?
Hi
I cant start a hvm domU with more than 3 nic's configured... why? it is
a bug?
With previous versions it was possible...
here the config - it is an opnsense (openbsd) hvm domU:
name = "fenrir.chao5.int"
uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859"
maxmem = 2048
memory = 2048
loader = '/usr/lib64/xen/boot/hvmloader'
type = "hvm"
vcpus = 2
2011 Jul 17
17
Failure to create HVM DomU at Xen 4.1 ( kernel 3.0.0-5-generic) Ubuntu 11.10 (alpha 2)
root@boris-P5Q-E:/mnt/usr/tmp# losetup -f ubuntu11.04.iso
root@boris-P5Q-E:/mnt/usr/tmp# losetup -a
/dev/loop0: [0809]:406494 (/mnt/usr/tmp/ubuntu11.04.iso)
root@boris-P5Q-E:~/vms/natty# cat natty.hvm
name = "NattyHVM"
builder = "hvm"
memory = "2048"
disk = [''phy:/dev/sda5,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r'']
vif = [
2011 Jul 17
17
Failure to create HVM DomU at Xen 4.1 ( kernel 3.0.0-5-generic) Ubuntu 11.10 (alpha 2)
root@boris-P5Q-E:/mnt/usr/tmp# losetup -f ubuntu11.04.iso
root@boris-P5Q-E:/mnt/usr/tmp# losetup -a
/dev/loop0: [0809]:406494 (/mnt/usr/tmp/ubuntu11.04.iso)
root@boris-P5Q-E:~/vms/natty# cat natty.hvm
name = "NattyHVM"
builder = "hvm"
memory = "2048"
disk = [''phy:/dev/sda5,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r'']
vif = [
2008 Dec 10
6
WIndows 2008, Quard Core Opteron, xen
Hello
I have trouble with Quard Core Opteron and windows 2008(x86).
By the way Windows device manager show 4 processors, BUT task manager
show only one core.
I found that my problem is not new. But solutions, provided by those
people did not helped me.
By the way, my windows is enterprise version, and as far as I know, it
allows up to 8 processor sockets, so the trouble is not, that windows