Le blog de Jean David TECHER, un Réunionnais à Saint-Priest/Lyon

Aller au contenu | Aller au menu | Aller à la recherche


< 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 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 >

jeudi 2 novembre 2017

Use LVM to back up and restore Virtual Machine

I am currently spending my nights on testing ReactOS with Qemu 2.10.1+ KVM + VFIO. It is a good idea to have the iso to reinstall the system. All my drivers are already available on the iso. BUT I am under the impression to waste my time while recovering a virtual machine from scratch. Here LVM and snapshot are helpful

  • Check the volum for the current machine
    root@kvm-ReactOS:~# lvdisplay kvm-ReactOS-vg/ReactOS
      --- Logical volume ---
      LV Path                /dev/kvm-ReactOS-vg/ReactOS
      LV Name                ReactOS
      VG Name                kvm-ReactOS-vg
      LV UUID                XFDmtn-e2mQ-urGk-1EhV-85eZ-LcCv-v3qRi3
      LV Write Access        read/write
      LV Creation host, time kvm-ReactOS, 2017-11-02 03:00:29 +0100
      LV Status              available
      # open                 0
      LV Size                10,00 GiB
      Current LE             2560
      Segments               1
      Allocation             inherit
      Read ahead sectors     auto
      - currently set to     256
      Block device           252:7
    
  • Once you are happy with the current installation that it is time to create a backup using a snapshot from LVM system. I took the exact same size, 10GB.
    root@kvm-ReactOS:~# lvcreate -L10GB -s -n ReactOS_snapshot /dev/kvm-ReactOS-vg/ReactOS
      Using default stripesize 64,00 KiB.
      Logical volume "ReactOS_snapshot" created.
    
  • Later... - after doing some tests -.... on the current virtual machine, you can check its status using lvs
    root@kvm-ReactOS:~# lvs
      LV               VG             Attr       LSize  Pool Origin  Data%  Meta%  Move Log Cpy%Sync Convert
      ReactOS          kvm-ReactOS-vg owi-aos--- 10,00g                                                     
      ReactOS_good     kvm-ReactOS-vg -wi-a----- 10,00g                                                     
      ReactOS_snapshot kvm-ReactOS-vg swi-a-s--- 10,00g      ReactOS 21,69                                  
      home             kvm-ReactOS-vg -wi-ao---- 50,00g                                                     
      root             kvm-ReactOS-vg -wi-ao---- 23,28g                                                     
      swap_1           kvm-ReactOS-vg -wi-ao----  5,74g                                                     
      tmp              kvm-ReactOS-vg -wi-ao----  1,86g                                                     
      var              kvm-ReactOS-vg -wi-ao----  9,31g                                                     
    
  • If something gets wrong then you can to restore the snapshot
    root@kvm-ReactOS:~# lvconvert --merge /dev/kvm-ReactOS-vg/ReactOS_snapshot
      Merging of volume kvm-ReactOS-vg/ReactOS_snapshot started.
      ReactOS: Merged: 78,34%
      ReactOS: Merged: 80,99%
      ReactOS: Merged: 83,68%
      ReactOS: Merged: 86,55%
      ReactOS: Merged: 88,85%
      ReactOS: Merged: 89,71%
      ReactOS: Merged: 89,78%
      ReactOS: Merged: 91,20%
      ReactOS: Merged: 93,94%
      ReactOS: Merged: 96,54%
      ReactOS: Merged: 99,06%
      ReactOS: Merged: 100,00%
    
Keep it mind that
  • Snapshot will be destroyed once original volume has been restored
  • You may have to regenerate a new snapshot as backup -- if required --
Source: https://www.tecmint.com/take-snapshot-of-logical-volume-and-restore-in-lvm/

Get meta-information about DLL file or EXE from Linux [ExifTool]

