Re: Boot of 9.1 under qemu-kvm 1.3 hangs at pci probing
In article 50ce5805.7010...@cran.org.uk you write: I'm trying to install FreeBSD 9.1 in a Proxmox KVM, using qemu-kvm 1.3, but the boot process is hanging: pbib0: matched entry for 0.1 INTA pbib0: slot 1 INTA hardwired to IRQ 9 ioapic0: Changing polarity for pin 9 to low found - vendor=0x1013, dev=0x00b8, revid=0x00 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0103, statreg=0x, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0ns), maxlat=0x00 (0ns) [hang] Has anyone come across this before and know of any workarounds? Just in case you haven't meanwhile found this yourself (and for the archives), this is caused by an incompatible change in seabios [1] that qemu uses. I hope this will be fixed for qemu 1.3.1, a fixed bios.bin that you can pass to qemu/kvm with -bios has been posted in this thread: https://lists.nongnu.org/archive/html/qemu-devel/2012-12/msg01703.html HTH, :) Juergen [1] http://git.qemu.org/?p=seabios.git;a=commit;h=4540409d19a4baeec5006d925cfca19f8038a96e ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Boot of 9.1 under qemu-kvm 1.3 hangs at pci probing
I'm trying to install FreeBSD 9.1 in a Proxmox KVM, using qemu-kvm 1.3, but the boot process is hanging: pbib0: matched entry for 0.1 INTA pbib0: slot 1 INTA hardwired to IRQ 9 ioapic0: Changing polarity for pin 9 to low found - vendor=0x1013, dev=0x00b8, revid=0x00 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0103, statreg=0x, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0ns), maxlat=0x00 (0ns) [hang] Has anyone come across this before and know of any workarounds? -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Possible to run freebsd mips under QEMU???
Hi is there any update on this? I would like to be able to run FreeBSD MIPS and I don't have a MIPS box! You wrote: On Tue, May 15, 2012 at 10:06 AM, Adrian Chadd adr...@freebsd.org wrote: The short answer is yes - I've seen this. I've not done it myself though, I've just acquired cheap mips hardware. I'd currently preference the use of GXemul over the use of QEMU. GXemul has a built-in test machine that we support disk, networking and SMP on now. I'll try to take the time to write-up complete instructions (I've done it so many times I'd surely leave something out if I wrote it up right now) in the next few days, or perhaps rwatson will, as I know his lab is using GXemul in that way. We should try to get something on the Wiki for this as soon as possible as it's a very easy way to get started with FreeBSD on MIPS, and is infinitely-useful for debugging and some kinds of performance testing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fw: qemu error mounting cd and no internet connection with custom kernel
--- On Sun, 5/23/10, Heshmat Ismail real_precious_st...@yahoo.com wrote: From: Heshmat Ismail real_precious_st...@yahoo.com Subject: qemu error mounting cd and no internet connection with custom kernel To: freebsd-emulat...@freebsd.org Date: Sunday, May 23, 2010, 8:35 PM Hi all, I have built and installed a custom kernel on a freebsd 8.0-RELEASE machine (host os),then i installed qemu from the packages and used the following commands:- # qemu-img create -f qcow2 freebsd.image 10G # qemu -m 256 -hda freebsd.image -cdrom /dev/acd0 -boot d # qemu freebsd.image So, the guest os is the same as the host os and i installed it from the same DVD (freebsd 8.0-RELEASE). I face two problems with the guest os (the host os is working fine):- Problem#1 When i try to install any packages from the DVD by running # sysinstall =configure=packages=Install from freebsd CD/DVD i got : Error mounting /dev/acd0 on /dist: Input/output error (5). Problem#2 I put these lines in /etc/rc.conf: hald_enable=YES dbus_enable=YES ifconfig_ed0=DHCP but i can not connect to the internet (the above configuration in the host os works fine).When i use the GENERIC kernel i get no problems.Here are the differences between the two kernels,the GENERIC and MYKERNEL. # cd /usr/src/sys/i386/conf # diff -u GENERIC MYKERNEL --- GENERIC 2009-11-09 23:48:01.0 + +++ MYKERNEL 2010-05-12 17:06:41.0 + @@ -1,4 +1,4 @@ -# + # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the config(5) manual page, @@ -18,10 +18,10 @@ # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.519.2.4.2.2 2009/11/09 23:48:01 kensmith Exp $ -cpu I486_CPU -cpu I586_CPU +#cpu I486_CPU +#cpu I586_CPU cpu I686_CPU -ident GENERIC +ident MYKERNEL # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. @@ -42,30 +42,30 @@ options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists -options UFS_DIRHASH # Improve performance on big directories +#options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device -options NFSCLIENT # Network Filesystem Client -options NFSSERVER # Network Filesystem Server -options NFSLOCKD # Network Lock Manager -options NFS_ROOT # NFS usable as /, requires NFSCLIENT -options MSDOSFS # MSDOS Filesystem -options CD9660 # ISO 9660 Filesystem -options PROCFS # Process filesystem (requires PSEUDOFS) -options PSEUDOFS # Pseudo-filesystem framework +#options NFSCLIENT # Network Filesystem Client +#options NFSSERVER # Network Filesystem Server +#options NFSLOCKD # Network Lock Manager +#options NFS_ROOT # NFS usable as /, requires NFSCLIENT +#options MSDOSFS # MSDOS Filesystem +#options CD9660 # ISO 9660 Filesystem +#options PROCFS # Process filesystem (requires PSEUDOFS) +#options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) -options COMPAT_FREEBSD4 # Compatible with FreeBSD4 -options COMPAT_FREEBSD5 # Compatible with FreeBSD5 -options COMPAT_FREEBSD6 # Compatible with FreeBSD6 +#options COMPAT_FREEBSD4 # Compatible with FreeBSD4 +#options COMPAT_FREEBSD5 # Compatible with FreeBSD5 +#options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 -options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI -options KTRACE # ktrace(1) support +#options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI +#options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory -options SYSVMSG # SYSV-style message queues -options SYSVSEM # SYSV-style semaphores +#options SYSVMSG # SYSV-style message queues +#options SYSVSEM # SYSV
Why is Qemu not in Handbook
For years I used Qemu to run Windows XP under FreeBSD. It worked fine. A few months ago I saw a message that VirtualBox was now working correctly under FreeBSD. So I tried to install it and it wouldn't build. But that's not the actual topic of my question. In the process of trying to install VirtualBox I noticed that Qemu is not mentioned in the Handbook. It's not even mentioned under Other Virtualization Options. So my actual question is: Why is Qemu not mentioned in the Handbook? There is already a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 Even just a mention with a link to http://wiki.freebsd.org/qemu would be helpful. Thanks, -- -- Bob Johnson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why is Qemu not in Handbook
On Wed, Apr 14, 2010 at 10:24 AM, Bob Johnson fbsdli...@gmail.com wrote: For years I used Qemu to run Windows XP under FreeBSD. It worked fine. A few months ago I saw a message that VirtualBox was now working correctly under FreeBSD. So I tried to install it and it wouldn't build. But that's not the actual topic of my question. In the process of trying to install VirtualBox I noticed that Qemu is not mentioned in the Handbook. It's not even mentioned under Other Virtualization Options. So my actual question is: Why is Qemu not mentioned in the Handbook? There is already a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 Even just a mention with a link to http://wiki.freebsd.org/qemu would be helpful. Thanks, you mean like this? http://www.freebsdgr.org/handbook-mine/virtualization-host.html I don't know why it's not on the official one, IIRC it used to be. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why is Qemu not in Handbook
On Wed, 14 Apr 2010 11:24:11 -0400 Bob Johnson fbsdli...@gmail.com wrote: Why is Qemu not mentioned in the Handbook? I don't know if this is the actual reason, but from the ports UPDATING file: Also note the 0.11 stable branch is the last qemu branch that still supports kqemu, so if you depend on reasonably fast emulation on FreeBSD you should start looking for alternatives some time soon. (VirtualBox?) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why is Qemu not in Handbook
On 14/04/2010 8:55 μ.μ., Adam Vande More wrote: On Wed, Apr 14, 2010 at 10:24 AM, Bob Johnson fbsdli...@gmail.com wrote: For years I used Qemu to run Windows XP under FreeBSD. It worked fine. A few months ago I saw a message that VirtualBox was now working correctly under FreeBSD. So I tried to install it and it wouldn't build. But that's not the actual topic of my question. In the process of trying to install VirtualBox I noticed that Qemu is not mentioned in the Handbook. It's not even mentioned under Other Virtualization Options. So my actual question is: Why is Qemu not mentioned in the Handbook? There is already a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 Even just a mention with a link to http://wiki.freebsd.org/qemu would be helpful. Thanks, you mean like this? http://www.freebsdgr.org/handbook-mine/virtualization-host.html I don't know why it's not on the official one, IIRC it used to be. This is not the official Handbook, but my own patch queue, and yes it has been in there for too long. Hopefully I will have a lot more free time in a few weeks, there are more patches like this that need to get reviewed and committed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why is Qemu not in Handbook
On Wed, Apr 14, 2010 at 2:45 PM, Manolis Kiagias son...@otenet.gr wrote: This is not the official Handbook, but my own patch queue, and yes it has been in there for too long. Hopefully I will have a lot more free time in a few weeks, there are more patches like this that need to get reviewed and committed. I think there will still be a number of people wanting to use qemu for it's usb pass though. So having a qemu entry could still be appropriate. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
QEMU - IPadresses.
Hi, I wonder how you restrict user inside a qemu-virtualization to a certain IP-adress. I mean, what happends if someone decides to change to a conflicting IP? -- Peter Ankerstål pe...@pean.org http://www.pean.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
UVC Webcam under Qemu/Windows
Hi, Have anyone succeeded using the USB UVC webcam under qemu (in Windows under Qemu because there are drivers for the webcam in Windows)? I tried and it almost worked. The webcam's led lighted up but I never got the image from the webcam and Windows told that the device (webcam) is not working. -- EforeZZ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: vde qemu write: No buffer space available
On Friday 26 June 2009 10:04:13 Adam Vande More wrote: I'm having issues with high network throughput with vde and qemu. There are two qemu vm's each running debian lenny and they are configured for drbd. The vm's work fine until drbd is started then the networking fails. The only message I get(on the host side) is write: No buffer space available It can be a driver issue, but the error message is somewhat misleading as it can be the result of an ill-configured firewall rule. Typically this happens when no state exists for the outgoing connection. which is echoed to console, and nothing appears in the logs. I believe this to be an issue with vde, but I can't be certain because I can't seem to find any way to turn on more extensive logging. Anyone have an idea how to resolve this? You should check netstat -m to make sure there are mbufs available and if there is check your firewall. If all seems ok, try freebsd-net list for any known issues, since you didn't get any me too's here. You may want to specify a bit more info, like pciconf -lv for the vde device, vmstat -i at the time of the errors, ifconfig vde0 output and any firewall information (including I don't have one or error persists if firewall is disabled). -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: QEMU + FreeBSD
El día Friday, June 26, 2009 a las 10:37:14AM -0400, Jim escribió: I have installed FreeBSD 7.2 on my notebook in the last week, and installed QEmu as well. I cannot seem to get the network interface working. It works on my desktop machine, but that is running 7.0 looking around, I tried to find some other options, and went here: http://wiki.freebsd.org/qemu and got stuck at this step: # sysctl net.link.ether.bridge_cfg=fxp0,tap0 # sysctl net.link.ether.bridge.enable=1 because nothing matching net.link.ether.bridge* exists. Does anyone know of a current good setup document? thanks, -Jim Stapleton Jim, You should have the following kernel modules loaded: # kldload kqemu # kldload if_tap # kldload aio Then you may either used a devd hook to ifconfig the interface or (as I do) start 'qemu' as root. It will execute a shell script when it brings up the interface as: $ cat /usr/local/etc/qemu-ifup #!/bin/sh /sbin/ifconfig $1 172.20.0.1 (for the 'ifconfig' you must be root, or use devd hook, or 'sudo' in the script). That's all. Set the other end of the NIC in the guest system to IP 172.20.0.2 end the communication with the host OS (your FreeBSD 7.2) should be fine. To reach the outerworld from the guest, I'm using NAT in the host OS. Check the FreeBSD handbook how to enable this. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: QEMU + FreeBSD
On Fri, Jun 26, 2009 at 9:37 AM, Jim stapleton...@gmail.com wrote: I have installed FreeBSD 7.2 on my notebook in the last week, and installed QEmu as well. I cannot seem to get the network interface working. It works on my desktop machine, but that is running 7.0 looking around, I tried to find some other options, and went here: http://wiki.freebsd.org/qemu and got stuck at this step: # sysctl net.link.ether.bridge_cfg=fxp0,tap0 # sysctl net.link.ether.bridge.enable=1 because nothing matching net.link.ether.bridge* exists. Does anyone know of a current good setup document? thanks, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org There is vde2 port for it depending networking needs, standard dhcp/nat slirp type should work straight from standard install of qemu though. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
QEMU + FreeBSD
I have installed FreeBSD 7.2 on my notebook in the last week, and installed QEmu as well. I cannot seem to get the network interface working. It works on my desktop machine, but that is running 7.0 looking around, I tried to find some other options, and went here: http://wiki.freebsd.org/qemu and got stuck at this step: # sysctl net.link.ether.bridge_cfg=fxp0,tap0 # sysctl net.link.ether.bridge.enable=1 because nothing matching net.link.ether.bridge* exists. Does anyone know of a current good setup document? thanks, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
vde qemu write: No buffer space available
I'm having issues with high network throughput with vde and qemu. There are two qemu vm's each running debian lenny and they are configured for drbd. The vm's work fine until drbd is started then the networking fails. The only message I get(on the host side) is write: No buffer space available which is echoed to console, and nothing appears in the logs. I believe this to be an issue with vde, but I can't be certain because I can't seem to find any way to turn on more extensive logging. Anyone have an idea how to resolve this? Thanks, -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
virtual network with qemu
Hi to all. I'd like to implement a little virtual network using QEMU 0.10.2, but, until now, I have failed. This is the situation. Host: AMD 64 running FreeBSD 7.2 #ifconfig nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=10bRXCSUM,TXCSUM,VLAN_MTU,TSO4 ether 00:15:f2:44:2d:f9 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT metric 0 mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 I've create an image using the FreeBSD 7.2 DVD: #qemu-img create -f qcow2 hda fbsd72.img 10G The image has been created. #qemu -L /usr/local/share/qemu/ -cdrom /dev/acd0 -m 512 -boot d fbsd72.img Alfter a long time, the installation of the guest system has been completed. When the installation program asked for information about network configuration, as a first step, I chose DHCP configuration and, as usualy, the network has been set like this: IP 10.0.2.15/255.255.255.0 gateway 10.0.2.2 nameserver 10.0.2.3 When the installation of the guest PC was finished, I've copied the image to pc01.img, to keep the original untouched. After that I've started qemu like this: #qemu -L /usr/local/share/qemu -localtime -net nic,macaddr=00:15:f2:44:2d:01 -net socket,mcast=230.0.0.1:1234 -hda pc01.img -cdrom /dev/acd0 but the network in the guest system does not work. ifconfig in the guest system tells: #ifconfig -a ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:15:f2:44:2d:01 media: Ethernet 10baseT/UTP full-duplex plip0: ... lo0: ... If I try: #ping 10.0.2.2 (the gateway) all packets are lost. For this reason, I've tryed a static IP configuration like this: IP 10.0.2.4/255.255.255.0 gateway 10.0.2.2 nameserver 10.0.2.3 but the gateway does not respond. So it is useless to try with a second guest system. Please help. Sorry for my bad english. Marco ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: virtual network with qemu
marco.borsat...@poste.it wrote: When the installation program asked for information about network configuration, as a first step, I chose DHCP configuration and, as usualy, the network has been set like this: IP 10.0.2.15/255.255.255.0 If I recall correctly qemu has a built-in DHCP server. That's the one that served you, not a real DHCP server running on your LAN, that is, you are not in any way connected to the real network. #qemu -L /usr/local/share/qemu -localtime -net nic,macaddr=00:15:f2:44:2d:01 -net socket,mcast=230.0.0.1:1234 -hda pc01.img -cdrom /dev/acd0 but the network in the guest system does not work. It makes sense, that the multicast option will work between virtual hosts only. That is, it uses multicast to provide a virtual broadcast domain, which appears to the host operating system as a ethernet device. ifconfig in the guest system tells: #ifconfig -a ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:15:f2:44:2d:01 media: Ethernet 10baseT/UTP full-duplex plip0: ... lo0: ... If I try: #ping 10.0.2.2 (the gateway) all packets are lost. For this reason, I've tryed a static IP configuration like this: IP 10.0.2.4/255.255.255.0 gateway 10.0.2.2 nameserver 10.0.2.3 but the gateway does not respond. So it is useless to try with a second guest system. No, infact it's the exact opposite. This type of device will work *only* if you add another virtual system. To get connected to the real network, you must use tap devices. Correction: Browsing the qemu's wiki I found out that there is a newer and simpler approach that I am not familiar with: http://calamari.reverse-dns.net:980/cgi-bin/moin.cgi/user-net So, if you do want internet access, just remove all network associated options and it will work automagically. If you just want to connect guest systems together use multicast or socket or ... HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
virtual network with qemu
First, thank you. You are right, qemu has an internal DHCP server, which should be perfect for me, becuse I would like to emulate a network without any contact with external (real) world. The problem is that my virtual PC can't ping the gateway. For my idea (this is just a way to study a project for a network without a real network) the communication is intended only among virtual PCs. But If I can't contact the (virtual) gateway will it be possible to contact another virtual PC on a different subnet? Or even on the same subnet? In my idea I would like to create a little but complex net with one master controller, a slave controller, a little number of client belonging to different subnets. Maybe with or without a DHCP server. Marco -- Original Header --- From : Nikos Vassiliadis nvass9...@gmx.com To : marco.borsat...@poste.it marco.borsat...@poste.it Cc : freebsd-questions@freebsd.org Date : Thu, 14 May 2009 11:28:59 +0300 Subject : Re: virtual network with qemu marco.borsat...@poste.it wrote: When the installation program asked for information about network configuration, as a first step, I chose DHCP configuration and, as usualy, the network has been set like this: IP 10.0.2.15/255.255.255.0 If I recall correctly qemu has a built-in DHCP server. That's the one that served you, not a real DHCP server running on your LAN, that is, you are not in any way connected to the real network. #qemu -L /usr/local/share/qemu -localtime -net nic,macaddr=00:15:f2:44:2d:01 -net socket,mcast=230.0.0.1:1234 -hda pc01.img -cdrom /dev/acd0 but the network in the guest system does not work. It makes sense, that the multicast option will work between virtual hosts only. That is, it uses multicast to provide a virtual broadcast domain, which appears to the host operating system as a ethernet device. ifconfig in the guest system tells: #ifconfig -a ed0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:15:f2:44:2d:01 media: Ethernet 10baseT/UTP full-duplex plip0: ... lo0: ... If I try: #ping 10.0.2.2 (the gateway) all packets are lost. For this reason, I've tryed a static IP configuration like this: IP 10.0.2.4/255.255.255.0 gateway 10.0.2.2 nameserver 10.0.2.3 but the gateway does not respond. So it is useless to try with a second guest system. No, infact it's the exact opposite. This type of device will work *only* if you add another virtual system. To get connected to the real network, you must use tap devices. Correction: Browsing the qemu's wiki I found out that there is a newer and simpler approach that I am not familiar with: http://calamari.reverse-dns.net:980/cgi-bin/moin.cgi/user-net So, if you do want internet access, just remove all network associated options and it will work automagically. If you just want to connect guest systems together use multicast or socket or ... HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: virtual network with qemu
marco.borsat...@poste.it wrote: First, thank you. You are right, qemu has an internal DHCP server, which should be perfect for me, becuse I would like to emulate a network without any contact with external (real) world. The problem is that my virtual PC can't ping the gateway. For my idea (this is just a way to study a project for a network without a real network) the communication is intended only among virtual PCs. But If I can't contact the (virtual) gateway will it be possible to contact another virtual PC on a different subnet? Or even on the same subnet? In my idea I would like to create a little but complex net with one master controller, a slave controller, a little number of client belonging to different subnets. Maybe with or without a DHCP server. Yes, hosts on the same IP network, which of course are on the same broadcast domain, are able to communicate with each other with no other intermediates. A gateway is required only if you want to communicate with other networks. So, you have to create, let's say, 3 virtual PCs: 1) host_a on network A 2) host_b on network B 3) router_a on both networks A and B That's all. I guess, qemu uses the multicast solution to create virtual broadcast domains, like a switch does. qemu, I guess, has no knowledge of what happens on these ethernets, like a real ethernet switch. It's a real cool solution, since the user is able to create networks than can span several physical machines. Maybe you should use socket instead of mcast, don't really know the pros and cons of those two. Last but not least, since you seem to look for a learning tool, let me suggest two great ones: 1) imunes, you need vmware player for a quick start. http://www.imunes.net/virtnet/ 2) netkit http://wiki.netkit.org/index.php/Download_Official I have extensively used imunes and it's great. You should also check netkit. In case, it matters, the latter is GNU/Linux based. HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: virtual network with qemu
Thank you twice: the communication between 2 virtual PCs works. Now should I configure another virtual PC as a gateway with a netmask, say, 255.0.0.0? The virtual PC have a calss B netmask. I will also try the tools I've suggested to me. Marco -- Original Header --- From : Nikos Vassiliadis nvass9...@gmx.com To : marco.borsat...@poste.it marco.borsat...@poste.it Cc : freebsd-questions@freebsd.org Date : Thu, 14 May 2009 16:08:01 +0300 Subject : Re: virtual network with qemu marco.borsat...@poste.it wrote: First, thank you. You are right, qemu has an internal DHCP server, which should be perfect for me, becuse I would like to emulate a network without any contact with external (real) world. The problem is that my virtual PC can't ping the gateway. For my idea (this is just a way to study a project for a network without a real network) the communication is intended only among virtual PCs. But If I can't contact the (virtual) gateway will it be possible to contact another virtual PC on a different subnet? Or even on the same subnet? In my idea I would like to create a little but complex net with one master controller, a slave controller, a little number of client belonging to different subnets. Maybe with or without a DHCP server. Yes, hosts on the same IP network, which of course are on the same broadcast domain, are able to communicate with each other with no other intermediates. A gateway is required only if you want to communicate with other networks. So, you have to create, let's say, 3 virtual PCs: 1) host_a on network A 2) host_b on network B 3) router_a on both networks A and B That's all. I guess, qemu uses the multicast solution to create virtual broadcast domains, like a switch does. qemu, I guess, has no knowledge of what happens on these ethernets, like a real ethernet switch. It's a real cool solution, since the user is able to create networks than can span several physical machines. Maybe you should use socket instead of mcast, don't really know the pros and cons of those two. Last but not least, since you seem to look for a learning tool, let me suggest two great ones: 1) imunes, you need vmware player for a quick start. http://www.imunes.net/virtnet/ 2) netkit http://wiki.netkit.org/index.php/Download_Official I have extensively used imunes and it's great. You should also check netkit. In case, it matters, the latter is GNU/Linux based. HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: virtual network with qemu
On Thu, 14 May 2009 13:39:17 +0200 marco\.borsati...@poste\.it marco.borsat...@poste.it wrote: First, thank you. You are right, qemu has an internal DHCP server, which should be perfect for me, becuse I would like to emulate a network without any contact with external (real) world. The problem is that my virtual PC can't ping the gateway. For my idea (this is just a way to study a project for a network without a real network) the communication is intended only among virtual PCs. But If I can't contact the (virtual) gateway will it be possible to contact another virtual PC on a different subnet? The problem is that ping is a setuid binary, so qemu cant send a ping into the outside world as an ordinary user process. I think you may be able to ping between two emulated machine within qemu. Even if you can't it might be worth staying with qemu's networking, if pings aren't essential, as it sounds closer to what you need than networking via tap. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: virtual network with qemu
On Thu, May 14, 2009 at 07:53:32AM +0200, marco.borsat...@poste.it wrote: Hi to all. I'd like to implement a little virtual network using QEMU 0.10.2, but, until now, I have failed. This is the situation. Host: AMD 64 running FreeBSD 7.2 #ifconfig nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=10bRXCSUM,TXCSUM,VLAN_MTU,TSO4 ether 00:15:f2:44:2d:f9 inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255 media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT metric 0 mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 I've create an image using the FreeBSD 7.2 DVD: #qemu-img create -f qcow2 hda fbsd72.img 10G The image has been created. #qemu -L /usr/local/share/qemu/ -cdrom /dev/acd0 -m 512 -boot d fbsd72.img Alfter a long time, the installation of the guest system has been completed. It would probably be faster to use a FreeBSD ISO image instead of the real CD drive. When the installation program asked for information about network configuration, as a first step, I chose DHCP configuration and, as usualy, the network has been set like this: IP 10.0.2.15/255.255.255.0 gateway 10.0.2.2 nameserver 10.0.2.3 When the installation of the guest PC was finished, I've copied the image to pc01.img, to keep the original untouched. After that I've started qemu like this: #qemu -L /usr/local/share/qemu -localtime -net nic,macaddr=00:15:f2:44:2d:01 -net socket,mcast=230.0.0.1:1234 -hda pc01.img -cdrom /dev/acd0 but the network in the guest system does not work. Try the following command instead: qemu -L /usr/local/share/qemu -localtime -net nic -net user -hda pc01.img Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpASfY2VzOsL.pgp Description: PGP signature
Re: virtual network with qemu
marco.borsat...@poste.it wrote: Thank you twice: the communication between 2 virtual PCs works. Now should I configure another virtual PC as a gateway with a netmask, say, 255.0.0.0? The virtual PC have a calss B netmask. Yes, read bellow. I will also try the tools I've suggested to me. All IP addressing is pretty much automated in imunes, so you can create quickly the needed simulation environment. It's also somehow integrated with quagga, so you can use dynamic routing(OSPF, RIP, BGP and maybe IS-IS) besides static routing. But, anyway, it's a time saver to have all network interfaces configured automatically by the program. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.0-STABLE qemu not terminating
El día Thursday, April 23, 2009 a las 10:22:52PM +0200, Juergen Lock escribió: a new effect is that the qemu proc ends on termination of guest OS; the flag -no-shutdown does not help; Oh, yeah, same here. I've just reported this on the qemu list, and btw kvm seems to be affected too: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/362550/+viewstatus another issue is, when I'm using: -kernel-kqemu Enable KQEMU full virtualization (default is user mode only). the guest system (XP SP3) crashes short after coming up; without -kernel-kqemu I'm not sure if Qemu does make use of the kqemu.ko, it is so slow, esp. on disk i/o; I have loaded kqemu.ko on boot and if Qemu is up I can't kldunload it; but I really don't know if it makes use of it; matthais -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.0-STABLE qemu not terminating
On Fri, Apr 24, 2009 at 02:17:51PM +0200, Matthias Apitz wrote: El día Thursday, April 23, 2009 a las 10:22:52PM +0200, Juergen Lock escribió: a new effect is that the qemu proc ends on termination of guest OS; the flag -no-shutdown does not help; Oh, yeah, same here. I've just reported this on the qemu list, and btw kvm seems to be affected too: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/362550/+viewstatus another issue is, when I'm using: -kernel-kqemu Enable KQEMU full virtualization (default is user mode only). the guest system (XP SP3) crashes short after coming up; without -kernel-kqemu I'm not sure if Qemu does make use of the kqemu.ko, it is so slow, esp. on disk i/o; I have loaded kqemu.ko on boot and if Qemu is up I can't kldunload it; but I really don't know if it makes use of it; Actually it does, just not for guest kernel code, only userland. (If you want to turn off kqemu completely use -no-kqemu, then it'll run even slower. :) Anyway I've got one report that reinstalling an xp guest (it was originally installed using an older qemu version) fixed -kernel-kqemu instabilites at least for one guy (it worked for him with the old qemu) - it is still true however that kqemu, especially with -kernel-kqemu, is far from perfect, i.e. it doesn't really work for all types of guests, and the fact that the linux folks have pretty much deprecated kqemu in favour of kvm doesn't really help its cause either... (And yes we really could use a finished kvm port for the people that do have a recent cpu with the necessary features, at least on linux kvm is also much faster than -kernel-kqemu, and it works for more guests.) HTH, Juergen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.0-STABLE qemu not terminating
El día Tuesday, March 24, 2009 a las 07:24:26PM +0100, Juergen Lock escribió: While I don't remeber seeing reports about this particular issue, it is still very well possible that it has been fixed in the meantime, so I'd advise you to update. (the port is at 0.10.1 now, which contains quite a few bugfixes and improvements... Don't forget to read UPDATING and the pkg-message of the port tho.) ... I've port updated to: kqemu-kmod-devel-1.4.0.p1_2 Kernel Accelerator for QEMU CPU Emulator (development versi qemu-0.10.2 QEMU CPU Emulator and the problem went away; a new effect is that the qemu proc ends on termination of guest OS; the flag -no-shutdown does not help; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.0-STABLE qemu not terminating
On Thu, Apr 23, 2009 at 11:43:56AM +0200, Matthias Apitz wrote: El día Tuesday, March 24, 2009 a las 07:24:26PM +0100, Juergen Lock escribió: While I don't remeber seeing reports about this particular issue, it is still very well possible that it has been fixed in the meantime, so I'd advise you to update. (the port is at 0.10.1 now, which contains quite a few bugfixes and improvements... Don't forget to read UPDATING and the pkg-message of the port tho.) ... I've port updated to: kqemu-kmod-devel-1.4.0.p1_2 Kernel Accelerator for QEMU CPU Emulator (development versi qemu-0.10.2 QEMU CPU Emulator and the problem went away; That's good to hear. :) a new effect is that the qemu proc ends on termination of guest OS; the flag -no-shutdown does not help; Oh, yeah, same here. I've just reported this on the qemu list, and btw kvm seems to be affected too: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/362550/+viewstatus HTH, Juergen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
qemu cutpaste between X11 -- Windows
Hello, Is there some way to cutpaste text between the UNIX desktop (KDE) and the qemu-0.10.2 VM running XP as a guest system? thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: qemu cutpaste between X11 -- Windows
Run the vm with -vnc flag enabled. Then connect using vncviewer. Alternatively connect to the XP system using rdesktop. /Craig B On Wed, 2009-04-22 at 10:00 +0200, Matthias Apitz wrote: Hello, Is there some way to cutpaste text between the UNIX desktop (KDE) and the qemu-0.10.2 VM running XP as a guest system? thx matthias ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
qemu: booting from USB key?
Hello, How could I let boot the VM qemu from an USB key? I've checked the man page but it is only saying ... Boot on floppy (a), hard disk (c), CD-ROM (d), or Etherboot (n).. any idea? thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: qemu: booting from USB key?
USB is a disk On Wed, 1 Apr 2009, Matthias Apitz wrote: Hello, How could I let boot the VM qemu from an USB key? I've checked the man page but it is only saying ... Boot on floppy (a), hard disk (c), CD-ROM (d), or Etherboot (n).. any idea? thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
qemu and kqemu - Version mismatch after upgrade
I just ran portsnap fetch update portupgrade -a and I've ended up with a complete disaster with qemu. Am I the only one? Firstly, I was under the impression that updates shouldn't (theoretically of course) upset a running server. I had 2 qemu vm's running which crashed during the process. Secondly, after the upgrade I normally run -kernel-kqemu options, (and I did ensure the install of the kqemu-devel port) but I'm getting the following error: Version mismatch between kqemu module and qemu (00010300 00010400) - disabling kqemu use The system still runs, but given the lack of this accelerator seriously impairs vm use especially with regards networking (ssh, etc). Also, just a note on the ImageMagick port: I've been getting ignore reports from portupgrade, I've done some investigationing into this and it seems that HDRI is broken as per the message (duh!), but in my config HDRI IS disabled, yet it seems the make still enters the define. So in my infinite lack of wisdom I commented out the defines for HDRI and left the config args to --disable-hdri - and hey presto! it installed. Any thoughts? Or should I enter a PR for this/these? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: qemu and kqemu - Version mismatch after upgrade
On Wed, Apr 1, 2009 at 11:36 PM, Da Rock rock_on_the_...@comcen.com.au wrote: I just ran portsnap fetch update portupgrade -a and I've ended up with a complete disaster with qemu. Am I the only one? Firstly, I was under the impression that updates shouldn't (theoretically of course) upset a running server. I had 2 qemu vm's running which crashed during the process. Secondly, after the upgrade I normally run -kernel-kqemu options, (and I did ensure the install of the kqemu-devel port) but I'm getting the following error: Version mismatch between kqemu module and qemu (00010300 00010400) - disabling kqemu use Have you read /usr/ports/UPDATING ? The qemu/kqemu ports were mentioned a few days ago. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: qemu and kqemu - Version mismatch after upgrade
On Thu, 2009-04-02 at 00:04 -0400, Glen Barber wrote: On Wed, Apr 1, 2009 at 11:36 PM, Da Rock rock_on_the_...@comcen.com.au wrote: I just ran portsnap fetch update portupgrade -a and I've ended up with a complete disaster with qemu. Am I the only one? Firstly, I was under the impression that updates shouldn't (theoretically of course) upset a running server. I had 2 qemu vm's running which crashed during the process. Secondly, after the upgrade I normally run -kernel-kqemu options, (and I did ensure the install of the kqemu-devel port) but I'm getting the following error: Version mismatch between kqemu module and qemu (00010300 00010400) - disabling kqemu use Have you read /usr/ports/UPDATING ? The qemu/kqemu ports were mentioned a few days ago. Sorry, I must have missed mentioning that it appears to me that the new kqemu-devel dependency instead of the old kqemu is broken. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: qemu and kqemu - Version mismatch after upgrade
On Thu, 2009-04-02 at 14:28 +1000, Da Rock wrote: On Thu, 2009-04-02 at 00:04 -0400, Glen Barber wrote: On Wed, Apr 1, 2009 at 11:36 PM, Da Rock rock_on_the_...@comcen.com.au wrote: I just ran portsnap fetch update portupgrade -a and I've ended up with a complete disaster with qemu. Am I the only one? Firstly, I was under the impression that updates shouldn't (theoretically of course) upset a running server. I had 2 qemu vm's running which crashed during the process. Secondly, after the upgrade I normally run -kernel-kqemu options, (and I did ensure the install of the kqemu-devel port) but I'm getting the following error: Version mismatch between kqemu module and qemu (00010300 00010400) - disabling kqemu use Have you read /usr/ports/UPDATING ? The qemu/kqemu ports were mentioned a few days ago. Sorry, I must have missed mentioning that it appears to me that the new kqemu-devel dependency instead of the old kqemu is broken. My apologies. You'll have to forgive my senility/dementia- I forgot qemu 101: kqemu is a kmod. I needed to unload/load the module- hence the version mismatch. That said: the ImageMagick issue still stands. Having hit something as stupid as this, I'm a little less confident in my diag. Any comments on what action I should take on this? Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: qemu and kqemu - Version mismatch after upgrade
Apologies for the top post. No idea about the other port. Have you tried deinstalling/reinstalling? --Original Message-- From: Da Rock To: Barber, Glen Cc: FreeBSD Mailing List Subject: Re: qemu and kqemu - Version mismatch after upgrade Sent: Apr 2, 2009 1:00 AM On Thu, 2009-04-02 at 14:28 +1000, Da Rock wrote: On Thu, 2009-04-02 at 00:04 -0400, Glen Barber wrote: On Wed, Apr 1, 2009 at 11:36 PM, Da Rock rock_on_the_...@comcen.com.au wrote: I just ran portsnap fetch update portupgrade -a and I've ended up with a complete disaster with qemu. Am I the only one? Firstly, I was under the impression that updates shouldn't (theoretically of course) upset a running server. I had 2 qemu vm's running which crashed during the process. Secondly, after the upgrade I normally run -kernel-kqemu options, (and I did ensure the install of the kqemu-devel port) but I'm getting the following error: Version mismatch between kqemu module and qemu (00010300 00010400) - disabling kqemu use Have you read /usr/ports/UPDATING ? The qemu/kqemu ports were mentioned a few days ago. Sorry, I must have missed mentioning that it appears to me that the new kqemu-devel dependency instead of the old kqemu is broken. My apologies. You'll have to forgive my senility/dementia- I forgot qemu 101: kqemu is a kmod. I needed to unload/load the module- hence the version mismatch. That said: the ImageMagick issue still stands. Having hit something as stupid as this, I'm a little less confident in my diag. Any comments on what action I should take on this? Cheers -- Glen Barber Sent from my BlackBerry handheld device.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: qemu and kqemu - Version mismatch after upgrade
On Thu, 2009-04-02 at 05:02 +, Glen Barber wrote: Apologies for the top post. No idea about the other port. Have you tried deinstalling/reinstalling? As a matter of fact I have. I finally sat down to nut it out and that idea came to me as I couldn't get an options dialog. A fresh install will do the same thing: I ran make rmconfig just to be sure. The only thing that made it install was to comment out the defines in the Makefile, leaving only --disable-hdri. Apparently no matter what the options say in the Makefile make goes into the if-defined anyway. My first impression was to submit a PR, or notify po...@. After my last stupid mistake I'm not entirely as confident in my diagnoses :( --Original Message-- From: Da Rock To: Barber, Glen Cc: FreeBSD Mailing List Subject: Re: qemu and kqemu - Version mismatch after upgrade Sent: Apr 2, 2009 1:00 AM On Thu, 2009-04-02 at 14:28 +1000, Da Rock wrote: On Thu, 2009-04-02 at 00:04 -0400, Glen Barber wrote: On Wed, Apr 1, 2009 at 11:36 PM, Da Rock rock_on_the_...@comcen.com.au wrote: I just ran portsnap fetch update portupgrade -a and I've ended up with a complete disaster with qemu. Am I the only one? Firstly, I was under the impression that updates shouldn't (theoretically of course) upset a running server. I had 2 qemu vm's running which crashed during the process. Secondly, after the upgrade I normally run -kernel-kqemu options, (and I did ensure the install of the kqemu-devel port) but I'm getting the following error: Version mismatch between kqemu module and qemu (00010300 00010400) - disabling kqemu use Have you read /usr/ports/UPDATING ? The qemu/kqemu ports were mentioned a few days ago. Sorry, I must have missed mentioning that it appears to me that the new kqemu-devel dependency instead of the old kqemu is broken. My apologies. You'll have to forgive my senility/dementia- I forgot qemu 101: kqemu is a kmod. I needed to unload/load the module- hence the version mismatch. That said: the ImageMagick issue still stands. Having hit something as stupid as this, I'm a little less confident in my diag. Any comments on what action I should take on this? Cheers -- Glen Barber Sent from my BlackBerry handheld device. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
qemu only talks to network on second boot
Got win2k on qemu for a couple years now. Funny thing is, it never sees the network or the samba shares on my host the second time I boot qemu on any given day. First time always times out. I get no console output. My win2k.sh file looks something like this. All the tap entries since my system seems to have some issue with naming tap. Maybe that's the issue, but I'll be darned if I could fix it. tap0 and nothing else would be just fine with me. When I just had tap0, it would make tap1 (then tap2, etc, etc.), but this seems always to wind up on tap9 and work (the second time I run qemu) Goofy. Best, Steve [st...@dynstant /usr/ports/emulators/wine]$ cat ~/bin/win2k #!/bin/sh sudo kldload kqemu if_tap if_bridge aio sudo sysctl net.link.tap.user_open=1 sudo sysctl net.link.tap.devfs_cloning=1 sudo sysctl net.link.tap.up_on_open=1 sudo ifconfig bridge0 create sudo ifconfig bridge0 addm vr0 sudo ifconfig bridge0 addm tap0 sudo ifconfig bridge0 addm tap1 sudo ifconfig bridge0 addm tap2 sudo ifconfig bridge0 addm tap3 sudo ifconfig bridge0 addm tap4 sudo ifconfig bridge0 addm tap5 sudo ifconfig bridge0 addm tap6 sudo ifconfig bridge0 addm tap7 sudo ifconfig bridge0 addm tap8 sudo ifconfig bridge0 addm tap9 sudo ifconfig bridge0 up sudo ifconfig vr0 up sudo ifconfig tap0 up sudo ifconfig tap1 up sudo ifconfig tap2 up sudo ifconfig tap3 up sudo ifconfig tap4 up sudo ifconfig tap5 up sudo ifconfig tap6 up sudo ifconfig tap7 up sudo ifconfig tap8 up sudo ifconfig tap9 up sudo dhclient bridge0 sudo /etc/rc.d/devfs restart sudo /etc/rc.d/sysctl restart qemu -m 384 -net nic -net tap -hda ~/bin/drivec.img -usb -usbdevice tablet -serial /dev/cuaU0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: qemu only talks to network on second boot
On Monday 30 March 2009 18:29:20 Steve Franks wrote:
Got win2k on qemu for a couple years now. Funny thing is, it never
sees the network or the samba shares on my host the second time I
boot qemu on any given day. First time always times out. I get no
console output. My win2k.sh file looks something like this. All the
tap entries since my system seems to have some issue with naming tap.
Maybe that's the issue, but I'll be darned if I could fix it. tap0
and nothing else would be just fine with me. When I just had tap0, it
would make tap1 (then tap2, etc, etc.), but this seems always to wind
up on tap9 and work (the second time I run qemu)
Goofy.
Best,
Steve
[st...@dynstant /usr/ports/emulators/wine]$ cat ~/bin/win2k
#!/bin/sh
sudo kldload kqemu if_tap if_bridge aio
sudo sysctl net.link.tap.user_open=1
sudo sysctl net.link.tap.devfs_cloning=1
sudo sysctl net.link.tap.up_on_open=1
sudo ifconfig bridge0 create
sudo ifconfig bridge0 addm vr0
sudo ifconfig bridge0 addm tap0
sudo ifconfig bridge0 addm tap1
sudo ifconfig bridge0 addm tap2
sudo ifconfig bridge0 addm tap3
sudo ifconfig bridge0 addm tap4
sudo ifconfig bridge0 addm tap5
sudo ifconfig bridge0 addm tap6
sudo ifconfig bridge0 addm tap7
sudo ifconfig bridge0 addm tap8
sudo ifconfig bridge0 addm tap9
sudo ifconfig bridge0 up
sudo ifconfig vr0 up
sudo ifconfig tap0 up
sudo ifconfig tap1 up
sudo ifconfig tap2 up
sudo ifconfig tap3 up
sudo ifconfig tap4 up
sudo ifconfig tap5 up
sudo ifconfig tap6 up
sudo ifconfig tap7 up
sudo ifconfig tap8 up
sudo ifconfig tap9 up
sudo dhclient bridge0
sudo /etc/rc.d/devfs restart
sudo /etc/rc.d/sysctl restart
qemu -m 384 -net nic -net tap -hda ~/bin/drivec.img -usb -usbdevice
tablet -serial /dev/cuaU0
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
Hi Steve;
Forgive the long post but
here is what I've got working for me:
[BEGIN]
*** loader.conf
# if_tap is compiled into the kernel
# but loading if_tap does it also
if_bridge_load=YES
*** rc.conf
##
## network stuff
# FBSD HOST(7.1-PRERELEASE)
# +-+
# | 10.10.10.1 |
# LAN -+- re0 |
# | |
# | +-+ |
# +---++tap0 | |
# | +++tap1 | |
# | || +-+ |
# | || bridge0 | (if_bridge)
# | || 10.1.200.254 |
# | |+-+
# | |
# | | QEMU GUEST 1 (linux Fedora core 5)
# | | +-+
# | | | |
# | +---+ eth0 |
# | | 10.1.200.1 |
# | | |
# | +-+
# | QEMU GUEST 2 (windows XP)
# | +-+
# | | |
# +--+--- realtek |
# | 10.1.200.2 |
# | |
# +-+
#
# The bridge IP is the default gateway
# for the guests and the LAN dns is
# guests' DNS server
##
gateway_enable=YES
# don't know why but WITHOUT -promisc- here, it doesnt work !
ifconfig_re0=inet 10.10.10.2 netmask 255.255.255.0 promisc
autobridge_interfaces=bridge0
autobridge_bridge0=tap0 tap1
cloned_interfaces=bridge0
ifconfig_bridge0=inet 10.1.200.254 netmask 255.255.255.0 up
pf_enable=YES
samba_enable=NO
smbd_enable=YES
kqemu_enable=YES
*** pf.conf (totally open - needed for NAT)
ext_if=re0# replace with actual external interface name i.e., dc0
int_if=bridge0# replace with actual internal interface name i.e., dc1
internal_net=10.1.200.0/24
set loginterface $ext_if
set block-policy drop
set fingerprints /etc/pf.os
scrub in all
nat on $ext_if from $internal_net to any - ($ext_if)
no rdr on { lo0, lo1 } from any to any
# pass traffic
pass quick on lo0 all
pass quick on re0 all
pass quick on bridge0 all
# maybe these are redundant but i left them here anyway
pass in on $ext_if proto { tcp, udp } from any to any keep state
pass in on $int_if from $internal_net to any keep state
pass out on $int_if from any to $internal_net keep state
pass out on $ext_if proto { tcp, udp, icmp, gre } all keep state
*** qemu-ifup.sh
#!/usr/local/bin/bash
/sbin/ifconfig $1 up
TEST=`ifconfig -a | grep member | grep $1`
if [ $TEST == ]; then
/sbin/ifconfig bridge0 addm $1
fi
*** qemu-ifdown (has to have this name !)
#!/usr/local/bin/bash
/sbin/ifconfig bridge0 deletem $1
/sbin/ifconfig $1 down
*** smb.conf
[global]
netbios name = Papi
workgroup = LOBOS
hosts allow = 10.1.200. 10.10.10. 127.
server string = Papi
guest account = nobody
log file = /var/log/samba/log.%m
max log size = 50
socket options = TCP_NODELAY
share modes = yes
security = share
interfaces
qemu-launcher problem
I am trying to run qemu-launcher from the command line and receive the following error: # qemu-launcher Xlib: extension Generic Event Extension missing on display :0.0. Xlib: extension Generic Event Extension missing on display :0.0. Xlib: extension Generic Event Extension missing on display :0.0. Xlib: extension Generic Event Extension missing on display :0.0. Xlib: extension Generic Event Extension missing on display :0.0. Xlib: extension Generic Event Extension missing on display :0.0. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated at /usr/local/bin/qemu-launcher line 2000. Bad system call: 12 (core dumped) I am running 7-stable amd64, Xorg7.4, gnome 2.24.3, qemu-0.10.1_1, kqemu-kmod-devel-1.4.0.p1_2, qemu-launcher-1.7.4_2. Any help is appreciated. What other info can I provide to troubleshoot? TIA ___ freebsd-questions
Re: 7.0-STABLE qemu not terminating
In article 20090317143537.ga12...@rebelion.sisis.de you write: Hello, My VM qemu (qemu-0.9.1_3 / kqemu-kmod-1.3.0.p11_2) does not terminate after the system (WinXP) is successfully halted and the qemu window is closed; it stays forever as: # ps ax | fgrep qemu 1687 ?? I 0:00,25 kdesu -u root -c /home/guru/qemu/w2k/qemu.sh 1713 ?? Is 0:00,00 sh -c /home/guru/qemu/w2k/qemu.sh 1714 ?? I 0:00,00 /bin/sh /home/guru/qemu/w2k/qemu.sh 1717 ?? DE11:51,11 qemu -localtime -hda disk0 -hdb disk1 -net nic -net tap -m 512 any ides? thx matthias While I don't remeber seeing reports about this particular issue, it is still very well possible that it has been fixed in the meantime, so I'd advise you to update. (the port is at 0.10.1 now, which contains quite a few bugfixes and improvements... Don't forget to read UPDATING and the pkg-message of the port tho.) Oh and also, there usually is no reason to run qemu as root if you setup tap permissions and (possibly) ifup/down scripts accordingly. (Or, if you are only using tuntap because you are on amd64 where slirp was broken, that also is fixed now.) HTH, Juergen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
7.0-STABLE qemu not terminating
Hello, My VM qemu (qemu-0.9.1_3 / kqemu-kmod-1.3.0.p11_2) does not terminate after the system (WinXP) is successfully halted and the qemu window is closed; it stays forever as: # ps ax | fgrep qemu 1687 ?? I 0:00,25 kdesu -u root -c /home/guru/qemu/w2k/qemu.sh 1713 ?? Is 0:00,00 sh -c /home/guru/qemu/w2k/qemu.sh 1714 ?? I 0:00,00 /bin/sh /home/guru/qemu/w2k/qemu.sh 1717 ?? DE11:51,11 qemu -localtime -hda disk0 -hdb disk1 -net nic -net tap -m 512 any ides? thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: QEMU: increase image size with FreeBSD partitions ...
Marc G. Fournier wrote: --On Tuesday, December 09, 2008 10:15:45 +0100 Ivan Voras [EMAIL PROTECTED] wrote: Marc G. Fournier wrote: I have FreeBSD 7 running in a QEMU VM ... works like a charm, but I'm wondering if there is some way of *increasing* the size of the image beyond what I configured it for? I'm only finding stuff pertaining to NTFS/FAT32, but nothing about Unix in general, or FreeBSD specifically ... Is there any way of doing this, or do I have to build a new, larger img, and copy the data from diskA - diskB, and reboot on diskB? Doable, but time consuming ... I don't think there's anything automatic but you can grow the virtual disk, then modify the last partition size by hand, then use growfs. 'k, that is what I figured, but how do I grow the virtual disk? I've checked the qemu-img man page, and there doesn't appear to be a method of doing this ... I think I've incorrectly assumed you're using plain raw disk images - from the context I'd say that you're actually using one of qemu's own formats, right? The only thing I've found is this: http://kev.coolcavemen.com/2007/04/how-to-grow-any-qemu-system-image/ signature.asc Description: OpenPGP digital signature
Re: QEMU: increase image size with FreeBSD partitions ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Tuesday, December 09, 2008 10:15:45 +0100 Ivan Voras [EMAIL PROTECTED] wrote: Marc G. Fournier wrote: I have FreeBSD 7 running in a QEMU VM ... works like a charm, but I'm wondering if there is some way of *increasing* the size of the image beyond what I configured it for? I'm only finding stuff pertaining to NTFS/FAT32, but nothing about Unix in general, or FreeBSD specifically ... Is there any way of doing this, or do I have to build a new, larger img, and copy the data from diskA - diskB, and reboot on diskB? Doable, but time consuming ... I don't think there's anything automatic but you can grow the virtual disk, then modify the last partition size by hand, then use growfs. 'k, that is what I figured, but how do I grow the virtual disk? I've checked the qemu-img man page, and there doesn't appear to be a method of doing this ... - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk/KvoACgkQ4QvfyHIvDvOEfQCghv9LtctUGSuagAlFbcEoNrWu udMAnixLBpCcfwOTUVkhjep/2dQSzNaD =YjqB -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mdconfig(8) with offset? Or: resizing a NTFS qemu image
On Sat, Nov 15, 2008 at 01:46:43AM +0100, cpghost wrote: Hello, I'm trying to extend a ntfs filesystem in a qemu raw image, by following the instructions here: http://qemu-forum.ipi.fi/viewtopic.php?p=12362 Of course, this requires sysutils/ntfsprogs and the equivalent of losetup. Of course, mdconfig is our losetup. Now, how is it possible to mdconfig a file, but starting from a specific offset? (Of course, taking the image file apart, mdconfig one of its fragments, then putting it back together could be a hackish work-around (?), but it would be nice if mdconfig were able to map a partial file directly.) Just one more data point: if I mdconfig the qemu raw image, I do get both a /dev/md0 and /dev/md0s1 device, so I can fdisk /dev/md0s1 directly. mdconfig to another offset in the raw image file is therefore not strictly needed in this special case; but it would still be a nice-to-have feature. Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mdconfig(8) with offset? Or: resizing a NTFS qemu image
Hello, I'm trying to extend a ntfs filesystem in a qemu raw image, by following the instructions here: http://qemu-forum.ipi.fi/viewtopic.php?p=12362 Of course, this requires sysutils/ntfsprogs and the equivalent of losetup. Of course, mdconfig is our losetup. Now, how is it possible to mdconfig a file, but starting from a specific offset? (Of course, taking the image file apart, mdconfig one of its fragments, then putting it back together could be a hackish work-around (?), but it would be nice if mdconfig were able to map a partial file directly.) Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Qemu network question
Hi: Please use a fixed font to see the diagram bellow: FBSD HOST(7.1-PRERELEASE) +-+ |10.10.10.1 | LAN -+- re0| | | |+-+ | +---++tap0 | | | +++tap1 | | | ||+-+ | | ||bridge0 | (if_bridge) | || 192.168.100.254 | | |+-+ | | | | QEMU GUEST 1 (linux Fedora core 5) | | +-+ | | | | | +---+ eth0| | | 192.168.100.1 | | | | | +-+ | QEMU GUEST 2 (windows XP) | +-+ | | | +--+--- realtek | | 192.168.100.2 | | | +-+ It's working like a charm ! I turned my FBSD desktop into a router/gateway, put pf to nat everything and set up an independent smb server on the host. Pings travel on any direction!. The guests have access to ALL the host's files and vice versa, BOTH guests have internet access and best of all, I can access the linux guest through an ssh shell and the windows guest through vncviewer, and, of course, the 2 guests see each other ! Imagine how happy I am ! I tried this without turning my desktop into a gateway. The guests had internet access but the host was invisible to them and I got tired of trying to make qemu's -smb option work, so I adapted this a-bit radical approach I saw on a how-to for Sun OS I found on the net. I'm really impressed with qemu performance !. I´ve compiled kernels, built RPMs and the reduction in performance from doing these things in a separate machine is really endurable. My question is: If I don't put re0 into promiscous mode, all of this falls apart ! The network goes totally down for the host-guests, but the host retains its internet conectivity. I discovered that by chance! I was trying to find out what was happening with conectivity so I tried pinging the host from the linux guest. As soon as I started tcpdump on the host, the pings went through so I found out what I needed from there. Is this normal or is there something wrong with my NIC? setup? Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winedows FREE) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
qemu bridge building
owntap0 moleque:moleque :q! # /etc/rc.d/devfs restart # kldload kqemu aio if_tap if_bridge kldload: can't load kqemu: File exists kldload: can't load aio: File exists # sysctl net.link.tap.user_open=1 net.link.tap.user_open: 0 - 1 # ifconfig bridge0 create # ifconfig rl0: flags=8802 metric 0 mtu 1500 options=8 ether 00:15:f2:7a:dc:83 media: Ethernet autoselect status: no carrier fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:11:d8:85:04:0b ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.11.d8.0.0.85.4.b.a.2.ff.fe.0.0.0.0 dc0: flags=8843 metric 0 mtu 1500 options=8 ether 00:04:5a:4f:ab:db inet 192.168.0.10 netmask 0xff00 broadcast 192.168.0.255 media: Ethernet autoselect (100baseTX ) status: active plip0: flags=108810 metric 0 mtu 1500 lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8802 metric 0 mtu 1500 ether 4e:48:d6:53:ff:2b id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0 # ifconfig bridge0 addm dc0 up # ifconfig bridge0 addm tap0 ifconfig: BRDGADD tap0: No such file or directory . Problem is there now. _ Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qemu bridge building
Hello Desmond! Desmond Chapman schrieb: owntap0 moleque:moleque :q! # /etc/rc.d/devfs restart # kldload kqemu aio if_tap if_bridge kldload: can't load kqemu: File exists kldload: can't load aio: File exists # sysctl net.link.tap.user_open=1 net.link.tap.user_open: 0 - 1 # ifconfig bridge0 create You will need a # ifconfig tap0 create here. Greetings, Uli. # ifconfig rl0: flags=8802 metric 0 mtu 1500 options=8 ether 00:15:f2:7a:dc:83 media: Ethernet autoselect status: no carrier fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:11:d8:85:04:0b ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.11.d8.0.0.85.4.b.a.2.ff.fe.0.0.0.0 dc0: flags=8843 metric 0 mtu 1500 options=8 ether 00:04:5a:4f:ab:db inet 192.168.0.10 netmask 0xff00 broadcast 192.168.0.255 media: Ethernet autoselect (100baseTX ) status: active plip0: flags=108810 metric 0 mtu 1500 lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8802 metric 0 mtu 1500 ether 4e:48:d6:53:ff:2b id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0 # ifconfig bridge0 addm dc0 up # ifconfig bridge0 addm tap0 ifconfig: BRDGADD tap0: No such file or directory . Problem is there now. _ Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qemu coredumps on any network activity
On Mon, May 5, 2008 at 11:38 AM, Atanu Ghosh [EMAIL PROTECTED] wrote: Hi, http://monkey.org/freebsd/archive/freebsd-questions/200802/msg01649.html I am seeing the same problem, did you ever get to the bottom of this? Atanu. I switched to using a tap bridge instead. I have not had any problems with it. FYI I am on FreeBSD 7.0-stable, amd64. Steve ~/bin/qemu.sh: sudo kldload kqemu if_tap if_bridge aio sudo sysctl net.link.tap.user_open=1 sudo sysctl net.link.tap.devfs_cloning=1 sudo sysctl net.link.tap.up_on_open=1 # sudo ifconfig bridge0 destroy # sudo ifconfig bridge1 destroy # sudo ifconfig tap0 destroy # sudo ifconfig tap1 destroy # sudo ifconfig tap2 destroy # sudo ifconfig tap3 destroy # sudo ifconfig tap4 destroy # sudo ifconfig tap5 destroy # sudo ifconfig tap6 destroy # sudo ifconfig tap7 destroy # sudo ifconfig tap8 destroy # sudo ifconfig tap9 destroy sudo ifconfig bridge0 create sudo ifconfig bridge0 addm vr0 # sudo ifconfig tap0 create sudo ifconfig bridge0 addm tap0 sudo ifconfig bridge0 addm tap1 sudo ifconfig bridge0 addm tap2 sudo ifconfig bridge0 addm tap3 sudo ifconfig bridge0 addm tap4 sudo ifconfig bridge0 addm tap5 sudo ifconfig bridge0 addm tap6 sudo ifconfig bridge0 addm tap7 sudo ifconfig bridge0 addm tap8 sudo ifconfig bridge0 addm tap9 sudo ifconfig bridge0 up sudo ifconfig vr0 up sudo ifconfig tap0 up sudo ifconfig tap1 up sudo ifconfig tap2 up sudo ifconfig tap3 up sudo ifconfig tap4 up sudo ifconfig tap5 up sudo ifconfig tap6 up sudo ifconfig tap7 up sudo ifconfig tap8 up sudo ifconfig tap9 up sudo dhclient bridge0 sudo /etc/rc.d/devfs restart sudo /etc/rc.d/sysctl restart ifconfig qemu -m 512 -net nic -net tap -hda /usr/local/share/qemu/drivec.img -usb -usbdevice tablet # -usbdevice disk:/dev/da0 -hdb fat:/mnt/flash -std-vga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qemu coredumps on any network activity
Hi, Thanks for the info, I am also using I am on FreeBSD 7.0-stable, amd64. Atanu. Steve == Steve Franks [EMAIL PROTECTED] writes: Steve On Mon, May 5, 2008 at 11:38 AM, Atanu Ghosh Steve [EMAIL PROTECTED] wrote: Hi, http://monkey.org/freebsd/archive/freebsd-questions/200802/msg01649.html I am seeing the same problem, did you ever get to the bottom of this? Atanu. Steve I switched to using a tap bridge instead. I have not had Steve any problems with it. FYI I am on FreeBSD 7.0-stable, amd64. Steve Steve Steve ~/bin/qemu.sh: Steve sudo kldload kqemu if_tap if_bridge aio Steve sudo sysctl net.link.tap.user_open=1 sudo sysctl Steve net.link.tap.devfs_cloning=1 sudo sysctl Steve net.link.tap.up_on_open=1 Steve # sudo ifconfig bridge0 destroy # sudo ifconfig bridge1 Steve destroy # sudo ifconfig tap0 destroy # sudo ifconfig tap1 Steve destroy # sudo ifconfig tap2 destroy # sudo ifconfig tap3 Steve destroy # sudo ifconfig tap4 destroy # sudo ifconfig tap5 Steve destroy # sudo ifconfig tap6 destroy # sudo ifconfig tap7 Steve destroy # sudo ifconfig tap8 destroy # sudo ifconfig tap9 Steve destroy Steve sudo ifconfig bridge0 create sudo ifconfig bridge0 addm vr0 # Steve sudo ifconfig tap0 create sudo ifconfig bridge0 addm tap0 Steve sudo ifconfig bridge0 addm tap1 sudo ifconfig bridge0 addm Steve tap2 sudo ifconfig bridge0 addm tap3 sudo ifconfig bridge0 Steve addm tap4 sudo ifconfig bridge0 addm tap5 sudo ifconfig Steve bridge0 addm tap6 sudo ifconfig bridge0 addm tap7 sudo Steve ifconfig bridge0 addm tap8 sudo ifconfig bridge0 addm tap9 Steve sudo ifconfig bridge0 up sudo ifconfig vr0 up sudo ifconfig Steve tap0 up sudo ifconfig tap1 up sudo ifconfig tap2 up sudo Steve ifconfig tap3 up sudo ifconfig tap4 up sudo ifconfig tap5 up Steve sudo ifconfig tap6 up sudo ifconfig tap7 up sudo ifconfig Steve tap8 up sudo ifconfig tap9 up sudo dhclient bridge0 Steve sudo /etc/rc.d/devfs restart sudo /etc/rc.d/sysctl restart Steve ifconfig Steve qemu -m 512 -net nic -net tap -hda Steve /usr/local/share/qemu/drivec.img -usb -usbdevice tablet # Steve -usbdevice disk:/dev/da0 -hdb fat:/mnt/flash -std-vga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
On Thu, Apr 17, 2008 at 1:40 PM, Mario Lobo [EMAIL PROTECTED] wrote: On Thursday 17 April 2008, Jim Stapleton wrote: Sorry for the delayed reply, I didn't see this sent. On Thursday 10 April 2008 22:01:32 Mario Lobo wrote I have a virtual Linux (Fedora 5) and winedows (XP) machines in QEMU and they are both network functional. I use qemu-launch because it does everything you need to create a virtual machine. Here are my pertinent configs: 1) # rc.conf ifconfig_re0=up polling - no IP here ! autobridge_interfaces=bridge0 autobridge_bridge0=tap0 re0 - important even if tap0 does not exist yet cloned_interfaces=bridge0 # the bridge gets the IP ifconfig_bridge0=inet 10.10.10.2 netmask 255.255.255.0 To verify, the 10.10.10.2 is the IP that everyone sees my host as on the network, correct? That's the IP that used to be set on re0? exactly ! 2) tell QEMU launch to open a tap device Open a TUN/TAP interface in the network interface configuration yes 3) tap up script to run when invoking the machine(s). # qemu-net #!/usr/local/bin/bash $1 = tap ifac created /sbin/ifconfig $1 up # test if tap is already added TEST=`ifconfig -a | grep -A 6 bridge | grep $1` if [ $TEST == ]; then /sbin/ifconfig bridge0 addm $1 fi # add a route to the virtual machine /sbin/route add -host 10.10.10.100 -iface bridge0 This is the tun/tap configuration script, the IP on the last line is the IP I want the guest to look like to the network (i.e. 192.168.1.85)? correct ! You will configure the guest's network interface with this IP. Thanks, I'll play with this more when I get home (I don't want to mess with my machine's network configuration while I've only got network access). This worked so fine fine for me that I left the bridge as my main interface for good. Even if QEMU is not up. It works just as well as re0 itself. Thanks, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You're welcome ! OK, I finally got to test it last night. It almost worked. I ran it from the console, and it spit out the command line. Something on the command line looked obviously off to me (I think it was the iface= part of the network section), anyway, I copied pasted it, added the tap0 reference, and it works perfectly. Thanks again, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
OK, I finally got to test it last night. It almost worked. I ran it from the console, and it spit out the command line. Something on the command line looked obviously off to me (I think it was the iface= part of the network section), anyway, I copied pasted it, added the tap0 reference, and it works perfectly. Thanks again, -Jim Stapleton All right, Jim !! Great ! if you use X, I think you could consider using qemu-launch. It is really handy. And it saves the configs for every particular guest you have and you can call any of them up at the tip of the mouse. -- Mario Lobo Segurança de Redes - Desenvolvimento e Análise IPAD - Instituto de Pesquisa e Apoio ao Desenvolvimento Tecnológico e Científico ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
Sorry for the delayed reply, I didn't see this sent. On Thursday 10 April 2008 22:01:32 Mario Lobo wrote I have a virtual Linux (Fedora 5) and winedows (XP) machines in QEMU and they are both network functional. I use qemu-launch because it does everything you need to create a virtual machine. Here are my pertinent configs: 1) # rc.conf ifconfig_re0=up polling - no IP here ! autobridge_interfaces=bridge0 autobridge_bridge0=tap0 re0 - important even if tap0 does not exist yet cloned_interfaces=bridge0 # the bridge gets the IP ifconfig_bridge0=inet 10.10.10.2 netmask 255.255.255.0 To verify, the 10.10.10.2 is the IP that everyone sees my host as on the network, correct? That's the IP that used to be set on re0? 2) tell QEMU launch to open a tap device Open a TUN/TAP interface in the network interface configuration 3) tap up script to run when invoking the machine(s). # qemu-net #!/usr/local/bin/bash $1 = tap ifac created /sbin/ifconfig $1 up # test if tap is already added TEST=`ifconfig -a | grep -A 6 bridge | grep $1` if [ $TEST == ]; then /sbin/ifconfig bridge0 addm $1 fi # add a route to the virtual machine /sbin/route add -host 10.10.10.100 -iface bridge0 This is the tun/tap configuration script, the IP on the last line is the IP I want the guest to look like to the network (i.e. 192.168.1.85)? Thanks, I'll play with this more when I get home (I don't want to mess with my machine's network configuration while I've only got network access). Thanks, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
On Thursday 17 April 2008, Jim Stapleton wrote: Sorry for the delayed reply, I didn't see this sent. On Thursday 10 April 2008 22:01:32 Mario Lobo wrote I have a virtual Linux (Fedora 5) and winedows (XP) machines in QEMU and they are both network functional. I use qemu-launch because it does everything you need to create a virtual machine. Here are my pertinent configs: 1) # rc.conf ifconfig_re0=up polling - no IP here ! autobridge_interfaces=bridge0 autobridge_bridge0=tap0 re0 - important even if tap0 does not exist yet cloned_interfaces=bridge0 # the bridge gets the IP ifconfig_bridge0=inet 10.10.10.2 netmask 255.255.255.0 To verify, the 10.10.10.2 is the IP that everyone sees my host as on the network, correct? That's the IP that used to be set on re0? exactly ! 2) tell QEMU launch to open a tap device Open a TUN/TAP interface in the network interface configuration yes 3) tap up script to run when invoking the machine(s). # qemu-net #!/usr/local/bin/bash $1 = tap ifac created /sbin/ifconfig $1 up # test if tap is already added TEST=`ifconfig -a | grep -A 6 bridge | grep $1` if [ $TEST == ]; then /sbin/ifconfig bridge0 addm $1 fi # add a route to the virtual machine /sbin/route add -host 10.10.10.100 -iface bridge0 This is the tun/tap configuration script, the IP on the last line is the IP I want the guest to look like to the network (i.e. 192.168.1.85)? correct ! You will configure the guest's network interface with this IP. Thanks, I'll play with this more when I get home (I don't want to mess with my machine's network configuration while I've only got network access). This worked so fine fine for me that I left the bridge as my main interface for good. Even if QEMU is not up. It works just as well as re0 itself. Thanks, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You're welcome ! -- Mario Lobo Segurança de Redes - Desenvolvimento e Análise IPAD - Instituto de Pesquisa e Apoio ao Desenvolvimento Tecnológico e Científico ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
OK, my stupid jokes aside, I got this result:
# ifconfig
re0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric
0 mtu 1500
options=98VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM
ether 00:1a:70:12:bc:55
inet 192.168.1.84 netmask 0xff00 broadcast 192.168.1.255
inet 192.168.1.85 netmask 0x broadcast 192.168.1.85
media: Ethernet autoselect (100baseTX full-duplex)
status: active
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
tap0: flags=8903UP,BROADCAST,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500
ether 00:bd:cd:fd:1a:00
bridge0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500
ether 8e:31:f1:19:61:13
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0
member: re0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
member: tap0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP
# cat WinXP\ VM
#!/bin/sh
qemu -boot c -net nic -net tap -hda /data/WinXP.img -m 512 -soundhw
es1370 -localtime -smb /data/
# ./WinXP\ VM
warning: could not open /dev/tap4 (No such file or directory): no
virtual network emulation Could not initialize device 'tap'
[EMAIL PROTECTED] 02:11:26 (1) ~/Desktop ls -lh /etc/ | grep qemu; cat
/etc/qemu-ifup
-rwxr-xr-x 1 root wheel 18 Apr 10 11:35 qemu-ifup*
ifconfig ${1} up
I tried to create tap4 to fix this, then it complained about tap5 not
existing. It creates the /dev/tap device it wants when there is an
error.
I figure I made a mistake (obviously), any ideas what?
Thanks,
-JIm Stapleton
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
Hi Mario, 1) # rc.conf ifconfig_re0=up polling - no IP here ! autobridge_interfaces=bridge0 autobridge_bridge0=tap0 re0 - important even if tap0 does not exist yet cloned_interfaces=bridge0 # the bridge gets the IP ifconfig_bridge0=inet 10.10.10.2 netmask 255.255.255.0 2) tell QEMU launch to open a tap device 3) tap up script to run when invoking the machine(s). # qemu-net #!/usr/local/bin/bash $1 = tap ifac created /sbin/ifconfig $1 up # test if tap is already added TEST=`ifconfig -a | grep -A 6 bridge | grep $1` if [ $TEST == ]; then /sbin/ifconfig bridge0 addm $1 fi # add a route to the virtual machine /sbin/route add -host 10.10.10.100 -iface bridge0 Set the gateway on both machines to the same gateway of the host. That's all. This works perfectly for me. If I want both virtual machines up, I have to add another route to the IP of the second machine through the bridge. I don't really understand why you need routing here. In my understanding a bridge works like a layer 2 switch so there should be no need for any routing. Cheers, Andrew -- accid.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
On Friday 11 April 2008 07:17:21 you wrote: Hi Mario, 1) # rc.conf ifconfig_re0=up polling - no IP here ! autobridge_interfaces=bridge0 autobridge_bridge0=tap0 re0 - important even if tap0 does not exist yet cloned_interfaces=bridge0 # the bridge gets the IP ifconfig_bridge0=inet 10.10.10.2 netmask 255.255.255.0 2) tell QEMU launch to open a tap device 3) tap up script to run when invoking the machine(s). # qemu-net #!/usr/local/bin/bash $1 = tap ifac created /sbin/ifconfig $1 up # test if tap is already added TEST=`ifconfig -a | grep -A 6 bridge | grep $1` if [ $TEST == ]; then /sbin/ifconfig bridge0 addm $1 fi # add a route to the virtual machine /sbin/route add -host 10.10.10.100 -iface bridge0 Set the gateway on both machines to the same gateway of the host. That's all. This works perfectly for me. If I want both virtual machines up, I have to add another route to the IP of the second machine through the bridge. I don't really understand why you need routing here. In my understanding a bridge works like a layer 2 switch so there should be no need for any routing. Cheers, Andrew I don't know exactly why. What I know is if I don't, it doesn't work. I think it's because the virtual machine is on the same subnet of the bridge and the host is not configured as a gateway. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winedows FREE) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
Yes, this needs to be setup on the host system. The way a bridge is
configured has changed on 7. Here are the steps assuming that your
external interface is em0:
# ifconfig tap0 create
# ifconfig tap0 up
# ifconfig em0 up
# ifconfig bridge0 create
# ifconfig bridge0 addm tap0 addm em0
Now tap0 and em0 are bridged together. You should configure your
external IP on the bridge instead of em0 as you normally would. If you
use DHCP then:
# dhclient bridge0
Forgot to add that you'll also need to create the /etc/qemu-ifup script,
otherwise this won't work. That's what the script should look like:
#!/bin/sh
ifconfig ${1} up
Don't forget to make it executable:
# chmod 755 /etc/qemu-ifup
And start qemu:
# qemu -boot c -net nic -net tap -hda path_to_your_disk_image
Now the VM should be able to see your LAN and get an IP from DHCP (if
that's what you use on your LAN)
--
accid.net
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
Hi Jim, I just CPed a huge section and tacked it on to the end of this mail. It says to do this within the emulator, but the emulator is supposedly running win2k. I take it this is done on the host system? Yes, this needs to be setup on the host system. The way a bridge is configured has changed on 7. Here are the steps assuming that your external interface is em0: # ifconfig tap0 create # ifconfig tap0 up # ifconfig em0 up # ifconfig bridge0 create # ifconfig bridge0 addm tap0 addm em0 Now tap0 and em0 are bridged together. You should configure your external IP on the bridge instead of em0 as you normally would. If you use DHCP then: # dhclient bridge0 And start qemu: # qemu -boot c -net nic -net tap -hda path_to_your_disk_image Now the VM should be able to see your LAN and get an IP from DHCP (if that's what you use on your LAN) Hope this helps, Andrew -- accid.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
Yes, this needs to be setup on the host system. The way a bridge is configured has changed on 7. Here are the steps assuming that your external interface is em0: Well, it seems pretty calm, and hasn't tried to cut itself yet... But I think I can adapt. # ifconfig tap0 create # ifconfig tap0 up # ifconfig em0 up # ifconfig bridge0 create # ifconfig bridge0 addm tap0 addm em0 Could I mimic this in RC.conf? Or is this saved between restarts? Also, for the bridge, could I do this, correct? #existing rc.conf hostname=elrond.var-dev.net ifconfig_re0=inet 192.168.1.84 netmask 255.255.255.0 ifconfig_re0_alias0=192.168.1.85 netmask 255.255.255.255 defaultrouter=192.168.1.1 #adding... Should I use an IP not aliased by re0? ifconfig_bridge0=inet 192.168.1.85 netmask 255.255.255.0 Thanks for your help, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
On Thursday 10 April 2008 12:33:29 Jim Stapleton wrote: Yes, this needs to be setup on the host system. The way a bridge is configured has changed on 7. Here are the steps assuming that your external interface is em0: Well, it seems pretty calm, and hasn't tried to cut itself yet... But I think I can adapt. # ifconfig tap0 create # ifconfig tap0 up # ifconfig em0 up # ifconfig bridge0 create # ifconfig bridge0 addm tap0 addm em0 Could I mimic this in RC.conf? Or is this saved between restarts? Also, for the bridge, could I do this, correct? #existing rc.conf hostname=elrond.var-dev.net ifconfig_re0=inet 192.168.1.84 netmask 255.255.255.0 ifconfig_re0_alias0=192.168.1.85 netmask 255.255.255.255 defaultrouter=192.168.1.1 #adding... Should I use an IP not aliased by re0? ifconfig_bridge0=inet 192.168.1.85 netmask 255.255.255.0 Thanks for your help, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I have a virtual Linux (Fedora 5) and winedows (XP) machines in QEMU and they are both network functional. I use qemu-launch because it does everything you need to create a virtual machine. Here are my pertinent configs: 1) # rc.conf ifconfig_re0=up polling - no IP here ! autobridge_interfaces=bridge0 autobridge_bridge0=tap0 re0 - important even if tap0 does not exist yet cloned_interfaces=bridge0 # the bridge gets the IP ifconfig_bridge0=inet 10.10.10.2 netmask 255.255.255.0 2) tell QEMU launch to open a tap device 3) tap up script to run when invoking the machine(s). # qemu-net #!/usr/local/bin/bash $1 = tap ifac created /sbin/ifconfig $1 up # test if tap is already added TEST=`ifconfig -a | grep -A 6 bridge | grep $1` if [ $TEST == ]; then /sbin/ifconfig bridge0 addm $1 fi # add a route to the virtual machine /sbin/route add -host 10.10.10.100 -iface bridge0 Set the gateway on both machines to the same gateway of the host. That's all. This works perfectly for me. If I want both virtual machines up, I have to add another route to the IP of the second machine through the bridge. I did not need to set up samba to access the local drives because I already have a samba server on the gateway and both the host and the guests can see it, and of course, is one less thing to set up at the host. My 2 cents. Hope it helps ! -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio YET!!] (99,7% winedows FREE) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
Hi Jim, The QEmu VM can access the web (I'm typing this out now in WindowsXP running safely in it's cage, for example). But it cannot VPN into work (timeout) or ping anything. I suspect it has to do with the way that QEmu is given network access. Is there any way to set up QEmu to access the network through an aliased IP address, and hence look like any other machine on my network, rather than to hide behind my BSD box? Is there another route I should take?+ I connect my qemu boxes via the tap interface and then bridge it to the external interface so it works like just another box on the LAN. It's quite easy to setup and works pretty well, checkout: http://people.freebsd.org/~maho/qemu/qemu.html Give us a shout if you get stuck. Andrew. -- accid.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
On Wed, 9 Apr 2008 10:18:59 +0100 Andrew Cid [EMAIL PROTECTED] wrote: Hi Jim, The QEmu VM can access the web (I'm typing this out now in WindowsXP running safely in it's cage, for example). But it cannot VPN into work (timeout) or ping anything. I suspect it has to do with the way that QEmu is given network access. Is there any way to set up QEmu to access the network through an aliased IP address, and hence look like any other machine on my network, rather than to hide behind my BSD box? Is there another route I should take?+ I connect my qemu boxes via the tap interface and then bridge it to the external interface so it works like just another box on the LAN. It's quite easy to setup and works pretty well, checkout: http://people.freebsd.org/~maho/qemu/qemu.html ping fails because the qemu process runs as an ordinary user and ping requires root privileges (the ping binary runs setuid). The VPN problem may be simply due to qemu's use of NAT. I would suggest you familiarise yourself with any NAT/firewall issues for your VPN before switching to tap. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU networking quirkiness on 7.0
On Wed, Apr 9, 2008 at 9:18 AM, Andrew Cid [EMAIL PROTECTED] wrote:
Hi Jim,
The QEmu VM can access the web (I'm typing this out now in WindowsXP
running safely in it's cage, for example). But it cannot VPN into work
(timeout) or ping anything. I suspect it has to do with the way that
QEmu is given network access. Is there any way to set up QEmu to
access the network through an aliased IP address, and hence look like
any other machine on my network, rather than to hide behind my BSD
box? Is there another route I should take?+
I connect my qemu boxes via the tap interface and then bridge it to the
external interface so it works like just another box on the LAN. It's
quite easy to setup and works pretty well, checkout:
http://people.freebsd.org/~maho/qemu/qemu.html
I just CPed a huge section and tacked it on to the end of this mail.
It says to do this within the emulator, but the emulator is supposedly
running win2k. I take it this is done on the host system?
Thanks,
-Jim Stapleton
Networking
Default, network is configured inside of the emulator; not visible
from outside. This is not absolutely confotable! There are pros and
cons: you must be the root and your qemu virtual machine is visible
from outside. Assume you know your network interface name. In my case
this is fxp0. you can check this by:
% dmesg | grep Ethernet
First, as root,
# kldload bridge.ko
# sysctl net.link.ether.bridge_cfg=fxp0,tap0
net.link.ether.bridge_cfg: - fxp0,tap0
# sysctl net.link.ether.bridge.enable=1
net.link.ether.bridge.enable: 0 - 1
create /etc/qemu-ifup script as
#!/bin/sh
ifconfig ${1} 0.0.0.0
and make this script runnable.
# chmod 755 /etc/qemu-ifup
To do this at every boot time, write /etc/sysctl.conf
net.link.ether.bridge_cfg=fxp0,tap0
net.link.ether.bridge.enable=1
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
QEMU networking quirkiness on 7.0
I'm not sure if this is QEmu or FreeBSD. I have a fairly boring 7.0/i386 setup. The QEmu VM can access the web (I'm typing this out now in WindowsXP running safely in it's cage, for example). But it cannot VPN into work (timeout) or ping anything. I suspect it has to do with the way that QEmu is given network access. Is there any way to set up QEmu to access the network through an aliased IP address, and hence look like any other machine on my network, rather than to hide behind my BSD box? Is there another route I should take?+ Thanks, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
qemu coredumps on any network activity
The only relevant info in dmesg is that pid qemuexitied on signal 11 (core dump). It runs fine until I access the network (either with ftp or iexplore), then cores. Just built from source 2 days ago (qemu 0.9.0_3). System is a vanilla amd64 7.0-RC2. Ssytem network access is fine. Thanks, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qemu coredumps on any network activity
The only relevant info in dmesg is that pid qemuexitied on signal 11 (core dump). It runs fine until I access the network (either with ftp or iexplore), then cores. Just built from source 2 days ago (qemu 0.9.0_3). System is a vanilla amd64 7.0-RC2. Ssytem network access is fine. what type of qemu network do you use? the default one or something else? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU Windows and X forwarding
David Schulz wrote: Hello, my Goal is to setup a FreeBSD Server that hosts about 5 Images of (licensed) Windows XP, which i made either using QEMU or Win4BSD. Those Images then i want to make accessible to old Macintosh PowerPC Machines, so the Users can access one or two Applications that only run under Windows XP. I would like to know from anyone in a similar situation how to accomplish this best. Currently, I pretty much have it setup for myself, so when i open X11 on my PowerPC Machine, and type in ssh -X server_address windows_xp , i do get an instance of Windows XP on my PowerPC Machine. The trouble here for now is server and network performance. I would like to know if anyone of you has any suggestions for me on how i can make the network load as little as possible. I read that freenx is offering really good responsiveness, but unfortunately it is marked as broken on my System using FreeBSD Version 6.3. I'm using net/rdesktop for that. It's native to win, easy to setup, easy to work. qemu bla-bla-bla -redir tcp:3389::3389 -nographic You can use different outside ports for different virtual machines. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
QEMU Windows and X forwarding
Hello, my Goal is to setup a FreeBSD Server that hosts about 5 Images of (licensed) Windows XP, which i made either using QEMU or Win4BSD. Those Images then i want to make accessible to old Macintosh PowerPC Machines, so the Users can access one or two Applications that only run under Windows XP. I would like to know from anyone in a similar situation how to accomplish this best. Currently, I pretty much have it setup for myself, so when i open X11 on my PowerPC Machine, and type in ssh -X server_address windows_xp , i do get an instance of Windows XP on my PowerPC Machine. The trouble here for now is server and network performance. I would like to know if anyone of you has any suggestions for me on how i can make the network load as little as possible. I read that freenx is offering really good responsiveness, but unfortunately it is marked as broken on my System using FreeBSD Version 6.3. Thanks and best regards, David Schulz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freesbie on USB stick + qemu
I should have been clearer, I am running Freesbie from a usb stick. However it is running inside Qemu with XP being the host machine. Michael --- William Bulley [EMAIL PROTECTED] wrote: According to Michael S [EMAIL PROTECTED]: Then I remembered Freesbie and decided to give it a try, running it from a usb stick using Qemu. I followed the instructions for Ubuntu http://www.pendrivelinux.com/2008/01/11/run-ubuntu-710-from-windows/ And the only thing that I had to do was to replace the Ubuntu ISO image with the one of Freesbie. It feels pretty snappy with Kqemu acceleration driver installed. G'day! I must be dense today, but I don't understand the QEMU connection in your above post. Are you using QEMU on the host machine or on the Freesbie pendrive system? And if the former, what is the point (or benefit) to you? And does this have anything to do with your broken main board? I take it you are running Freesbie on your OpenBSD laptop? Else why make the reference to it? Like I said, I am confused... :-( Regards, web... -- William Bulley Email: [EMAIL PROTECTED] Michael Sherman http://msherman77.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Freesbie on USB stick + qemu
Good day all, Just recently I discovered a new (for me) way of using Freesbie and I wanted to share it with you. A few months ago the motherboard on my FreeBSD machine gave up, and I had no way of running Unix anymore (aside from my ancient Toshiba that runs OpenBSD). Ive always liked Freesbie, but using it as a LiveCD and rebooting between it and XP is daunting. Googling for linux usb brought me to this site http://www.pendrivelinux.com/ . I tried most of the Linux distros they have on that site, however for some reason or another I was not satisfied, either it didnt have gcc (damn small) or couldnt connect to the internet (ubuntu). Then I remembered Freesbie and decided to give it a try, running it from a usb stick using Qemu. I followed the instructions for Ubuntu http://www.pendrivelinux.com/2008/01/11/run-ubuntu-710-from-windows/ And the only thing that I had to do was to replace the Ubuntu ISO image with the one of Freesbie. It feels pretty snappy with Kqemu acceleration driver installed. I can even store stuff on the stick; after running the mountdisks script, an ext2fs partition is mounted and I was able to save files on it and they were there the next time I started Freesbie. I am able to connect to the network. The only issue that I have is when running X (startx), the window is tiny (800 X 600 pixels I believe), but its not a big deal. Hope someone finds it interesting, Michael Michael Sherman http://msherman77.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
converting VM from VMWare-format to Qemu
Hello, I've a Zip archive with a VM which runs fine in VMPlayer on Linux; it is just the contents of the directory and the VMWare files in this like: $ unzip -t Evergreen_1.2.0_Gentoo_x86.zip Archive: Evergreen_1.2.0_Gentoo_x86.zip testing: Evergreen_Gentoo_1.2.0/ OK testing: Evergreen_Gentoo_1.2.0/Other Linux 2.6.x kernel.vmsd OK testing: Evergreen_Gentoo_1.2.0/vmware-0.log OK testing: Evergreen_Gentoo_1.2.0/Gentoo-s003.vmdk OK testing: Evergreen_Gentoo_1.2.0/Other Linux 2.6.x kernel.vmx OK testing: Evergreen_Gentoo_1.2.0/Gentoo-s004.vmdk OK testing: Evergreen_Gentoo_1.2.0/vmware-2.log OK testing: Evergreen_Gentoo_1.2.0/nvram OK testing: Evergreen_Gentoo_1.2.0/Gentoo-s001.vmdk OK testing: Evergreen_Gentoo_1.2.0/core OK testing: Evergreen_Gentoo_1.2.0/vmware.log OK testing: Evergreen_Gentoo_1.2.0/Gentoo.vmdk OK testing: Evergreen_Gentoo_1.2.0/Gentoo-s002.vmdk OK testing: Evergreen_Gentoo_1.2.0/vmware-1.log OK testing: Evergreen_Gentoo_1.2.0/README OK Is there some way to convert this with 'qemu-img' to an image usable with Qemu on FreeBSD? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: converting VM from VMWare-format to Qemu
On 09/01/2008, Matthias Apitz [EMAIL PROTECTED] wrote: Hello, I've a Zip archive with a VM which runs fine in VMPlayer on Linux; it is just the contents of the directory and the VMWare files in this like: $ unzip -t Evergreen_1.2.0_Gentoo_x86.zip Archive: Evergreen_1.2.0_Gentoo_x86.zip testing: Evergreen_Gentoo_1.2.0/ OK testing: Evergreen_Gentoo_1.2.0/Other Linux 2.6.x kernel.vmsd OK testing: Evergreen_Gentoo_1.2.0/vmware-0.log OK testing: Evergreen_Gentoo_1.2.0/Gentoo-s003.vmdk OK testing: Evergreen_Gentoo_1.2.0/Other Linux 2.6.x kernel.vmx OK testing: Evergreen_Gentoo_1.2.0/Gentoo-s004.vmdk OK testing: Evergreen_Gentoo_1.2.0/vmware-2.log OK testing: Evergreen_Gentoo_1.2.0/nvram OK testing: Evergreen_Gentoo_1.2.0/Gentoo-s001.vmdk OK testing: Evergreen_Gentoo_1.2.0/core OK testing: Evergreen_Gentoo_1.2.0/vmware.log OK testing: Evergreen_Gentoo_1.2.0/Gentoo.vmdk OK testing: Evergreen_Gentoo_1.2.0/Gentoo-s002.vmdk OK testing: Evergreen_Gentoo_1.2.0/vmware-1.log OK testing: Evergreen_Gentoo_1.2.0/README OK Is there some way to convert this with 'qemu-img' to an image usable with Qemu on FreeBSD? Thx I think the only part that needs converting is the VMDK files which is the virtual hard disc drive. I'm not entirely sure if qemu-img handles split VMDK files, I would be surprised if that was the case. I also think the image is a sparse one go by the s in two of the VMDK's file name. You can all but try. better place to have asked maybe is the qemu malling list available on qemu.org have you (anyone?) tried running VMware Player under FreeBSD's linux emulation? matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Regards, Kimi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: converting VM from VMWare-format to Qemu
El día Wednesday, January 09, 2008 a las 11:06:28AM +, Kimi escribió: I think the only part that needs converting is the VMDK files which is the virtual hard disc drive. I'm not entirely sure if qemu-img handles split VMDK files, I would be surprised if that was the case. I also think the image is a sparse one go by the s in two of the VMDK's file name. You can all but try. Thx for the answer; this is how the running VM sees the disk: # fdisk -l /dev/sda Disk /dev/sda: 6442 MB, 6442450944 bytes 255 heads, 63 sectors/track, 783 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 5 40131 83 Linux /dev/sda2 6 68 506047+ 82 Linux swap / Solaris /dev/sda3 69 783 5743237+ 83 Linux maybe it is an idea to just punch the complete disk /dev/sda with dd(1) to a file outside the VM and convert/use this with Qemu? better place to have asked maybe is the qemu malling list available on qemu.org this is not a mailing list, but a BBS with web interface; I asked there already other stuff in the past w/o any answers; but will do give it a try again; have you (anyone?) tried running VMware Player under FreeBSD's linux emulation? not me; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: converting VM from VMWare-format to Qemu
On 09/01/2008, Matthias Apitz [EMAIL PROTECTED] wrote: El día Wednesday, January 09, 2008 a las 11:06:28AM +, Kimi escribió: I think the only part that needs converting is the VMDK files which is the virtual hard disc drive. I'm not entirely sure if qemu-img handles split VMDK files, I would be surprised if that was the case. I also think the image is a sparse one go by the s in two of the VMDK's file name. You can all but try. Thx for the answer; this is how the running VM sees the disk: # fdisk -l /dev/sda Disk /dev/sda: 6442 MB, 6442450944 bytes 255 heads, 63 sectors/track, 783 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 5 40131 83 Linux /dev/sda2 6 68 506047+ 82 Linux swap / Solaris /dev/sda3 69 783 5743237+ 83 Linux maybe it is an idea to just punch the complete disk /dev/sda with dd(1) to a file outside the VM and convert/use this with Qemu? it was one of two other possibles I was going to suggest along with running VMware Server for Linux. maybe overkill? I just try to think free incase qemu-img cannot do what you need. better place to have asked maybe is the qemu malling list available on qemu.org this is not a mailing list, but a BBS with web interface; I asked there already other stuff in the past w/o any answers; but will do give it a try again; sorry, you can post user questions on the developer mailing list, I see a few times. you know, maybe your question has been asked before? maybe use gmane.org and see. have you (anyone?) tried running VMware Player under FreeBSD's linux emulation? not me; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html -- Regards, Kimi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: converting VM from VMWare-format to Qemu
On Wednesday 09 January 2008 13:35:29 Matthias Apitz wrote: maybe it is an idea to just punch the complete disk /dev/sda with dd(1) to a file outside the VM and convert/use this with Qemu? Yes, that's going to work. You'll be much better if boot (or switch) to single user mode to avoid writes on the mounted filesystems while copying... Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Qemu: mouse doesn't work
Hello! I installed Qemu 0.9.0 with kqemu 1.3.0.p11 on FreeBSD 6.2 in order to get Kanotix running under FreeBSD. Kanotix boots well under qemu (I use the ISO-image) - but after the KDE desktop appears, my mouse doesn't work properly any more. When I move my mouse, the cursor sometimes moves a bit in the same direction, sometimes it jumps to the other side of the Kanotix desktop - and every few seconds the moving cursor disappears. But I can see some old cursors that did not disappear as I moved my mouse. So I cannot work with Kanotix under qemu at all because I don't really see where the cursor is when I move my mouse. I already tried using -usbdevice tablet, I tried setting SDL_VIDEO_X11_DGAMOUSE=0 and I even tried to use Qemu via vnc - nothing solves my problem. Any ideas how I could get Kanotix working under Qemu? What might cause the trouble in my case? Is this problem caused by Qemu or is it caused by FreeBSD? Many thanks in advance, Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Qemu: mouse doesn't work
Written by Michael Gerhards on 10/26/07 10:58 Hello! I installed Qemu 0.9.0 with kqemu 1.3.0.p11 on FreeBSD 6.2 in order to get Kanotix running under FreeBSD. Kanotix boots well under qemu (I use the ISO-image) - but after the KDE desktop appears, my mouse doesn't work properly any more. When I move my mouse, the cursor sometimes moves a bit in the same direction, sometimes it jumps to the other side of the Kanotix desktop - and every few seconds the moving cursor disappears. But I can see some old cursors that did not disappear as I moved my mouse. So I cannot work with Kanotix under qemu at all because I don't really see where the cursor is when I move my mouse. I already tried using -usbdevice tablet, I tried setting SDL_VIDEO_X11_DGAMOUSE=0 and I even tried to use Qemu via vnc - nothing solves my problem. Any ideas how I could get Kanotix working under Qemu? What might cause the trouble in my case? Is this problem caused by Qemu or is it caused by FreeBSD? Many thanks in advance, Michael You might try unloading kqemu, some systems don't do too well with the kqemu accelerator. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Qemu: mouse doesn't work
Reid Linnemann [EMAIL PROTECTED] wrote: Kanotix boots well under qemu (I use the ISO-image) - but after the KDE desktop appears, my mouse doesn't work properly any more. When I move my mouse, the cursor sometimes moves a bit in the same direction, sometimes it jumps to the other side of the Kanotix desktop - and every few seconds the moving cursor disappears. But I can see some old cursors that did not disappear as I moved my mouse. So I cannot work with Kanotix under qemu at all because I don't really see where the cursor is when I move my mouse. You might try unloading kqemu, some systems don't do too well with the kqemu accelerator. Unfortunately, this doesn't help either. Any more ideas? I have no idea what might go wrong... My hardware should be fast enough: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, 2 GB RAM So where is the problem? Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU and tap problems
On Thu, September 20, 2007 20:47, RW wrote: On Thu, 20 Sep 2007 06:21:20 -0500 Doug Poland [EMAIL PROTECTED] wrote: I've been following the various instructions I've found on the web in an attempt to get tap networking with qemu-devel-0.9.0s.20070802 Are you actually sure that you actually need tap? Good question. My reason for running Win2K server under QEMU is I'm working on a java app that speaks to SQLServer. Initially, all I need is to communicate with the host/guest on the same machine. After that, I'll need the QEMU guest to be on the network so I can connect to the java app from other computers. A lot of the how-tos are out of date I've noticed that :( - recent versions of Qemu can give a guest network access without it. When I started QEMU with the -net nic -net user switches, then Windows gets a 10. address and the guest can see the network. However, I cannot see open ports I'm interested in, 1433 and 3389, from the host. Windows thinks it has connectivity, but I cannot ping the default gateway from the guest and I cannot ping the IP of the guest from the host. This suggest you are accessing the net without tap, ping is a setuid binary so pings generated in the guest can't be passed on by qemu. The guest definitely could not see the hosts network with tap set up the way I described. I was using ping as a basic diagnostic tool and did not know the limitation you described. -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU and tap problems
On Fri, 21 Sep 2007 07:08:41 -0500 (CDT) Doug Poland [EMAIL PROTECTED] wrote: On Thu, September 20, 2007 20:47, RW wrote: On Thu, 20 Sep 2007 06:21:20 -0500 Doug Poland [EMAIL PROTECTED] wrote: I've been following the various instructions I've found on the web in an attempt to get tap networking with qemu-devel-0.9.0s.20070802 Are you actually sure that you actually need tap? Good question. My reason for running Win2K server under QEMU is I'm working on a java app that speaks to SQLServer. Initially, all I need is to communicate with the host/guest on the same machine. After that, I'll need the QEMU guest to be on the network so I can connect to the java app from other computers. A lot of the how-tos are out of date I've noticed that :( - recent versions of Qemu can give a guest network access without it. When I started QEMU with the -net nic -net user switches, then Windows gets a 10. address and the guest can see the network. However, I cannot see open ports I'm interested in, 1433 and 3389, from the host. I understand it when you run a guest without any networking switches, it sees an emulated ethernet interface that behaves as if it's connected to a basic NAT router. This emulation is running as an ordinary user in the host, so it can't do anything that requires root access - which is why you can't ping out. And because of the NAT you can't make incoming connections to the guest (which prevents incoming pings). IIRC there is some kind of redirection switch that will allow you to connect to guest ports via ports on the host (analogous to the port forwarding on a NAT router). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU and tap problems
Have a look at this article: http://sysnotes.hia.no/2007/09/21/how-to-fix-network-bridging-for-qemu/ It may give you some ideas although it is for Linux. The basic premise is to make qemu emulate the guest host so it appears as any other physical host on the network. It may work better. Regards Oz RW wrote: On Fri, 21 Sep 2007 07:08:41 -0500 (CDT) Doug Poland [EMAIL PROTECTED] wrote: On Thu, September 20, 2007 20:47, RW wrote: On Thu, 20 Sep 2007 06:21:20 -0500 Doug Poland [EMAIL PROTECTED] wrote: I've been following the various instructions I've found on the web in an attempt to get tap networking with qemu-devel-0.9.0s.20070802 Are you actually sure that you actually need tap? Good question. My reason for running Win2K server under QEMU is I'm working on a java app that speaks to SQLServer. Initially, all I need is to communicate with the host/guest on the same machine. After that, I'll need the QEMU guest to be on the network so I can connect to the java app from other computers. A lot of the how-tos are out of date I've noticed that :( - recent versions of Qemu can give a guest network access without it. When I started QEMU with the -net nic -net user switches, then Windows gets a 10. address and the guest can see the network. However, I cannot see open ports I'm interested in, 1433 and 3389, from the host. I understand it when you run a guest without any networking switches, it sees an emulated ethernet interface that behaves as if it's connected to a basic NAT router. This emulation is running as an ordinary user in the host, so it can't do anything that requires root access - which is why you can't ping out. And because of the NAT you can't make incoming connections to the guest (which prevents incoming pings). IIRC there is some kind of redirection switch that will allow you to connect to guest ports via ports on the host (analogous to the port forwarding on a NAT router). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
QEMU and tap problems
Hello,
I've been following the various instructions I've found on the web in an
attempt to get tap networking with qemu-devel-0.9.0s.20070802 and
kqemu-kmod-1.3.0.p11_2 on 6.2-STABLE.
qemu was compiled with:
_OPTIONS_READ=qemu-devel-0.9.0s.20070802
WITH_KQEMU=true
WITHOUT_HACKS_CIRRUS=true
WITHOUT_RTL8139_TIMER=true
WITHOUT_SAMBA=true
WITH_SDL=true
WITH_CDROM_DMA=true
The kernel modules are loaded:
if_tap, bridge, aio, kqemu
The sysctls are changed:
sysctl net.link.ether.bridge_cfg=ath0,tap0
sysctl net.link.ether.bridge.enable=1
The tap device exists:
crw--- 1 root wheel0, 134 Sep 19 22:42 /dev/tap0
tap0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 0.0.0.0 netmask 0xff00 broadcast 0.255.255.255
ether 00:bd:01:3c:01:00
Opened by PID 1317
The qemu-ifup script exists:
cat /etc/qemu-ifup
#!/bin/sh
ifconfig ${1} 0.0.0.0
I launch qemu like this:
qemu -m 512 -localtime -hda VMs/w2k3.img -net nic -net tap
Windows Server 2003 comes up. If I attempt to use DHCP to configure the
interface in W2K3, I get a several minute pause while it attempts to
contact a DHCP server, finally it fails with the message:
This connection has limited or no connectivity
and windows assigns itself the 169.254.244.101 address.
If I try to manually configure the windows interface, i.e.,
IP: 172.16.1.15
NM: 255.255.255.0
DG: 172.16.1.1
NS: 172.16.1.17
NS: 172.16.1.21
Windows thinks it has connectivity, but I cannot ping the default
gateway from the guest and I cannot ping the IP of the guest from the
host.
So at this point, I have no networking from the guest OS. About the
only thing that I haven't seen on the web is people using wireless NICs
in the host. In my case, I have an atheros chipset connected via WPA2
to my WAP.
All help is appreciated...
--
Regards,
Doug
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU and tap problems
On 9/20/07, Doug Poland [EMAIL PROTECTED] wrote:
Hello,
I've been following the various instructions I've found on the web in an
attempt to get tap networking with qemu-devel-0.9.0s.20070802 and
kqemu-kmod-1.3.0.p11_2 on 6.2-STABLE.
qemu was compiled with:
_OPTIONS_READ=qemu-devel-0.9.0s.20070802
WITH_KQEMU=true
WITHOUT_HACKS_CIRRUS=true
WITHOUT_RTL8139_TIMER=true
WITHOUT_SAMBA=true
WITH_SDL=true
WITH_CDROM_DMA=true
The kernel modules are loaded:
if_tap, bridge, aio, kqemu
The sysctls are changed:
sysctl net.link.ether.bridge_cfg=ath0,tap0
sysctl net.link.ether.bridge.enable=1
The tap device exists:
crw--- 1 root wheel0, 134 Sep 19 22:42 /dev/tap0
tap0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 0.0.0.0 netmask 0xff00 broadcast 0.255.255.255
ether 00:bd:01:3c:01:00
Opened by PID 1317
The qemu-ifup script exists:
cat /etc/qemu-ifup
#!/bin/sh
ifconfig ${1} 0.0.0.0
I launch qemu like this:
qemu -m 512 -localtime -hda VMs/w2k3.img -net nic -net tap
Windows Server 2003 comes up. If I attempt to use DHCP to configure the
interface in W2K3, I get a several minute pause while it attempts to
contact a DHCP server, finally it fails with the message:
This connection has limited or no connectivity
and windows assigns itself the 169.254.244.101 address.
If I try to manually configure the windows interface, i.e.,
IP: 172.16.1.15
NM: 255.255.255.0
DG: 172.16.1.1
NS: 172.16.1.17
NS: 172.16.1.21
Windows thinks it has connectivity, but I cannot ping the default
gateway from the guest and I cannot ping the IP of the guest from the
host.
So at this point, I have no networking from the guest OS. About the
only thing that I haven't seen on the web is people using wireless NICs
in the host. In my case, I have an atheros chipset connected via WPA2
to my WAP.
All help is appreciated...
I just got tap working with an earlier build of qemu using clues from this site:
http://forums.bsdnexus.com/viewtopic.php?id=1563
Also, I can only get it working when I run it with sudo at the moment
and I have only tried with a wired nic. I have read in some places
that encryption causes problems with tap, but I don't have a link to
where I read it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QEMU and tap problems
On Thu, 20 Sep 2007 06:21:20 -0500 Doug Poland [EMAIL PROTECTED] wrote: Hello, I've been following the various instructions I've found on the web in an attempt to get tap networking with qemu-devel-0.9.0s.20070802 and Are you actually sure that you actually need tap? A lot of the how-tos are out of date - recent versions of Qemu can give a guest network access without it. Windows thinks it has connectivity, but I cannot ping the default gateway from the guest and I cannot ping the IP of the guest from the host. This suggest you are accessing the net without tap, ping is a setuid binary so pings generated in the guest can't be passed on by qemu. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qemu and usb
on 15/08/2007 20:06 Juergen Lock said the following: On Wed, Aug 15, 2007 at 12:57:36PM +0300, Andriy Gapon wrote: Is it possible on FreeBSD to provide access to host USB devices for qemu guests ? I tried playing with -usb and -usbdevice and to follow some linux how-to's but with no luck. Does the following snippet from the ports' pkg-message help? [...] - if you want to use usb devices connected to the host in the guest (usb_add host:... monitor command) you need to make sure the host isn't claiming them, e.g. for umass devices (like memory sticks or external harddrives) make sure umass isn't in the kernel (you can then still load it as a kld when needed), also unless you are running qemu as root you then need to fix permissions for /dev/ugen* device nodes: if you are on 5.x or later (devfs) put a rule in /etc/devfs.rules, activate it in /etc/rc.conf and run /etc/rc.d/devfs restart. example devfs.rules: [ugen_ruleset=20] add path 'ugen*' mode 660 group operator corresponding rc.conf line: devfs_system_ruleset=ugen_ruleset - still usb: since the hub is no longer attached to the uchi controller and the wakeup mechanism, resume interrupt is not implemented yet linux guests will suspend the bus, i.e. they wont see devices usb_add'ed after its (linux') uhci module got loaded. workaround: either add devices before linux loads the module or rmmod and modprobe it afterwards. [...] With this I was able to mount an usb cardreader from the guest. (although that is pretty slow...) Juergen, thank you very much! While I unloaded umass I totally forgot to load ugen. -- Andriy Gapon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
qemu and usb
Is it possible on FreeBSD to provide access to host USB devices for qemu guests ? I tried playing with -usb and -usbdevice and to follow some linux how-to's but with no luck. Thank you. -- Andriy Gapon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qemu and usb
On Wed, Aug 15, 2007 at 12:57:36PM +0300, Andriy Gapon wrote: Is it possible on FreeBSD to provide access to host USB devices for qemu guests ? I tried playing with -usb and -usbdevice and to follow some linux how-to's but with no luck. Does the following snippet from the ports' pkg-message help? [...] - if you want to use usb devices connected to the host in the guest (usb_add host:... monitor command) you need to make sure the host isn't claiming them, e.g. for umass devices (like memory sticks or external harddrives) make sure umass isn't in the kernel (you can then still load it as a kld when needed), also unless you are running qemu as root you then need to fix permissions for /dev/ugen* device nodes: if you are on 5.x or later (devfs) put a rule in /etc/devfs.rules, activate it in /etc/rc.conf and run /etc/rc.d/devfs restart. example devfs.rules: [ugen_ruleset=20] add path 'ugen*' mode 660 group operator corresponding rc.conf line: devfs_system_ruleset=ugen_ruleset - still usb: since the hub is no longer attached to the uchi controller and the wakeup mechanism, resume interrupt is not implemented yet linux guests will suspend the bus, i.e. they wont see devices usb_add'ed after its (linux') uhci module got loaded. workaround: either add devices before linux loads the module or rmmod and modprobe it afterwards. [...] With this I was able to mount an usb cardreader from the guest. (although that is pretty slow...) Juergen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Qemu host with 5-8 virtual machines for Linux
Hello, I'm using Qemu (0.8.2) and kqemu (1.3.0.p11) in my FreeBSD 6.2-REL laptop, but only from time to time, mostly to edit some Winword docs when the addressed people don't like OpenOffice stuff. We are a software company and need to test our applications in Linux environment. Actually this is done on some Linux host with 6 GByte RAM and VMWare Workstation 4.5.2. It seems that there is some limitation not allowing more RAM for the guest systems as real RAM in the host, i.e. 6 GByte as max. I'm thinking in reinstalling this server with FreeBSD and using Qemu for the VM's. The idea is to have at least 5-8 VM's running at the same time, each with 1-2 GByte (virt.) RAM. Any comments on this? Thx Matthias -- Matthias Apitz Manager Technical Support - OCLC PICA GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclcpica.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ OCLC PICA GmbH, Geschaeftsfuehrer: Christine Magin-Weeger, Norbert Weinberger Sitz der Gesellschaft: Oberhaching, HRB Muenchen: 113261 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Nothing happens with Qemu
Hi, I'm trying to get Qemu working on my FreeBSD 6.2 PC. But nothing seems to be happening. I posted my problem at the Qemu forums but haven't got any replies there (I wonder if any one even uses those forums coz mine is like the last post there!) Just trying my luck here too in case I get some tips/ ideas. Installed Qemu from the ports. Without SDL (coz I don't have X etc installed and I just SSH into this box). With KQEMU module. After that I ran /usr/local/etc/rc.d/kqemu for loading the modules aio and kqemu. All went fine. Next I created a 2G image. qemu-img create /tmp/something.img 2G. That too went fine. Then I tried to install some OS into this image. Put the CD in the drive, and tried qemu -boot d -cdrom /dev/acd0 -hda /tmp/something.img. But nothing happens! The CD starts spinning in the drive but nothing happens after that. I ran top and I can see the qemu process is active and taking some 128MB memory, but there's no other signs of life. I tried the above with two OSes. I tried with an Ubuntu server and also an OpenBSD 4.1. Tried both to make sure its not a OS specific problem. I even ripped the CDs to ISO files and tried running from that (coz I read someplace that FreeBSD Qemu has problems reading from CDs). But no luck ... whatever I do, nothing happens. I also tried with the -full-screen option. But no go. Finally, I tried running with the -nographic option. I remm reading somewhere that that usually helps. That time I get a (qemu) prompt and that's it -- nothing happens. Tried stuff like Ctrl+Alt+1,2,F, etc but nothing happens. Can't even Ctrl-C out. Finally had to kill the process from another terminal. I also tried with the option -monitor stdio. That gives me a (qemu) prompt in which I can type commands. But I couldn't figure a way to proceed further after that. I tried all these steps through SSH as well as on the console (including uncommenting the console entry in /etc/tty and trying). No luck. Any ideas what could be going wrong? I figure it must be something to do with me not having X and not compiling Qemu with SDL/ X support ... is that the case? Thanks, Rakhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nothing happens with Qemu
Rakhesh Sasidharan [EMAIL PROTECTED] wrote: Hi, I'm trying to get Qemu working on my FreeBSD 6.2 PC. But nothing seems to be happening. I posted my problem at the Qemu forums but haven't got any replies there (I wonder if any one even uses those forums coz mine is like the last post there!) Just trying my luck here too in case I get some tips/ ideas. Installed Qemu from the ports. Without SDL (coz I don't have X etc installed and I just SSH into this box). With KQEMU module. After that I ran /usr/local/etc/rc.d/kqemu for loading the modules aio and kqemu. All went fine. Next I created a 2G image. qemu-img create /tmp/something.img 2G. That too went fine. Then I tried to install some OS into this image. Put the CD in the drive, and tried qemu -boot d -cdrom /dev/acd0 -hda /tmp/something.img. But nothing happens! The CD starts spinning in the drive but nothing happens after that. I ran top and I can see the qemu process is active and taking some 128MB memory, but there's no other signs of life. I tried the above with two OSes. I tried with an Ubuntu server and also an OpenBSD 4.1. Tried both to make sure its not a OS specific problem. I even ripped the CDs to ISO files and tried running from that (coz I read someplace that FreeBSD Qemu has problems reading from CDs). But no luck ... whatever I do, nothing happens. I also tried with the -full-screen option. But no go. That option probably requires X to work. Normally, qemu runs under X. If you're new to qemu, you'll probably have an easier time with the learning curve if you start out on a machine with X installed, as the default setting work well with that. Finally, I tried running with the -nographic option. I remm reading somewhere that that usually helps. That time I get a (qemu) prompt and that's it -- nothing happens. Tried stuff like Ctrl+Alt+1,2,F, etc but nothing happens. Can't even Ctrl-C out. Finally had to kill the process from another terminal. You're in the qemu Monitor at that point. I doubt CTRL+ALT+1 will help at that point, because you haven't specified anywhere for the console to connect to. I also tried with the option -monitor stdio. That gives me a (qemu) prompt in which I can type commands. But I couldn't figure a way to proceed further after that. I tried all these steps through SSH as well as on the console (including uncommenting the console entry in /etc/tty and trying). No luck. Any ideas what could be going wrong? I figure it must be something to do with me not having X and not compiling Qemu with SDL/ X support ... is that the case? Have you tried using the vnc option and connecting to qemu through a vnc client? As I already said, I recommend starting out on a machine with X until you're more familiar with qemu, as the default settings pretty much do that anyway, but I expect a vnc connection will be the second easiest. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nothing happens with Qemu
Have you tried using the vnc option and connecting to qemu through a vnc client? As I already said, I recommend starting out on a machine with X until you're more familiar with qemu, as the default settings pretty much do that anyway, but I expect a vnc connection will be the second easiest. Thank you for your suggestions Bill. I don't want to install X coz I just use this as a headless machine but the VNC idea seems worth a try. :) Do you have any experience with this method btw? I mean, what do I do? Run with the VNC option and then use TightVNC or something to connect to some IP? Thanks! Rakhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nothing happens with Qemu
It seems logical that qemu would need to run on top of X, in much the same way that Firefox [just to pick an example at random] won't work without X. I'm still a FreeBSD newbie though, so I have no idea how X works. I'm still struggling to upgrade my Xorg to 7.2. [Stupid missing OpenGL drivers! :( ] Agreed, just that there are references a lot of places on the Net that Qemu can work without X. And the -no-graphic option is to force it to start that way in case you don't have X. Strange ... Thanks! Rakhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nothing happens with Qemu
Rakhesh Sasidharan wrote: Hi, I'm trying to get Qemu working on my FreeBSD 6.2 PC. But nothing seems to be happening. I posted my problem at the Qemu forums but haven't got any replies there (I wonder if any one even uses those forums coz mine is like the last post there!) Just trying my luck here too in case I get some tips/ ideas. Installed Qemu from the ports. Without SDL (coz I don't have X etc installed and I just SSH into this box). With KQEMU module. After that I ran /usr/local/etc/rc.d/kqemu for loading the modules aio and kqemu. All went fine. Next I created a 2G image. qemu-img create /tmp/something.img 2G. That too went fine. Then I tried to install some OS into this image. Put the CD in the drive, and tried qemu -boot d -cdrom /dev/acd0 -hda /tmp/something.img. But nothing happens! The CD starts spinning in the drive but nothing happens after that. I ran top and I can see the qemu process is active and taking some 128MB memory, but there's no other signs of life. I tried the above with two OSes. I tried with an Ubuntu server and also an OpenBSD 4.1. Tried both to make sure its not a OS specific problem. I even ripped the CDs to ISO files and tried running from that (coz I read someplace that FreeBSD Qemu has problems reading from CDs). But no luck ... whatever I do, nothing happens. I also tried with the -full-screen option. But no go. Finally, I tried running with the -nographic option. I remm reading somewhere that that usually helps. That time I get a (qemu) prompt and that's it -- nothing happens. Tried stuff like Ctrl+Alt+1,2,F, etc but nothing happens. Can't even Ctrl-C out. Finally had to kill the process from another terminal. I also tried with the option -monitor stdio. That gives me a (qemu) prompt in which I can type commands. But I couldn't figure a way to proceed further after that. I tried all these steps through SSH as well as on the console (including uncommenting the console entry in /etc/tty and trying). No luck. Any ideas what could be going wrong? I figure it must be something to do with me not having X and not compiling Qemu with SDL/ X support ... is that the case? Thanks, Rakhesh Hi Rakhesh, I see you have covered the usual bases with qemu. I can't suggest anything else there. It seems logical that qemu would need to run on top of X, in much the same way that Firefox [just to pick an example at random] won't work without X. I'm still a FreeBSD newbie though, so I have no idea how X works. I'm still struggling to upgrade my Xorg to 7.2. [Stupid missing OpenGL drivers! :( ] I would try installing X [good luck with that!] and see if that helps. Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nothing happens with Qemu
On 29/07/07, Rakhesh Sasidharan [EMAIL PROTECTED] wrote: It seems logical that qemu would need to run on top of X, in much the same way that Firefox [just to pick an example at random] won't work without X. I'm still a FreeBSD newbie though, so I have no idea how X works. I'm still struggling to upgrade my Xorg to 7.2. [Stupid missing OpenGL drivers! :( ] Agreed, just that there are references a lot of places on the Net that Qemu can work without X. And the -no-graphic option is to force it to start that way in case you don't have X. Strange ... From the man page: -nographic Normally, QEMU uses SDL to display the VGA output. With this option, you can totally disable graphical output so that QEMU is a simple command line application. The emulated serial port is redi- rected on the console. Therefore, you can still use QEMU to debug a Linux kernel with a serial console. But, I do not think you can run most (any?) installers like this, without the serial console being redirected to _something_, and if you're doing this over ssh, that default something may not be immediately visible. The -vnc option looks like a win, maybe. Per above (not quoted) -cdrom /dev/acd0 might not work if the permissions are not set correctly on /dev/acd0. It is usually easier under qemu to use the downloaded image instead of burning to CD and all that. Or use dd to make a new image if you've already deleted it. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nothing happens with Qemu
The -vnc option looks like a win, maybe. That sounds good. Doesn't VNC require X, though? Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nothing happens with Qemu
On 29/07/07, Adam J Richardson [EMAIL PROTECTED] wrote: The -vnc option looks like a win, maybe. That sounds good. Doesn't VNC require X, though? Having not fiddled with it, I would hesitate to assume much. I would guess that it would work with mswin or X, and maybe with a terminal. It might also work with X forwarding. I am, of course, making the assumption that the original author is ssh-ing from something with a graphical desktop that he could forward to. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nothing happens with Qemu
-nographic Normally, QEMU uses SDL to display the VGA output. With this option, you can totally disable graphical output so that QEMU is a simple command line application. The emulated serial port is redi- rected on the console. Therefore, you can still use QEMU to debug a Linux kernel with a serial console. But, I do not think you can run most (any?) installers like this, without the serial console being redirected to _something_, and if you're doing this over ssh, that default something may not be immediately visible. Point. Which is why I even plugged in my monitor/ keyboard to the machine and ran Qemu at the console (I also uncommented the line in /etc/tty to enable console). Shouldn't that work then? Per above (not quoted) -cdrom /dev/acd0 might not work if the permissions are not set correctly on /dev/acd0. It is usually easier under qemu to use the downloaded image instead of burning to CD and all that. Or use dd to make a new image if you've already deleted it. Yup, had read that somewhere. So tried with an image file instead of the actual CD. No go. :-/ Regards, RAkhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
