search for: vncconsol

...nbr0, model=ne2k_pci'' ] disk = [ ''phy:store/windows-test,hda,w'', ''file:/mnt/store/backup/wide032a01.iso,hdc:cdrom,r''] device_model = "/usr/lib/xen-ioemu-3.1/bin/qemu-dm" boot="d" sdl=0 vnc=1 vnclisten="0.0.0.0" vncconsole=1 vncpasswd='''' <<< Thanx _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...39; ] device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot="dc" sdl=0 vnc=1 vncconsole=1 vncpasswd='''' #serial=''pty'' #usbdevice=''tablet'' And I''ve activated the listenig to 0.0.0.0 into the xend config. When I start the VM I try to connect to the vnc (vncviewer localhost or vncviewer localhost:1) and it allways return...

...quot; vif = [ ''type=ioemu, bridge=xenbr0'' ] acpi = 1 apic = 1 disk = [ ''file:/vm/win2008r2-01.img,hda,w'', ''file:/root/iso/w2008rc2.iso,hdc:cdrom,r'' ] device_model = ''/usr/lib64/xen/bin/qemu-dm'' boot="dc" sdl=0 vnc=1 vncconsole=1 vncpasswd='''' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...s there''s a listener on 0.0.0.0:5900, but I am unable to connect using vnc from my remote system. vncviewer reports "connection refused". dom0 is not running any firewalling and the relevant parts of the domU config file are: vnc = 1 vnclisten=''0.0.0.0'' vncconsole = 0 Any ideas what I need to do to make it work? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...=''/usr/lib/xen/bin/qemu-dm'' name="win01" vcpus=1 vif=[''type=ioemu,bridge=xenbr0''] disk = [ ''phy:vg/win01,sda,w'',''file:/mnt/winxp.iso,hdc:cdrom,r'' ] device_model=''/usr/lib/xen/bin/qemu-dm'' sdl=0 vnc=1 vncconsole=0 vncpasswd='''' ne2000=0 boot=''dc'' -----------</code>---------------------------------------- I have tried changing removing the "''file:/mnt/winxp.iso,hdc:cdrom,r''" line for the disk between reboots, but the thing will not cre...

...br0'' ] disk = [ ''file:/var/lib/xen/images/symbiosis.img,ioemu:hda,w'',''file:/root/RHEL4.6-x86_64-AS-disc1.iso,ioemu:hdc:cdrom,r'' ] device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' boot="d" vncunused=0 vncconsole=1 vncpasswd=''secret'' stdvga=0 serial=''pty'' usb=1 usbdevice=''mouse'' I run "xm create symbiosis" and get: Error: Device 5632 (vbd) could not be connected. losetup -r /dev/loop0 /root/RHEL4.6-x86_64-AS-disc1.iso failed But, I can manu...

...=xenbr1'' ] disk = [ ''phy:/dev/sda5,ioemu:hda,w'', ''phy:/dev/cdrom,hdc:cdrom,r'' ] boot="dac" #-GRAPHICS- # enable SDL library for graphics, default = 0 sdl=1 # enable VNC library for graphics, default = 1 vnc=1 vnclisten="192.168.0.22" #vncconsole=1 stdvga=0 serial=''pty'' -- Guillaume _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...r Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02 > Copyright (C) 2002-2005 RealVNC Ltd. > See http://www.realvnc.com for information on VNC. > vncviewer: unable to open display "" >   vnc=3 could mean it''s presenting a session on 5903, not 5900. Put ''vncconsole=1'' in your config to automatically spawn a vnc session. After the guest is up, do a ''/bin/ps a -HA'' on dom0, for a threaded process listing with command line args. The line under the one with ''qemu-dm'' should be something like ''vncviewer :59...

[This email is either empty or too large to be displayed at this time]

...9;'] on_poweroff = ''destroy'' on_reboot = ''destroy'' on_crash = ''preserve'' device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' boot=''cd'' sdl=0 vnc=1 vnclisten="0.0.0.0" vncconsole=1 vncpasswd=''abc'' nographic=0 stdvga=0 serial=''null'' And also the performance is not great when I boot s10 with more than one VCPU. Any recent fixes which went in dom0 or hypervisor? I''m using snv_80 build for dom0. # xm info xen_major...

This patch does 3 things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a

...9.3-32bit.disk,sda,w''] #disk=[''file:/IMG/sles9.3-32bit.disk,sda,w'',''file:/ISO/Knoppix-5.0.1.iso,hdc:cdrom,r''] device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' #boot="d" sdl=1 vnc=0 vncunused=1 vncconsole=0 stdvga=0 -------------------------------------------- I am not a novice in Linux and do not suspect I made a mistake installing it for some 1000th time. So why disk not recognised by XEN? Could not find an answer so far. Environment: XEN3.1, dom0 runs SLES9.3-64bit, SUN X4600 server. __...