I am currently working on building a version of d3d9.dll provided by Google which should work on ReactOS. From my main Linux workstation, I wanted to get meta-information from the d3d9.dll file. Doing some search on Internet, I found a pretty perl script Exiftool

Installation

Return metainformation

Let's test the recent file d3d9.dll built from a virtual machine. I've just copied the file on my Linux workstation
david@amdgaming:/opt/Builds/wine/data/tmp/Telechargements/Duck_old/Release$ exiftool d3d9.dll
ExifTool Version Number         : 10.65
File Name                       : d3d9.dll
Directory                       : .
File Size                       : 4.3 MB
File Modification Date/Time     : 2017:11:01 04:23:02+01:00
File Access Date/Time           : 2017:11:01 04:23:20+01:00
File Inode Change Date/Time     : 2017:11:01 04:23:02+01:00
File Permissions                : rwxrwxr-x
File Type                       : Win32 DLL
File Type Extension             : dll
MIME Type                       : application/octet-stream
Machine Type                    : Intel 386 or later, and compatibles
Time Stamp                      : 2017:11:01 03:09:50+01:00
PE Type                         : PE32
Linker Version                  : 14.11
Code Size                       : 3400704
Initialized Data Size           : 1171968
Uninitialized Data Size         : 0
Entry Point                     : 0x82422
OS Version                      : 5.1
Image Version                   : 0.0
Subsystem Version               : 5.1
Subsystem                       : Windows GUI
File Version Number             : 3.3.0.2
Product Version Number          : 3.3.0.2
File Flags Mask                 : 0x001f
File Flags                      : Private build
File OS                         : Win32
Object File Type                : Dynamic link library
File Subtype                    : 0
Language Code                   : English (U.S.)
Character Set                   : Unicode
Company Name                    : Google Inc.
File Description                : SwiftShader Direct3D 9 Renderer
File Version                    : 3.3.0.2
Internal Name                   : D3D9
Legal Copyright                 : Copyright (C) 2016 Google Inc.
Original File Name              : d3d9.dll
Private Build                   : 2
Product Name                    : SwiftShader Direct3D 9 Renderer
Product Version                 : 3.3.0.2

mercredi 25 octobre 2017

[Debian 9] File /etc/rc.local is missing? How to re-enable /etc/rc.local ?

Just refer to this link

samedi 14 octobre 2017

ReactOS on real hardware: NVIDIA GFX 3450 256MB

For Summer 2017, the link https://reactos.org/wiki/Supported_Hardware/Video_cards was recently updated. Someone did a test for GPU = NVIDIA Geforce 6600. Test was done for ReactOS 0.4.5 but with a workaround to install/use native NVIDIA driver.

Reading that on Friday 13Oct2017 I took decision to try a pretty old card I have at home. GFX 3450. I was pretty surprised to see that it works using workaround for the NVDisp.nvu file.


Screenshot from Device Manager - Listed as GFX3450 using native driver
Pros
  • Once driver installed you may have better resolutions 1920x1080@60Hz and over
Cons
  • Don't expect to play some 3D games
  • This is only usefull for a standard office station
BUT it is nice and fun to have a resolution 1920x1080@60Hz

Tests for some old drivers for Quadro FX 3450

After some researchs on the Web I found the link for archived drivers for quadro : http://www.nvidia.com/object/winxp-2k_archive.html. I tried a couple of drivers. Below are the results of my tests

DriverResults
169.06
  • Installation without any problem. Workaround for NVDisp.nvu file is useless
  • BSOD while rebooting the PC -- "Restart" option
  • No issue for "control panel"
181.20
  • Installation without any problem. Workaround for NVDisp.nvu file is useless
  • Issue for control panel: Panel will not appear if you click on "control panel"
182.65
  • Issue for control panel: Panel will not appear if you click on "control panel"
Drivers are far from perfect. That being said, I will recommend either driver 162.65 or 169.06

Video: Tests on NVIDIA GFX 3450 using driver 162.65