This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathLOG
39 lines (34 loc) · 2.68 KB
/
LOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
LOG 01-05-09
* Virtio block drivers from iggy are shite. Use the ones from linux-kvm.org. Maybe they're good for 7. Haven't had the chance to test yet.
* Running 3cx voip server software from kvm virtualized windows 2003 server rc2 machine, great with ethernet and virtio block drivers, otherwise unbearable.
LOG 02-04-09
d* Tried booting raw win2k3 image with virtio_blk, stil bsod; drivers are probably not getting picked up, found http://www.linux-kvm.org/page/Boot_from_virtio_block_device
* Trying new drivers on vm guest for win2k3 from some person called iggy on irc.freenode.net
LOG 25-11-09
* while testing ./etc/sudoers and mv /etc/sudoers /etc/sudoers.bak, I managed to fuck up the whole system, because root password wasn't set yet. Don't try this on a raid5 machine. Because there is also a chance that your grub will die, after you mount the raid devices as md0 and write on them.
* command to mount a raid5 system: mdadm --create /dev/md0 --level=5 --raid-devices=5 /dev/sd[a-d]1 /dev/hdc1
* watch out when mounting a ext4 as an ext3, this will fuck up your fs.
LOG 31-07-09
* Windows xp vm guest's transfer rate is slow like I thought. Iperf proves this.
* Run 'iperf -c the_server_ip_addr' from the to be tested vm guest, and iperf -s' starts the listener.
* Fixed the hardcoded crap in my start-*.sh scripts
* Apparently different nic models influence the ethernet data transfer speed:
* Available models from the qemu man page: i82551, i82557b, i82559er, ne2k_pci, ne2k_isa, pcnet, rtl8139,
=> e1000, smc91c111, lance, mcf_fec and usb
* Another source says these are available, from the qemu userspace kvm -net,model=?:
=> i82551 i2557b i82559er ne2k_pci pcnet rtl8139 e1000 virtio
* Apparently the drivers for model e1000 on windows is excellent, just install those and you're ready to run e1000 on windows.
* For running x86_64 stuff, it might help to add '-cpu qemu64,-nx'
LOG 30-07-09
* Download and tried to install windows virtio drivers, then system hung.
* Now defragmentizing the windows xp image, pointless exercise, but what the hey.
* Turns out, that the bandwidth transfer speed is not great, gotta use iperf.exe the next time around.
* You can turn off the graphics by adding a 3rd parameter to the start-....sh scripts, "-nographic
LOG 29-07-09
* Got tap devices to load/unload with scripts qemu-ifdown/up.sh
* Testing hypothesis: static ip of vm guest must be the same as tap device ip address
=> Fail, no internet! Maybe gateway is wrong. Not 254, but vm host machine's bridge.
=> Setting gateway to the bridge also does not work.
=> Next I'll try removing the ip address from the tap device.
=> Fail, no internet, but local network is online.
=> Aha! It was the dns, it must be set to the provider's.