...hda,w'', ''phy:/dev/disk/by-path/ip-192.168.1.16:....,hdb,w'', ] vif=[ ''mac=00:16:3e:30:09:01,bridge=xenbr1,model=rtl8139,type=ioemu'', # ''mac=00:16:3e:30:09:03,bridge=xenbr2,model=rtl8139,type=ioemu'', ] sdl=0 vnc=1 vncconsole=1 apic=1 acpi=1 # pae=0 # usb=1 usbdevice=''tablet'' serial="pty" ------------------------------------------------------------------------------------------------ Thanks for advance JP Pozzi This message contains information that may be privileged or confidential...

...ae'', ''rtc_timeoffset'', ''serial'', ''sdl'', ''soundhw'',''stdvga'', ''usb'', ''usbdevice'', ''vnc'', ''vncconsole'', ''vncdisplay'', ''vnclisten'', ''timer_mode'', - ''vncpasswd'', ''vncunused'', ''xauthority'', ''pci'', ''vhpt''] +...

...l_version=''qemu-xen'' device_model_override=''/usr/src/qemu/i386-softmmu/qemu-system-i386'' #device_model_override=''/usr/src/qemu/x86_64-softmmu/qemu-system-x86_64'' boot="dc" acpi=1 xen_platform_pci=1 xiridian=1 stdvga=1 #sdl = 1 vnc =0 vncconsole=0 vncpasswd='''' vncunused=1 vnclisten=''0.0.0.0'' vncdisplay=3 spice=1 spicehost=''0.0.0.0'' spiceport=6000 spicedisable_ticketing=1 spicepasswd = ''password'' Thanks in advance. Daniel. ________________________________________...

...-tools 3.9 on Wed Jul 8 14:44:12 2009. # # # Kernel + memory size # kernel = ''/usr/lib/xen-3.2-1/boot/hvmloader'' builder = ''hvm'' memory = ''1024'' device_model=''/usr/lib/xen-3.2-1/bin/qemu-dm'' acpi = 1 apic = 1 stdvga=0 pae=1 vncconsole=1 vncpasswd='''' vcpus=4 serial=''pty'' usbdevice=''tablet'' shadow_memory = 8 # # Disk device(s). # disk = [ ''phy:/dev/loop2,ioemu:hda:ide,w'' ''phy:/dev/loop2,ioemu:hdc:cdrom,r'' ] # Behaviour boot=''d...

.../xen/vm/freebsd.cfg builder = "hvm" vcpus = 1 memroy = 2048 disk = [ ''phy:/dev/xen-dom0/freebsd,hda,w'' ] name = "freebsd" #vif = [''bridge=xenbr0,mac=00:16:3e:00:af:d8''] serial = ''pty'' vnc=1 vnclisten="0.0.0.0" vncconsole=1 vncpasswd=''''" The domU stops at boot with a kernel panic that it has run out of memory. The OS only sees 1M or RAM. Has anyone encountered this, and if so, how does one solve it? I have tried installing the OS from the install media and using a xen-enabled FreeBSD disk...

...9;' ] acpi = 1 apic = 1 disk = [ ''file:/etc/xen/xenwin.img,hda,w'', ''file:/media/RAID5/Software/Operating Systems/Windows/Windows 7 64 (Universal).iso,hdc:cdrom,r'' ] device_model = ''/usr/lib/xen-4.1/bin/qemu-dm'' boot="dc" #vnc=1 #vncconsole=1 xen_platform_pci=1 gfx_passthrough #pci=[''00:14.2''] pci=[''00:01.0''] serial=''pty'' usbdevice=''tablet'' #extra=''xencons=tty'' #extra="console=hvc0" -- View this message in context: http://xen.1045...

...dev/sdc,hda,w'' ] # /dev/sdc is the USB stick pci = [ ''00:11.0'' ] # This is the SATA controller with 5 drives vif = [''bridge=vlan14'' ] boot=''dc'' sdl=0 vnc=1 vnclisten=''0.0.0.0'' vncconsole=1 stdvga=0 The SATA controller according to ''lspci'': 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] (rev 40) Everything "works", but is it painfully slow. Reading from a single SATA drive within the DomU gives me about 0.5MB/s:...

Hi, I''m on a HP DL365, amd64, running SLES10sp1, but with kernel and xen of SLES10sp2, therefore using Xen 3.2. The domU shall be a Windows HVM guest. I want use the Qlogic SAN card in a domU. I''m following these instructions: http://www.novell.com/communities/node/2880/assign-dedicated-network-card-or-pci-device-xen-virtual-machine well, there is written that this only