Hello! I use Fedora 7 and virt-manager to install xen 3.1.0. I have installed Win XP 64 successfully but I have two problems: 1. How to switch Windows to full screen mode? Ctrl+Alt+F does not work. "Full screen"-option of virt-manager does not work too... 2. Windows does not recognize host cd-rom. I have tried to attach \dev\cdrom by means of virt-manager interface but Windows does not see it... I have also tried to attach iso-file, image of cd but situation is the same... Thank you. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of ymed > Sent: 19 June 2007 11:23 > To: xen-users@lists.xensource.com > Subject: [Xen-users] Xen and Windows in Fedora 7 > > Hello! > > I use Fedora 7 and virt-manager to install xen 3.1.0. > I have installed Win XP 64 successfully but I have two problems: > > 1. How to switch Windows to full screen mode? Ctrl+Alt+F does > not work. "Full screen"-option of virt-manager does not work too...Full-screen is not currently supported for HVM domains. There are a number of problems with this. You can solve some (but certainly not all) by replacing the "qemu-dm" in the config file with a script that adds "-full-screen" (or whatever it''s called) to the "qemu-dm" command-line. You can probably find some more info on this if you search the archive here on Xen-users and on xen-devel.> 2. Windows does not recognize host cd-rom. I have tried to > attach \dev\cdrom by means of virt-manager interface but > Windows does not see it... I have also tried to attach > iso-file, image of cd but situation is the same...Using the form "phy:/dev/cdrom,hdc:cdrom,r" or "file:some-filename-with-path,hdc:cdrom,r" should get the CDROM visible in Windows. I just tried it with my WinXP install, and I can read the MSDN Vista install DVD with that setup. Note: I''m NOT using Virt-Manager - not because there''s something wrong with it, but rather because I''m just using the tools that are available from XenSource. -- Mats> > Thank you. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of ymed >> Sent: 19 June 2007 11:23 >> To: xen-users@lists.xensource.com >> Subject: [Xen-users] Xen and Windows in Fedora 7 >> >> Hello! >> >> I use Fedora 7 and virt-manager to install xen 3.1.0. >> I have installed Win XP 64 successfully but I have two problems: >> >> 1. How to switch Windows to full screen mode? Ctrl+Alt+F does >> not work. "Full screen"-option of virt-manager does not work too... > >Full-screen is not currently supported for HVM domains. There are a >number of problems with this. You can solve some (but certainly not all) >by replacing the "qemu-dm" in the config file with a script that adds >"-full-screen" (or whatever it''s called) to the "qemu-dm" command-line. >You can probably find some more info on this if you search the archive >here on Xen-users and on xen-devel. > >> 2. Windows does not recognize host cd-rom. I have tried to >> attach \dev\cdrom by means of virt-manager interface but >> Windows does not see it... I have also tried to attach >> iso-file, image of cd but situation is the same... > >Using the form "phy:/dev/cdrom,hdc:cdrom,r" or >"file:some-filename-with-path,hdc:cdrom,r" should get the CDROM visible >in Windows. I just tried it with my WinXP install, and I can read the >MSDN Vista install DVD with that setup. > >Note: I''m NOT using Virt-Manager - not because there''s something wrong >with it, but rather because I''m just using the tools that are available >from XenSource. > >-- >Mats > >> >> Thank you. >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >>Yes, I have used this line when I tried Opensuse xen 3.0.3. But there was a file in /etc/xev/vm/ dir. I could not find the such file in /etc/xen in fedora 7. Where is this configuration file is located? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, The new IDE drivers now cause all IDE drives to have device names such as /dev/sdX instead of /dev/hdX. Ref.: http://docs.fedoraproject.org/release-notes/f7/en_US/sn-Kernel.html Look at your dmesg output, you''ll get something like this: scsi 2:0:0:0: CD-ROM TSSTcorp CD/DVDW SH-S182D SB02 PQ: 0 ANSI: 5 scsi 2:0:0:0: Attached scsi generic sg1 type 5 sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 2:0:0:0: Attached scsi CD-ROM sr0 -- Atenciosamente, Celio Santana Koho Network Services Fone: (11) 4063-0363 r. 202 Em Ter 19 Jun 2007, Petersson, Mats escreveu:> > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of ymed > > Sent: 19 June 2007 11:23 > > To: xen-users@lists.xensource.com > > Subject: [Xen-users] Xen and Windows in Fedora 7 > > > > Hello! > > > > I use Fedora 7 and virt-manager to install xen 3.1.0. > > I have installed Win XP 64 successfully but I have two problems: > > > > 1. How to switch Windows to full screen mode? Ctrl+Alt+F does > > not work. "Full screen"-option of virt-manager does not work too... > > Full-screen is not currently supported for HVM domains. There are a > number of problems with this. You can solve some (but certainly not all) > by replacing the "qemu-dm" in the config file with a script that adds > "-full-screen" (or whatever it''s called) to the "qemu-dm" command-line. > You can probably find some more info on this if you search the archive > here on Xen-users and on xen-devel. > > > 2. Windows does not recognize host cd-rom. I have tried to > > attach \dev\cdrom by means of virt-manager interface but > > Windows does not see it... I have also tried to attach > > iso-file, image of cd but situation is the same... > > Using the form "phy:/dev/cdrom,hdc:cdrom,r" or > "file:some-filename-with-path,hdc:cdrom,r" should get the CDROM visible > in Windows. I just tried it with my WinXP install, and I can read the > MSDN Vista install DVD with that setup. > > Note: I''m NOT using Virt-Manager - not because there''s something wrong > with it, but rather because I''m just using the tools that are available > from XenSource. > > -- > Mats > > > > > Thank you._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> >Using the form "phy:/dev/cdrom,hdc:cdrom,r" or > >"file:some-filename-with-path,hdc:cdrom,r" should get the > CDROM visible > >in Windows. I just tried it with my WinXP install, and I can read the > >MSDN Vista install DVD with that setup. > > > >Note: I''m NOT using Virt-Manager - not because there''s > something wrong > >with it, but rather because I''m just using the tools that > are available > >from XenSource. > > > >-- > >Mats > > > Yes, I have used this line when I tried Opensuse xen 3.0.3. > But there was a > file in /etc/xev/vm/ dir. I could not find the such file in > /etc/xen in > fedora 7. Where is this configuration file is located?First of all, I think this may be a virt-manager problem, rather than a Xen problem. Second, there are now two ways (at least) to store the Xen configuration, and it depends on what tools you use how it''s stored. I still use the "xm create config" way to start my VM''s, so I don''t really know where it''s stored when using other methods. [And I usually store my config files next to the VM disk image or in a "home" directory on my machine - but that''s a choice each individual has to make]. -- Mats> > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>> >Using the form "phy:/dev/cdrom,hdc:cdrom,r" or >> >"file:some-filename-with-path,hdc:cdrom,r" should get the >> CDROM visible >> >in Windows. I just tried it with my WinXP install, and I can read the >> >MSDN Vista install DVD with that setup. >> > >> >Note: I''m NOT using Virt-Manager - not because there''s >> something wrong >> >with it, but rather because I''m just using the tools that >> are available >> >from XenSource. >> > >> >-- >> >Mats >> > >> Yes, I have used this line when I tried Opensuse xen 3.0.3. >> But there was a >> file in /etc/xev/vm/ dir. I could not find the such file in >> /etc/xen in >> fedora 7. Where is this configuration file is located? > >First of all, I think this may be a virt-manager problem, rather than a >Xen problem. > >Second, there are now two ways (at least) to store the Xen >configuration, and it depends on what tools you use how it''s stored. I >still use the "xm create config" way to start my VM''s, so I don''t really >know where it''s stored when using other methods. [And I usually store my >config files next to the VM disk image or in a "home" directory on my >machine - but that''s a choice each individual has to make]. > >-- >MatsThank you, Mats. I have tried xm create based on the *.hvm file below. I see in virt-manager console that my domain xp64domain started sucessfully below dom0, but I cannot see any Windows screen... despite the fact that SDL=1. See the hvm-file below.... # -*- mode: python; -*- #===========================================================================# Python configuration setup for ''xm create''. # This script sets the parameters used when a domain is created using ''xm create''. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #=========================================================================== import os, re arch = os.uname()[4] if re.search(''64'', arch): arch_libdir = ''lib64'' else: arch_libdir = ''lib'' #---------------------------------------------------------------------------- # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" # The domain build function. HVM domain uses ''hvm''. builder=''hvm'' # Initial memory allocation (in megabytes) for the new domain. # # WARNING: Creating a domain with insufficient memory may cause out of # memory errors. The domain needs enough memory to boot kernel # and modules. Allocating less than 32MBs is not recommended. memory = 1024 # Shadow pagetable memory for the domain, in MB. # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. # shadow_memory = 8 # A name for your domain. All domains must have different names. name = "xp64domain" # 128-bit UUID for the domain. The default behavior is to generate a new UUID # on each call to ''xm create''. #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" #----------------------------------------------------------------------------- # The number of cpus guest platform has, default=1 vcpus=1 # Enable/disable HVM guest PAE, default=1 (enabled) #pae=1 # Enable/disable HVM guest ACPI, default=1 (enabled) acpi=1 # Enable/disable HVM APIC mode, default=1 (enabled) # Note that this option is ignored if vcpus > 1 #apic=1 # List of which CPUS this domain is allowed to use, default Xen picks #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] # type=ioemu specify the NIC is an ioemu device not netfront #vif = [ ''type=ioemu, bridge=xenbr0'' ] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. #disk = [ ''phy:hda1,hda1,r'' ] disk = [ ''file:/etc/xen/xp64.img,hda,w'', '',hdc:cdrom,r'' ] #---------------------------------------------------------------------------- # Configure the behaviour when a domain exits. There are three ''reasons'' # for a domain to stop: poweroff, reboot, and crash. For each of these you # may specify: # # "destroy", meaning that the domain is cleaned up as normal; # "restart", meaning that a new domain is started in place of the old # one; # "preserve", meaning that no clean-up is done until the domain is # manually destroyed (using xm destroy, for example); or # "rename-restart", meaning that the old domain is not cleaned up, but is # renamed and a new domain started in its place. # # The default is # # on_poweroff = ''destroy'' # on_reboot = ''restart'' # on_crash = ''restart'' # # For backwards compatibility we also support the deprecated option restart # # restart = ''onreboot'' means on_poweroff = ''destroy'' # on_reboot = ''restart'' # on_crash = ''destroy'' # # restart = ''always'' means on_poweroff = ''restart'' # on_reboot = ''restart'' # on_crash = ''restart'' # # restart = ''never'' means on_poweroff = ''destroy'' # on_reboot = ''destroy'' # on_crash = ''destroy'' #on_poweroff = ''destroy'' #on_reboot = ''restart'' #on_crash = ''restart'' #=========================================================================== # New stuff device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot="cd" #----------------------------------------------------------------------------- # write to temporary files instead of disk image files #snapshot=1 #---------------------------------------------------------------------------- # enable SDL library for graphics, default = 0 sdl=1 #---------------------------------------------------------------------------- # enable VNC library for graphics, default = 1 #vnc=0 #---------------------------------------------------------------------------- # address that should be listened on for the VNC server if vnc is set. # default is to use ''vnc-listen'' setting from /etc/xen/xend-config.sxp #vnclisten="127.0.0.1" #---------------------------------------------------------------------------- # set VNC display number, default = domid vncdisplay=0 #---------------------------------------------------------------------------- # try to find an unused port for the VNC server, default = 1 #vncunused=1 #---------------------------------------------------------------------------- # enable spawning vncviewer for domain''s console # (only valid when vnc=1), default = 0 #vncconsole=0 #---------------------------------------------------------------------------- # set password for domain''s VNC console # default is depents on vncpasswd in xend-config.sxp vncpasswd='''' #---------------------------------------------------------------------------- # no graphics, use serial port #nographic=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) #stdvga=1 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect serial=''pty'' #----------------------------------------------------------------------------- # Qemu Monitor, default is disable # Use ctrl-alt-2 to connect monitor=1 #----------------------------------------------------------------------------- # enable sound card support, [sb16|es1370|all|..,..], default none soundhw=''sb16'' #----------------------------------------------------------------------------- # set the real time clock to local time [default=0 i.e. set to utc] localtime=1 #----------------------------------------------------------------------------- # set the real time clock offset in seconds [default=0 i.e. same as dom0] #rtc_timeoffset=3600 #----------------------------------------------------------------------------- # start in full screen #full-screen=0 #----------------------------------------------------------------------------- # Enable USB support (specific devices specified at runtime through the # monitor window) usb=1 # Enable USB mouse support (only enable one of the following, `mouse'' for # PS/2 protocol relative mouse, `tablet'' for # absolute mouse) #usbdevice=''mouse'' #usbdevice=''tablet'' #----------------------------------------------------------------------------- # Set keyboard layout, default is en-us keyboard. #keymap=''ja'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jun 19, 2007 at 03:07:00PM +0400, ymed wrote:> Yes, I have used this line when I tried Opensuse xen 3.0.3. But there was a > file in /etc/xev/vm/ dir. I could not find the such file in /etc/xen in > fedora 7. Where is this configuration file is located?This was changed in Xen 3.0.4 or later. Previously XenD had no knowledge of inactive domains which made their management rather limited / hard. In Xen 3.0.4 there is now full lifecycle management of domains and as such their config files are stored by XenD itself. They are in a directory /var/lib/xend/domains, but they are not user-editable there - XenD will ignore / overwrite any changes you try to make there. In Fedora 7 our recommendation is to use libvirt''s virsh tool to alter the configs by first extracting them in XML format, then reloading them into XenD virsh dumpxml [guest name] > guest.xml vi guest.xml virsh define guest.xml XML is described at http://libvirt.org/format.html NB, the XML format does not yet support all of the config options available (in particular for HVM), so won''t work for the --fullscreen example mentioned earlier in this thread. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: ymed@yandex.ru [mailto:ymed@yandex.ru] > Sent: 19 June 2007 14:17 > To: Petersson, Mats > Cc: ymed@yandex.ru; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Xen and Windows in Fedora 7 > > >> >Using the form "phy:/dev/cdrom,hdc:cdrom,r" or > >> >"file:some-filename-with-path,hdc:cdrom,r" should get the > >> CDROM visible > >> >in Windows. I just tried it with my WinXP install, and I > can read the > >> >MSDN Vista install DVD with that setup. > >> > > >> >Note: I''m NOT using Virt-Manager - not because there''s > >> something wrong > >> >with it, but rather because I''m just using the tools that > >> are available > >> >from XenSource. > >> > > >> >-- > >> >Mats > >> > > >> Yes, I have used this line when I tried Opensuse xen 3.0.3. > >> But there was a > >> file in /etc/xev/vm/ dir. I could not find the such file in > >> /etc/xen in > >> fedora 7. Where is this configuration file is located? > > > >First of all, I think this may be a virt-manager problem, > rather than a > >Xen problem. > > > >Second, there are now two ways (at least) to store the Xen > >configuration, and it depends on what tools you use how it''s > stored. I > >still use the "xm create config" way to start my VM''s, so I > don''t really > >know where it''s stored when using other methods. [And I > usually store my > >config files next to the VM disk image or in a "home" directory on my > >machine - but that''s a choice each individual has to make]. > > > >-- > >Mats > > Thank you, Mats. I have tried xm create based on the *.hvm file > below. I see in virt-manager console that my domain > xp64domain started sucessfully below dom0, but I cannot see > any Windows screen... despite the fact that SDL=1. See the > hvm-file below....If you''re trying to run 64-bit XP, you will need to set PAE=1, and probably also APIC=1. Not sure if the comments are right or not about the defaults. Of course, this doesn''t explain why you get no "screen". Check your /var/log/xen/qemu-dm.<pid>.log for the domain you''ve just created. -- Mats> # The number of cpus guest platform has, default=1 > vcpus=1 > > # Enable/disable HVM guest PAE, default=1 (enabled) > #pae=1 > > # Enable/disable HVM guest ACPI, default=1 (enabled) > acpi=1 > > # Enable/disable HVM APIC mode, default=1 (enabled) > # Note that this option is ignored if vcpus > 1 > #apic=1_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > >> -----Original Message----- >> From: ymed@yandex.ru [mailto:ymed@yandex.ru] >> Sent: 19 June 2007 14:17 >> To: Petersson, Mats >> Cc: ymed@yandex.ru; xen-users@lists.xensource.com >> Subject: RE: [Xen-users] Xen and Windows in Fedora 7 >> >> >> >Using the form "phy:/dev/cdrom,hdc:cdrom,r" or >> >> >"file:some-filename-with-path,hdc:cdrom,r" should get the >> >> CDROM visible >> >> >in Windows. I just tried it with my WinXP install, and I >> can read the >> >> >MSDN Vista install DVD with that setup. >> >> > >> >> >Note: I''m NOT using Virt-Manager - not because there''s >> >> something wrong >> >> >with it, but rather because I''m just using the tools that >> >> are available >> >> >from XenSource. >> >> > >> >> >-- >> >> >Mats >> >> > >> >> Yes, I have used this line when I tried Opensuse xen 3.0.3. >> >> But there was a >> >> file in /etc/xev/vm/ dir. I could not find the such file in >> >> /etc/xen in >> >> fedora 7. Where is this configuration file is located? >> > >> >First of all, I think this may be a virt-manager problem, >> rather than a >> >Xen problem. >> > >> >Second, there are now two ways (at least) to store the Xen >> >configuration, and it depends on what tools you use how it''s >> stored. I >> >still use the "xm create config" way to start my VM''s, so I >> don''t really >> >know where it''s stored when using other methods. [And I >> usually store my >> >config files next to the VM disk image or in a "home" directory on my >> >machine - but that''s a choice each individual has to make]. >> > >> >-- >> >Mats >> >> Thank you, Mats. I have tried xm create based on the *.hvm file >> below. I see in virt-manager console that my domain >> xp64domain started sucessfully below dom0, but I cannot see >> any Windows screen... despite the fact that SDL=1. See the >> hvm-file below.... > >If you''re trying to run 64-bit XP, you will need to set PAE=1, and >probably also APIC=1. > >Not sure if the comments are right or not about the defaults. > >Of course, this doesn''t explain why you get no "screen". > >Check your /var/log/xen/qemu-dm.<pid>.log for the domain you''ve just >created. > >-- >Mats > >> # The number of cpus guest platform has, default=1 >> vcpus=1 >> >> # Enable/disable HVM guest PAE, default=1 (enabled) >> #pae=1 >> >> # Enable/disable HVM guest ACPI, default=1 (enabled) >> acpi=1 >> >> # Enable/disable HVM APIC mode, default=1 (enabled) >> # Note that this option is ignored if vcpus > 1 >> #apic=1 >I have found that Xen HVMs in Fedora 7 work only via VNC. virsh dumpxml xp64 > xp64.xml shows me <graphics type=''vnc'' port=''-1''/> and Windows screen is available. When I set it to <graphics type=''sdl''/> virt-manager says that the console is currently unavailable... The same situation is when I use xm create... but domain starts sucessfully... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jun 19, 2007 at 07:34:14PM +0400, ymed wrote:> I have found that Xen HVMs in Fedora 7 work only via VNC. > virsh dumpxml xp64 > xp64.xml > shows me <graphics type=''vnc'' port=''-1''/> and Windows screen is available. > When I set it to <graphics type=''sdl''/> virt-manager says that the console > is currently unavailable... The same situation is when I use xm create... > but domain starts sucessfully...SDL graphics are used to popup a standalone X window. Virt-manager wants to have the virtual console embedded within its own UI. So if you want to be able to display the console in virt-manager, VNC is the only practical option for now. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>On Tue, Jun 19, 2007 at 07:34:14PM +0400, ymed wrote: >> I have found that Xen HVMs in Fedora 7 work only via VNC. >> virsh dumpxml xp64 > xp64.xml >> shows me <graphics type=''vnc'' port=''-1''/> and Windows screen is available. >> When I set it to <graphics type=''sdl''/> virt-manager says that the console >> is currently unavailable... The same situation is when I use xm create... >> but domain starts sucessfully... > >SDL graphics are used to popup a standalone X window. Virt-manager wants to >have the virtual console embedded within its own UI. So if you want to be >able to display the console in virt-manager, VNC is the only practical option >for now. > >Dan.But in VNC it''s not possible to use cd-rom or iso-files. Also full screen is not available and mouse works with interrupts. Usually I used SDL for local graphic and VNC for remote.... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jun 19, 2007 at 08:01:21PM +0400, ymed wrote:> >On Tue, Jun 19, 2007 at 07:34:14PM +0400, ymed wrote: > >> I have found that Xen HVMs in Fedora 7 work only via VNC. > >> virsh dumpxml xp64 > xp64.xml > >> shows me <graphics type=''vnc'' port=''-1''/> and Windows screen is available. > >> When I set it to <graphics type=''sdl''/> virt-manager says that the console > >> is currently unavailable... The same situation is when I use xm create... > >> but domain starts sucessfully... > > > >SDL graphics are used to popup a standalone X window. Virt-manager wants to > >have the virtual console embedded within its own UI. So if you want to be > >able to display the console in virt-manager, VNC is the only practical option > >for now. > > But in VNC it''s not possible to use cd-rom or iso-files. Also full screen > is not available and mouse works with interrupts. Usually I used SDL for > local graphic and VNC for remote....Huh? CDROM/ISO files work just fine with VNC. If you want to change the media / file, then the command line ''xm block-configure'' command can be used. Now full screen capabilities are upto the VNC client - virt-manager can make its main window go full screen, but won''t currently stretch the guest console to fill the entire screen. We''ve got a new VNC widget being written to allow us to do that better. As for mouse, that''s another thing that will be attacked in a not-too-distant release, by making it choose either a USB tablet, or regular tablet which allows absolute mouse co-ords to be used. In the meantime we ''grab'' the local mouse cursor and hide it so you only see the remote cursor - this is (almost) equivalent to what SDL does with the mouse. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>On Tue, Jun 19, 2007 at 08:01:21PM +0400, ymed wrote: >> >On Tue, Jun 19, 2007 at 07:34:14PM +0400, ymed wrote: >> >> I have found that Xen HVMs in Fedora 7 work only via VNC. >> >> virsh dumpxml xp64 > xp64.xml >> >> shows me <graphics type=''vnc'' port=''-1''/> and Windows screen is available. >> >> When I set it to <graphics type=''sdl''/> virt-manager says that the console >> >> is currently unavailable... The same situation is when I use xm create... >> >> but domain starts sucessfully... >> > >> >SDL graphics are used to popup a standalone X window. Virt-manager wants to >> >have the virtual console embedded within its own UI. So if you want to be >> >able to display the console in virt-manager, VNC is the only practical option >> >for now. >> >> But in VNC it''s not possible to use cd-rom or iso-files. Also full screen >> is not available and mouse works with interrupts. Usually I used SDL for >> local graphic and VNC for remote.... > >Huh? CDROM/ISO files work just fine with VNC. If you want to change the >media / file, then the command line ''xm block-configure'' command can be >used. > >Now full screen capabilities are upto the VNC client - virt-manager >can make its main window go full screen, but won''t currently stretch the >guest console to fill the entire screen. We''ve got a new VNC widget being >written to allow us to do that better. As for mouse, that''s another thing >that will be attacked in a not-too-distant release, by making it choose >either a USB tablet, or regular tablet which allows absolute mouse co-ords >to be used. In the meantime we ''grab'' the local mouse cursor and hide it >so you only see the remote cursor - this is (almost) equivalent to what SDL >does with the mouse. > >Dan.Unfortunately I do not know how to use xm block-configure command because I do not know front and back names. The output of virsh for VNC domain is: <disk type=''file'' device=''disk''> <driver name=''file''/> <source file=''/myiso.iso/> <target dev=''hdb''/> </disk> But I do not see this disk in Windows... When I add iso-file by means of virt-manager (Tab "Hardware" -> Add-> Storage device -> Simple File -> myiso.iso) there is no disk in Windows too... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users