Bonjour, i''have installed Xen on a red hat entreprise . I''ve tried many guest on ParaVirtualisation and it works And after i''ve actived the bios option of full virtualisation and I would like to install guest in Full Virtualisation... But there is an "error : device 768 (vbd) could not be connected..." Device /dev/... in mounted in privilege mode and so cannot be mounted by a guest. i''ve googled for 2 days ... please some idea? Thanks a lot . _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/2/07, benjamin henrion <benjhenrion@gmail.com> wrote:> "error : device 768 (vbd) could not be connected..." > Device /dev/... in mounted in privilege mode and so cannot be mounted by a > guest.Please show us your domU config. Are you sure the disk you are trying tpo run you domain on is not mounted at the same time in dom0? Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Please show us your domU config. > > Are you sure the disk you are trying tpo run you domain on is not > mounted at the same time in dom0?Sounds like something is accessing the disk... Xen is preventing the domain from starting as a safety precaution, since having several domains accessing the same disk can be unsafe. Is the virtual disk mounted in dom0? Have you allowed another domain (either paravirt or full virt) to have access to it? Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
---------- Forwarded message ---------- From: Mark Williamson <mark.williamson@cl.cam.ac.uk> Date: 5 févr. 2007 06:12 Subject: Re: [Xen-users] full virtualization To: xen-users@lists.xensource.com Cc: Henning Sprang <henning_sprang@gmx.de>, benjamin henrion < benjhenrion@gmail.com>> Please show us your domU config. > > Are you sure the disk you are trying tpo run you domain on is not > mounted at the same time in dom0?Sounds like something is accessing the disk... Xen is preventing the domain from starting as a safety precaution, since having several domains accessing the same disk can be unsafe. Is the virtual disk mounted in dom0? Have you allowed another domain (either paravirt or full virt) to have access to it? Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! Ok ! this is my conf # -*- 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 = 512 # 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 = "debianFull" vif = [''type=ioemu, mac=aa:00:0b:00:00:11, bridge=xenbr0'' ] # 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 = [ ''phy:/dev/VG_Guests/Debian1.img,ioemu:hda,w''] #disk = [''file:/var/images/min-el3-i386.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) or CD-ROM (d) # default: hard disk, cd-rom, floppy cdrom="/tmp/debian-testing-i386-netinst.iso" #boot="d" #----------------------------------------------------------------------------- # 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=1 vmcviewer=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=1 #---------------------------------------------------------------------------- # 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 #------------------------ ne2000=0 #------------------------ #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) #stdvga=0 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect #serial=''pty'' #----------------------------------------------------------------------------- # 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 #----------------------------------------------------------------------------- # start in full screen #full-screen=1 #----------------------------------------------------------------------------- # 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
Hi Benjamin, please remove unnecessary comments the next time, it''s hard to get through a fully commented config file... On 2/5/07, benjamin henrion <benjhenrion@gmail.com> wrote:> disk = [ ''phy:/dev/VG_Guests/Debian1.img,ioemu:hda,w'']ioemu is outdated since Xen 3.0.2 AFAIK. What version of Xen do you use? See this example (in your own config file):> #disk = [''file:/var/images/min-el3-i386.img,hda,w'', '',hdc:cdrom,r'' ] >> vmcviewer=0This doesn''t affect your disk problem, but it''s "vncviewer" Unfortunately, it''s probably too hard for xen to check the python config files for incorrectly-named config options. (It''s possible, but complex: maybe try to check all locall variables _before_ the config file is sourced, and check again after, see which ones are new, and if all those variables are allowed. but then you could not use custom variables for scripting stuff). Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Benjamin, are you using loop devices ??? if so, do you have enough available loop devices ??? Marcos benjamin henrion <benjhenrion@gmail.com> escreveu: Bonjour, i''have installed Xen on a red hat entreprise . I''ve tried many guest on ParaVirtualisation and it works And after i''ve actived the bios option of full virtualisation and I would like to install guest in Full Virtualisation... But there is an "error : device 768 (vbd) could not be connected..." Device /dev/... in mounted in privilege mode and so cannot be mounted by a guest. i''ve googled for 2 days ... please some idea? Thanks a lot . _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users __________________________________________________ Fale com seus amigos de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com/ --0-2025000716-1171461474=:90107 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi Benjamin,<br><br>are you using loop devices ???<br>if so, do you have enough available loop devices ???<br><br>Marcos<br><br><b><i>benjamin henrion <benjhenrion@gmail.com></i></b> escreveu:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Bonjour,<br>i''have installed Xen on a red hat entreprise .<br>I''ve tried many guest on ParaVirtualisation and it works<br>And after i''ve actived the bios option of full virtualisation and I would like to install guest in Full Virtualisation... <br>But there is an <br>"error : device 768 (vbd) could not be connected..."<br>Device /dev/... in mounted in privilege mode and so cannot be mounted by a guest.<br>i''ve googled for 2 days ...<br>please some idea? <br><br>Thanks a lot .<br><br> _______________________________________________<br>Xen-users mailing list<br>Xen-users@lists.xensource.com<br>http://lists.xensource.com/xen-users</blockquote><br><p> __________________________________________________<br>Fale com seus amigos de graça com o novo Yahoo! Messenger <br>http://br.messenger.yahoo.com/ --0-2025000716-1171461474=:90107-- --===============1047725449=Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --===============1047725449==--
I am trying to get Xen to work with full virtualization, i had a domu working fine para virtualized, but when do "sudo xm create kubuntu" i get Name ID Mem VCPUs State Time(s) Domain-0 0 251 8 r----- 181.9 kubuntu 10 512 1 ------ 0.0 and if i do "sudo xm console kubuntu" i get xenconsole: Could not read tty from store: No such file or directory _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/16/07, Michael Wineland <mike@idealso.com> wrote:> and if i do "sudo xm console kubuntu" i get xenconsole: Could not read > tty from store: No such file or directoryYou don''t "xm console" into a hvm domain''s console. You use vnc, or start it in sdl mode - depending on how you configured it. See docs - but come back if you have further questions... Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Feb 16, 2007 at 06:17:14PM +0100, Henning Sprang wrote:> On 2/16/07, Michael Wineland <mike@idealso.com> wrote: > >and if i do "sudo xm console kubuntu" i get xenconsole: Could not read > >tty from store: No such file or directory > > > You don''t "xm console" into a hvm domain''s console.Actually can get it working, but it involves a little more setup than with paravirt. In the Xen config file for the HVM guest add serial=''pty'' In the grub.conf for the guest you need to have console=tty0 console=ttyS0,9600 And in the /etc/inittab for the guest you need to add s0:2345:respawn:/sbin/agetty -L 9600 ttyS0 vt100 That basically configures a virtual serial console in QEMU, tells the kernel to send messages to it as well as the normal console, and finally runs a login process on the serial console IIRC that ought to be enough to make ''xm console'' work kfor HVM 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Henning Sprang wrote:> On 2/16/07, Michael Wineland <mike@idealso.com> wrote: >> and if i do "sudo xm console kubuntu" i get xenconsole: Could not read >> tty from store: No such file or directory > > > You don''t "xm console" into a hvm domain''s console. > > You use vnc, or start it in sdl mode - depending on how you configured > it. See docs - but come back if you have further questions...Actually, we use xm console for our VM domain - add the following to grub.conf serial --unit=0 --speed=9600 terminal --timeout=15 serial console and append "console=ttyS0 console=tty0" to the kernel command line, and s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100 to /etc/inittab. The biggest caveat for this is that you can only have one session opened at a time (xm will happily let you connect multiple sessions, but all you''ll get is gibberish as only part of the data will be sent to each one.) - -Karl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFF1eoor6qWhNgoahURAh6JAJ9g9gWHHuEgBtrcdOHDyQcbOfLbzwCgwJEa uBlw4IvtA68HTGdPh0A5qq4=u2om -----END PGP SIGNATURE----- __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 2007-02-16 at 17:22 +0000, Daniel P. Berrange wrote:> On Fri, Feb 16, 2007 at 06:17:14PM +0100, Henning Sprang wrote: > > On 2/16/07, Michael Wineland <mike@idealso.com> wrote: > > >and if i do "sudo xm console kubuntu" i get xenconsole: Could not read > > >tty from store: No such file or directory > > > > > > You don''t "xm console" into a hvm domain''s console. > > Actually can get it working, but it involves a little more setup than > with paravirt. > > In the Xen config file for the HVM guest add > > serial=''pty'' > > In the grub.conf for the guest you need to have > > console=tty0 console=ttyS0,9600 > > And in the /etc/inittab for the guest you need to add > > s0:2345:respawn:/sbin/agetty -L 9600 ttyS0 vt100 > > That basically configures a virtual serial console in QEMU, tells the > kernel to send messages to it as well as the normal console, and finally > runs a login process on the serial console > > IIRC that ought to be enough to make ''xm console'' work kfor HVM >That should find its way into the wiki, very handy if you just need to do a curses based install remotely. Thanks for posting that, X over SSH from Manila Wi-Fi to Texas is *painful*. Best, --Tim> Regards, > Dan._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I will try that, i guess i assumed i had to use the console, I didnt think i could use vnc while trying to get it to boot off of the install cd, thank you all very much =) Karl Stevens wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Henning Sprang wrote: > >> On 2/16/07, Michael Wineland <mike@idealso.com> wrote: >> >>> and if i do "sudo xm console kubuntu" i get xenconsole: Could not read >>> tty from store: No such file or directory >>> >> You don''t "xm console" into a hvm domain''s console. >> >> You use vnc, or start it in sdl mode - depending on how you configured >> it. See docs - but come back if you have further questions... >> > > Actually, we use xm console for our VM domain - add the following to > grub.conf > > serial --unit=0 --speed=9600 > terminal --timeout=15 serial console > > and append "console=ttyS0 console=tty0" to the kernel command line, and > > s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100 > > to /etc/inittab. > > The biggest caveat for this is that you can only have one session opened > at a time (xm will happily let you connect multiple sessions, but all > you''ll get is gibberish as only part of the data will be sent to each one.) > > - -Karl > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iD8DBQFF1eoor6qWhNgoahURAh6JAJ9g9gWHHuEgBtrcdOHDyQcbOfLbzwCgwJEa > uBlw4IvtA68HTGdPh0A5qq4> =u2om > -----END PGP SIGNATURE----- > > __ > This communication is intended for the use of the recipient to whom it > is addressed, and may contain confidential, personal, and or privileged > information. Please contact us immediately if you are not the intended > recipient of this communication, and do not copy, distribute, or take > action relying on it. Any communications received in error, or > subsequent reply, should be deleted or destroyed. > --- > _______________________________________________ > 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
WOOT, I got it up thanks to an e-mail from Mats Paetersson:>Xenconsole doesn''t work for fully virtualized domains.>To get more info, we need to see "xm dmesg", your config file, perhaps >(if it looks useful) /var/log/xen/xend{-debug}.log or >/var/log/xen/qemu-dm.<pid>.log>First thing: check if there''s a "qemu-dm" running (ps ax|grep qemu) - if >you give the wrong settings in the config file, the qemu-dm may die and >that leaves the guest "not doing anything"."ps ax|grep qemu" showed qemu-dm [defunct], then i looked for the log and there wasnt one, so i did an apt-get install qemu and now the hardware virtualized domain starts and stays up weee, now i just need to figure out how to access it because i am on ubuntu server with no gui, and i am trying to boot off an install disk, would doing the walkthrough to enable console in HVM work on ubuntu server? Henning Sprang wrote:> On 2/16/07, Michael Wineland <mike@idealso.com> wrote: >> and if i do "sudo xm console kubuntu" i get xenconsole: Could not read >> tty from store: No such file or directory > > > You don''t "xm console" into a hvm domain''s console. > > You use vnc, or start it in sdl mode - depending on how you configured > it. See docs - but come back if you have further questions... > > Henning_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/16/07, Michael Wineland <mike@idealso.com> wrote:> "ps ax|grep qemu" showed qemu-dm [defunct], then i looked for the log > and there wasnt one, so i did an apt-get install qemu and now the > hardware virtualized domain starts and stays up weee,I think it''s strange that you need to install the qemu packge to get that going. It _could_ be that this really made it work, but _normally_ you should get the GUI running without having a normal qemu package installed - all the qemu stuff you need for the Xen HVM functions is included in Xen itself, and I doubt that really other qemu libs are used, even when installed. Still, it _could_ be. Maybe you just missed the SDL libs, they are probably not documented as dependencies in the README, and now they are pulled in by the qemu package.>now i just need to > figure out how to access it because i am on ubuntu server with no gui, > and i am trying to boot off an install disk, would doing the walkthrough > to enable console in HVM work on ubuntu server?You can export the GUI via VNC from the dom0 server, or/and install any remote GUI software on the machine. You start the VM with vnc=1 and then you should be able to use vncviewer to connect to the GUI. BTW: sure Daniel is right, I should have written "most people don''t want to run a console with hvm, but access the GUI with SDL(only when the host has a GUI) or vnc. Using a console in hvm domains is a bit config tinkering". Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Donnerstag, 22. Februar 2007, Henning Sprang wrote:> On 2/16/07, Michael Wineland <mike@idealso.com> wrote: > > "ps ax|grep qemu" showed qemu-dm [defunct], then i looked for the log > > and there wasnt one, so i did an apt-get install qemu and now the > > hardware virtualized domain starts and stays up weee,Thanks Michael, that was the right suggestion !!! In my case /usr/lib/xen/bin/qemu-dm was missing, can''t work. But no hint in xend.log, the only hint is the missing qemu-dm.*.log. But that''s an install problem on my side. @Henning: No idea why xenoppix don''t work in my case. Again: Thanks Michael Christian -- "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Xen 3.0.3 installed from debian packages XP 32bit. No qemu-dm log files found and qemu was not in excution... How must I do? thanks --------- Original Message -------- From: Petersson, Mats <Mats.Petersson@amd.com> To: Carlo Granisso <carlo@granisso.it>, xen-users@lists.xensource.com <xen-users@lists.xensource.com> Subject: RE: [Xen-users] FULL VIRTUALIZATION Date: 28/02/07 12:09> > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > Carlo Granisso > > Sent: 27 February 2007 20:50 > > To: xen-users@lists.xensource.com > > Subject: [Xen-users] FULL VIRTUALIZATION > > > > I''ve installed xen from Debian Etch packets (apt-get > > install..). All work > > fine but when I try to run a Windows domU, execution time remain to0:> > > > Name ID Mem(MiB) VCPUs > > State Time(s) > > Domain-0 0 251 2 > > r----- 1080.5 > > ftp_srv 7 512 1 > > ------ 0.0 > > What version of Windows (XP, Server 2K, 2K3, Vista, NT or ??), and > "bitness" (32 or 64-bit?) > > What exact version of Xen are you using (xm info will give that). > > Is the qemu-dm process running (ps ax|grep qemu)? > > Anything in the /var/log/xen/qemu-dm.<qemu-pid>.log file? > > -- > Mats > > > > tun and tap device created... > > > > Have you got ideas? > > > > Thanks, > > > > Carlo > > > > > > _______________________________________________ > > 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 > >________________________________________________ Message sent using UebiMiau 2.7.10 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: Carlo [mailto:carlo@granisso.it] > Sent: 28 February 2007 10:41 > To: Petersson, Mats; Carlo Granisso; xen-users@lists.xensource.com > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > Xen 3.0.3 installed from debian packages > XP 32bit. > > No qemu-dm log files found and qemu was not in excution...I''d recommend updating to Xen 3.0.4-1 before you try other things to debug this... -- Mats> > How must I do? > > thanks > > --------- Original Message -------- > From: Petersson, Mats <Mats.Petersson@amd.com> > To: Carlo Granisso <carlo@granisso.it>, xen-users@lists.xensource.com > <xen-users@lists.xensource.com> > Subject: RE: [Xen-users] FULL VIRTUALIZATION > Date: 28/02/07 12:09 > > > > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > > Carlo Granisso > > > Sent: 27 February 2007 20:50 > > > To: xen-users@lists.xensource.com > > > Subject: [Xen-users] FULL VIRTUALIZATION > > > > > > I''ve installed xen from Debian Etch packets (apt-get > > > install..). All work > > > fine but when I try to run a Windows domU, execution > time remain to > 0: > > > > > > Name ID Mem(MiB) VCPUs > > > State Time(s) > > > Domain-0 0 251 2 > > > r----- 1080.5 > > > ftp_srv 7 512 1 > > > ------ 0.0 > > > > What version of Windows (XP, Server 2K, 2K3, Vista, NT or ??), and > > "bitness" (32 or 64-bit?) > > > > What exact version of Xen are you using (xm info will give that). > > > > Is the qemu-dm process running (ps ax|grep qemu)? > > > > Anything in the /var/log/xen/qemu-dm.<qemu-pid>.log file? > > > > -- > > Mats > > > > > > tun and tap device created... > > > > > > Have you got ideas? > > > > > > Thanks, > > > > > > Carlo > > > > > > > > > _______________________________________________ > > > 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 > > > > > > ________________________________________________ > Message sent using UebiMiau 2.7.10 > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''ve solved the first problem: path of qemu-dm in the config file was
uncorrect...
Now, qemu-dm say:
domid: 6
qemu: the number of cpus is 1
shared page at pfn:1ffff, mfn: df18
buffered io page at pfn:1fffd, mfn: df1a
---------------------- DirectFB v0.9.25 ---------------------
(c) 2000-2002 convergence integrated media GmbH
(c) 2002-2004 convergence GmbH
-----------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2006-12-04 07:00)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(!) Direct/Util: opening ''/dev/fb0'' and
''/dev/fb/0'' failed
--> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER
environment
variable.
(!) DirectFB/Core: Could not initialize ''system'' core!
--> Initialization error!
Could not initialize SDL - exiting
Any ideas?
--------- Original Message --------
From: Petersson, Mats <Mats.Petersson@amd.com>
To: Carlo <carlo@granisso.it>, xen-users@lists.xensource.com
<xen-users@lists.xensource.com>
Subject: RE: [Xen-users] FULL VIRTUALIZATION
Date: 28/02/07 12:46
>
> > -----Original Message-----
> > From: Carlo [mailto:carlo@granisso.it]
> > Sent: 28 February 2007 10:41
> > To: Petersson, Mats; Carlo Granisso; xen-users@lists.xensource.com
> > Subject: RE: [Xen-users] FULL VIRTUALIZATION
> >
> > Xen 3.0.3 installed from debian packages
> > XP 32bit.
> >
> > No qemu-dm log files found and qemu was not in excution...
>
> I''d recommend updating to Xen 3.0.4-1 before you try other things
to
> debug this...
>
> --
> Mats
> >
> > How must I do?
> >
> > thanks
> >
> > --------- Original Message --------
> > From: Petersson, Mats <Mats.Petersson@amd.com>
> > To: Carlo Granisso <carlo@granisso.it>,
xen-users@lists.xensource.com> > <xen-users@lists.xensource.com>
> > Subject: RE: [Xen-users] FULL VIRTUALIZATION
> > Date: 28/02/07 12:09
> >
> > >
> > >
> > > &gt; -----Original Message-----
> > > &gt; From: xen-users-bounces@lists.xensource.com
> > > &gt;
[mailto:xen-users-bounces@lists.xensource.com] On
Behalf Of > > > &gt; Carlo Granisso
> > > &gt; Sent: 27 February 2007 20:50
> > > &gt; To: xen-users@lists.xensource.com
> > > &gt; Subject: [Xen-users] FULL VIRTUALIZATION
> > > &gt;
> > > &gt; I''ve installed xen from Debian Etch
packets (apt-get
> > > &gt; install..). All work
> > > &gt; fine but when I try to run a Windows domU,
execution
> > time remain to
> > 0:
> > > &gt;
> > > &gt; Name ID
Mem(MiB)
VCPUs > > > &gt; State Time(s)
> > > &gt; Domain-0 0
251
2 > > > &gt; r----- 1080.5
> > > &gt; ftp_srv 7
512
1 > > > &gt; ------ 0.0
> > >
> > > What version of Windows (XP, Server 2K, 2K3, Vista, NT or
??),
and> > > &quot;bitness&quot; (32 or 64-bit?)
> > >
> > > What exact version of Xen are you using (xm info will
give
that). > > >
> > > Is the qemu-dm process running (ps ax|grep qemu)?
> > >
> > > Anything in the
/var/log/xen/qemu-dm.&lt;qemu-pid&gt;.log
file?> > >
> > > --
> > > Mats
> > > &gt;
> > > &gt; tun and tap device created...
> > > &gt;
> > > &gt; Have you got ideas?
> > > &gt;
> > > &gt; Thanks,
> > > &gt;
> > > &gt; Carlo
> > > &gt;
> > > &gt;
> > > &gt;
_______________________________________________
> > > &gt; Xen-users mailing list
> > > &gt; Xen-users@lists.xensource.com
> > > &gt; http://lists.xensource.com/xen-users
> > > &gt;
> > > &gt;
> > > &gt;
> > >
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> > >
> > >
> >
> > ________________________________________________
> > Message sent using UebiMiau 2.7.10
> >
> >
> >
> >
> >
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
________________________________________________
Message sent using UebiMiau 2.7.10
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> -----Original Message----- > From: Carlo [mailto:carlo@granisso.it] > Sent: 28 February 2007 10:54 > To: Petersson, Mats; Carlo; xen-users@lists.xensource.com > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > I''ve solved the first problem: path of qemu-dm in the config file was > uncorrect... > > Now, qemu-dm say: > > domid: 6 > qemu: the number of cpus is 1 > shared page at pfn:1ffff, mfn: df18 > buffered io page at pfn:1fffd, mfn: df1a > > ---------------------- DirectFB v0.9.25 --------------------- > (c) 2000-2002 convergence integrated media GmbH > (c) 2002-2004 convergence GmbH > ----------------------------------------------------------- > > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00) > (*) Direct/Memcpy: Using MMXEXT optimized memcpy() > (!) Direct/Util: opening ''/dev/fb0'' and ''/dev/fb/0'' failed > --> No such file or directory > (!) DirectFB/FBDev: Error opening framebuffer device! > (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER environment > variable. > (!) DirectFB/Core: Could not initialize ''system'' core! > --> Initialization error! > Could not initialize SDL - exitingNever seen that before. Sounds like something is up with your X-windows setup, but I''m not an expert on that. -- Mats> > > Any ideas? > > --------- Original Message -------- > From: Petersson, Mats <Mats.Petersson@amd.com> > To: Carlo <carlo@granisso.it>, xen-users@lists.xensource.com > <xen-users@lists.xensource.com> > Subject: RE: [Xen-users] FULL VIRTUALIZATION > Date: 28/02/07 12:46 > > > > > > -----Original Message----- > > > From: Carlo [mailto:carlo@granisso.it] > > > Sent: 28 February 2007 10:41 > > > To: Petersson, Mats; Carlo Granisso; > xen-users@lists.xensource.com > > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > > > > Xen 3.0.3 installed from debian packages > > > XP 32bit. > > > > > > No qemu-dm log files found and qemu was not in excution... > > > > I''d recommend updating to Xen 3.0.4-1 before you try other things to > > debug this... > > > > -- > > Mats > > > > > > How must I do? > > > > > > thanks > > > > > > --------- Original Message -------- > > > From: Petersson, Mats <Mats.Petersson@amd.com> > > > To: Carlo Granisso <carlo@granisso.it>, > xen-users@lists.xensource.com > > > <xen-users@lists.xensource.com> > > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > Date: 28/02/07 12:09 > > > > > > > > > > > > > > > &gt; -----Original Message----- > > > > &gt; From: xen-users-bounces@lists.xensource.com > > > > &gt; [mailto:xen-users-bounces@lists.xensource.com] On > Behalf Of > > > > &gt; Carlo Granisso > > > > &gt; Sent: 27 February 2007 20:50 > > > > &gt; To: xen-users@lists.xensource.com > > > > &gt; Subject: [Xen-users] FULL VIRTUALIZATION > > > > &gt; > > > > &gt; I''ve installed xen from Debian Etch > packets (apt-get > > > > &gt; install..). All work > > > > &gt; fine but when I try to run a Windows > domU, execution > > > time remain to > > > 0: > > > > &gt; > > > > &gt; Name > ID Mem(MiB) > VCPUs > > > > &gt; State Time(s) > > > > &gt; Domain-0 > 0 251 > 2 > > > > &gt; r----- 1080.5 > > > > &gt; ftp_srv > 7 512 > 1 > > > > &gt; ------ 0.0 > > > > > > > > What version of Windows (XP, Server 2K, 2K3, > Vista, NT or ??), > and > > > > &quot;bitness&quot; (32 or 64-bit?) > > > > > > > > What exact version of Xen are you using (xm info will give > that). > > > > > > > > Is the qemu-dm process running (ps ax|grep qemu)? > > > > > > > > Anything in the > /var/log/xen/qemu-dm.&lt;qemu-pid&gt;.log file? > > > > > > > > -- > > > > Mats > > > > &gt; > > > > &gt; tun and tap device created... > > > > &gt; > > > > &gt; Have you got ideas? > > > > &gt; > > > > &gt; Thanks, > > > > &gt; > > > > &gt; Carlo > > > > &gt; > > > > &gt; > > > > &gt; _______________________________________________ > > > > &gt; Xen-users mailing list > > > > &gt; Xen-users@lists.xensource.com > > > > &gt; http://lists.xensource.com/xen-users > > > > &gt; > > > > &gt; > > > > &gt; > > > > > > > > > > > > > > > > _______________________________________________ > > > > Xen-users mailing list > > > > Xen-users@lists.xensource.com > > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > ________________________________________________ > > > Message sent using UebiMiau 2.7.10 > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > ________________________________________________ > Message sent using UebiMiau 2.7.10 > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats <Mats.Petersson <at> amd.com> writes:> > > > -----Original Message----- > > From: Carlo [mailto:carlo <at> granisso.it] > > Sent: 28 February 2007 10:54 > > To: Petersson, Mats; Carlo; xen-users <at> lists.xensource.com > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > > I''ve solved the first problem: path of qemu-dm in the config file was > > uncorrect... > > > > Now, qemu-dm say: > > > > domid: 6 > > qemu: the number of cpus is 1 > > shared page at pfn:1ffff, mfn: df18 > > buffered io page at pfn:1fffd, mfn: df1a > > > > ---------------------- DirectFB v0.9.25 --------------------- > > (c) 2000-2002 convergence integrated media GmbH > > (c) 2002-2004 convergence GmbH > > ----------------------------------------------------------- > > > > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00) > > (*) Direct/Memcpy: Using MMXEXT optimized memcpy() > > (!) Direct/Util: opening ''/dev/fb0'' and ''/dev/fb/0'' failed > > --> No such file or directory > > (!) DirectFB/FBDev: Error opening framebuffer device! > > (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER environment > > variable. > > (!) DirectFB/Core: Could not initialize ''system'' core! > > --> Initialization error! > > Could not initialize SDL - exitinggot the same Problem here :) You don´t have a Framebufferdevice /dev/fb0. Create one withe mknod or configure udev properly. Second choice, use vnc (vnc=1) and connect with xvncviewer ip:0, so I do. here my config: kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' builder = ''hvm'' memory = ''1024'' device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' disk = [ ''file:/home/xen/windoof/windisk.img,ioemu:hda,w'', ''file:/home/ar/WXPVOL_DE.ISO,ioemu:hdc:cdrom,r'' ] #disk = [ ''phy:/dev/hda,hda,r'' ] name = ''windoof'' vif = [''type=ioemu, bridge=xenbr0''] boot=''d'' vnc=1 vncpassword=''xyz'' vncunused=1 vncviewer=0 #vnclisten="127.0.0.1" serial=''pty'' sdl=0 greetings _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Jun-20 16:53 UTC
RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0
Hello, I have the same problem like the one described below... Did somebody resolved the issue with the missing /dev/fd0 device? Mknod does not help. What does it mean "configure udev properly"? If fb works OK without Xen, how should I configure udev for xen - what should be modified in the xen configuration to get Dom0 working again, like if running without Xen? Any help would be appreciated, With best regards Archie -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Andre Rein Sent: Wednesday, February 28, 2007 4:09 PM To: xen-users@lists.xensource.com Subject: [Xen-users] Re: FULL VIRTUALIZATION Petersson, Mats <Mats.Petersson <at> amd.com> writes:> > > > -----Original Message----- > > From: Carlo [mailto:carlo <at> granisso.it] > > Sent: 28 February 2007 10:54 > > To: Petersson, Mats; Carlo; xen-users <at> lists.xensource.com > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > > I''ve solved the first problem: path of qemu-dm in the config file was > > uncorrect... > > > > Now, qemu-dm say: > > > > domid: 6 > > qemu: the number of cpus is 1 > > shared page at pfn:1ffff, mfn: df18 > > buffered io page at pfn:1fffd, mfn: df1a > > > > ---------------------- DirectFB v0.9.25 --------------------- > > (c) 2000-2002 convergence integrated media GmbH > > (c) 2002-2004 convergence GmbH > > ----------------------------------------------------------- > > > > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00) > > (*) Direct/Memcpy: Using MMXEXT optimized memcpy() > > (!) Direct/Util: opening ''/dev/fb0'' and ''/dev/fb/0'' failed > > --> No such file or directory > > (!) DirectFB/FBDev: Error opening framebuffer device! > > (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER environment > > variable. > > (!) DirectFB/Core: Could not initialize ''system'' core! > > --> Initialization error! > > Could not initialize SDL - exitinggot the same Problem here :) You don´t have a Framebufferdevice /dev/fb0. Create one withe mknod or configure udev properly. Second choice, use vnc (vnc=1) and connect with xvncviewer ip:0, so I do. here my config: kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' builder = ''hvm'' memory = ''1024'' device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' disk = [ ''file:/home/xen/windoof/windisk.img,ioemu:hda,w'', ''file:/home/ar/WXPVOL_DE.ISO,ioemu:hdc:cdrom,r'' ] #disk = [ ''phy:/dev/hda,hda,r'' ] name = ''windoof'' vif = [''type=ioemu, bridge=xenbr0''] boot=''d'' vnc=1 vncpassword=''xyz'' vncunused=1 vncviewer=0 #vnclisten="127.0.0.1" serial=''pty'' sdl=0 greetings _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users __________ Informace od NOD32 2082 (20070226) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-Jun-21 08:57 UTC
RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Artur Linhart - Linux communication > Sent: 20 June 2007 17:54 > To: ''Andre Rein''; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > Hello, > > I have the same problem like the one described below... > > Did somebody resolved the issue with the missing > /dev/fd0 device? > > Mknod does not help. What does it mean "configure udev > properly"? If > fb works OK without Xen, how should I configure udev for xen > - what should > be modified in the xen configuration to get Dom0 working > again, like if > running without Xen?I don''t think there should be any difference between udev for native Linux and Xen-ified linux - the hint on configuring it "properly" was more to the point of "make sure it''s set up". But I guess another point is that /dev/fbN is the "frame-buffer", which is only available on certain models of graphics cards - you may not be able to do that with the graphics card you''ve specified in the domain config (are you by any chance using "stdvga=1"?). -- Mats> > Any help would be appreciated, > > With best regards > > Archie > > -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Andre Rein > Sent: Wednesday, February 28, 2007 4:09 PM > To: xen-users@lists.xensource.com > Subject: [Xen-users] Re: FULL VIRTUALIZATION > > Petersson, Mats <Mats.Petersson <at> amd.com> writes: > > > > > > > > -----Original Message----- > > > From: Carlo [mailto:carlo <at> granisso.it] > > > Sent: 28 February 2007 10:54 > > > To: Petersson, Mats; Carlo; xen-users <at> lists.xensource.com > > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > > > > I''ve solved the first problem: path of qemu-dm in the > config file was > > > uncorrect... > > > > > > Now, qemu-dm say: > > > > > > domid: 6 > > > qemu: the number of cpus is 1 > > > shared page at pfn:1ffff, mfn: df18 > > > buffered io page at pfn:1fffd, mfn: df1a > > > > > > ---------------------- DirectFB v0.9.25 > --------------------- > > > (c) 2000-2002 convergence integrated media GmbH > > > (c) 2002-2004 convergence GmbH > > > > ----------------------------------------------------------- > > > > > > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00) > > > (*) Direct/Memcpy: Using MMXEXT optimized memcpy() > > > (!) Direct/Util: opening ''/dev/fb0'' and ''/dev/fb/0'' failed > > > --> No such file or directory > > > (!) DirectFB/FBDev: Error opening framebuffer device! > > > (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER > environment > > > variable. > > > (!) DirectFB/Core: Could not initialize ''system'' core! > > > --> Initialization error! > > > Could not initialize SDL - exiting > > got the same Problem here :) > You don´t have a Framebufferdevice /dev/fb0. Create one withe > mknod or > configure udev properly. > > Second choice, use vnc (vnc=1) and connect with xvncviewer > ip:0, so I do. > > here my config: > > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > builder = ''hvm'' > memory = ''1024'' > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > > > disk = [ > > ''file:/home/xen/windoof/windisk.img,ioemu:hda,w'', > ''file:/home/ar/WXPVOL_DE.ISO,ioemu:hdc:cdrom,r'' > ] > #disk = [ ''phy:/dev/hda,hda,r'' ] > > > name = ''windoof'' > > > vif = [''type=ioemu, bridge=xenbr0''] > > > boot=''d'' > vnc=1 > vncpassword=''xyz'' > vncunused=1 > vncviewer=0 > #vnclisten="127.0.0.1" > serial=''pty'' > sdl=0 > > > > greetings > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > __________ Informace od NOD32 2082 (20070226) __________ > > Tato zprava byla proverena antivirovym systemem NOD32. > http://www.nod32.cz > > > > _______________________________________________ > 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
Artur Linhart - Linux communication
2007-Jun-21 10:03 UTC
RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0
Hello, Mats, I have problems with "xenified" Dom0 (Etch). The original Etch booted directly works normally, also framebuffer device is present and I can start the graphical applications like directvnc, etc.. But if I boot Etch as xen Dom0, the /dev/df0 is not present - also if I specify the kernel parameter vga=... then it is not reflected, the console is still in text mode... So, from the point of view of the mail before, it "is correctly set up" - in the original etch system - but udev does not recognize the devices under xen... Are there any other kernel options for xen kernel which could impact this behavior or any other configuration possibilities? For example something similar for Dom0 like I can specify for domU? With best regards Archie -----Original Message----- From: Petersson, Mats [mailto:Mats.Petersson@amd.com] Sent: Thursday, June 21, 2007 10:58 AM To: Artur Linhart - Linux communication; Andre Rein; xen-users@lists.xensource.com Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Artur Linhart - Linux communication > Sent: 20 June 2007 17:54 > To: ''Andre Rein''; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > Hello, > > I have the same problem like the one described below... > > Did somebody resolved the issue with the missing > /dev/fd0 device? > > Mknod does not help. What does it mean "configure udev > properly"? If > fb works OK without Xen, how should I configure udev for xen > - what should > be modified in the xen configuration to get Dom0 working > again, like if > running without Xen?I don''t think there should be any difference between udev for native Linux and Xen-ified linux - the hint on configuring it "properly" was more to the point of "make sure it''s set up". But I guess another point is that /dev/fbN is the "frame-buffer", which is only available on certain models of graphics cards - you may not be able to do that with the graphics card you''ve specified in the domain config (are you by any chance using "stdvga=1"?). -- Mats> > Any help would be appreciated, > > With best regards > > Archie > > -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Andre Rein > Sent: Wednesday, February 28, 2007 4:09 PM > To: xen-users@lists.xensource.com > Subject: [Xen-users] Re: FULL VIRTUALIZATION > > Petersson, Mats <Mats.Petersson <at> amd.com> writes: > > > > > > > > -----Original Message----- > > > From: Carlo [mailto:carlo <at> granisso.it] > > > Sent: 28 February 2007 10:54 > > > To: Petersson, Mats; Carlo; xen-users <at> lists.xensource.com > > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > > > > I''ve solved the first problem: path of qemu-dm in the > config file was > > > uncorrect... > > > > > > Now, qemu-dm say: > > > > > > domid: 6 > > > qemu: the number of cpus is 1 > > > shared page at pfn:1ffff, mfn: df18 > > > buffered io page at pfn:1fffd, mfn: df1a > > > > > > ---------------------- DirectFB v0.9.25 > --------------------- > > > (c) 2000-2002 convergence integrated media GmbH > > > (c) 2002-2004 convergence GmbH > > > > ----------------------------------------------------------- > > > > > > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00) > > > (*) Direct/Memcpy: Using MMXEXT optimized memcpy() > > > (!) Direct/Util: opening ''/dev/fb0'' and ''/dev/fb/0'' failed > > > --> No such file or directory > > > (!) DirectFB/FBDev: Error opening framebuffer device! > > > (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER > environment > > > variable. > > > (!) DirectFB/Core: Could not initialize ''system'' core! > > > --> Initialization error! > > > Could not initialize SDL - exiting > > got the same Problem here :) > You don´t have a Framebufferdevice /dev/fb0. Create one withe > mknod or > configure udev properly. > > Second choice, use vnc (vnc=1) and connect with xvncviewer > ip:0, so I do. > > here my config: > > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > builder = ''hvm'' > memory = ''1024'' > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > > > disk = [ > > ''file:/home/xen/windoof/windisk.img,ioemu:hda,w'', > ''file:/home/ar/WXPVOL_DE.ISO,ioemu:hdc:cdrom,r'' > ] > #disk = [ ''phy:/dev/hda,hda,r'' ] > > > name = ''windoof'' > > > vif = [''type=ioemu, bridge=xenbr0''] > > > boot=''d'' > vnc=1 > vncpassword=''xyz'' > vncunused=1 > vncviewer=0 > #vnclisten="127.0.0.1" > serial=''pty'' > sdl=0 > > > > greetings > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > __________ Informace od NOD32 2082 (20070226) __________ > > Tato zprava byla proverena antivirovym systemem NOD32. > http://www.nod32.cz > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >__________ Informace od NOD32 2342 (20070621) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-Jun-21 10:22 UTC
RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0
> -----Original Message----- > From: Artur Linhart - Linux communication > [mailto:AL.LINUX@bcpraha.com] > Sent: 21 June 2007 11:03 > To: Petersson, Mats; ''Andre Rein''; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > Hello, Mats, > > I have problems with "xenified" Dom0 (Etch). The original Etch > booted directly works normally, also framebuffer device is > present and I can > start the graphical applications like directvnc, etc.. But if > I boot Etch as > xen Dom0, the /dev/df0 is not present - also if I specify the kernel > parameter vga=... then it is not reflected, the console is > still in text > mode... > > So, from the point of view of the mail before, it "is > correctly set > up" - in the original etch system - but udev does not > recognize the devices > under xen... > > Are there any other kernel options for xen kernel which > could impact > this behavior or any other configuration possibilities? For example > something similar for Dom0 like I can specify for domU?What graphics driver are you using for your graphic card? Is it loading correctly for your Dom0 installation? Check "dmesg" for both native and Dom0 to see if there''s any differences. -- Mats> > With best regards > > Archie > > > -----Original Message----- > From: Petersson, Mats [mailto:Mats.Petersson@amd.com] > Sent: Thursday, June 21, 2007 10:58 AM > To: Artur Linhart - Linux communication; Andre Rein; > xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > Artur Linhart - Linux communication > > Sent: 20 June 2007 17:54 > > To: ''Andre Rein''; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > Hello, > > > > I have the same problem like the one described below... > > > > Did somebody resolved the issue with the missing > > /dev/fd0 device? > > > > Mknod does not help. What does it mean "configure udev > > properly"? If > > fb works OK without Xen, how should I configure udev for xen > > - what should > > be modified in the xen configuration to get Dom0 working > > again, like if > > running without Xen? > > I don''t think there should be any difference between udev for > native Linux > and Xen-ified linux - the hint on configuring it "properly" > was more to the > point of "make sure it''s set up". > > But I guess another point is that /dev/fbN is the > "frame-buffer", which is > only available on certain models of graphics cards - you may > not be able to > do that with the graphics card you''ve specified in the domain > config (are > you by any chance using "stdvga=1"?). > > -- > Mats > > > > Any help would be appreciated, > > > > With best regards > > > > Archie > > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Andre Rein > > Sent: Wednesday, February 28, 2007 4:09 PM > > To: xen-users@lists.xensource.com > > Subject: [Xen-users] Re: FULL VIRTUALIZATION > > > > Petersson, Mats <Mats.Petersson <at> amd.com> writes: > > > > > > > > > > > > -----Original Message----- > > > > From: Carlo [mailto:carlo <at> granisso.it] > > > > Sent: 28 February 2007 10:54 > > > > To: Petersson, Mats; Carlo; xen-users <at> lists.xensource.com > > > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > > > > > > I''ve solved the first problem: path of qemu-dm in the > > config file was > > > > uncorrect... > > > > > > > > Now, qemu-dm say: > > > > > > > > domid: 6 > > > > qemu: the number of cpus is 1 > > > > shared page at pfn:1ffff, mfn: df18 > > > > buffered io page at pfn:1fffd, mfn: df1a > > > > > > > > ---------------------- DirectFB v0.9.25 > > --------------------- > > > > (c) 2000-2002 convergence integrated media GmbH > > > > (c) 2002-2004 convergence GmbH > > > > > > ----------------------------------------------------------- > > > > > > > > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00) > > > > (*) Direct/Memcpy: Using MMXEXT optimized memcpy() > > > > (!) Direct/Util: opening ''/dev/fb0'' and ''/dev/fb/0'' failed > > > > --> No such file or directory > > > > (!) DirectFB/FBDev: Error opening framebuffer device! > > > > (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER > > environment > > > > variable. > > > > (!) DirectFB/Core: Could not initialize ''system'' core! > > > > --> Initialization error! > > > > Could not initialize SDL - exiting > > > > got the same Problem here :) > > You don´t have a Framebufferdevice /dev/fb0. Create one withe > > mknod or > > configure udev properly. > > > > Second choice, use vnc (vnc=1) and connect with xvncviewer > > ip:0, so I do. > > > > here my config: > > > > > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > > builder = ''hvm'' > > memory = ''1024'' > > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > > > > > > disk = [ > > > > ''file:/home/xen/windoof/windisk.img,ioemu:hda,w'', > > ''file:/home/ar/WXPVOL_DE.ISO,ioemu:hdc:cdrom,r'' > > ] > > #disk = [ ''phy:/dev/hda,hda,r'' ] > > > > > > name = ''windoof'' > > > > > > vif = [''type=ioemu, bridge=xenbr0''] > > > > > > boot=''d'' > > vnc=1 > > vncpassword=''xyz'' > > vncunused=1 > > vncviewer=0 > > #vnclisten="127.0.0.1" > > serial=''pty'' > > sdl=0 > > > > > > > > greetings > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > __________ Informace od NOD32 2082 (20070226) __________ > > > > Tato zprava byla proverena antivirovym systemem NOD32. > > http://www.nod32.cz > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > > > > > __________ Informace od NOD32 2342 (20070621) __________ > > Tato zprava byla proverena antivirovym systemem NOD32. > http://www.nod32.cz > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Jun-21 11:01 UTC
RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0
Hello, Yes there are a lot of differences (for example, in the section dedicated to the initialization of the CPU1-3 there are no messages by Xen, by etch it is normally initialized - see evt. the attachments). Related to the console and the fb device there are following differences: Dmesg-xen: io scheduler cfq registered (default) Real Time Clock Driver v1.12ac - between both this two lines there is nothing by xen, but by etch there is the loading of the vesafb driver and creation of /dev/fb0: Dmesg-etch: io scheduler cfq registered (default) PCI: Setting latency timer of device 0000:00:02.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:02.0:pcie00] Allocate Port Service[0000:00:02.0:pcie01] PCI: Setting latency timer of device 0000:00:03.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:03.0:pcie00] Allocate Port Service[0000:00:03.0:pcie01] PCI: Setting latency timer of device 0000:00:04.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:04.0:pcie00] Allocate Port Service[0000:00:04.0:pcie01] PCI: Setting latency timer of device 0000:00:05.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:05.0:pcie00] Allocate Port Service[0000:00:05.0:pcie01] PCI: Setting latency timer of device 0000:00:06.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:06.0:pcie00] Allocate Port Service[0000:00:06.0:pcie01] PCI: Setting latency timer of device 0000:00:07.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:07.0:pcie00] Allocate Port Service[0000:00:07.0:pcie01] PCI: Setting latency timer of device 0000:01:00.0 to 64 Allocate Port Service[0000:01:00.0:pcie10] Allocate Port Service[0000:01:00.0:pcie11] PCI: Setting latency timer of device 0000:02:00.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:02:00.0:pcie20] Allocate Port Service[0000:02:00.0:pcie21] Allocate Port Service[0000:02:00.0:pcie22] PCI: Setting latency timer of device 0000:02:01.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:02:01.0:pcie20] Allocate Port Service[0000:02:01.0:pcie21] PCI: Setting latency timer of device 0000:02:02.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:02:02.0:pcie20] Allocate Port Service[0000:02:02.0:pcie21] vesafb: framebuffer at 0xb0000000, mapped to 0xffffc20010100000, using 3072k, total 16384k vesafb: mode is 1024x768x16, linelength=2048, pages=9 vesafb: scrolling: redraw vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 Console: switching to colour frame buffer device 128x48 fb0: VESA VGA frame buffer device Real Time Clock Driver v1.12ac I have no idea, why by xen nothing happens... Cheers Archie -----Original Message----- From: Petersson, Mats [mailto:Mats.Petersson@amd.com] Sent: Thursday, June 21, 2007 12:23 PM To: Artur Linhart - Linux communication; Andre Rein; xen-users@lists.xensource.com Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0> -----Original Message----- > From: Artur Linhart - Linux communication > [mailto:AL.LINUX@bcpraha.com] > Sent: 21 June 2007 11:03 > To: Petersson, Mats; ''Andre Rein''; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > Hello, Mats, > > I have problems with "xenified" Dom0 (Etch). The original Etch > booted directly works normally, also framebuffer device is > present and I can > start the graphical applications like directvnc, etc.. But if > I boot Etch as > xen Dom0, the /dev/df0 is not present - also if I specify the kernel > parameter vga=... then it is not reflected, the console is > still in text > mode... > > So, from the point of view of the mail before, it "is > correctly set > up" - in the original etch system - but udev does not > recognize the devices > under xen... > > Are there any other kernel options for xen kernel which > could impact > this behavior or any other configuration possibilities? For example > something similar for Dom0 like I can specify for domU?What graphics driver are you using for your graphic card? Is it loading correctly for your Dom0 installation? Check "dmesg" for both native and Dom0 to see if there''s any differences. -- Mats> > With best regards > > Archie > > > -----Original Message----- > From: Petersson, Mats [mailto:Mats.Petersson@amd.com] > Sent: Thursday, June 21, 2007 10:58 AM > To: Artur Linhart - Linux communication; Andre Rein; > xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > Artur Linhart - Linux communication > > Sent: 20 June 2007 17:54 > > To: ''Andre Rein''; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > Hello, > > > > I have the same problem like the one described below... > > > > Did somebody resolved the issue with the missing > > /dev/fd0 device? > > > > Mknod does not help. What does it mean "configure udev > > properly"? If > > fb works OK without Xen, how should I configure udev for xen > > - what should > > be modified in the xen configuration to get Dom0 working > > again, like if > > running without Xen? > > I don''t think there should be any difference between udev for > native Linux > and Xen-ified linux - the hint on configuring it "properly" > was more to the > point of "make sure it''s set up". > > But I guess another point is that /dev/fbN is the > "frame-buffer", which is > only available on certain models of graphics cards - you may > not be able to > do that with the graphics card you''ve specified in the domain > config (are > you by any chance using "stdvga=1"?). > > -- > Mats > > > > Any help would be appreciated, > > > > With best regards > > > > Archie > > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Andre Rein > > Sent: Wednesday, February 28, 2007 4:09 PM > > To: xen-users@lists.xensource.com > > Subject: [Xen-users] Re: FULL VIRTUALIZATION > > > > Petersson, Mats <Mats.Petersson <at> amd.com> writes: > > > > > > > > > > > > -----Original Message----- > > > > From: Carlo [mailto:carlo <at> granisso.it] > > > > Sent: 28 February 2007 10:54 > > > > To: Petersson, Mats; Carlo; xen-users <at> lists.xensource.com > > > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > > > > > > I''ve solved the first problem: path of qemu-dm in the > > config file was > > > > uncorrect... > > > > > > > > Now, qemu-dm say: > > > > > > > > domid: 6 > > > > qemu: the number of cpus is 1 > > > > shared page at pfn:1ffff, mfn: df18 > > > > buffered io page at pfn:1fffd, mfn: df1a > > > > > > > > ---------------------- DirectFB v0.9.25 > > --------------------- > > > > (c) 2000-2002 convergence integrated media GmbH > > > > (c) 2002-2004 convergence GmbH > > > > > > ----------------------------------------------------------- > > > > > > > > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00) > > > > (*) Direct/Memcpy: Using MMXEXT optimized memcpy() > > > > (!) Direct/Util: opening ''/dev/fb0'' and ''/dev/fb/0'' failed > > > > --> No such file or directory > > > > (!) DirectFB/FBDev: Error opening framebuffer device! > > > > (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER > > environment > > > > variable. > > > > (!) DirectFB/Core: Could not initialize ''system'' core! > > > > --> Initialization error! > > > > Could not initialize SDL - exiting > > > > got the same Problem here :) > > You don´t have a Framebufferdevice /dev/fb0. Create one withe > > mknod or > > configure udev properly. > > > > Second choice, use vnc (vnc=1) and connect with xvncviewer > > ip:0, so I do. > > > > here my config: > > > > > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > > builder = ''hvm'' > > memory = ''1024'' > > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > > > > > > disk = [ > > > > ''file:/home/xen/windoof/windisk.img,ioemu:hda,w'', > > ''file:/home/ar/WXPVOL_DE.ISO,ioemu:hdc:cdrom,r'' > > ] > > #disk = [ ''phy:/dev/hda,hda,r'' ] > > > > > > name = ''windoof'' > > > > > > vif = [''type=ioemu, bridge=xenbr0''] > > > > > > boot=''d'' > > vnc=1 > > vncpassword=''xyz'' > > vncunused=1 > > vncviewer=0 > > #vnclisten="127.0.0.1" > > serial=''pty'' > > sdl=0 > > > > > > > > greetings > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > __________ Informace od NOD32 2082 (20070226) __________ > > > > Tato zprava byla proverena antivirovym systemem NOD32. > > http://www.nod32.cz > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > > > > > __________ Informace od NOD32 2342 (20070621) __________ > > Tato zprava byla proverena antivirovym systemem NOD32. > http://www.nod32.cz > > > > >__________ Informace od NOD32 2342 (20070621) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-Jun-21 11:06 UTC
RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0
> -----Original Message----- > From: Artur Linhart - Linux communication > [mailto:AL.LINUX@bcpraha.com] > Sent: 21 June 2007 12:02 > To: Petersson, Mats; ''Andre Rein''; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > Hello, > > Yes there are a lot of differences (for example, in the section > dedicated to the initialization of the CPU1-3 there are no > messages by Xen, > by etch it is normally initialized - see evt. the attachments). > Related to the console and the fb device there are following > differences: > > Dmesg-xen: > io scheduler cfq registered (default) > Real Time Clock Driver v1.12ac > > - between both this two lines there is nothing by xen, but by > etch there is > the loading of the vesafb driver and creation of /dev/fb0: > > Dmesg-etch: > io scheduler cfq registered (default) > PCI: Setting latency timer of device 0000:00:02.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:02.0:pcie00] > Allocate Port Service[0000:00:02.0:pcie01] > PCI: Setting latency timer of device 0000:00:03.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:03.0:pcie00] > Allocate Port Service[0000:00:03.0:pcie01] > PCI: Setting latency timer of device 0000:00:04.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:04.0:pcie00] > Allocate Port Service[0000:00:04.0:pcie01] > PCI: Setting latency timer of device 0000:00:05.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:05.0:pcie00] > Allocate Port Service[0000:00:05.0:pcie01] > PCI: Setting latency timer of device 0000:00:06.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:06.0:pcie00] > Allocate Port Service[0000:00:06.0:pcie01] > PCI: Setting latency timer of device 0000:00:07.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:07.0:pcie00] > Allocate Port Service[0000:00:07.0:pcie01] > PCI: Setting latency timer of device 0000:01:00.0 to 64 > Allocate Port Service[0000:01:00.0:pcie10] > Allocate Port Service[0000:01:00.0:pcie11] > PCI: Setting latency timer of device 0000:02:00.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:02:00.0:pcie20] > Allocate Port Service[0000:02:00.0:pcie21] > Allocate Port Service[0000:02:00.0:pcie22] > PCI: Setting latency timer of device 0000:02:01.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:02:01.0:pcie20] > Allocate Port Service[0000:02:01.0:pcie21] > PCI: Setting latency timer of device 0000:02:02.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:02:02.0:pcie20] > Allocate Port Service[0000:02:02.0:pcie21] > vesafb: framebuffer at 0xb0000000, mapped to 0xffffc20010100000, using > 3072k, total 16384k > vesafb: mode is 1024x768x16, linelength=2048, pages=9 > vesafb: scrolling: redraw > vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 > Console: switching to colour frame buffer device 128x48 > fb0: VESA VGA frame buffer device > Real Time Clock Driver v1.12ac > > I have no idea, why by xen nothing happens...I don''t think the "Found MSI capability" has much to do with the FB, but I would say that it indicates that youre VESA-FB driver is either not loading at all (do you have "CONFIG_FB_VESA=y" in the .config for your Linux build?) or there''s something wrong with the driver that decides to not instantiate itself with no error message. -- Mats> > Cheers > > Archie > > -----Original Message----- > From: Petersson, Mats [mailto:Mats.Petersson@amd.com] > Sent: Thursday, June 21, 2007 12:23 PM > To: Artur Linhart - Linux communication; Andre Rein; > xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > > -----Original Message----- > > From: Artur Linhart - Linux communication > > [mailto:AL.LINUX@bcpraha.com] > > Sent: 21 June 2007 11:03 > > To: Petersson, Mats; ''Andre Rein''; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > Hello, Mats, > > > > I have problems with "xenified" Dom0 (Etch). The original Etch > > booted directly works normally, also framebuffer device is > > present and I can > > start the graphical applications like directvnc, etc.. But if > > I boot Etch as > > xen Dom0, the /dev/df0 is not present - also if I specify the kernel > > parameter vga=... then it is not reflected, the console is > > still in text > > mode... > > > > So, from the point of view of the mail before, it "is > > correctly set > > up" - in the original etch system - but udev does not > > recognize the devices > > under xen... > > > > Are there any other kernel options for xen kernel which > > could impact > > this behavior or any other configuration possibilities? For example > > something similar for Dom0 like I can specify for domU? > > What graphics driver are you using for your graphic card? > > Is it loading correctly for your Dom0 installation? Check > "dmesg" for both > native and Dom0 to see if there''s any differences. > > -- > Mats > > > > With best regards > > > > Archie > > > > > > -----Original Message----- > > From: Petersson, Mats [mailto:Mats.Petersson@amd.com] > > Sent: Thursday, June 21, 2007 10:58 AM > > To: Artur Linhart - Linux communication; Andre Rein; > > xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > > Artur Linhart - Linux communication > > > Sent: 20 June 2007 17:54 > > > To: ''Andre Rein''; xen-users@lists.xensource.com > > > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - > missing /dev/fb0 > > > > > > Hello, > > > > > > I have the same problem like the one described below... > > > > > > Did somebody resolved the issue with the missing > > > /dev/fd0 device? > > > > > > Mknod does not help. What does it mean "configure udev > > > properly"? If > > > fb works OK without Xen, how should I configure udev for xen > > > - what should > > > be modified in the xen configuration to get Dom0 working > > > again, like if > > > running without Xen? > > > > I don''t think there should be any difference between udev for > > native Linux > > and Xen-ified linux - the hint on configuring it "properly" > > was more to the > > point of "make sure it''s set up". > > > > But I guess another point is that /dev/fbN is the > > "frame-buffer", which is > > only available on certain models of graphics cards - you may > > not be able to > > do that with the graphics card you''ve specified in the domain > > config (are > > you by any chance using "stdvga=1"?). > > > > -- > > Mats > > > > > > Any help would be appreciated, > > > > > > With best regards > > > > > > Archie > > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > Andre Rein > > > Sent: Wednesday, February 28, 2007 4:09 PM > > > To: xen-users@lists.xensource.com > > > Subject: [Xen-users] Re: FULL VIRTUALIZATION > > > > > > Petersson, Mats <Mats.Petersson <at> amd.com> writes: > > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: Carlo [mailto:carlo <at> granisso.it] > > > > > Sent: 28 February 2007 10:54 > > > > > To: Petersson, Mats; Carlo; xen-users <at> lists.xensource.com > > > > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > > > > > > > > I''ve solved the first problem: path of qemu-dm in the > > > config file was > > > > > uncorrect... > > > > > > > > > > Now, qemu-dm say: > > > > > > > > > > domid: 6 > > > > > qemu: the number of cpus is 1 > > > > > shared page at pfn:1ffff, mfn: df18 > > > > > buffered io page at pfn:1fffd, mfn: df1a > > > > > > > > > > ---------------------- DirectFB v0.9.25 > > > --------------------- > > > > > (c) 2000-2002 convergence integrated media GmbH > > > > > (c) 2002-2004 convergence GmbH > > > > > > > > ----------------------------------------------------------- > > > > > > > > > > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00) > > > > > (*) Direct/Memcpy: Using MMXEXT optimized memcpy() > > > > > (!) Direct/Util: opening ''/dev/fb0'' and ''/dev/fb/0'' failed > > > > > --> No such file or directory > > > > > (!) DirectFB/FBDev: Error opening framebuffer device! > > > > > (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER > > > environment > > > > > variable. > > > > > (!) DirectFB/Core: Could not initialize ''system'' core! > > > > > --> Initialization error! > > > > > Could not initialize SDL - exiting > > > > > > got the same Problem here :) > > > You don´t have a Framebufferdevice /dev/fb0. Create one withe > > > mknod or > > > configure udev properly. > > > > > > Second choice, use vnc (vnc=1) and connect with xvncviewer > > > ip:0, so I do. > > > > > > here my config: > > > > > > > > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > > > builder = ''hvm'' > > > memory = ''1024'' > > > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > > > > > > > > > disk = [ > > > > > > ''file:/home/xen/windoof/windisk.img,ioemu:hda,w'', > > > ''file:/home/ar/WXPVOL_DE.ISO,ioemu:hdc:cdrom,r'' > > > ] > > > #disk = [ ''phy:/dev/hda,hda,r'' ] > > > > > > > > > name = ''windoof'' > > > > > > > > > vif = [''type=ioemu, bridge=xenbr0''] > > > > > > > > > boot=''d'' > > > vnc=1 > > > vncpassword=''xyz'' > > > vncunused=1 > > > vncviewer=0 > > > #vnclisten="127.0.0.1" > > > serial=''pty'' > > > sdl=0 > > > > > > > > > > > > greetings > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > __________ Informace od NOD32 2082 (20070226) __________ > > > > > > Tato zprava byla proverena antivirovym systemem NOD32. > > > http://www.nod32.cz > > > > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > > > > __________ Informace od NOD32 2342 (20070621) __________ > > > > Tato zprava byla proverena antivirovym systemem NOD32. > > http://www.nod32.cz > > > > > > > > > > > > > > __________ Informace od NOD32 2342 (20070621) __________ > > Tato zprava byla proverena antivirovym systemem NOD32. > http://www.nod32.cz > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Artur Linhart - Linux communication
2007-Jun-21 13:02 UTC
RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0
The kernel options are the same and are set to "y". But I have found in /dev/.udev/failed the file devices@platform@vesafb.0 But in no log found what could be wrong with vesafb... Is there any logging of udev events? I found only /dev/hotplug.log, which does not contain any interesting information (errors, etc.)... With regards Archie -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Petersson, Mats Sent: Thursday, June 21, 2007 1:06 PM To: Artur Linhart - Linux communication; Andre Rein; xen-users@lists.xensource.com Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0> -----Original Message----- > From: Artur Linhart - Linux communication > [mailto:AL.LINUX@bcpraha.com] > Sent: 21 June 2007 12:02 > To: Petersson, Mats; ''Andre Rein''; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > Hello, > > Yes there are a lot of differences (for example, in the section > dedicated to the initialization of the CPU1-3 there are no > messages by Xen, > by etch it is normally initialized - see evt. the attachments). > Related to the console and the fb device there are following > differences: > > Dmesg-xen: > io scheduler cfq registered (default) > Real Time Clock Driver v1.12ac > > - between both this two lines there is nothing by xen, but by > etch there is > the loading of the vesafb driver and creation of /dev/fb0: > > Dmesg-etch: > io scheduler cfq registered (default) > PCI: Setting latency timer of device 0000:00:02.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:02.0:pcie00] > Allocate Port Service[0000:00:02.0:pcie01] > PCI: Setting latency timer of device 0000:00:03.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:03.0:pcie00] > Allocate Port Service[0000:00:03.0:pcie01] > PCI: Setting latency timer of device 0000:00:04.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:04.0:pcie00] > Allocate Port Service[0000:00:04.0:pcie01] > PCI: Setting latency timer of device 0000:00:05.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:05.0:pcie00] > Allocate Port Service[0000:00:05.0:pcie01] > PCI: Setting latency timer of device 0000:00:06.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:06.0:pcie00] > Allocate Port Service[0000:00:06.0:pcie01] > PCI: Setting latency timer of device 0000:00:07.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:00:07.0:pcie00] > Allocate Port Service[0000:00:07.0:pcie01] > PCI: Setting latency timer of device 0000:01:00.0 to 64 > Allocate Port Service[0000:01:00.0:pcie10] > Allocate Port Service[0000:01:00.0:pcie11] > PCI: Setting latency timer of device 0000:02:00.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:02:00.0:pcie20] > Allocate Port Service[0000:02:00.0:pcie21] > Allocate Port Service[0000:02:00.0:pcie22] > PCI: Setting latency timer of device 0000:02:01.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:02:01.0:pcie20] > Allocate Port Service[0000:02:01.0:pcie21] > PCI: Setting latency timer of device 0000:02:02.0 to 64 > assign_interrupt_mode Found MSI capability > Allocate Port Service[0000:02:02.0:pcie20] > Allocate Port Service[0000:02:02.0:pcie21] > vesafb: framebuffer at 0xb0000000, mapped to 0xffffc20010100000, using > 3072k, total 16384k > vesafb: mode is 1024x768x16, linelength=2048, pages=9 > vesafb: scrolling: redraw > vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 > Console: switching to colour frame buffer device 128x48 > fb0: VESA VGA frame buffer device > Real Time Clock Driver v1.12ac > > I have no idea, why by xen nothing happens...I don''t think the "Found MSI capability" has much to do with the FB, but I would say that it indicates that youre VESA-FB driver is either not loading at all (do you have "CONFIG_FB_VESA=y" in the .config for your Linux build?) or there''s something wrong with the driver that decides to not instantiate itself with no error message. -- Mats> > Cheers > > Archie > > -----Original Message----- > From: Petersson, Mats [mailto:Mats.Petersson@amd.com] > Sent: Thursday, June 21, 2007 12:23 PM > To: Artur Linhart - Linux communication; Andre Rein; > xen-users@lists.xensource.com > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > > -----Original Message----- > > From: Artur Linhart - Linux communication > > [mailto:AL.LINUX@bcpraha.com] > > Sent: 21 June 2007 11:03 > > To: Petersson, Mats; ''Andre Rein''; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > Hello, Mats, > > > > I have problems with "xenified" Dom0 (Etch). The original Etch > > booted directly works normally, also framebuffer device is > > present and I can > > start the graphical applications like directvnc, etc.. But if > > I boot Etch as > > xen Dom0, the /dev/df0 is not present - also if I specify the kernel > > parameter vga=... then it is not reflected, the console is > > still in text > > mode... > > > > So, from the point of view of the mail before, it "is > > correctly set > > up" - in the original etch system - but udev does not > > recognize the devices > > under xen... > > > > Are there any other kernel options for xen kernel which > > could impact > > this behavior or any other configuration possibilities? For example > > something similar for Dom0 like I can specify for domU? > > What graphics driver are you using for your graphic card? > > Is it loading correctly for your Dom0 installation? Check > "dmesg" for both > native and Dom0 to see if there''s any differences. > > -- > Mats > > > > With best regards > > > > Archie > > > > > > -----Original Message----- > > From: Petersson, Mats [mailto:Mats.Petersson@amd.com] > > Sent: Thursday, June 21, 2007 10:58 AM > > To: Artur Linhart - Linux communication; Andre Rein; > > xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - missing /dev/fb0 > > > > > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > > Artur Linhart - Linux communication > > > Sent: 20 June 2007 17:54 > > > To: ''Andre Rein''; xen-users@lists.xensource.com > > > Subject: RE: [Xen-users] Re: FULL VIRTUALIZATION - > missing /dev/fb0 > > > > > > Hello, > > > > > > I have the same problem like the one described below... > > > > > > Did somebody resolved the issue with the missing > > > /dev/fd0 device? > > > > > > Mknod does not help. What does it mean "configure udev > > > properly"? If > > > fb works OK without Xen, how should I configure udev for xen > > > - what should > > > be modified in the xen configuration to get Dom0 working > > > again, like if > > > running without Xen? > > > > I don''t think there should be any difference between udev for > > native Linux > > and Xen-ified linux - the hint on configuring it "properly" > > was more to the > > point of "make sure it''s set up". > > > > But I guess another point is that /dev/fbN is the > > "frame-buffer", which is > > only available on certain models of graphics cards - you may > > not be able to > > do that with the graphics card you''ve specified in the domain > > config (are > > you by any chance using "stdvga=1"?). > > > > -- > > Mats > > > > > > Any help would be appreciated, > > > > > > With best regards > > > > > > Archie > > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > > Andre Rein > > > Sent: Wednesday, February 28, 2007 4:09 PM > > > To: xen-users@lists.xensource.com > > > Subject: [Xen-users] Re: FULL VIRTUALIZATION > > > > > > Petersson, Mats <Mats.Petersson <at> amd.com> writes: > > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: Carlo [mailto:carlo <at> granisso.it] > > > > > Sent: 28 February 2007 10:54 > > > > > To: Petersson, Mats; Carlo; xen-users <at> lists.xensource.com > > > > > Subject: RE: [Xen-users] FULL VIRTUALIZATION > > > > > > > > > > I''ve solved the first problem: path of qemu-dm in the > > > config file was > > > > > uncorrect... > > > > > > > > > > Now, qemu-dm say: > > > > > > > > > > domid: 6 > > > > > qemu: the number of cpus is 1 > > > > > shared page at pfn:1ffff, mfn: df18 > > > > > buffered io page at pfn:1fffd, mfn: df1a > > > > > > > > > > ---------------------- DirectFB v0.9.25 > > > --------------------- > > > > > (c) 2000-2002 convergence integrated media GmbH > > > > > (c) 2002-2004 convergence GmbH > > > > > > > > ----------------------------------------------------------- > > > > > > > > > > (*) DirectFB/Core: Single Application Core. (2006-12-04 07:00) > > > > > (*) Direct/Memcpy: Using MMXEXT optimized memcpy() > > > > > (!) Direct/Util: opening ''/dev/fb0'' and ''/dev/fb/0'' failed > > > > > --> No such file or directory > > > > > (!) DirectFB/FBDev: Error opening framebuffer device! > > > > > (!) DirectFB/FBDev: Use ''fbdev'' option or set FRAMEBUFFER > > > environment > > > > > variable. > > > > > (!) DirectFB/Core: Could not initialize ''system'' core! > > > > > --> Initialization error! > > > > > Could not initialize SDL - exiting > > > > > > got the same Problem here :) > > > You don´t have a Framebufferdevice /dev/fb0. Create one withe > > > mknod or > > > configure udev properly. > > > > > > Second choice, use vnc (vnc=1) and connect with xvncviewer > > > ip:0, so I do. > > > > > > here my config: > > > > > > > > > kernel = ''/usr/lib/xen-3.0.3-1/boot/hvmloader'' > > > builder = ''hvm'' > > > memory = ''1024'' > > > device_model=''/usr/lib/xen-3.0.3-1/bin/qemu-dm'' > > > > > > > > > disk = [ > > > > > > ''file:/home/xen/windoof/windisk.img,ioemu:hda,w'', > > > ''file:/home/ar/WXPVOL_DE.ISO,ioemu:hdc:cdrom,r'' > > > ] > > > #disk = [ ''phy:/dev/hda,hda,r'' ] > > > > > > > > > name = ''windoof'' > > > > > > > > > vif = [''type=ioemu, bridge=xenbr0''] > > > > > > > > > boot=''d'' > > > vnc=1 > > > vncpassword=''xyz'' > > > vncunused=1 > > > vncviewer=0 > > > #vnclisten="127.0.0.1" > > > serial=''pty'' > > > sdl=0 > > > > > > > > > > > > greetings > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > __________ Informace od NOD32 2082 (20070226) __________ > > > > > > Tato zprava byla proverena antivirovym systemem NOD32. > > > http://www.nod32.cz > > > > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > > > > __________ Informace od NOD32 2342 (20070621) __________ > > > > Tato zprava byla proverena antivirovym systemem NOD32. > > http://www.nod32.cz > > > > > > > > > > > > > > __________ Informace od NOD32 2342 (20070621) __________ > > Tato zprava byla proverena antivirovym systemem NOD32. > http://www.nod32.cz > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users __________ Informace od NOD32 2342 (20070621) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users